I managed for it to do it’s thing to produce a folder, and follow the instructions as per the installation page, but when trying to launch it from there, and this is after setting it’s permissions and the rest I get the following error.
I tried using Wine with the windows/exe version of it in Wine and just get errors when it’s trying to run.
I’m not strong with Linux with software installs, it’s always been hit or miss, but I really prefer using it. I did buy a cheap windows laptop just to try out Lightburn and to make my new laser cutter actually work, but I really would rather have it working on my Linux box since that’s my daily driver along with I absolutely loath windows in any shape or form for very many reasons.
What version and Edition of Linux Mint are you using?
I’ll try installing this to see how it behaves. I suspect whatever desktop environment you’re using doesn’t use the .desktop convention for launch icons.
Linux Mint uses GLIBC_2.27. LightBurn requires GLIBC_2.29. libc is a very fundamental component of the system so there’s not a very safe way of simply updating this in place.
Your best option is to upgrade to the latest Mint if that’s possible for you. That should bring up to parity against the same version of Ubuntu that LightBurn is compiled for.
If for some reason upgrading is extremely difficult or otherwise not an option, you could try to compile a completely separate entire libc and companion libraries and utilities and try to use that for LightBurn. I wouldn’t recommend this if you’re not comfortable doing this or maintaining such a system as you’d not be responsible for keeping this current.
[EDIT]
One correction. Linux Mint 21.1 looks like it’s built on Ubuntu 22.04. That would put you ahead of the build system which is based on 20.04. 22.04 also works but if you want the least chance of possible incompatibilities then I’d suggest sticking with a Ubuntu 20.04 based Mint. The highest version looks like Mint 20.3.
For the record, I tested this on a Linux Mint 21.1 installation and LightBurn came up without incident using the .run .desktop icon.
Thank you so much! It’s going to be needing a new ISO to burn and new install all together to upgrade it appears. I’ll start with getting it ran with a dual boot on the Windows laptop with the latest version of Mint and see if it’s stable and then decide if I want to go for it with my main workstation or stick with that or the just settle with 20.3 after seeing what the lap top does. My daily driver/box files are extensive and critical and nothing I take lightly so don’t want to risk losing anything, and I’ll see if it’s doable to have dual partitions on it, both mint old and new as well.
I would never have figured out remotely where to start from with out your help, thank you so much! I’ll chime in to let you know how it went.
The way I do it, I download the .run file for Linux 64, go into properties of the downloaded file under permissions and make it executable. (Mint, Manjaro, Ubuntu…)
But, I have to say it too, I’m a big fan of Mint and also Manjaro, but both versions are not officially supported and (can) also cause problems with LightBurn, I’ve been there.
If you want a stable system that also handles LightBurn’s camera without problems, then it is Ubuntu 20.04 which works perfectly, it is in any case the only Linux version that I, as a non-Linux expert, have full success with.
hello! First I clarify that I am using google translator, sorry about that.
If you’re sure you didn’t skip any steps in the official tutorial, try running LightBurn from the terminal which should report any errors, please share them here.
But I think that perhaps you are missing some component to run the AppRun, so I recommend that you install AppRun Launcher. Which will make things easier for you. If you don’t know how to do it, ask us!
Thanks for the feedback and direction everybody. I’m downloading the 20.3 version, that’s the last one they have to offer before they moved up to 21. Linux Mint 20.3 "Una" - Linux Mint
The one thing that has some degree of concern. I’m just about done with the trial period so I have to pull the trigger on purchasing it. They give you up to two systems you can use it on, via. to be officially licenced. They obviously are going to count each partition/installation as one separate computer but I want to have at least dual partitions on the windows laptop, with the windows OS still using Lightburn as a back up or if there are some weird bugs with software/hardware compatibility in the future and to include upgrading my laser, and it’s second partition running Mint, again it’s own going to get a copy of Lightburn on, and the additional computer, my main one, it too being technically a third installation. I hope I don’t have to choose only two and stay limited to only two on the same purchase.
I’m digging into mastering Lightburn as a secondary, or that final filter/software/driver for the laser cutter, knowing full well that I need control in this environment regardless of the models/designs being created with other software, cad, or in this case, I’ll be digging into Fusion 360 next.
When you change out a motherboard, Lightburn seems to detect it as a new computer…
I suspect it will run on both partitions, if it’s looking at hardware…
Lightburn is also very good about issuing you a 3rd seat if you need it…
I’ve been in hard/software since the 70’s. Lightburn has got to be the best product I’ve ever used. Support is fantastic, on top of that they are nice people.
If you pass on Lightburn, it’ll be a huge mistake.
Thanks, that’s good go know. My daily driver has 700 gigs of data to back up, so creating a separate partition and dual boot may be the route to go so I can keep the original OS in tact without having to buy another hard drive just to back up files on, for I would rather back them up to the new partition after it’s proven stable. It’s a frankenbox so wasn’t exactly easy to get the original OS dialed in when I moved away from windows in 2019. It would be also a neat thing for all 32 gigs of ram to be recognized rather then limited to it’s only seeing 16 and nothing in bios was able to change that.
I’m not passing on LightBurn, it’s still going to be kept and used, but working in 3d is better especially with the models I’m focused upon for the laser cutter which are remote control aircraft.
Regarding testing LightBurn on several comuters / partitions at the same time, an easy way to do it is, as you also write yourself, to have a comuter as “master” which is not touched, I use my macbook for that, it is my “construction and design” computer. In the workshop I have two old PCs with LightBurn installed. When I’ve tried the different variations of Linux, it was easy to start up LigtBurn and “unregister” the program from within LightBurn itself, and use it on the next Linux version. I did until I landed on Ubuntu 20.04
I wish you success with that.
Word: if you have only one copy of any data, tomorrow you will have none.
Backing them up on a different partition means when that drive dies, it takes both copies down.
Newegg sells 4 TB spinning-rust USB 3.0 external drives for a hundred bucks, so if your data is worth having, give up your favorite vice for a week and make a real backup before messing with partitions.
Source: been there, broke that, kept all the pieces.
Make some progress. I ended installing 20.3 Mint along side the old one and that at least got Lightburn working. It will not recognize my laser so have more rabbit trails to follow to attempt to get that element going. Seeing it’s a common thing with Linux not being able to recognize laser cutters so I may end up forced to still use the windows laptop just for the cutting part and do the design work on my main system, now upgraded.
QinHeng Elecronics HL-340 USB-Serial adapter is what appears to be the laser, unplugging the usb from it, it goes missing so at least have it somewhat pinpointed, so it’s not ghosted or something.
enterprise-e@enterprise-e:~$ lsusb
Bus 002 Device 004: ID 0b05:17cf ASUSTek Computer, Inc.
Bus 002 Device 006: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 002 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 046d:c00c Logitech, Inc. Optical Wheel Mouse
Bus 005 Device 002: ID 0bda:ffef Realtek Semiconductor Corp. 802.11n NIC
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 010: ID 21c4:8005
Bus 003 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
enterprise-e@enterprise-e:~$ lsusb
Bus 002 Device 004: ID 0b05:17cf ASUSTek Computer, Inc.
Bus 002 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 046d:c00c Logitech, Inc. Optical Wheel Mouse
Bus 005 Device 002: ID 0bda:ffef Realtek Semiconductor Corp. 802.11n NIC
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 010: ID 21c4:8005
Bus 003 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
enterprise-e@enterprise-e:~$ cp /lib/modules/$(uname -r)/kernel/drivers/usb/serial/ch341.ko /lib/modules/$(uname -r)/kernel/drivers/usb/serial/ch341.ko.orig
cp: cannot create regular file ‘/lib/modules/5.4.0-91-generic/kernel/drivers/usb/serial/ch341.ko.orig’: Permission denied
enterprise-e@enterprise-e:~$ dmesg | tail -n 50
[ 4866.887256] usb-storage 3-1.3:1.0: USB Mass Storage device detected
[ 4866.887340] scsi host18: usb-storage 3-1.3:1.0
[ 4866.887411] usbcore: registered new interface driver usb-storage
[ 4866.896408] usbcore: registered new interface driver uas
[ 4867.901244] scsi 18:0:0:0: Direct-Access General USB Flash Disk 1.00 PQ: 0 ANSI: 4
[ 4867.901755] sd 18:0:0:0: Attached scsi generic sg2 type 0
[ 4867.902184] sd 18:0:0:0: [sdb] 60653760 512-byte logical blocks: (31.1 GB/28.9 GiB)
[ 4867.902395] sd 18:0:0:0: [sdb] Write Protect is off
[ 4867.902398] sd 18:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 4867.902630] sd 18:0:0:0: [sdb] No Caching mode page found
[ 4867.902636] sd 18:0:0:0: [sdb] Assuming drive cache: write through
[ 4867.934969] sdb: sdb1 sdb2 sdb3
[ 4867.953725] sd 18:0:0:0: [sdb] Attached SCSI removable disk
[ 4868.571667] ISO 9660 Extensions: Microsoft Joliet Level 3
[ 4868.573800] ISO 9660 Extensions: Microsoft Joliet Level 3
[ 4868.575592] ISO 9660 Extensions: RRIP_1991A
[ 8106.676514] usb 3-1.4: USB disconnect, device number 9
[ 8106.676785] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[ 8106.676813] ch341 3-1.4:1.0: device disconnected
[ 8115.743322] usb 2-1.4: new full-speed USB device number 6 using ehci-pci
[ 8115.852424] usb 2-1.4: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.34
[ 8115.852428] usb 2-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 8115.852431] usb 2-1.4: Product: USB Serial
[ 8115.852871] ch341 2-1.4:1.0: ch341-uart converter detected
[ 8115.853775] usb 2-1.4: ch341-uart converter now attached to ttyUSB0
[12946.325575] R8188EU: ap recv disassoc reason code(3) sta:c0:61:9a:94:8f:ab
[12946.327694] R8188EU: indicate disassoc
[28264.459017] perf: interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
[40548.676536] Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7
[43085.599829] R8188EU: assoc success
[43085.612602] IPv6: ADDRCONF(NETDEV_CHANGE): wlx681ca207d6cb: link becomes ready
[46770.114883] perf: interrupt took too long (3150 > 3135), lowering kernel.perf_event_max_sample_rate to 63500
[50171.193391] usb 2-1.4: USB disconnect, device number 6
[50171.193704] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[50171.193732] ch341 2-1.4:1.0: device disconnected
[50171.523712] usb 2-1.4: new full-speed USB device number 7 using ehci-pci
[50171.633014] usb 2-1.4: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.34
[50171.633018] usb 2-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[50171.633021] usb 2-1.4: Product: USB Serial
[50171.633437] ch341 2-1.4:1.0: ch341-uart converter detected
[50171.634353] usb 2-1.4: ch341-uart converter now attached to ttyUSB0
[50171.961396] usb 2-1.4: USB disconnect, device number 7
[50171.961635] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[50171.961659] ch341 2-1.4:1.0: device disconnected
[50267.929637] usb 2-1.4: new full-speed USB device number 8 using ehci-pci
[50268.038532] usb 2-1.4: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.34
[50268.038536] usb 2-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[50268.038538] usb 2-1.4: Product: USB Serial
[50268.038959] ch341 2-1.4:1.0: ch341-uart converter detected
[50268.039867] usb 2-1.4: ch341-uart converter now attached to ttyUSB0
enterprise-e@enterprise-e:~$ ls -l /dev/USB
crw-rw---- 1 root dialout 188, 0 Mar 5 17:35 /dev/ttyUSB0
enterprise-e@enterprise-e:~$
enterprise-e@enterprise-e:~$ ls -l /dev/USB
crw-rw---- 1 root dialout 188, 0 Mar 5 17:35 /dev/ttyUSB0
enterprise-e@enterprise-e:~$ $USER dialout && sudo adduser $USER tty
enterprise-e: command not found
enterprise-e@enterprise-e:~$
enterprise-e@enterprise-e:~$ sudo adduser $USER dialout && sudo adduser $USER tty
[sudo] password for enterprise-e:
Adding user enterprise-e' to group dialout’ …
Adding user enterprise-e to group dialout
Done.
Adding user enterprise-e' to group tty’ …
Adding user enterprise-e to group tty
Done.
enterprise-e@enterprise-e:~$