I’m aware of their reason for dropping support but it’s not sensible to drop a functioning system and replace it with nothing and then talk about how to do it better for years. That post is from 2017, it’s 2024 now and there is still no replacement in sight.

Or, use KDE. Which does it all without any extension, even if the current API sucks.

It’s not acceptable to me to require a third party extension to achieve a basic useable desktop environment.

I also really like GNOME the software but I moved away a few months ago because of this.

As is, the current GNOME is unusable to me without extensions because they refuse to implement support for appindicators. You literally cannot use applications that minimize to tray on vanilla GNOME right now. They have been talking about adding their own protocol for years but that is of no use when things are broken right now.

Important features and bug fixes are always stuck in merge request limbo for years. VRR for Wayland got merged recently after 4 years and it’s still experimental. DRM leasing is still missing on Wayland, KDE added it 3 years ago.

The final straw was when KDE announced HDR support last year I switched over because I knew GNOME would probably lag behind by months or even years.

Same issue here, Plasma 6 has broken Flatpak theming in general for me.

Both the cursor size differs between native and Flatpak applications and also the dark mode is not applied correctly in some applications.

For example, VS Code in Flatpak has white context menus even though dark mode is activated:

That’s strange. Do you happen to use a USB extension cables to reach your steering wheel?

I noticed that Linux is far worse than Windows in recovering from USB errors. Most of the time it will just stop working where Windows will ignore the error and continue.

If you are interested in diagnosing the issue you can run journalctl -f in a terminal while playing and check the logs when an issue occurs. USB errors will be marked red in the log.

Calling something that can be fixed with a simple software update a deal breaker is strange to me, yes.

Adding it as critique so it can be fixed is fair, as a reviewer I expect them to note things like these. I do not need them to add their own opinion on whether this is a deal breaker or not.

His recent video on the Fairphone is what did it for me.

His “deal breaker” is that the notification sound is too loud? Replacing a battery by heating up your phone, prying it open, disconnecting the flimsy battery cable and prying out the glued in battery is apparently just as easy as using your hands. Seriously?

Do you mean the G923? Can’t find a G928 anywhere. The G923 is supported since kernel 6.3.

Which one? The G27/G920/G29 and some others are supported pretty much out of the box.

Not thanks to Logitech but they do work fine.

Fedora 40. Runs pretty well, even pre-beta.

Ah, not sure how I overlooked that one.

However, it seems to be tied to the normal screen timeout which I can’t use because KDE does not recognize all fullscreen applications correctly when playing games with a controller. I put 360 minutes as timeout for now, that should be sufficient.

Out of interest, is the “Run command” option still available somewhere or was it removed in Plasma 6?

SteamVR on Linux works out of the box if you have a Valve Index or a HTC Vive.

There are some others that work via ALVR but can’t speak about that.

Two caveats though:

• Valve likes to break SteamVR for Linux with every third update and then takes weeks to fix it
• It works but there’s a lot of issues with it. From incorrectly scaled UI, to missing features, to SteamVR Home not working for a year straight

Most of the time there are community workarounds but there’s only so much they can do.

Thanks for the response, excited to see more support being added!

You can run Steam in gamescope, doesn’t matter if it’s sandboxed or not.

So, installing your Vulkan layers and gamescope-git on the host and running ENABLE_HDR_WSI=1 gamescope --hdr-enabled --hdr-debug-force-output --steam -- env ENABLE_GAMESCOPE_WSI=1 DXVK_HDR=1 DISABLE_HDR_WSI=1 flatpak run com.valvesoftware.Steam -bigpicture should do it on Plasma 6?

With HDR making its debut on Plasma, what are the plans moving forward?

From what I have seen getting games to work in HDR currently requires the correct vulkan layers and a recent gamescope version?

As a side question, will there be an easy way to get HDR working with the Steam flatpak for the Plasma 6 launch?

Out of interest, which one is it?

Variable Refresh Rate support for the whole desktop

What’s the difference to the current Plasma 5 implementation? I was under the impression VRR always worked over the whole desktop if enabled.

Plex is a fork of Kodi

Just as a side note, Plex has absolutely nothing to do with Kodi. Jellyfin is a fork of Emby, maybe you mixed them up.

why the majority is acting like it is the ordinary people’s fault?

Because it is. The market produces what consumers buy.

If nobody buys SUVs, nobody produces SUVs. It’s 100% on the consumer in the EU, there’s enough other cars available.

Extreme stuttering in Yuzu. It reads 60fps but it is absolutely not. Using the AUR version, since the Flatpak can’t load my roms folder from my NAS. (Before you assume the network drive is the issue, know that it is over a 10g SFP+ on an NVMe on the NAS. No problems in Windows.)

I don’t have an Nvidia GPU but give the pineappleEA builds a try. It contains all the changes in the current early access build as well.

As for running the Flatpak, you have to whitelist the folder your NAS folder is mounted on. Best way to do that is by installing Flatseal. Just search for yuzu, scroll down to Filesystem and add the folder where your games are contained in Other files.

Check out Btrfs Assistant. It does what Timeshift does with a similar UI but works with any subvolume layout.