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

Strange. Discord, ProtonMail, ProtonUp-Qt, and Spotify should all work perfectly. Except maybe some drag and drop issues for Discord and ProtonMail? And Discord’s activity status is blocked from tracking you. What issues did you have specifically?

I can see OpenRGB having issues given that tries to talk to the hardware itself, did you install the udev rules?

Handbrake has access to all your files by default so that shouldn’t be an issue.

What Flatpaks did you have issues with?

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?

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

Fortunately this update won’t require additional porting work over 1.21.6. It’s just minor fixes.

I’m not a fan of how they do drops either. Makes updates feel less special, I can barely remember the names of the drops, and makes things more complicated for modders.

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.