@bernd.dk Can you share any console output related to gstreamer/camera output you see? And is this with the AppImage or one of the other two installation methods?
I have tested the applmage and run files with the same result (without working camera).
For the requested (console output related to gstreamer/camera), I need your help, I’m not Linux geek enough, but I’m very good at copy/paste 
Nb. I’m a little confused that I can’t find the last, for me, working Linux version of LB, or I’ve lost track of all the attempts of the different versions. With the last RC-3 I also have no camera, just the black block and LB camera listed.
When you start the appimage, do you do so from a terminal window, or just double clicking on it? If you simply click, try to edit the file properties and find the "run in terminal"option. Enable that, and when it starts, you ought to see a Linux terminal window starting. The output I need will be in there, so don’t close LB until you’ve copied the output. Try to switch cameras (even with none is fine) a couple of times, to make sure we get repeatability of the errors.
If you can then attach the output to your post as a text file I’d appreciate it.
I was able to use the camera on an arch linux install without problems so far. Tested with the RC2 and RC3 AppImage.
This is my kernel log, when i plug in the LightBurn camera. Can you show us yours? You can install lnav for this.
Sep 03 11:38:38 p14s kernel: [ 6281.250565] usb 6-2: new high-speed USB device number 7 using xhci_hcd │
│Sep 03 11:38:38 p14s kernel: [ 6281.492874] usb 6-2: New USB device found, idVendor=1bcf, idProduct=28c4, bcdDevice= 7.21 │
│Sep 03 11:38:38 p14s kernel: [ 6281.492886] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 │
│Sep 03 11:38:38 p14s kernel: [ 6281.492890] usb 6-2: Product: Lightburn Camera │
│Sep 03 11:38:38 p14s kernel: [ 6281.492893] usb 6-2: Manufacturer: WN 210721 │
│Sep 03 11:38:38 p14s kernel: [ 6281.492895] usb 6-2: SerialNumber: 01.00.00 │
│Sep 03 11:38:38 p14s kernel: [ 6281.538236] usb 6-2: Found UVC 1.00 device Lightburn Camera (1bcf:28c4)
For testing the camera, I used guvcview
I only have this option with the .run file and I cannot “capture” what is written in the terminal, it disappears too quickly and before LB starts.
So you have to cut it out for me, how I can get that information from my system. I would love to be of assistance, just directing me…
…same as before, send me in the direction where I can find that information
I use Chees and it works fine
What Jon asked for can also be done by launching the AppImage directly from the terminal - Go to the directory where the AppImage is and right click to “Launch Terminal here”. Then type: ./LightBurn-Linux64-v1.7.00-RC-3-c013d8e.AppImage
This should keep the terminal open and show us some more logs.
To view the kernel log, I use the command line program called “lnav” - Install it with the command sudo apt install lnav Then launch it in the terminal. It will show many lines but I’m interested to see, what happens on your system when you plug in the LightBurn camera.
Both cheese and guvcview work the same way, which is a different path than lightburn, they directly call into the V4L2 stack. As we use Qt, we have to go through it, and gstreamer, to test. However, from what I can tell, if it works in one, it’ll work with the other.
@bernd.dk to start from a terminal, you open a terminal from your application menu. The prompt will show something like
username@hostname ~: $
This is in your home directory.
You can use cd <DirectoryName> to move your working directory to where the AppImage file is. Note that you can hit the tab key a few times to get autocomplete options and thus avoid typos.
Once where the AppImage is, start it with ./LightBurn-Linux64-v1.7.0-RC3-c013d8e.AppImage
laser@laser-computer:~/Hentet$ ./LightBurn-Linux64-v1.7.00-RC-3-c013d8e.AppImage
Using the core prefs dir
QMetaObject::connectSlotsByName: No matching signal for on_actionSettings_triggered()
QMetaObject::connectSlotsByName: No matching signal for on_actionEdit_GameControllers_triggered()
connected
Setting camera to “/dev/video0”
res: 640 x 480
res: 800 x 600
res: 960 x 720
res: 1280 x 720
res: 1280 x 960
res: 1600 x 1200
res: 1920 x 1080
res: 2560 x 1440
res: 2592 x 1944
default: -1 x -1
Setting res: 2592 x 1944
qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id
qt.network.ssl: QSslSocket: cannot resolve SSL_get_peer_certificate
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_get_peer_certificate
qt.network.ssl: QSslSocket: cannot call unresolved function EVP_PKEY_base_id
downloaded 994 of -1
downloaded 994 of 994
6s││Sep 3 14:10:29 laser-computer kernel: [ 1496.181445] audit: type=1400 audit(1725365429.061:75): apparmor=“ALLOWED” operation="co│
1d22h7m46s││Sep 3 14:10:29 laser-computer kernel: [ 1496.181647] audit: type=1400 audit(1725365429.061:76): apparmor=“ALLOWED” operation="fi│
1d22h7m46s││Sep 3 14:10:29 laser-computer kernel: [ 1496.181662] audit: type=1400 audit(1725365429.061:77): apparmor=“ALLOWED” operation="fi│
1d22h8m14s││Sep 3 14:10:57 laser-computer systemd[1]: tmp-.mount_LightB6J073I.mount: Deactivated successfully. │
1d22h8m14s││Sep 3 14:10:57 laser-computer systemd[1459]: vte-spawn-d5995dca-6f8f-4e00-9d4a-c12f4c17de54.scope: Consumed 11.928s CPU time. │
1d22h14m18s││Sep 3 14:17:01 laser-computer CRON[4687]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) │
1d22h14m25s││Sep 3 14:17:08 laser-computer systemd[1]: tmp-.mount_LightB410BY2.mount: Deactivated successfully. │
1d22h14m53s││Sep 3 14:17:36 laser-computer goa-daemon[1927]: secret_password_lookup_sync() returned NULL │
1d22h15m1s││Sep 3 14:17:44 laser-computer dbus-daemon[781]: [system] Activating via systemd: service name=‘org.freedesktop.PackageKit’ unit=│
1d22h15m1s││Sep 3 14:17:44 laser-computer systemd[1]: Starting PackageKit Daemon… │
1d22h15m1s││Sep 3 14:17:44 laser-computer PackageKit: daemon start │
1d22h15m2s││Sep 3 14:17:45 laser-computer dbus-daemon[781]: [system] Successfully activated service ‘org.freedesktop.PackageKit’ │
1d22h15m2s││Sep 3 14:17:45 laser-computer systemd[1]: Started PackageKit Daemon. │
1d22h16m52s││Sep 3 14:19:35 laser-computer kernel: [ 2042.519330] usb 2-1.4: USB disconnect, device number 4 │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2048.791125] usb 2-1.4: new high-speed USB device number 5 using ehci-pci │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2048.963108] usb 2-1.4: New USB device found, idVendor=1bcf, idProduct=2cb4, bcdDevice= │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2048.963122] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2048.963126] usb 2-1.4: Product: Lightburn Camera │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2048.963129] usb 2-1.4: Manufacturer: WN-210621 │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2048.963131] usb 2-1.4: SerialNumber: 01.00.00 │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2048.977304] usb 2-1.4: Found UVC 1.00 device Lightburn Camera (1bcf:2cb4) │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2049.066998] usb 2-1.4: 3:1: cannot get freq at ep 0x86 │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2049.069875] usb 2-1.4: 3:2: cannot set freq 11025 to ep 0x86 │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2049.071602] usb 2-1.4: 3:3: cannot set freq 16000 to ep 0x86 │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2049.073122] usb 2-1.4: 3:4: cannot set freq 22050 to ep 0x86 │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2049.079626] usb 2-1.4: 3:5: cannot get freq at ep 0x86 │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2049.082359] usb 2-1.4: 3:6: cannot set freq 32000 to ep 0x86 │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2049.084126] usb 2-1.4: 3:7: cannot set freq 44100 to ep 0x86 │
1d22h16m58s││Sep 3 14:19:41 laser-computer kernel: [ 2049.085597] usb 2-1.4: 3:8: cannot set freq 48000 to ep 0x86 │
1d22h16m59s││Sep 3 14:19:42 laser-computer kernel: [ 2049.128248] usb 2-1.4: Warning! Unlikely big volume range (=4096), cval->res is probabl│
1d22h16m59s││Sep 3 14:19:42 laser-computer kernel: [ 2049.128257] usb 2-1.4: [7] FU [Mic Capture Volume] ch = 1, val = 0/4096/1 │
1d22h16m59s││Sep 3 14:19:42 laser-computer mtp-probe: checking bus 2, device 5: “/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4” │
1d22h16m59s││Sep 3 14:19:42 laser-computer mtp-probe: bus: 2, device: 5 was not an MTP device │
1d22h16m59s││Sep 3 14:19:42 laser-computer mtp-probe: checking bus 2, device 5: “/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4” │
1d22h16m59s││Sep 3 14:19:42 laser-computer mtp-probe: bus: 2, device: 5 was not an MTP device │
1d22h16m59s││Sep 3 14:19:42 laser-computer kernel: [ 2049.254526] usb 2-1.4: 3:7: cannot get freq at ep 0x86 │
1d22h16m59s││Sep 3 14:19:42 laser-computer rtkit-daemon[1231]: Supervising 5 threads of 3 processes of 1 users. │
1d22h16m59s││Sep 3 14:19:42 laser-computer rtkit-daemon[1231]: Successfully made thread 4904 of process 1470 owned by ‘1000’ RT at priority 5│
1d22h16m59s││Sep 3 14:19:42 laser-computer rtkit-daemon[1231]: Supervising 6 threads of 3 processes of 1 users.
Interesting, thank you.
Can I ask which version of Ubuntu you’re testing this on?
laser@laser-computer:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
laser@laser-computer:~$
Curiouser and curiouser. That’s the version we’re building on for 1.7, so it doesn’t look like an incompatibility issue.
A post was merged into an existing topic: Public Release Candidate - 1.7.00
tir sep 03 1 /var/log/syslog:: syslog_log:: LOG
│Sep 3 14:40:00 laser-computer dbus-daemon[1487]: [session uid=1000 pid=1487] │
│Sep 3 14:40:00 laser-computer systemd[1467]: Starting Evolution calendar serv│
│Sep 3 14:40:00 laser-computer kernel: [ 110.325455] audit: type=1326 audit(1│
│Sep 3 14:40:00 laser-computer kernel: [ 110.325475] audit: type=1326 audit(1│
│Sep 3 14:40:01 laser-computer dbus-daemon[1487]: [session uid=1000 pid=1487] │
│Sep 3 14:40:01 laser-computer systemd[1467]: Started Evolution calendar servi│
│Sep 3 14:40:01 laser-computer dbus-daemon[1487]: [session uid=1000 pid=1487] │
│Sep 3 14:40:01 laser-computer systemd[1467]: Starting Evolution address book │
│Sep 3 14:40:01 laser-computer goa-daemon[1925]: secret_password_lookup_sync()│
│Sep 3 14:40:01 laser-computer goa-daemon[1925]: secret_password_lookup_sync()│
│Sep 3 14:40:01 laser-computer snapd-desktop-i[2171]: New theme: gtk=Yaru-MATE│
│Sep 3 14:40:01 laser-computer snapd-desktop-i[2171]: All available theme snap│
│Sep 3 14:40:02 laser-computer dbus-daemon[1487]: [session uid=1000 pid=1487] │
│Sep 3 14:40:02 laser-computer systemd[1467]: Started Evolution address book s│
│Sep 3 14:40:16 laser-computer systemd[1]: systemd-hostnamed.service: Deactiva│
│Sep 3 14:40:22 laser-computer systemd[1]: systemd-timedated.service: Deactiva│
│Sep 3 14:40:24 laser-computer systemd[1]: blueman-mechanism.service: Deactiva│
│Sep 3 14:40:28 laser-computer xdg-desktop-por[2227]: Failed to get applicatio│
│
┌──── Last message: a second ago; Files: 1; Error rate: 0,00/min; Time span: │
Filters :: Press TAB to edit
L13.667 100% ?:View Help
Press e/E to move forward/backward through error messages
Here a cleaner log, only with “lnav” and LightBurn.
Camera selected, camera off, camera started…
I also tried today on another computer with “Manjaro” without success (camera)
FYI @bernd.dk and @goeland86 I split this off into its own topic so it didn’t flood the main thread.
3 Likes
Thanks @adammhaile
@bernd.dk I’ve now been able to replicate it on my laptop, where my desktop was running with the camera just fine. So I suspect there may be some conflict with a laptop package/configuration item. I will keep investigating to figure out what it could be.
1 Like
…sounds good that you have made some progress. 
…oddly the" laptop package/config problem" that had an impact on my desktop PC…, no matter if it just works in the end
so your laser computer is a desktop machine? 
Yes Sir, old PC on Linux
1 Like
Any data highlighting the difference is helpful. I will investigate and hopefully resolve it. I am encouraged that at least we’re not running into the issue of the gstreamer errors appearing - those I’ve finally solved.