Latest Fedora update broke snap and flatpak apps

Ask Fedora
, ,
22

If someone else faces that problem with Silverblue or another immutable variant, here are the steps I took to revert to mutter-48.2-2 (the version before the bug):

First, I downloaded the commit history of the last 10 days

sudo ostree pull fedora:fedora/42/x86_64/silverblue --commit-metadata-only --depth=10
ostree log fedora:fedora/42/x86_64/silverblue

Then I checked the differences day by day and found the commit from May 26 to contain the older mutter version.

rpm-ostree db diff 71a337e442a2dc36df79e123bb5011a1ffc5e2bd0ce8aac61157fd6ecd477491

After that, I downgraded my system with rpm-ostree deploy 71a337e442a2dc36df79e123bb5011a1ffc5e2bd0ce8aac61157fd6ecd477491 and pinned the deployment with sudo ostree admin pin 0 so I would have a working system until the fix is published.

2 Likes
23

The bug is in the Mutter component, and the work on fixing the package is being tracked here:

Please do not use “sudo dnf downgrade”. It gives you Mutter 48.1, a version with over a dozen different known bugs.

The best solution for fixing your system is described in the third comment on the linked Bugzilla issue.

25

Small followup regarding that:

  • The patch was discovered to be incomplete. It fixes the mouse cursor issues, but application windows can still become invisible. GNOME will most likely be reverting the entire original bug instead of trying to patch it for now.
  • GNOME are preparing a 48.3.1 hotfix here, but it hasn’t been updated yet after the discovery that the patch was incomplete:
26

The fix is now in for Silverblue in the latest image.

2 Likes
27

The Mutter 48.3-2 package should be available on all package mirrors now. It resolves the issue by reverting the code that caused the bug. This approach is also the most likely course of action for the GNOME project, and given the circumstances, we decided not to delay implementation any further.

28

it fixes the window interactions I’ve previously tested.

29

My original issue is resolved now with the new release of mutter-48.3-2.fc42. :tada:

1 Like
30

I might make a separate topic for my situation in case it’s different from yours, but I am using Fedora Workstation on GNOME 48.2 (System is up-to-date) and I’m having issues with most if not all Electron-based Flatpaks (in my case Signal and FreeTube refuse to open. Signal shows a blank screen, FreeTube shows nothing). I have the latest version of mutter installed ( mutter-48.3-2.fc42).

I don’t appear to have this issue if I use a native RPM (I tried FreeTube’s RPM and it works just fine, compared to it’s flatpak which still just doesn’t function)

It appears as if I’m not the only one with this issue and that the fixes in the latest release of mutter are insufficient: Mutter 48.3 hides xwayland windows after any screen reconfiguration (#4133) · Issues · GNOME / mutter · GitLab

If of any help, I can provide more details about my system.

31

Did you try downgrading mutter just to see if that resolves your issue? Did you try the workaround mentioned in the bug report?

killall mutter-x11-frames
/usr/libexec/mutter-x11-frames &

I don’t see any mentions of the issue remaining in the link you shared.

32

Okay, so, after a system update that didn’t update mutter (I checked), the issue is somehow resolved. Electron flatpaks work again.

But I’ve already migrated all of my Electron flatpaks to their native versions (For FreeTube I now use their RPM, for Signal I use a Debian distrobox) and those already worked flawlessly before the Electron flatpaks got fixed with a fairly recent update for me (And migrating data to them was as simple as knowing the right locations to copy and paste from).

All in all, this situation somewhat damaged my trust in Fedora Workstation as a stable distro that I can rely on not to break, but now I at least know how to install programs in a more reliable way (I’ll at least try to avoid flatpaks for apps built with Electron now).