I successfully burnt my first image, ran off the pi. something I have yet been able to do thru virtual here, are you still working on getting the camera function to work? I can see my camera, and select it. but there’s just something missing in the middle, it’s way over my head, and really when I need the camera it won’t be an image so I can just swap pi’s. but it would be amazing to have it all. I can’t get over how good LB runs on a pi. thank you
I am not actively working on this. I don’t have a Pi that’s sufficiently fast enough to make that sort of troubleshooting tolerable and I suspect will take some deep analysis to understand what’s going on.
I know there’s also some work being done on the camera subsystem and some open issues with camera support on the Linux builds so I’m content to see how those changes affect the camera in the future.
I’d be thrilled if someone else were to run with this to see if they can sort it out, however. I just don’t have any immediate plans to look at it unless something fundamental changes or prompts a review.
1 Like
Hello, Thanks for these instructions. I have successfully gotten everything installed and working (sort of). At least for the first run.
I’m using a pi4 and as I said was successful at installing box64, and lightburn. I have used both the 1.6.04 and 1.4.03 versions of Lightburn and I get the same behavior from both. I start it up the first time and it loads and runs. I can activate the trial, and setup and control the Ortur laser.
The problem comes when I close and reopen Lightburn. It will load and than crashes with this in the terminal window.
Using emulated /lib/x86_64-linux-gnu/libssl.so.1.1
3534|SIGSEGV @0x34ff61f4 (???(/home/blata/LightBurn/LightBurn+0x7f61f4)) (x64pc=0x3f3916b490/“/lib/x86_64-linux-gnu/libcrypto.so.1.1/EVP_CIPHER_CTX_ctrl”, rsp=0x7f50b8e448, stack=0x7f50390000:0x7f50b90000 own=0x7f50390000 fp=0x3f39082540), for accessing 0xa (code=1/prot=0), db=(nil)((nil):(nil)/(nil):(nil)/???:clean, hash:0/0) handler=(nil)
RSP-0x20:0x0000003f3917e879 RSP-0x18:0x0000007f3c030fd0 RSP-0x10:0x0000007f3c031270 RSP-0x08:0x0000003f394a3dc0
RSP+0x00:0x0000003f39184f0c RSP+0x08:0x0000007f3c030fd0 RSP+0x10:0x0000003f39159809 RSP+0x18:0x0000007f3c031270
RAX:0x0000000000000041 RCX:0x000000007ed83203 RDX:0xc9bb1e9bda909b7c RBX:0x0000007f3c031450
RSP:0x0000007f50b8e448 RBP:0x0000003f39082540 RSI:0x0000007f3c0314a0 RDI:0x0000007f3c0314b0
R8:0x0000000000000000 R9:0x00000000ffffffff R10:0x000000007ed83203 R11:0x0000000020080128
R12:0x0000007f3c0248c0 R13:0x0000003f394a05a0 R14:0x0000000000000000 R15:0x0000007f50b8e6b0
ES:0x002b CS:0x0033 SS:0x002b DS:0x002b FS:0x0043 GS:0x0053
./launch.sh: line 9: 3486 Segmentation fault box64 “${SCRIPT_DIR}”/LightBurn
Any ideas whats going on here? I appreciate all the work that has gone into this.
I’m wondering if this might be related to the update check that LightBurn does on startup.
What OS version are you using? And are you current on updates to the OS?
Also, can you capture the full log from launch to segfault and paste here?
First of all, I don’t spend a ton of time on the forums anymore so I completely missed this! I had no idea you had gotten LB to run via box64, that’s really cool! Nice work @berainlb 
I realize this is on the tail of us dropping Linux but please be assured I do actually really like seeing this… I’ve been pondering getting it working on the Pi (officially) for years. So it’s cool to see it working in any capacity.
The update check happens 2 seconds after the main window is shown so if it’s not launching at all it seems unlikely to be the culprit.
One good way to check is to open the prefs.ini file in your preferences directory and set AutoCheckForUpdates to false - then it won’t check at start up and you can rule that in or out.
3 Likes
I got that message the first time I ran the 1.6 v or LB but havent seen it since.
Itls also funny you should say the update check is 2sec after the main LB window opens. Just long enugh to be excited about it working. Then you see the segfult in the term window
I will edit the prefs.ini see what happens and report back hopefully also with the log.
[Update]
disabling the AutoCheckForUpdates in the prefs.ini file stopped the crash.
@Laser:~/LightBurn $ sudo uname -a
Linux Laser 6.6.40-v8+ #1784 SMP PREEMPT Tue Jul 16 13:53:31 BST 2024 aarch64 GNU/Linux
@Laser:~/LightBurn $ ./launch.sh
Dynarec for ARM64, with extension: ASIMD CRC32 PageSize:4096 Running on Cortex-A72 with 4 Cores
Will use Hardware counter measured at 54.0 MHz emulating 3.4 GHz
Params database has 87 entries
Box64 with Dynarec v0.3.1 b26ae588 built on Jul 23 2024 17:03:11
BOX64: Didn’t detect 48bits of address space, considering it’s 39bits
BOX64: Prefering Emulated libs
Counted 52 Env var
BOX64 LIB PATH: /home/blata/LightBurn/lib_amd64/lib/x86_64-linux-gnu/:/home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/:/home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/pulseaudio/:/home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/gstreamer-1.0/:/lib/x86_64-linux-gnu/:/usr/lib/x86_64-linux-gnu/
BOX64 BIN PATH: ./:bin/:/usr/local/sbin/:/usr/local/bin/:/usr/sbin/:/usr/bin/:/sbin/:/bin/:/usr/local/games/:/usr/games/
Looking for /home/blata/LightBurn/LightBurn
Rename process to “LightBurn”
Using native(wrapped) libusb-1.0.so.0
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/libzstd.so.1
Using emulated /home/blata/LightBurn/lib/libQt5MultimediaWidgets.so.5
Using emulated /home/blata/LightBurn/lib/libQt5PrintSupport.so.5
Using emulated /home/blata/LightBurn/lib/libQt5Widgets.so.5
Using emulated /home/blata/LightBurn/lib/libQt5Multimedia.so.5
Using emulated /home/blata/LightBurn/lib/libQt5Gui.so.5
Using emulated /home/blata/LightBurn/lib/libQt5SerialPort.so.5
Using emulated /home/blata/LightBurn/lib/libQt5Network.so.5
Using emulated /home/blata/LightBurn/lib/libQt5Xml.so.5
Using emulated /home/blata/LightBurn/lib/libQt5Core.so.5
Using native(wrapped) libpthread.so.0
Using emulated /lib/x86_64-linux-gnu/libstdc++.so.6
Using native(wrapped) libm.so.6
Using emulated /lib/x86_64-linux-gnu/libgcc_s.so.1
Using native(wrapped) libc.so.6
Using native(wrapped) ld-linux-x86-64.so.2
Using native(wrapped) libdl.so.2
Using native(wrapped) libutil.so.1
Using native(wrapped) librt.so.1
Using native(wrapped) libbsd.so.0
Using native(wrapped) libz.so.1
Using emulated /home/blata/LightBurn/lib/libicui18n.so.56
Using emulated /home/blata/LightBurn/lib/libicuuc.so.56
Using emulated /home/blata/LightBurn/lib/libicudata.so.56
Using native(wrapped) libgthread-2.0.so.0
Using native(wrapped) libglib-2.0.so.0
Using native(wrapped) libgssapi_krb5.so.2
Using native(wrapped) libGL.so.1
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/libpulse-mainloop-glib.so.0
Using native(wrapped) libpulse.so.0
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
Using native(wrapped) libxcb.so.1
Using native(wrapped) libXau.so.6
Using native(wrapped) libXdmcp.so.6
Using emulated /home/blata/LightBurn/lib_amd64/lib/x86_64-linux-gnu/libsystemd.so.0
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/libwrap.so.0
Using native(wrapped) libsndfile.so.1
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/libasyncns.so.0
Using emulated /home/blata/LightBurn/lib_amd64/lib/x86_64-linux-gnu/libdbus-1.so.3
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/libapparmor.so.1
Using native(wrapped) liblzma.so.5
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/liblz4.so.1
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/libgcrypt.so.20
Using emulated /home/blata/LightBurn/lib_amd64/lib/x86_64-linux-gnu/libgpg-error.so.0
Using native(wrapped) libresolv.so.2
Using native(wrapped) libnsl.so.1
Using global gdk_display for gdk-x11 (0x7fecaf27a8:0x360e2e80)
Using emulated /home/blata/LightBurn/lib/libQt5OpenGL.so.5
qt.qpa.plugin: Could not find the Qt platform plugin “wayland” in “”
Using emulated /home/blata/LightBurn/plugins/platforms/libqxcb.so
Using emulated /home/blata/LightBurn/plugins/platforms/…/…/lib/libQt5XcbQpa.so.5
Using native(wrapped) libfontconfig.so.1
Using native(wrapped) libexpat.so.1
Using native(wrapped) libfreetype.so.6
Using emulated /home/blata/LightBurn/plugins/platforms/…/…/lib/libQt5DBus.so.5
Using native(wrapped) libX11-xcb.so.1
Using native(wrapped) libxcb-icccm.so.4
Using native(wrapped) libxcb-image.so.0
Using native(wrapped) libxcb-shm.so.0
Using native(wrapped) libxcb-util.so.1
Using native(wrapped) libxcb-keysyms.so.1
Using native(wrapped) libxcb-randr.so.0
Using native(wrapped) libxcb-render-util.so.0
Using native(wrapped) libxcb-render.so.0
Using native(wrapped) libxcb-shape.so.0
Using native(wrapped) libxcb-sync.so.1
Using native(wrapped) libxcb-xfixes.so.0
Using native(wrapped) libxcb-xinerama.so.0
Using native(wrapped) libxcb-xkb.so.1
Using native(wrapped) libXext.so.6
Using native(wrapped) libX11.so.6
Using native(wrapped) libxkbcommon-x11.so.0
Using native(wrapped) libxkbcommon.so.0
Using native(wrapped) libXcursor.so.1
Using native(wrapped) libXfixes.so.3
Using native(wrapped) libXrender.so.1
Using emulated /home/blata/LightBurn/plugins/platforminputcontexts/libcomposeplatforminputcontextplugin.so
Using emulated /home/blata/LightBurn/plugins/imageformats/libqgif.so
Using emulated /home/blata/LightBurn/plugins/imageformats/libqicns.so
Using emulated /home/blata/LightBurn/plugins/imageformats/libqico.so
Using emulated /home/blata/LightBurn/plugins/imageformats/libqjpeg.so
Using emulated /home/blata/LightBurn/plugins/imageformats/libqsvg.so
Using emulated /home/blata/LightBurn/plugins/imageformats/…/…/lib/libQt5Svg.so.5
Using emulated /home/blata/LightBurn/plugins/imageformats/libqtga.so
Using emulated /home/blata/LightBurn/plugins/imageformats/libqtiff.so
Using emulated /home/blata/LightBurn/plugins/imageformats/libqwbmp.so
Using emulated /home/blata/LightBurn/plugins/imageformats/libqwebp.so
Using emulated /home/blata/LightBurn/plugins/xcbglintegrations/libqxcb-glx-integration.so
Using native(wrapped) libxcb-glx.so.0
Using the core prefs dir
Using emulated /home/blata/LightBurn/plugins/iconengines/libqsvgicon.so
QMetaObject::connectSlotsByName: Connecting slot on_sbNumberOfPasses_valueChanged() with the first of the following compatible signals: (“valueChanged(int)”, “valueChanged(QString)”)
QMetaObject::connectSlotsByName: Connecting slot on_sbFrequency_valueChanged() with the first of the following compatible signals: (“valueChanged(double)”, “valueChanged(QString)”)
QMetaObject::connectSlotsByName: Connecting slot on_sbQPulseWidth_valueChanged() with the first of the following compatible signals: (“valueChanged(double)”, “valueChanged(QString)”)
QMetaObject::connectSlotsByName: No matching signal for on_sbInterval_valueChanged()
QMetaObject::connectSlotsByName: Connecting slot on_sbMaterialHeight_valueChanged() with the first of the following compatible signals: (“valueChanged(double)”, “valueChanged(QString)”)
QMetaObject::connectSlotsByName: Connecting slot on_sbSupportHeight_valueChanged() with the first of the following compatible signals: (“valueChanged(double)”, “valueChanged(QString)”)
QMetaObject::connectSlotsByName: No matching signal for on_actionEdit_Text_closed(int)
connected
Using emulated /home/blata/LightBurn/plugins/mediaservice/libgstcamerabin.so
Using emulated /home/blata/LightBurn/plugins/mediaservice/…/…/lib/libQt5MultimediaGstTools.so.5
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/libgstapp-1.0.so.0
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/libgstpbutils-1.0.so.0
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/libgstallocators-1.0.so.0
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
Using native(wrapped) libgobject-2.0.so.0
Using native(wrapped) libasound.so.2
Using native(wrapped) libgmodule-2.0.so.0
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/libgsttag-1.0.so.0
Using emulated /home/blata/LightBurn/lib_amd64/usr/lib/x86_64-linux-gnu/liborc-0.4.so.0
Using native(wrapped) libudev.so.1
Using emulated /home/blata/LightBurn/plugins/bearer/libqconnmanbearer.so
Using emulated /home/blata/LightBurn/plugins/bearer/libqgenericbearer.so
Using emulated /home/blata/LightBurn/plugins/bearer/libqnmbearer.so
Using emulated /lib/x86_64-linux-gnu/libcrypto.so.1.1
Using emulated /lib/x86_64-linux-gnu/libssl.so.1.1
3532|SIGSEGV @0x34ff61f4 (???(/home/blata/LightBurn/LightBurn+0x7f61f4)) (x64pc=0x3f3916b490/“/lib/x86_64-linux-gnu/libcrypto.so.1.1/EVP_CIPHER_CTX_ctrl”, rsp=0x7f5311e448, stack=0x7f52920000:0x7f53120000 own=0x7f52920000 fp=0x3f39082540), for accessing 0xa (code=1/prot=0), db=(nil)((nil):(nil)/(nil):(nil)/???:clean, hash:0/0) handler=(nil)
RSP-0x20:0x0000003f3917e879 RSP-0x18:0x0000007f40030fd0 RSP-0x10:0x0000007f40031270 RSP-0x08:0x0000003f394a3dc0
RSP+0x00:0x0000003f39184f0c RSP+0x08:0x0000007f40030fd0 RSP+0x10:0x0000003f39159809 RSP+0x18:0x0000007f40031270
RAX:0x0000000000000041 RCX:0x000000007ed83203 RDX:0xaea1bcf47668054e RBX:0x0000007f40031450
RSP:0x0000007f5311e448 RBP:0x0000003f39082540 RSI:0x0000007f400314a0 RDI:0x0000007f400314b0
R8:0x0000000000000000 R9:0x00000000ffffffff R10:0x000000007ed83203 R11:0x0000000020080128
R12:0x0000007f400248c0 R13:0x0000003f394a05a0 R14:0x0000000000000000 R15:0x0000007f5311e6b0
ES:0x002b CS:0x0033 SS:0x002b DS:0x002b FS:0x0043 GS:0x0053
./launch.sh: line 9: 3481 Segmentation fault box64 “${SCRIPT_DIR}”/LightBurn
Nice. In that case it’s very likely related to library versions. If you do a full update of the OS that may resolve the issue.
Thanks for all the help and insight but after having read through lightburns plans to twilight the Linux version I don’t see a reason to continue. I’ll go back to k40whisperer for my CO2 and since the laptop that ran lasergrbl, in a vm, died. I guess I’ll just get rid of the Ortur. Now I’m glad I didn’t buy a licence. Thanks again for doing this in the first place it was fun while it lasted. I’ll just finish this project and move on.
Oh forgot to mention. Everything is 100% uptodate vi apt. I even had to do a firmware and bootloader flash because the usb and hdmi ports were acting wonky. So if its a package problem my guess is it would have to be a newer package problem.
Bummed by the sad news that LightBurn is dropping Linux support after v1.7… on a brighter note, I’m still happily using v1.3.01! And with renewed interest in this forum thread regarding LightBurn on Raspberry Pi… I, too, have successfully installed and run Lightburn on a RPi4 running Linux. While a comprehensive how-to seems virtually non-existent I was able to gather enough vital bits of information on how to pull it off with a bit of research.
Lazy as I am, I’m still sitting in my recliner (I insist!) with my Acer Chromebook (Developer mode) in hand, talking wirelessly to RPi4 desktop through VNC, and running Lightburn that’s controlling the laser engraver through USB. The RPi4 (4Gig) runs RaspberryPi OS (Debian 11 “bullseye”) and Lightburn quite nicely.
It is also somewhat instructive that my latest Chromebook in Developer mode is also running Debian 11 “bullseye” underneath… Chromebooks have been my primary Lightburn platform for years. I’ve always downloaded the .run file when updating… and it provides a simple install and a chance to look at where things are being put. This was helpful when trying to put all the “extra” libraries in the proper place on the RPi4. Chromebook above, RPi4 below…
LightBurn on RPi4, displaying grand-daughter’s sketch of my “baby” brother and me at his 75th birthday get-together…
Daughter’s Roly LaserMATIC Mk2 30w laser engraver…
Fun project! 
– David
3 Likes
That’s fantastic that you were able to get this to work.
To be clear, did you reference post #32 where I list out the overall steps to make this work?
At the time I deliberately left it at a high level for a couple of reasons:
- to ensure that people attempting this would be sufficiently skilled as to reduce any sort of support burden on the LightBurn team given that this was entirely experimental
- at the initial time of release there were a number of limitations that would make this method somewhat impractical. Specifically, the need for offline activation. That no longer exists but was one of the initial drivers.
Looking at your screenshot it’s not apparent to me that you used the provided archive files.
I’m nearly 78 years old, long retired, and really slowing down… and have forgotten way more Linux than I ever knew. I usually can “muddle” my way through however, given enough time… so please forgive if/when I’m not as technically correct as I should be.
Your post #32 wasn’t enough for me and I wondered about the LB and libs version differences, so I used a bit of BOTH @bhimio’s post#1 in this thread and your post #32. I was using LB v1.3.01 so downloaded the same .run file that matches the latest LB update my license allows for. After getting Box64 installed, I ran the .run and all files extracted to the .local/share/LightBurn directory as shown on both the Chromebook and the RPi4… both are running Debian 11 “bullseye”. It also added a LightBurn launcher icon in the applications menu.
I’m not certain but I think I downloaded either the tar files from @bhimio’s step3 (or your’s from post#32) and extracted it into a “lib2” directory alongside the “lib” in the .local/share/LightBurn directory. Using @bhimio’s BOX64_ALLOWMISSINGLIBS=1 BOX64_LD_LIBRARY_PATH=lib2 ./LightBurn from the command line, I actually got LB to launch and display on screen. I’m not certain what, if anything, I did to get enough libs “seen” so that BOX64_LD_LIBRARY_PATH=lib2 ./LightBurn was then enough to launch LB. Then I simply moved the “lib2” contents into “lib” and was able to launch simply with ./LightBurn… and from the LB launcher icon in the menus. Once everything seemed stable, I was able to activate the license and connect to my laser engraver.
1 Like
somewhere I have a script I wrote which takes an rPi SD image( 2 directories ) and compresses them into an X.img.gz file so getting a working version of what was on the disk was just extracting the image like you normally do with rPi images.
It’s just so much easier for people setting up a new image for a particular project, like a laser engraving or CNC machine when it’s already been done before instead of everyone going through all the girations.
I have done the same with Lubuntu customized images for running MakerBots, 3D printers, teaching Arduino or IoT projects etc. If I ever get LightBurn running on the rPi, I’ll do the same and post a link to my gDrive folder for download.
1 Like
Hi all, and my first post to the forum (from NZ).
Not really a reply, but having succeeded with loading LB on my rpi5 I felt I should give a big shout out for berainlb and all the others who have worked this out. I suspect I will continue to do my designing on my PC laptop, but having the pi version next door ready and waiting to handle the cutting duties is a real boon.
So thank you to all who contributed. In fact I still find it amazing it works but after a week it seems solid. Only clash so far seems to be with the move commands using Alt + Ctrl and one of the arrow keys seems to change the window.
Am hoping my appreciation for the rpi port adds to any chance of reconsidering dropping Linux support in future.
Here’s hoping, but meanwhile back to my scale Mosquito aircraft project.
Cheers.
Richard
1 Like
Glad this is working for you.
Can you elaborate on this? What are you doing, what do you expect to happen, and what happens instead?
Happy to help. Its not really a bug but I will explain the difference as well as possible.
On my W10 laptop LB I have been impressed by the multiple options for moving selected objects. However Alt + arrow (L or R) is functionally the same as Alt+ Ctrl + (L or R), and I have used both combos without fully realising that.
On the rpi5 version Alt + (L or R) works as before but Alt + Ctrl + (L or R) changes the Window size and goes sideways L or R. Resizing to max goes back to where we were, so no harm done, but its a slight difference.
Two other small differences in passing: 1 the on-screen menu items (icons) seem fragmented ie not complete, although they are generally recognisable. This may be a pi screen resolution issue and I just haven’t found the best one yet. 2 when guiding the laser using the locator pin, there is a little red cross on the screen workspace grid under Windows but no mark that I can see on the rpi.
Performance on the pi version is slighly laggy cf Windows, but still workable and for use as a laser server perfectly acceptable.
Hope that is of some help.
Richard
Whoops. Slight correction to the above.
It is Ctrl + Arrow and Ctrl + Alt + Arrow that are similar on Windows to give eg 1mm jumps. Only the first of these works on the rpi.
Alt + Arrow give coarser jumps and works on the rpi.
I suspect these things don’t actually work the way that you’re thinking that they work. I don’t believe ALT+arrow is an intended movement key combination. Note that the movement should be the same as arrow with no ALT.
There should be 3 move operation combinations:
- No modifier, just arrows - course adjustment
- CTRL + arrow - fine adjustment
- SHIFT + CTRL + arrow - even finer adjustment
This key combination is likely triggering the window management features of Pi OS and not really related to LightBurn.
Can you take a screenshot of this?
Do you have “Show Last Position” enabled in Laser window? If not, enable it.
This is less likely to be a Windows vs non-Windows issue and more a Pi vs proper computer issue. Your computer is likely dramatically faster and has more RAM than the Pi. It’s a tribute to the Pi and LightBurn that it runs as well as it does.
Something I have noticed is if I try to run LB 1.6 after a fresh boot of my Pi4 It will crash right after the splash screen. However, if I launch LB 1.4 first than close it and launch LB 1.6 it works just fine until the next reboot.
I’ve never seen that issue with the icons before. If you change the size of the icons in Edit->Settings does this change anything?
I’ve not seen this in my limited testing. What version of Pi OS are you running, are you up to date on updates, and have you used the instructions on post #32 to setup LightBurn?
