Heroic is really nice and what I recommend, but the UI is a bit clunky and spread out.

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

Probably the biggest one is the next piece of the Wayland session restore puzzle clicking into place: David Edmundson has implemented support for the xx-session-management-v1 Wayland session restore protocol in Qt 6.10! This means that software built on top of Qt 6.10 (for example, Plasma and KDE apps) will be able to start implementing the protocol themselves. Once they do, then finally real session restore will work on Wayland

I hope we’re able to opt out of apps positioning their own Windows. My favorite thing about Wayland is that apps can’t control where their windows open, so they always open in a consistent location chosen by the compositor.

Annoys me whenever I use Windows, MacOS, or Xwayland apps that open up in seemingly random locations.

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

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.

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.

The benefit for Amazon is good PR and supporting open source projects their engineers use.

You can check if you are using Xorg or Wayland in the Settings -> System -> About -> System Details page. If you’re using Wayland, you’re all good, nothing changes. If you’re using Xorg, you may notice some changes. If you’re using NVIDIA on Ubuntu 24.04, you’ll be on Xorg by default. If you’re using a later version or AMD/Intel, you’ll be on Wayland be default.

To keep it short, X11 was the old protocol for creating and managing windows. Xorg implemented this protocol. But both the protocol and implementation have many shortcomings that are difficult to address for a multitude of reasons (breaking compatibility, poor code base, a ton of work, etc).

Rather than putting lipstick on a pig, a new protocol, called Wayland, was created. It was designed for modern needs and tries to avoid the pitfalls that X11, Windows, and MacOS have. It doesn’t just copy what those three did, it’s more opinionated, so some people love it a lot (like me) or hate it a lot because it changes the way things have to be done and simply does not implement some functionality, either purposefully or because the work hasn’t been done yet.

Gnome isn’t locked-in. For being an important open source project, AWS has given Gnome credits so that they can use AWS free of charge for years. Once those credits expire, they are free to leave. So long as they do their proper preparation to migrate away, they get multiple years of hosting for free.

Gnome has already been in this circumstance. Their free hosting from another provider expired so they moved. Though as I’m researching this, I can’t find the sources I’ve read this from.

Could you please explain further?

How does free infrastructure hosting from AWS hurt anyone? There’s no privacy concerns and this helps Gnome’s development.

The only way this will hurt is if Gnome is not prepared to switch away once their credits are up.