-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running on Linux using flatpak, window content is black #8337
Comments
Work aroundSwitch to x11. 🤢 Getting this as well on flatpak, and appimage. It seems to be related to Wayland/XWayland. Don't know if this helps but I had the same issue on windows 10 until I let microsoftedgeupdate though a firewall. OrcaSlicer VersionV2.3.0-dev Operating System (OS)Linux OS VersionArch, KDE Plasma 6.2.5 Additional system informationKernel Version: 6.13.1-arch1-1 (64-bit) |
Oh, thank you. But :/ switching back to X really isn't on the cards due to the problems it would cause elsewhere. It's a real shame (and unclear what the reason is...) that, of all the major slicers, Orca is the only one I've used which isn't trivial to run as an appimage on Linux. The Orca AppImage has serious issues and it seems the new flatpak still has teething problems. Closest yet, though. I will probably end up building it myself to finally be able to try Orca. |
|
Incredible, that seems to have done the trick. It now works and displays the window contents. Thanks! |
Can confirm that after the above fix, the flatpak is fully functional, I've tested it quite thoroughly in actual use now |
Glad it seems to be working for some! still broken on both flatpak and appimage for me. I at least can see the startup wizard now after adding WEBKIT_DISABLE_COMPOSITING_MODE=1 but the main preview still does not render. |
Try #8372 in along with |
I have encountered this same issue with the beta flatpak on my workstation running CachyOS (Arch) and Nvidia graphics. On my laptop (Framework 13 AMD with AMD Graphics) the flatpak behaves normally. This leads me to believe that Nvidia is to blame here. At least for me. |
2.3.0-beta2 flatpak updated this morning and still no change. Work area fails to show the build plate. |
Maybe try adding |
I reinstalled the flatpak and added the zink env variable. No change and it still launches XWayland. I added every env variable mention via Yes,
|
Also, when I connect the printer profile to Klipper, |
See #7210 |
Getting a similar problem on EndevourOS (EOS is just arch with GUI installer it uses arch repos/kernels and updates the same as arch) I tried to force zlink as well. 50_mesa.json is where it should be. The old overrides never worked for me either. Operating System: EndeavourOS |
For arch based users facing this issue, they would need to download the latest nightly builds and run the AppImage directly, since the aur versions only point to the beta version and the patchdidnt get merged in the beta build, in addition to that building it by just changing the aur pkgbuild to point to the nightly builds also wont work since the maintainer for that package deletes AppRun and just directly runs the app, they will need to modify the script to have it use the AppRun and not remove it I'll create an aur account to make a pull request to fix this once i have time |
I have the issue with the nightly flatpak I have not used the version in the aur |
Is there an existing issue for this problem?
OrcaSlicer Version
V2.3.0-dev
Operating System (OS)
Linux
OS Version
NixOS
Additional system information
No response
Printer
n/a
How to reproduce
OrcaSlicer-Linux-flatpak_V2.3.0-dev.flatpak
from github releases pageflatpak --user install ~/Downloads/OrcaSlicer-Linux-flatpak_V2.3.0-dev.flatpak
flatpak --user run io.github.softfever.OrcaSlicer
Actual results
Expected results
Program runs correctly
Project file & Debug log uploads
Checklist of files to include
Anything else?
No response
The text was updated successfully, but these errors were encountered: