Flatpak install of 25.1 on Fedora 42 fails to start, possibly relating to Qt
Expected Behaviour
App starts normally as expected.
Actual Behaviour
Splash screen loads as application is starting up then disappears.
When attempting to start from command line using flatpak run org.stellarium.Stellarium
The last two lines indicate an error occured.
[ 2.761][INFO] Loading DSO outline data ...
[ 2.765][INFO] Loaded 100 DSO outline records successfully
[ 2.765][INFO] Loading DSO discovery data ...
[ 2.766][INFO] Loaded 183 / 183 DSO discovery records successfully
[ 2.863][INFO] Using Qt multimedia with FFmpeg version 7.0.2 LGPL version 2.1 or later
[ 3.802][INFO] LandscapeMgr: initialized Cache for 100 MB.
[ 3.802][WARN] QOpenGLShader: could not create shader
[ 3.802][FATAL] Error while compiling atmosphere vertex shader:
Have attached the log.txt file
Steps to reproduce
Open the app from application menu
Open from cmd line using flatpak run org.stellarium.Stellarium
System
- Stellarium version: 25.1 (Installed via flathub)
- Operating system: Fedora 42, (updated with all latest updates from dnf)
- Graphics Card: NVIDIA 2070ti Ver 570.144
- Screen type (if applicable): Resolution, 3440 x 1440 60hz, 100% scale
Logfile
Additional Comments
Have also attempting to install the RPM version, that version crashes with a segmentation fault.
Looks like a duplicate of #4143.
Does it help if you remove libvdpau-va-gl package?
I've progressed a bit, I can get the RPM version to work correctly.
I ran the following command sudo dnf install nvidia-vaapi-driver libva-utils vdpauinfo which was missing from my install and now Stellarium is loading as expected.
Flatpak version of Stellarium still isn't loading
Does it help if you remove
libvdpau-va-glpackage?
Do you mean via dnf (RPM) or a flatpak package?
Do you mean via dnf (RPM) or a flatpak package?
Do you have both? I think there's only the system one, RPM, and I suspect it may be used flatpak Stellarium, although I'm not sure.
In any case, the symptoms still look like this is a duplicate of the above mentioned issue, which should be fixed soon.
Is the issue still exist?