Hyprland
Hyprland copied to clipboard
hyprwm
PrusaSlicer not opening
Distro: Arch Linux
I have tried several PrusaSlicer versions (main repos, git and bin from the AUR and even flatpak) as well as SuperSlicer, none of them go past the loading screen, if I switch to Sway all of them work perfectly.
Launch log for PrusaSlicer:
I don't even know wtf that is
Have you tried forcing xwayland with GTK_BACKEND=x11?
Hi, I'm having the same issue. PrusaSlicer is already using x11 backend, see https://github.com/prusa3d/PrusaSlicer/issues/8284#issuecomment-1117203502
doesn't seem to me like something Hyprland should control here...
Does it crash or just never opens a window?
Also, can you launch hyprland (ONLY hyprland, no exec-onces) and then the faulty app, and provide the hyprland log?
The process doesn't crash, but never opens the main window. As miscawelo said there is first a loading window, then nothing.
The hyprland log file is attached, I just opened a foot terminal first to be able to launch the prusa-slicer command.
Well, maybe you should consider switching to a real slicer, like Cura. (I'm jocking)
I got triggered a bit, @Estebiu :)
But yeah. same issue here. splash windows shows, then nothing visible, process running in bg
I just stumbled upon this one. Cura5 does not open either.
However it shows an error "Could not probe OpenGL. This program requires OpenGL 2.0 or higher. Please check your video card drivers."
hyprland uses gles 3.2, and gl 2 iirc is the oldest ver. Whut
Lol.. dunno, man! I've cura-5-bin from AUR installed, if that helps.
I just stumbled upon this one. Cura5 does not open either.
However it shows an error "Could not probe OpenGL. This program requires OpenGL 2.0 or higher. Please check your video card drivers."
I decided to use Cura in the meantime and got the same error, I have to temporarily set QT_QPA_PLATFORM as "xcb" for it to open but it works for now.
Hi, As a workaround, I got prusaslicer running using Xpra. You can run it using:
xpra start --attach :100
DISPLAY=:100 prusaslicer
and running xpra stop 100 once finished (or even add the xpra start command into your hyprland.conf file and letting the xpra session run in the background).
I'm not sure if this is linked at all with the initial issue, but I noticed that I couldn't start prusaslicer right away with xpra start --start-on-connect=prusaslicer (or other variants). The main window would just not open.
Just wanted to tune in here as well. The GTK2 builds of prusa-slicer and superslicer both open up fine for me, so it may be something related to GTK3 that causes issues here.
Hi, As a workaround, I got prusaslicer running using Xpra. You can run it using:
xpra start --attach :100 DISPLAY=:100 prusaslicerand running
xpra stop 100once finished (or even add the xpra start command into your hyprland.conf file and letting the xpra session run in the background).I'm not sure if this is linked at all with the initial issue, but I noticed that I couldn't start prusaslicer right away with
xpra start --start-on-connect=prusaslicer(or other variants). The main window would just not open.
@4rnoP I was able to launch using xpra in one line with:
xpra start --start-child="prusa-slicer" --attach --exit-with-children
this way you don't have to manually stop xpra afterwards either. thanks for the workaround!
Xpra does seem to work as a workaround for this, and can confirm both PrusaSlicer and SuperSlicer don't work by default. The performance is atrocious though.
I've seen the devs over at the Prusaslicer repo mention that the recent issues regarding Wayland/Linux are already fixed in their internal builds. So hopefully the next release will finally be usable without workarounds.
This is no longer happening for me on the latest version, PrusaSlicer is opening fine within Hyprland on Arch Linux. prusa-slicer 2.5.1-1 hyprland 0.23.0beta-2
