PLEASE fix orcaslicer for fedora/nobara!! help us quit windows!

[ghost48000-cmyk]

orca slicer running on nobara 43 has hang and crash issues when installed both through the appimage and dnf installed. Not sure if its an nvidia issue, memory leak, or what the problem is. 9900ks, rtx 3080ti (Nvidia drivers), 32 gbs ram.

[Gorlinux]

OrcaSlicer 2.3.1 works like a charm on Nobara 43 (AMD Radeon 6900XT).
Maybe the issue comes from your closed source NVIDIA drivers?

[ghost48000-cmyk]

I really don't think it's a Nvidia issue this time, for me orca slicer works more or less without issue both on fedora 43 KDE and on CachyOS KDE/Niri while having a 4070ti super (my daily is the CachyOS running the AUR -git version)

I think you're right. The 40gb chunk ram calls are the issue currently I feel. It must be related somehow to an interaction with nobara Nvidia build and orca

[AlexandruBaia]

Did you try any x11 desktop enviroments ? I also had problems with Creality Print on Wayland so I had to force a x11 session

[ghost48000-cmyk]

Can you select x11 specifically on nobara? I know it has x11 to Wayland running all the time. I think I read they did away with x11 or Wayland desktops in favor of Wayland with x11 compatibility layer always active. Hmm I'll have to do more research on that

[Gorlinux]

Nobara 43 uses Wayland as default so switching to X11 may help.
And as said before, OrcaSlicer 2.3.1 never gave me any issues using Wayland on Radeon 6900XT.

This answer comes from deepseek.com:

Based on the search results, frequent crashes of OrcaSlicer on Nobara 43 with an NVIDIA RTX 3080 are almost certainly caused by incompatibilities between NVIDIA's proprietary graphics drivers and OrcaSlicer's OpenGL rendering engine on Linux. This is a widespread issue specifically affecting NVIDIA GPUs.

Here are the specific reasons and corresponding fixes, ranked by likelihood for your specific setup (Nobara 43 + RTX 3080):

1. Recent NVIDIA Driver Update (e.g., 555/570/575 series)
   Multiple users report that updating to newer NVIDIA proprietary drivers (specifically versions like 555, 570.133.07, and 575.64.03) immediately causes OrcaSlicer to crash on startup or fail to render the 3D viewport
   . Nobara 43 likely ships with or recommends these newer drivers.
   Solution: Try rolling back to an older, stable driver branch (e.g., 550 series) using Nobara’s driver management tool (sudo /usr/lib/nobara/drivers/modify-driver.sh). Ensure Secure Boot is disabled in your BIOS

2. GBM/EGL Backend Failure (The Flatpak Fix)
   This is the most documented fix for NVIDIA cards. OrcaSlicer (especially the Flatpak version) fails to create hardware-accelerated buffers on NVIDIA, leading to crashes or black screens. The error log typically shows: Failed to create GBM buffer of size... Invalid argument
   Solution: Force the use of the correct backend.
   If using Flatpak: Run this command in the terminal:
   bash flatpak override --user --env=GBM_BACKEND=dri io.github.softfever.OrcaSlicer
   Note: While this fixes the crash, it may force CPU rendering (causing lag)

3. Moonraker API / Printer Configuration Bug
   There is a specific bug where OrcaSlicer crashes when loading the Mainsail web UI (port 80) for printer communication. This occurs because the software tries to load a web interface that conflicts with the NVIDIA driver on Linux
   Solution: In OrcaSlicer, go to your printer settings and ensure you add the Moonraker API port (7125) explicitly to the printer address. Avoid adding port 80 for the device UI

4. Wayland + NVIDIA OpenGL Stack Corruption
   NVIDIA’s OpenGL implementation on Wayland (which Nobara likely uses) is fundamentally broken for some Qt/OpenGL applications like OrcaSlicer
   Solution A (Zink/Hardware Acceleration): Launch OrcaSlicer with these environment variables to force OpenGL to run on top of Vulkan (hardware accelerated):
   bash
   __GLX_VENDOR_LIBRARY_NAME=mesa __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json MESA_LOADER_DRIVER_OVERRIDE=zink GALLIUM_DRIVER=zink WEBKIT_DISABLE_DMABUF_RENDERER=1 orca-slicer

Solution B (X11): Switch your Nobara session from Wayland to X11 at the login screen. This avoids the NVIDIA Wayland issues entirely

