Hi everyone, I have a weird problem, I got a galvo machine and add it on my installation and was working fine, well my laptop died, so I got another laptop and installed Debian, installed Lightburn but I can’t connect to the laser, it doesn’t the detect the port, but if I open Lightburn with sudo it does detect the port, I was reading about user permission, I added my user to dialout and tty group but still the problem persists, any idea why?
Normally, I’d suggest you go to the /dev directory and set protection levels there for read/write access, depending on what/who owns it.
However, I’ve tried to chase down how the fiber connects via USB and I can’t seem to figure out how it works… as this brings the same point up again.
Maybe @gilaraujo can advise or suggest where to go … I fresh out of suggestions on where to look. It’s clearly a protection issue with the usb access.
Linux is really outside the realm of what I know best.
@goeland86 @Aaron.F might be able to provide some thoughts
1 Like
The answer to that question is definitely a permissions issue, but on which device is the question.
Can you do the following steps?
- Unplug the laser
- Open a console
- Type in
sudo tail -f /var/log/syslog - Plug in the laser
- Paste the output of the new lines appearing in the console
- Ctrl-C to exit the
tailcommand
Fiber lasers can be a device other than a serial port, sometimes they’ll be an FTDI device or something else entirely. We won’t be able to track it down without knowing how Linux interfaces with it.
Hi Luis,
@goeland beat me to it. 
Here’s my approach:
While Ubuntu is Debian-based, there may be some dependencies missing to run LightBurn.
Can you send us the reply of this command in the terminal?
lsb_release -a
This will tell us the version of Debian you are running.
See, if you are missing the FUSE library.
Enter this comment in the terminal:
sudo apt install libfuse2
Were you also running Debian on the last machine and was it possible to control the galvo laser there? (I’ve never tried a galvo controller on Linux and not sure, if this is expected to work.)
Are you using the .AppImage version?
The Braille display driver BRLTTY available on some distributions can also cause driver conflicts.
Thanks to all you, I’m not right now at home, I will try that later, @Aaron.F yes I was using Debian on my other machine and yes I was able to control it, even I tried using USBIP to control it wirelessly and it was working fine, that’s why its weird that it doesn’t work on this machine, however there were some differences, I was using Debian testing on my other machine, on this one I just installed stable, I don’t think that’s an issue, I’m going to try to put my old drive on the new machine and see if I can make it work or check my user’s permissions /groups, I’ll get back with what you requested later, thanks again.
Edit. Sorry I forgot, no, I’m not using the appimage, I’m using .run version
This would mean he couldn’t startup LightBurn at all from the appimage if it was missing 
1 Like
Edit. I copied the wrong results, these are the correct
25-07-30T18:45:29.741878-06:00 RazorCrest mtp-probe bus 1, device: 12 was not an MTP device
25-07-30T18:45:29.815339-06:00 RazorCrest kernel: [ 683.020672] usb 1-3.2: new high-speed USB device number 13 using xhci hed
25-07-30T18:45:29.915256-06:00 RazorCrest kernel: [ 683.121696] usb 1-3.2: New USB device found, idvendor-9588, idProduct=9899, bcdDevice= 0.00 525-07-30T18:45:29.915302-06:00 RazorCrest kernel: [ 683.121710] usb 1-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
225-07-30T18:45:29.915308-06:00 RazorCrest kernel: [ 683.121717] usb 1-3.2: Product: USBLMCV2
025-07-30T18:45:29.915312-06:00 RazorCrest kernel: [ 683.121722] usb 1-3.2: Manufacturer: BJJCZ
025-07-30T18:45:29.915316-06:00 RazorCrest kernel: [ 683.121727] usb 1-3.2: SerialNumber: 20120331001
I
Well, I finally got it working, I have to create a udev rule
SUBSYSTEM=“usb”, ATTR{1dVendor)==“9588”, ATTR(idProduct)==“9899”, MODE=“0666”, GROUP=“plugdev”, TAG+="uaccess
Edit. Thank you all for your help, and just wanted to add that is sad Linux won’t be supported anymore, I understand why, and hope that maybe using wine we can still use newer versions of Lightburn (I believe there’s a limitation because of how lightburn license interacts with WMI)
3 Likes
Having spent a lot of time to get the AppImage working properly, I was also sad that when I finally got it working it became work used only for 1 major version.
As far as I know Wine won’t work, unfortunately. Your best bet for using newer versions will be a dual-boot setup, or a used mac.
Just to add more info, I fixed my other computer (there was a problem with the ram slot) didn’t have any special udev rules, I copied the same permissions, and still no good, I’m not sure why this computer needed a special udev rule, I mean the only difference between this new computer and the other is the new one is using Debian Stable and the old one Debian testing
Debian stable generally lags behind testing in terms of versions, and the udev rules get updated as the device database gets validated and expanded over time.
I suspect that this is what happened to you in this case, the stable version is focused on stability and requires a lot longer testing and validation of any updates before it’s integrated.