I use PrusaSlicer from Flathub. I was using PrusaSlicer on Windows before switching to Linux. I’ve been using it since the original Slic3r stopped getting updates. Because it’s available as a flatpak it should work on pretty much any distro and immutable distros

Lychee and Cura.

Lychee because I always liked the feature set for supports better than Chitubox.

Cura because I spent a couple days comparing prints side by side with Prusa and my printer liked Cura better. It gave me better prints all around. Prusa needed an endless amount of tweaking. I don’t mind tweaking but at some point enough is enough.

I’m using Fedora KDE 42 and I found that to run Orca well I had to switch to the flatpak of the nightly builds. It still crashes sometimes, but not very often.

Bambu Studio was stable, but I have ditched it for Orca. I also use Prusa Slicer to run my Klipperized Mk3s. Prusa Slicer has always been rock solid for me no matter the distro or OS.

Huh, I have not had any issues with orca slicer on Linux Mint at all, I’ve been using it exclusively for over a year now. Haven’t had issues linking my printer via WiFi either, I just put the IP and port and it worked right away.

OrcaSlicer has now a Flatpak Version on there Github. I always used Cura but since one year i use Orca

I use orca, ideamaker (for the cr30)

And for resin printing i use chitubox

I think all of them I downloaded the appimage from the repo or their main site.

The problem you’re seeing is likely related to this bug. There seems to be a lot of overlap in issues with Wayland and slicers. I’m using the AppImage version of the Creality Print slicer, and it suffers the same issue. I have to use the following command line to launch it:
__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json WEBKIT_FORCE_COMPOSITING_MODE=1 WEBKIT_DISABLE_COMPOSITING_MODE=1 WEBKIT_DISABLE_DMABUF_RENDERER=1 ~/.local/bin/CrealityPrint_Ubuntu2404-V6.2.1.3044-x86_64-Release.AppImage %F

That’s all on a single line. Ultimately, I created a .desktop file: ~/.local/share/applications/CrealityPrint.desktop
To run the slicer with that command in the EXEC line and everything works fine. Assuming the modified command to launch the slicer works for you, you should be able to create/modify the .desktop file to launch Orca Slicer similarly. Desktop File:

[Desktop Entry]
Categories=Utility;
Comment=
Exec= __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json WEBKIT_FORCE_COMPOSITING_MODE=1 WEBKIT_DISABLE_COMPOSITING_MODE=1 WEBKIT_DISABLE_DMABUF_RENDERER=1 ~/.local/bin/CrealityPrint_Ubuntu2404-V6.2.1.3044-x86_64-Release.AppImage %F
Icon=CrealityPrint
MimeType=model/stl;application/vnd.ms-3mfdocument;application/prs.wavefront-obj;application/x-amf;
Name=CrealityPrint
NoDisplay=false
Path=
StartupNotify=true
Terminal=false
TerminalOptions=
Type=Application
X-KDE-SubstituteUID=false
X-KDE-Username=

I don’t run Linux , but I love Prusaslicer and it is available for Linux: https://flathub.org/apps/com.prusa3d.PrusaSlicer

I used Lychee, I haven’t seen it mentioned here and it is very good.

I use cura on Ubuntu without issues, the appimage version. I did also try prusa/super slicer not too long ago and it worked without issues as well.

I use Orca on EndeavorOS and it works perfectly. There’s an AUR package for it so it’s simple and well supported (would work as well on anything Arch based).

Linux (Mint) and Nvidia GPU here. I use Cura. There is a weird bug where, if you open a file right after the program loads, it will act as if nothing happened (you can open menus, rotate the view etc) for maybe a minute until the model pops up and you can go about your business. Other than that, no issues.

I use Orca,but within a Linuxserver.io container. Which has the advantage that you can use it from a tablet,etc. as well.

SuperSlicer

I use cura and octoprint for my Flashforge creator pro. Works great.