Latest Fedora update broke snap and flatpak apps

Hi,

I’ve been troubleshooting all day after Mullvad broke my server after an update. Now I’m troubleshooting my workstation after I ran the latest system updates and all my flatpak and snap apps stopped working (like Signal, Spotify, Vivaldi browser).

When I try to run the apps all I get is a transparent window, I can’t see any app. Anyone know how to troubleshoot this?


Apps using the Electron framework are affected too. Seems like a serious issue. And a very annoying one for that matter.

I am having the same issue since the latest update for Fedora 42, most of the apps that open a modal (zoom, slack) would not display it, I just see the icon on the screen

Any workaround that you can share with us? My system is mostly unusable because of this.

Unfortunately, I still haven’t found a solution. I wonder if it had to do with the nvidia driver update. What’s your GPU? If you share some specs maybe we can narrow down the issue.

Is a new Framework 13 laptop, AMD Ryzen™ AI 9 HX 370 w/ Radeon™ 890M × 24

Maybe is related to this issue Attaching files broken in fedora 42 after recent update - #2 by tqcharm

I’ve started a gnome session in x11 and it solves this issues.

Actually I don’t know what the f*** is going on, I’ve loged out and started a normal session and apps work again. At least for some time after some time is like an overlay gets over them and I can’t click or tap on them anymore.

I’ve downgraded to mutter.x86_64 48.1-1.fc42 fedora and it all seems fairly stable for now

2 Likes

hey
i just did a fresh install of slack flatpak just to see if I could see similar behavior, with mutter-48.2-1.fc42 installed. The default slack window pops up for me.

I just point it out because its going to complicate resolution of this issue if there is a difference in behavior between paks already installed before the mutter update and paks installs after the mutter update. A quick test by someone trying to reproduce may not see the behavior and that may cause confusion in a ticket discussion. It’s weird. I need to see if I can get the problem to fire for me.

1 Like

I tracked the issue here Issues · GNOME / mutter · GitLab

2 Likes

that upstream report comments seems to suggest there are usage patterns that trigger it. So while we wait for the identified patch to be reverted or whatever the technical solution in the next update, maybe there is a mitigation strategy to help avoid triggering it.

You will get it with 48.3. For slack is a little intresting, the main window will show but if you get in a huddle with someone and try to pop-out the huddle window you will get this behaviour.

You can try this with zoom, opens the main window and if you tap on a meeting the window that it suppose to show up it will never show.

it took a little more effort but i got there with zoom. I could interact with the main window and the meeting window i started.. but once i opened up settings window lost ability to interact with main and meeting.

1 Like

Slightly different behavior then what I had. You could try one more if you have jetbrains editors (golang or rubymine) open settings and you will notice the same behavior.

yeah its not avoidable… its entirely has to do with modal windows and losing track of which layer is suppose to be the interactive one. Seems the only mitigation is package downgrade right now.

Whelp, this gave me a good reason to install the updates testing repo on one of my systems.

1 Like

Downgrading mutter-48.3-1.fc42.x86_64 to mutter-48.1-1.fc42.x86_64 worked for me as well.

Downgrading to 48.1-1 worked for me too (solved my problems with KiCad).

looks like upstream has a fixed merged in the last 8 hours.

1 Like