5. Installation Method Instability
   The AppImage and system packages (AUR/Nix) have a history of immediate segfaults on NVIDIA systems, while the Flatpak is generally more stable (though still requires the GBM_BACKEND fix mentioned above)
   Solution: If you are using the AppImage or a custom build, uninstall it and install the Flatpak version from Flathub, then apply the GBM_BACKEND override

Summary Checklist for Nobara 43:
Switch to X11 session.
Use the Flatpak version of OrcaSlicer.
Run the flatpak override --user --env=GBM_BACKEND=dri... command.

[AlexandruBaia]

Not to familiar with nobara perse but usually you can install other desktop envirments that support x11.
If you want to try and force it, should be something like "flatpak override --nosocket=wayland --socket=x11 [app-id]" or you can use Flatseal for the GUI option. What I did for creality print in the end was to setup a distrobox + gamescope that ran ubuntu since cachy had some other broken dependencies and this is how my launch command looks: "env __GLX_VENDOR_LIBRARY_NAME=nvidia __EGL_VENDOR_LIBRARY_NAME=nvidia gamescope -w 3440 -h 1440 -W 3440 -H 1440 -b -- distrobox enter slicer-box -- /home/alex/VFX_Software/Slicers/CrealityPrint-V7.0.0.4127-x86_64-Release.AppImage"

[Gorlinux]

This is an interesting tip too: Check your printer connection: Use port 7125, avoid port 80

Explanation:
The port 7125 fix addresses a specific Linux/NVIDIA crash bug related to OrcaSlicer loading a web interface in the background. It is not a general networking tip—it is a direct fix for a specific crash scenario.

Here is exactly what this has to do with your issue:

1. The Bug (Identified by Users)
   Users on Mastodon/Reddit discovered that OrcaSlicer crashes on Linux with NVIDIA GPUs specifically when it tries to load the printer’s web UI (Mainsail/Fluidd) on port 80
   The crash occurs because OrcaSlicer’s method of rendering this web view conflicts with the NVIDIA OpenGL drivers on Linux.

2. The Mechanism (Why port 7125 fixes it)
   Port 80 (HTTP) : This is the port for the visual "Device UI" (Mainsail/Fluidd dashboard). When you add your printer via IP only (e.g., 192.168.1.50), OrcaSlicer defaults to port 80. It attempts to load the graphical web interface in a background tab.
   The Crash: The NVIDIA/Linux OpenGL stack crashes when trying to render this WebKit/Gtk web view. This happens even if you never click the "Device" tab. The software initializes the web engine in the background, causing an immediate segfault
   The Fix: By appending :7125 (e.g., 192.168.1.50:7125), you are telling OrcaSlicer to connect directly to the Moonraker API port. Moonraker handles file transfers and printer commands via pure JSON/HTTP, not a graphical web page. This bypasses the buggy web renderer entirely, preventing the crash

3. Why this applies to YOU (Nobara 43 + RTX 3080)
   You are on Linux (Nobara/Fedora) : This bug is exclusive to Linux. It does not occur on Windows, which is why 90% of the troubleshooting guides (including the official ones you cited) do not mention it .
   You have NVIDIA: This bug is exacerbated by the proprietary NVIDIA driver’s poor handling of the specific graphics calls made by the OrcaSlicer web view.
   You have a printer configured: If you have added a printer in OrcaSlicer, the software is attempting to connect to it and load the UI, triggering the crash.

Summary:
It is not about "fixing your Wi-Fi" or "404 errors." It is a surgical workaround to stop OrcaSlicer from touching the graphical web interface (port 80) which is poisoning your NVIDIA/Linux graphics session. Change your printer address to use port 7125 immediately. This is very likely the solution to your frequent crashes.

[Gorlinux]

I highly recommend that you get an LLM account (like on chat.deepseek.com) and describe your issue.
It helped me a lot in the past.
With its help, I even got an X11 VNC-Server running on Fedora 43 on my Strix-Halo NAS and this was not an easy task.

[HenrySturm]

I am also on Nobara 43 with an Nvidia GPU and ran into a similar issue. For me Orca was mostly stable except it would hang and then crash consistently after hitting print. I was able to fix it by changing the Network plugin version to the latest (02.03.00.62) in Preferences -> Online -> Network plugin. For some reason it was set to legacy by default