Rayforge crashes with signal "SIGILL" upon launch

[khalleu]

Description
Rayforge crashes with the signal "SIGILL" upon launch. The workstation is in my home and isn't plugged into a CNC machine. You can view the log here.

Steps to reproduce the behavior:

1. Run flatpak run org.rayforge.rayforge

Expected behavior
The application launches with a graphical interface.

Screenshots

Extra info:
The machine is running Fedora Workstation 43 with GNOME 49.

[knipknap]

Ouch, and the logs include no error... does flatpak run org.rayforge.rayforge --version work?

Did you run the app before? Perhaps deleting the config will work? (rm -R ~/.config/rayforge)

[khalleu]

flatpak run org.rayforge.rayforge --version works! I'm on version 0.26.

I've just deleted the config folder. Since I'm using the Flatpak version, it's located in ~/.var/app/org.rayforge.rayforge/config. ~/.config/rayforge doesn't exist on my machine. Unfortunately, Rayforge still won't launch.

I've also tried giving it access to all files via Flatseal to no avail.

[knipknap]

@fllmn maybe you have any idea? There seems to be not much to go on. I found some docs for SIGILL that say:

The SIGILL signal is raised when an attempt is made to execute an invalid, privileged, or ill-formed instruction. SIGILL is usually caused by a program error that overlays code with data or by a call to a function that is not linked into the program load module.

So maybe something is not correctly linked?

[fllmn]

That is certainly confusing, I don't really have a clue but maybe with some more information/testing we could narrow this down. I'm on Fedora Workstation 43 as well so it should work... or at least does on my machine 😅.

After worker setup the next step seems to be pipeline setup followed by icon loading

2025-12-02 23:09:40,608 - rayforge.shared.tasker.pool - INFO - Worker process 21 started and ready.
2025-12-02 23:09:41,462 - rayforge.pipeline.pipeline - DEBUG - Pipeline.__init__[139987565336224] called
2025-12-02 23:09:41,462 - rayforge.pipeline.pipeline - DEBUG - [139987565336224] Initializing stages and connections.
2025-12-02 23:09:41,463 - rayforge.pipeline.pipeline - DEBUG - Pipeline.reconcile_all called
2025-12-02 23:09:41,463 - rayforge.pipeline.stage.workpiece_stage - DEBUG - WorkPiecePipelineStage reconciling...
2025-12-02 23:09:41,490 - rayforge.icons - DEBUG - Using local icon for 'open-symbolic' from: /app/lib/python3.13/site-packages/rayforge/resources/icons/open-symbolic.svg
2025-12-02 23:09:41,493 - rayforge.icons - DEBUG - Using local icon for 'save-symbolic' from: /app/lib/python3.13/site-packages/rayforge/resources/icons/save-symbolic.svg

I don't know the code well enough but I can't think of anything that would that wrong.

@khalleu Is there anything special with the machine you're trying run this on, like running a virtual machine, very old/new hardware or something similar? Have you tried any earlier releases?

[khalleu]

Nothing special, it's not a virtual machine, specs are AMD Ryzen 5 3600 (12) @ 4.208GHz, NVIDIA GeForce RTX 2080 SUPER, and 32 GB of memory. It's built from secondhand parts.

I've also tried installing it by following the instructions here, but I keep running into the error

Failed to build PyOpenGL_accelerate

As for earlier versions, I've downloaded the tarball of version 0.25 from the releases page but, honestly, I don't really know what to do with it (sorry). I believe what I'm looking for is under the "rayforge" subdirectory with all the .py files, but when I try to run "app.py", I get

ModuleNotFoundError: No module named 'rayforge'

[fllmn]

Alright, yes that doesn't sound like the problem.

Regarding earlier versions, I think you could try installing previous versions of the flatpak

flatpak remote-info --log flathub org.rayforge.rayforge to show what releases are available

then

flatpak update --commit=52c445932d6b01ee87ce7d84ebd8d49d702d9802580ba99ea304feb40c48784d org.rayforge.rayforge

to revert to the previous release

[khalleu]

Sweet! I didn't know I could do that, thank you so much.

Version 0.24 works!

[fllmn]

That's a start at least, unfortunately there were no Flathub releases for 0.25 or 0.25.1.

If you prefer to continue to investigate you can try to build the intermediary flatpak releases locally. If you clone the flathub respostory, build and installation instructions are in the README, just remember to revert the release tag to 0.25 or 0.25.1

https://github.com/flathub/org.rayforge.rayforge/blob/8efea69c736eb87515879c5e123a0b96e5d19b27/org.rayforge.rayforge.yml#L208-L212

[khalleu]

Decided to take a look at this again after a fresh Debian install (switching back after using Fedora for a year), the latest Flatpak version still doesn't launch. It seems to crash after

2026-01-11 16:10:45,931 - rayforge.shared.tasker.pool - INFO - Worker process 18 started and ready.

[fllmn]

That's unfortunate, but still confusing 🤔 . Version 0.27 has just been merged to Flathub and I'm hoping to test 0.27.1 tomorrow. It would be interesting to know if they behave any different

If none of them work you could try installing snapd and see if the snap release behaves any different.

[knipknap]

@khalleu Is there anything unusual about your system? e.g. what architecture, how many CPU/cores, ...?

[knipknap]

Perhaps also, is it Wayland? Or X11?

[knipknap]

Something more to try:

flatpak run --filesystem=xdg-config/rayforge:create --filesystem=xdg-data/rayforge:create org.rayforge.rayforge

And can you try starting it with:

flatpak run --env=PYOPENGL_PLATFORM=glx org.rayforge.rayforge

[fllmn]

System was covered here

I think it would be valuable to try the snap release to see if this is a flatpak or system issue