I’ve had no issues with the ProtonVPN flatpak on Fedora Silverblue.

Firefox is taking that icon from your GTK theme. And that’s the maximize button in the Papirus theme. So this is intended behavior.

You’d have to modify the theme or tell Firefox to use a title bar to fix it.

Are you using an icon theme? Papirus?

You probably ran an update before this and updated the screen locker. Then the OS was in a mismatched that caused the screen locker to break.

Throughout the entire thread.

Here’s the suggestions I remember

• Recommend the Steam flatpak (cons: VR requires more tinkering to get working, flatpak version of gamescope apparently has limitations for dedicated Big Screen mode)
• Ship Steam in a container (cons: breaks gaming on Asahi Linux, relies on third parties)
• Ship a curated list of 32 bit software (cons: even if there’s just one 32 bit package, it’s still a lot of work and infrastructure, current infrastructure work need to be reworked)
• Use ELN for building 32 bit packages (avoids the above mentioned infrastucture rework)
• Stop shipping 32 bit stuff and rely on third party repos for it (cons: rpmfusion can’t afford to do this)
• Create a SIG to represent 32 bit software or repurpose the Gaming SIG

They’re joking, the comment the link is to writes about this same behavior.

Thankfully this isn’t actually being dropped. A more concrete plan of how to drop 32 bit but keep Steam and older games working is underway.

That’s what I thought at first, but I changed it after searching it up.

But I just realized that when I was checking “widthdrawled”, DuckDuckGo was actually showing me the definition for “withdraw”.

The Change proposal has been withdrawn by the author: https://discussion.fedoraproject.org/t/f43-change-proposal-x11libre-system-wide/156330/57

I believe some of the other toolbar buttons also stop working.

Fedora and Red Hat are innovating image-based operating systems. Universal Blue builds on that work.

It would take effort to port that work to Arch. Arch is also a rolling distro, not updating means not getting security updates. Fedora’s release cycle allows them to get more stability, they don’t have to be using the latest version.

Paragon’s NTFS driver was also upstreamed in the kernel in like 5.15.

SteamOS does not get reported as Arch.

It seems that KDE does not plan on supporting Xlibre, though it may still work.

It makes sense that they would not support it. Their goal is to move to Wayland, not to support yet another thing.

Yes, it’s ok for Arch to break things. As their Wiki describes, it’s for “the proficient GNU/Linux user, or anyone with a do-it-yourself attitude who is willing to read the documentation, and solve their own problems.” You’re expected to follow Arch Linux news to watch out for things that require user intervention to avoid breakages.

It isn’t Ubuntu or Fedora who try to make a system accessible to everyone.

Updated the title

But you don’t need a status icon to run in the background.

If Firefox wanted to, they could make Firefox continue running in the background. They could even app a system tray entry for Firefox to access recently visited sites or favorite sites, like what Steam does.

This paradigm is actually the norm on MacOS. When you X out of an app, it doesn’t actually close. It will just have no open windows but stay open on your dock.

All those same options are available by right clicking on the app. Though thinking some more, the status icon being dynamic does give it some extra flexibility, I think it can show recently launched games. Still, does that mean Firefox should get a status icon so that you can access recently opened sites? Should your file manager?

The complaint against the app indicators is that apps tend to throw their icon in there for no reason. Why does Steam need to show itself there? Why doesn’t Firefox?

There’s also some technical reasons why they’re bad. There’s quite a few different protocols to show the icons up there, all each with their own pros and cons. But none can handle sandboxing properly, so work is being done towards a new protocol.

Setting the environmental variable

GSK_RENDERER=gl

in Flatseal or on your entire system should fix the issue. It tells GTK to use the old OpenGL renderer backend for GTK. Once the issue is fixed upstream, it would be a good idea to remove the change.