-
-
Notifications
You must be signed in to change notification settings - Fork 821
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
Cannot launch under wayland : Qt platform problem #3967
Comments
Reads like a driver setup problem to me. |
Does any other Qt6-based app work? The following hints that the problem may be quite general:
Also, do you have a discrete GPU installed, possibly in an NVIDIA Optimus-like way? |
I'm not using any NVIDIA driver.
|
You should report this to your distro maintainers, because this looks like a breakage of Wayland OpenGL support for all Qt6 apps. |
OK. I'll do. |
The package is from our PPA and standard package may have differences |
Yep, standard packages in Ubuntu are Qt5-based |
In any case, the messages from Qt indicate a serious problem with OpenGL support. Or is Qt6 also provided by the PPA? |
No, we’re using qt packages from standard repository |
So then indeed, it looks like the standard Qt6 packages are broken. |
Can we just add that environment variable to the startup? Or detect the necessity to do so first? (Is there a system configuration where you won't set xcb?) |
We shouldn't try to work around all possible broken setups. |
I agree. |
I did not mean to set xcb globally. But just as we can set some OpenGL variable to ANGLE or SOFTWARE(?) for Windows, we could set another envvar to xcb on Linux, if needed. Is there a way to automatically detect if it's needed? |
It seems to me that you are rushing to insert kludges for issues that may well be solved relatively soon by Ubuntu maintainers (assuming the OP has reported it there). Such things should work out of the box, whether on X11 or on Wayland, and I suppose they used to work before the upgrade. It's just the upgrade that broke them, and, if I understood the OP correctly, it was a system upgrade, not a Stellarium upgrade. If Qt can't figure out that it's on Wayland, or that it should use EGL, or whatever else, there's something broken, and it should be sorted out in the distro, rather than getting worked around by the apps. |
I happily leave the actual 5-minute fix to those affected. |
The kludge for choosing XCB is included already in desktop file (it was added a long time ago) ;) |
Bug has been reported to Ubuntu/Debian Qt6 developpers |
Expected Behaviour
Normal application launch, as worked "before" last system update.
Actual Behaviour
Freeze when launching (see log attached)
Steps to reproduce
Simply type "Stellarium" in terminal
System
Logfile
See attachments
Terminal output: Stellarium Log.txt
Log file: log.txt
The text was updated successfully, but these errors were encountered: