Open Firnthon opened 2 months ago
To fix this problem X window app should use Wayland by default. This is not working. To force Orca using Wayland in the terminal type unset $WAYLAND_DISPLAY
and then tun Orca from terminal. If this will not solve the problemu - reboot OS.
To fix this problem X window app should use Wayland by default. This is not working. To force Orca using Wayland in the terminal type
unset $WAYLAND_DISPLAY
and then tun Orca from terminal. If this will not solve the problemu - reboot OS.
So the app only works under wayland? Not possible support for systems without wayland?
I tested with Cosmic DE (wayland) on Pop!_OS 24.04 and got the same as above, I also have GNOME added to this install and when starting a GNOME (wayland) session I do not get this problem. Just added here in case it helps developers to understand. Also used the dev-release of OrcaSlicer which is made for Ubuntu 24.04 (new version for WebKit) and it is the same, however the symlink-trick is not needed. My suspicion is on Cosmic DE rather than OrcaSlicer.
Updated my Cosmic DE today, after that I can now start OrcaSlicer (the U24.04 version).
Is there an existing issue for this problem?
OrcaSlicer Version
2.1.1
Operating System (OS)
Linux
OS Version
Pop!_OS 24.04 alpha
Additional system information
No response
Printer
QIDI X-Max 3
How to reproduce
sudo ln -s /lib/x86_64-linux-gnu/libwebkit2gtk-4.1.so.0 /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37;sudo ln -s /lib/x86_64-linux-gnu/libjavascriptcoregtk-4.1.so.0 /lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
(orca-slicer:5567): Gdk-WARNING **: 09:19:51.343: The program 'orca-slicer' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 3763 error_code 3 request_code 4 (core protocol) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)