-
-
Notifications
You must be signed in to change notification settings - Fork 865
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
Crash on startup #4169
Comments
Hmm… Qt 6.8.2 and Arch Linux in both cases… |
@alex-w in my case it's (official?) flatpak from Flathub. I believe it uses it's own copy of Qt. |
Updated Arch (including Nvidia driver) and flatpaks - issue is still here. |
It’s semi-official - yes, I pushes changes when new releases are coming, but I don’t use flatpak and I’m not well for flatpak infrastructure.
It maybe some regression in version 6.8.2 of Qt framework |
Please check our weekly snapshot |
@alex-w where can i get it? Is it available i flatpak? This bug report is about flatpak. |
AppImage: https://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot |
It works (qt6 version). |
Edit: but 24.4 qt6 appimage works too. That's why i asked about flatpak. |
Please share logs |
@alex-w what logs? I already attached them 4 days ago. |
I meant logs from an AppImage - I want to see what happens here |
Well, as expected both appimages used Qt 6.2.4 and doesn't have troubles, but flatpack using Qt 6.8.2 (Stellarium was compiled with Qt 6.8.1). Is it possible to compile Stellarium from source code to see the behaviour in standard environment? |
I just built 24.4 from sources and it works. |
Sorry, I am not familiar with any of AppImages or Flatpacks. Shaders are compiled into a cache that of course must be writable. Maybe this is broken? |
Looks like issue #4143 but i don't use Mesa.
System
Logfile
log.txt
The text was updated successfully, but these errors were encountered: