Flatpaks crashing after rebasing to stable from gts (nvidia-dx) #1647
Comments
dosubot
bot
added
bug
|
Problems persists with "latest" branch |
|
Anything on the terminal when you try to launch one by hand? |
|
Running
|
|
devpod isn't a flatpak, it'd be |
|
You're right, sorry about the misleading issue title. Gnome Software also isn't a flatpak, but it crashes in the same way. Couldn't find a way to run it from terminal without the command finishing, so can't find error outputs for that. Captured two flatpak crashes however: flatpak run com.rtosta.zapzap:
flatpak run io.github.zen_broswer.zen:All crashes came after varying periods of the apps running, not immediate like dev-pods |
|
Can you try on the X11 session? (Log into the GNOME Xorg session at the login screen via the gear icon on the bottom right). |
|
This seems to work better. No flatpak crashes yet, but dev-pods still isn't working. It doesn't crash, but just gives a white screen Running dev-pods in terminal: |
|
Yeah the wayland errors led me to believe that it's an nvidia issue on wayland. Not sure on devpod but maybe someone else might have a clue. |
ZapZap is dead on Wayland for many people including me. I can confirm this, also there is a bug issue on their github about it. When it comes to Gnome Software it was always flaky, no matter the distro. At least for me. Zen Browser uses Firefox and Firefox have issues on Wayland. All your problems are unfortunately related to Wayland and Nvidia. Or just Wayland in some cases. |
|
I also have the same problem with devpod crashing immediately. Also rebasing to stable from gts Run dev-pod in terminal: |
|
Are you on nvidia also? |
Yes |
|
Hi there! I used the
|
|
A temporary fix I've found is to run dev-pod with the following environment variable, as shown in this terminal command: |
|
Another fix i've found is just add this to .bashrc file |
|
A report from a like user's perspective but with the dGPU off (nvidia modules not loaded): I was on bluefin-dx-nvidia:gts, then rebased to bluefin-dx-nvidia:stable as well, with currently no nvidia modules enabled. I have no problems with random crashes specifically (also no problems with devpod), but I do have a lot of flatpaks that simply won't launch. The common errors for them seem to be:
It seems to indicate that the mesa vulkan backend for intel graphics is used (correct me if wrong). This post from the bazzite repo suggests a fix that sets the use of the GL backend, which supposedly does work. It is possible we are all sharing the same underlying problem (nvidia and intel users alike), namely that the mesa vulkan backend is acting up for some reason (but the error conditions and logs are different in both cases). My guess for the cause would then be Mesa or GTK (?). The above link to the bazzite post also references to what seems to be the same bug on redhat: https://bugzilla.redhat.com/show_bug.cgi?id=2301725. You might find some more info there, but honestly it is somewhat confusing to me. Someone says it is an upstream bug in GTK that is now fixed (recently), so we fedora users may have to just wait it out. Then the last two messengers say it is actually a nvidia driver issue (proprietary). I don't know what to make of it. Is it possible I am somehow affected by this issue through the nvidia driver even though I am not using it? @saltrocks are the flatpaks from gnome also working on your latest bluefin branch (Papers, Calculator, Calendar, Text Editor, etc.)? Btw, also Mission Center. |
|
I'm in a similar situation with Intel/Nvidia hybrid graphics. Calendar, Calculator, Text Editor and Mission Center all fail to launch for me (on stable). Output trying to launch Mission Center: Seems as if it is running but without a window? |
Describe the bug
After rebasing to stable from gts (nvidia-dx), several flatpaks became unstable and crashes frequently. Obsidian, Zen browser, Software center to name a few.
Devpod isn't usable at all, crashing immediately after starting.
What did you expect to happen?
Flatpaks working as they did before (not crashing randomly).
Output of
rpm-ostree statusState: idle AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot Deployments: ● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:stable Digest: sha256:2a636edacae4ed133547475a4b6f4f8d4c20de2227716548ed35ec658e910fb8 Version: 40.20240902.0 (2024-09-03T05:53:45Z) LayeredPackages: gnome-shell-extension-pop-shell ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:gts Digest: sha256:0524a47515e10033d6daa58bf361c7256ec868f2b52ae7f2ba927be3131aa3e5 Version: 39.20240831.0 (2024-09-01T17:53:39Z) LayeredPackages: gnome-shell-extension-pop-shellOutput of
groupsExtra information or context
Using nvidia-dx stable branch.
The problem was not present on gts branch.
The text was updated successfully, but these errors were encountered: