You are not logged in.
I've been having an issue with my Flatpaks for the past month or so, and I have gotten around some of the issues for a while by using workarounds (.Appimage or browser-based applications), but after updating recently multiple times, I've seen no improvement or change. I had assumed a dependency or other issue had temporarily caused my Flatpaks to stop working on Arch, but I don't know if that's actually the case.
In short, several Flatpaks I use stopped working entirely. Here are my Flatpaks in particular as well as their statuses.
Discord - Launches briefly with the updating screen, then crashes right away. Using flatpak run command reveals "6 Segmentation fault" and a message about zypak-wrapper
Flatseal - Actually launches with no issues.
Microsoft Edge - Doesn't launch at all. Flatpak run command reveals a GDBus.Error.org message instead of a segfault.
Obsidian - Launches briefly and loads UI if I'm lucky, but crashes soon afterward. Usually loads nothing. Flatpak run reveals "14 Segmentation fault" and a similar message about zypak-wrapper
Bottles - Launches with no issues
Floorp - Launches with no issues
GIMP - Launches with no issues
Signal - Had some message about the host portal, but I don't really use this app anymore to begin with. Crashed as well.
Upscayl - Fails to run at all. Flatpak run command shows "3 Segmentation fault" and another zypak-wrapper message.
I would assume that the zypak-wrapper and segfaults were the common thread if it weren't for Signal and Edge not launching for those same reasons, as far as I could tell from the "flatpak run" command.
So far, I've tried the following to troubleshoot.
Repeatedly updated Arch and all Flatpaks with "flatpak update"
Tried opening problem Flatpaks with different desktop environments than my preferred Wayland (Hyprland) setup. GNOME with X11, for instance, showed no difference. Same problem Flatpaks crashed exactly the same way.
Repairing my Flatpak setup with "sudo flatpak repair" and rebooting. No changes.
Changed some settings in Flatseal before related to forcing X11 windowing, Wayland windowing, and so on in the socket settings. Various combinations led to no real changes.
Changed a few other settings in Flatseal like GPU acceleration, but nothing changed.
I looked a little into zypak from online searches, but I'm not sure just how relevant trying to do something with it would actually help because many of the issues are from a few years ago and were fixed with subsequent updates. Additionally, a lot of the threads I've come across about zypak suggest that Wayland is a factor, but running the apps on X11 gave me the same result, so I'm not sure if that makes a real difference.
Anyway, I would appreciate suggestions on how else to troubleshoot this. I'm not sure what else to do at the moment, but maybe there's something else I'm overlooking.
Last edited by NightPatrolman (2024-11-16 13:53:47)
Offline
Funny I find myself here after searching online for this solution again. This forum thread came up as a result because I still haven't fully solved this issue.
However, I do have a minor update that at least makes me somewhat happy. I am able to launch the Obsidian Flatpak from Rofi after clearing it's GPU cache.
rm -rf .config/obsidian/GPUCacheNow Obsidian launches without crashing almost instantly. I can actually click things, access settings, and type using the Flatpak installation again. The strange thing is that running the Flatpak from Terminal like so:
flatpak run md.obsidian.ObsidianWill result in an error and crash, which I don't understand the reasoning behind. Some apps such as Upscayl do run again from Rofi as well, but Discord still crashes and segfaults no matter what I do. I cleared its directory like so and still have the same instant crash issues with it.
rm -rf .var/app/com.discordapp.DiscordAfter a bit more searching, I'm starting to wonder if my mesa drivers (AMD GPU user here) might be the issue, but I'm not 100% sure what my first step should be to continue troubleshooting this.
Offline