Recently upgraded Lightburn to operate a new galvo laser. On laser initialization (about 20 seconds after program start) the program crashes. Error is:
*** bit out of range 0 - FD_SETSIZE on fd_set ***
This appears to be an issue that arises with certain appimages and requires either a change in the image or local compilation.
Guidance would be appreciated, noting that I can’t upgrade since I’m on Linux and switching to Windows is not a reasonable solution.
It doesn’t crash there, but it does hang. Terminal reports that after the BSL fiber library loads, there’s a qt.network.ssl error, as the app was built with OpenSSL 1.x and the system runs OpenSSL >= 3.x. I’m uncertain if anything I installed changed that, and I’m cautious about rolling the version back.
Lightburn does appear to run normally, but whenever the laser is online, the program freezes. Then the laser goes offline, it resumes function. At one point it froze my entire window manager and I had to switch to a different TTY session to reboot the computer. I expect that’s an issue with me killing the Lightburn process and opening a new one, so I doubt that’s a real issue.
I can try to get another Linux machine up, but I’m curious as to if other Linux users have had these issues with galvo? It was pretty bulletproof on CO2.
I can sign onto the box from either the local keyboard or the RDP connection, but not both.
I turned off every data-sharing switch I could find and, because the box is not used for anything else, the Microsoft data-siphoning “features” don’t have much to work with.
Because LightBurn’s Linux code is unmaintained, it will gradually bit-rot in contemporary Linux distros, which is what I think you’re seeing.
A Windows 11 box doesn’t solve any of the issues I currently face. I dug up a Windows 11 laptop and it does control the laser, but Microsoft’s random, unilateral nonsense has broken SMB, so I can’t even connect to my network shares. After configuring my network’s firewalls I have blocked it from outside access except to my whitelisted servers, but that’s all work that could’ve been avoided, and three days on network sharing issues is an utter waste of time that could’ve been avoided with an actually functional operating system.
And while the lack of maintenance and bitrot will eventually be a valid excuse, this version of Lightburn was built within days of my Linux distro and is less than a year old. These issues would’ve appeared out of the bow when it was still under support and I’m beginning to suspect nobody actually used galvo lasers on Linux or the FD_SETSIZE failure in the flatpak would’ve been noticed. The targeting of OpenSSL 1 is another discussion, but considering I paid an additional $100 to get features I were told existed but apparently don’t unless I use Windows, I’m pretty grumpy about the whole situation.
I keep all the design files on a Linux “file server” (an old Dell Optiplex) shared with NFS (for Linux boxen) and SMB (for Windows). Works fine, apart from minor jank about when Win 11 refreshes its view of the shares to see new files.
I vaguely recall differences between “Windows 11 Pro” and “Windows 11 Home”, one of which was (IIRC) the latter not having RDP. Maybe there’s something about SMB missing, too, if your laptop has a different flavor of Win 11 than the Pro on my mini-PC.
IIRC, @jkwilborn has a galvo and runs Linux. Maybe he’ll drop into the conversation.
Plenty of Linux updates since then, with many opportunities for something to stop working the way it used to.
I have a similar setup using Open Media Vault. SMB works like a champ on Windows 10 systems and Linux has plenty of options to connect. However, this Windows 11 box sees the shares, authenticates, then tells me it doesn’t exist, and I should check the spelling. Ran the error code through the usual places and all I see are complaints with zero solutions. People are going so far as to say to enable NetBIOS, which is a blast from the past, but none of it works. I’ve even tried SMB 1, but nope. If it works for you, that’s great, but it doesn’t work on my end, and it’s clearly a Win11 issue if no other system, Microsoft or not, has the issue.
Regarding Linux updates, I don’t have autoupdates enabled, and I haven’t installed anything since initial setup (as far as the package manager is concerned, I did install Lightburn). This is basically a fixed state to avoid these kinds of breaking problems. I’ve worked with plenty of legacy systems in my time, and I don’t update systems that are doing their job. Lightburn has had issues with Windows updates, I had my phone brick a drone because it updated without my consent, and generally I don’t believe that autoupdates are worth doing. If you have sufficient network security and aren’t doing risky activities, internal systems don’t need to be treated as if they were on the DMZ.
If I need an updated system, I’ll spin up a VM or grab one of the piles of e-waste laptops I have in the basement. I specifically have single-use systems for this exact reason.
So, long story short, this system is as it would’ve been at install when this version of Lightburn was published.
Huh. Maybe those missing server refreshes are symptomatic of Something Else about to go wrong. Thanks for the description so I’ll know where to look when it goes completely toes-up.
Sadly, I don’t have any firm solutions for you. After changing registry entries, changing “windows components” and changing settings on the Samba share, I finally got Windows to talk to the NFS.
While I still would rather have a full Linux solution, even for the 1.7 that was at EoL, at least I can make this airgapped system work now. Since my license is almost a year old, I’ll probably stick with that over 2.0 as my forever version anyway. Honestly, this is the standard level of disappointment I have in life, so what else can you do?
