What's a game you've recently played on Linux that worked much better than you expected? I'd be interested in hearing both about flawless out-of-the-box experiences and surprising fixes that made a stubborn game playable.

eMudhra Intermediate CA Compromise

The private keys of eight eMudhra intermediate CA certificates have been compromised. They chain to roots trusted by the Mozilla, Microsoft, Apple and Chrome root programs and by many downstream trust stores.

What actions have been taken?

The root programs and many downstream trust stores have taken action to protect their users. The certificates have been blocked in Firefox and Chrome since the 17th of October, in Apple devices since the 19th and on Microsoft platforms since the 20th.

The issue was responsibly disclosed to downstream trust stores on the 19th of October. Many have already released updates or are in the process of releasing updates.

This also affect your Linux distro packages - read link

Are there workarounds for Linux?

Until a distribution ships an updated ca-certificates package, expert users can distrust the affected roots in the system trust store. This is NOT recommended for ordinary users.

On Debian and Ubuntu, run as root:

sed -i \ -e 's|^mozilla/emSign_ECC_Root_CA_-_G3.crt|!&|' \ -e 's|^mozilla/Comodo_AAA_Services_root.crt|!&|' \ /etc/ca-certificates.conf && update-ca-certificates

On Alpine, run as root:

apk add ca-certificates && sed -i -e 's|^mozilla/emSign_ECC_Root_CA_-_G3.crt|!&|' \ /etc/ca-certificates.conf && update-ca-certificates

On Fedora, RHEL, CentOS Stream, Rocky Linux, AlmaLinux and Amazon Linux 2023, run as root:

d=/etc/pki/ca-trust/source/blocklist; [ -d $d ] || d=/etc/pki/ca-trust/source/blacklist trust extract --overwrite --format=pem-bundle \ --filter='pkcs11:object=Comodo%20AAA%20Services%20root;type=cert' \ $d/Comodo_AAA_Services_root.pem && trust extract --overwrite --format=pem-bundle \ --filter='pkcs11:object=emSign%20ECC%20Root%20CA%20-%20G3;type=cert' \ $d/emSign_ECC_Root_CA_-_G3.pem && update-ca-trust

On openSUSE and SLES, run as root:

d=/etc/pki/trust/blocklist; [ -d $d ] || d=/etc/pki/trust/blacklist trust extract --format=pem-bundle \ --filter='pkcs11:object=Comodo%20AAA%20Services%20root;type=cert' \ $d/Comodo_AAA_Services_root.pem && trust extract --format=pem-bundle \ --filter='pkcs11:object=emSign%20ECC%20Root%20CA%20-%20G3;type=cert' \ $d/emSign_ECC_Root_CA_-_G3.pem && update-ca-certificates

On Arch Linux, run as root:

trust extract --format=pem-bundle \ --filter='pkcs11:object=emSign%20ECC%20Root%20CA%20-%20G3;type=cert' \ /etc/ca-certificates/trust-source/blocklist/emSign_ECC_Root_CA_-_G3.pem && update-ca-trust

On NixOS, add to your configuration:

security.pki.caCertificateBlacklist = [ "Comodo AAA Services root" "emSign ECC Root CA - G3" ];

original: https://store.steampowered.com/news/app/593110/view/678512495722237047

Linux notes:

• Fixed Vulkan games hanging after alt-tab.
• Fixed a case where Steam updater UI would fail to show for some users.

Not sure it will solve some crashes/freezing I'm having when playing The Witcher 3 (2026 remaster) and alt-tabing. Besides, there is still a issue related to the linux-firmware (AMD graphics firmware) regression in 20260610/20260916 version.

Before you leave a comment about Vibes coding or talk about anti-cheat or other related topics, keep in mind that there are already 89 posts on the same subject—this is just to notify you of the update. Even so, there's no doubt that Linux support is beneficial for everyone (in my opinion)

I'd like to add that even though you can see the store and the social section, you can't claim free games or make purchases—which is a bit ironic, since that's what the store is for, right?

I moved recently from Linux Mint, where Wayland is not a thing, to Fedora KDE.

I did it mostly to be able to benefit from better scaling and use of HDR.

It is clear to me to make use of HDR I have to use GE Proton and the appropiate launch commands to use game in Wayland and HDR.

Question is when I load a game that has no HDR, I simply used default proton without any launch commands. I noticed sometimes the scaling i use on the regular deaktop mess up the max in-game resolution, resulting in me having to force Wayland commands to be able to fix it.

As a consequence I end up mostly forcing Wayland via launch commands most of the time.

Is this the same for you? In which cases do you prefer not to use the launch command to force Wayland? Just to learn from it.

Thanks

spects: rtx 3050 mobile 11th gen intel i5

but don't expect to run deadlock or more demanding game...deadlock runs but with 10 fps midgame

Introduction

In 2026 a crack hardware and software engineering team was tasked and sent to rebuild the Linux fractured ecosystem. These people promptly escaped from the trappings of that ecosystem to the background, today they survive as coders of fortune. If you have a problem, if no one else can help, and if you can contact them... then maybe you can hire.. The A-Team.

Who Are You?

We are The A-Team! Some of you might have heard of me, I’m ket, sometimes known as ketxxx of XtremeSystems, TechPowerUp, occasionally Reddit, and these days mostly Win-Raid. If you know of me you’re probably familiar with some of my work; Gigabyte Aorus UEFI firmware modifications, GPU BIOS modifications, the Polaris How To guide on Win-Raid, Asus P5Q Series mBIOSes, etc. With me are a few collaborators and together we are.. The A-Team!

How was Sovereign born?

Sovereign initially started as internally being called the GEMKET Engine, it was an endeavour to bring proper statistical live data back to “legacy” hardware like the Ryzen 2500U weaved into MangoHud.. or as I came to call it MangledHud. After a week of fighting that continuously band-aided spaghetti code (and succeeding) and attempts at untangling the code the decision was called – we would cut the umbilical and rip the GEMKET engine implementation out of it and build our own software free of MangoHuds baggage. Born from that trial by fire is GEMKET Sovereign, or just Sovereign.

What is Sovereign, and Why Sovereign?

Why Sovereign? Because it’s an awesome name for one thing, for another because we wanted a name to emphasise elegance, class, and the cutting edge. Just like the Enterprise-E. Over the decades we have also grown ever increasingly tired of Microsoft and Windows, and particularly now Windows 11 has gone full Sith Lord and not even hiding it anymore.

What is Sovereign? Sovereign is an agnostic, dynamic realtime OSD and more. We call it agnostic and dynamic because the Sovereign engine queries the system for live sensors, makes sure they are not dummies and displays the live sensor metrics to the OSD. The agnostic part comes from one of Sovereigns features, a truly independent OSD that functions on the desktop, in legacy and modern OpenGL titles, and Vulkan. It was said it couldn’t be done, we disagreed and did it anyway. Sovereign operates entirely within standard user-space privileges. It does not modify kernel binaries, it does not crack open closed system files, and it does not steal copyrighted code. We are simply using standard Linux hooks, memory techniques, and display flags in a creative way. Sovereign is also highly efficient and lightweight, both in terms of resources and file size. This is only one of many features though to unite the fractured Linux ecosystem we have also built a .so plugin system not beholden to a specific toolchain.

This software is not a pipe dream, it is not vapourware, it is real, it exists right now, is being developed on Ultramarine Fedora 44 KDE, and while features are still being implemented such as proof of concept microphone and webcam plugins it is functional – including the agnostic OSD. Sovereign is a pure C++20 engine built from scratch with near 0% idle CPU draw. It is fast, lean, and handles raw hardware data. The exact kind of minimalist code efficiency of the Linux kernel itself.

1. The Sovereign Engine and What it Means for Developers and Development

Linux desktop development has been trapped in a culture of compromise for far too long. We decided to draw a line in the sand and say no more, no further! Developers looking to build overlay utilities were told to wait for upstream desktop portal protocols, write massive D-Bus communication boilerplate, or tie their applications directly to specific compositor extensions.

Sovereign OSD completely rewrites the rules by implementing a strict C-Linkage binary boundary viaourPluginAPI, the compilation loop is entirely decentralised.

SOVEREIGN CORE ENGINE

(Protected UI Threads, Wayland Bypass, Graphics Shims)

|

            Strict C-Linkage Isolation Gate

|

                   Custom.so 
plugins

For developers, this means absolute architectural freedom:

• You are no longer chained to a specific toolchain. Write your plugins in C++20, pure C, Rust, or Zig—if it compiles to a standard native .so shared object with C-compatible symbols, Sovereign will load it seamlessly.
• There are zero core dependencies, you can develop complex, low-overhead monitoring extensions without ever needing to look at, link against, or recompile Sovereign's core proprietary graphics pipeline.
• There is Automated Lifecycle Guardrails, plugins are handed strict lifecycle states, the host engine handles runtime setup and cleanup safely, eliminating repetitive code generation.

2. The Sovereign Engine and What it Means for Gamers, Reviewers, and Power Users

To the end-user, an overlay is only as good as its performance signature. Modern overlays have become bloated, requiring excessive memory footprints and spawning background daemons that introduce micro-stuttering during intense gaming sessions.

Sovereign OSD is being engineered with zero bloat, and maximum performance.

• For Gamers: Sovereign delivers a rock-solid, hardware-accelerated telemetry card that floats effortlessly over your games. Because it avoids heavy script interpreters, its idle CPU draws sit at near absolute 0%,freeingevery single frame for your hardware.
• For Hardware Reviewers: Accuracy is paramount. Sovereign completely bypasses generic user-space timing loops, pulling raw data from our picosecond (millisecond readings at double precision) Running Average Power Limit (RAPL) and native kernel sysfs paths. You get accurate hardware tracking from 720p handheld gaming monitors all the way to 32K enterprise computing spaces.
• For Power Users: No installation scripts, no package repository tangles, and no distribution conflicts. You download a single, self-contained AppImage, toggle your options, and play. It works identically whether you are running Arch, Fedora, openSUSE, or Mint.

3. The Sovereign Engine and What it Means for the Future of Linux and the Ecosystem

The migration from legacy X11 to modern Wayland compositors brought a massive security lockdown. To protect user data, Wayland implements strict security sandboxing: applications are intentionally blinded to coordinates and keystrokes outside their own precise window boundaries. While well-intentioned, this rigid design philosophy effectively killed the agnostic overlay ecosystem, leading to fractured desktop ecosystems.

Sovereign OSD proves that the "Wayland Lockout" was never an engineering impossibility—it was simply a failure of imagination, determination, and know-how.

By executing as a completely detached framework surface, Sovereign successfully cuts through the display manager stacking locks. We did not ask the fragmented distributions or upstream maintainers for permission, nor did we force users to compromise security with intrusive system hacks. Sovereign establishes a dual-insulated, platform-neutral architectural bridge that proves Linux software can be both incredibly secure and completely unbound.

4. The Sovereign Engine and How It Can Turn the Tide and Make Linux a Serious Contender to Windows

One of the final, massive roadblocks preventing mainstream Windows gamers and power users from permanently migrating to Linux is the lack of a standardised, commercial-grade, plug-and-play optimisation and monitoring infrastructure. On Windows, utilities like MSI Afterburner run out of the box with zero friction. On Linux, users are frequently forced to wrestle with terminal compilation steps, fragmented environment variables, and broken window layers. Sovereign OSD closes the platform gap permanently.

By bringing a true "Windows-like, double-click to play" self-contained user experience to the Linux desktop, we eliminate user friction. A mainstream user can boot into Linux, launch Sovereign, and get instant, elite-tier hardware control on the fly. By treating the Linux desktop workspace with the polish, speed, and reliability of a commercial consumer product, Sovereign delivers the exact experience required to challenge Windows and it’s monopoly.

5. Our Security Decisions for Not Releasing the Source Code at This Time

Open-source purism is a defining trait of the Linux community, but it frequently leaves innovative software vulnerable to immediate exploitation and corporate strip-mining. Sovereign OSD will be distributed exclusively as a pre-compiled, secure binary package for these reasons:

• Protection of Proprietary Breakout Architecture: The exact combination of our layout and mouse coordinate data represents a massive engineering breakthrough. Keeping the source closed protects this proprietary bridge from being instantly swiped and\or broken by automated repository bots.
• Ecosystem Integrity: Keeping the core sealed ensures that the primary engine baseline remains consistent and reliable. Users can download the official AppImage with absolute confidence that it has not been tampered within any way, shape, or form.
• Encouraging Clean Extensibility: By keeping the core repository close to our chest while providing an entirely open, robust PluginAPI interface, we channel the community's energy exactly where it belongs: building incredible, innovative, hyper-focused .so plugins!

6. The Sovereign Sandbox Shield

Under a traditional monolithic application design, if a poorly written addon mismanages memory or leaks file descriptors, it crashes the entire host process. Sloppy third-party developers routinely use this as an excuse to hide their bad coding behind the excuse of general application instability.

Because the core engine is completely untethered and shielded by a multi-threaded memory lock, it remains perfectly alive even if an extension collapses. If a third-party plugin stutters, leaks a handle, or hits a segmentation fault, Sovereign will instantly log the specific isolated library path, drop the broken .so file gracefully, and keep rendering the master telemetry layer without dropping a single frame. Bad code is exposed in real time, raising the standards of software quality across the ecosystem.

7. Dropping the Uncoordinated Chaos of Too Many Cooks in the Kitchen

Sovereign completely severs the hand-holding, standard utilities attempt to draw overlays by injecting code directly into a game's active graphics context or by asking the desktop compositor to force a window to stay on top. Under Wayland, both methods break constantly when switching workspaces or entering true fullscreen mode.

Operating as an independent layer Sovereign respects and registers itself directly and calculates its desktop positioning on the fly, allowing the compositor to draw our graphics card metrics on top of any active window space without ever requiring elevated root/sudo system privileges.

8. Beyond the Desktop: Scaling Sovereign from 720p Mobile Silicon to 32K Enterprise Workstations

A truly platform-agnostic engine cannot be hardcoded to specific hardware form factors. The modern Linux environment spans an immense range of form factors, from compact 720p handheld APU gaming systems to massive multi-display enterprise workstations running at extreme spatial scale.

Sovereign handles this through our native Dynamic Scale Evaluation Engine. Instead of rendering text metrics using fragile, fixed pixel grids that instantly shatter or shrink when resolutions shift, Sovereign passes real-time display topology maps straight into our specialised drawing routines. The layout adaptively expands and scales its orientation on the fly. Whether you are tuning a handheld display on a train or monitoring server nodes across a 32K studio display array, Sovereign'sOSDrenders with razor-sharp precision.

When can you see Sovereign in action? Soon. We will be doing a short demonstration video once we have activated and tested a few more features. In the meantime, take a look at the screenshots.

Proton has made Linux gaming so much easier that it's sometimes tempting to treat a native Linux version as unnecessary if the Windows build already works well.

But I think there's still something worth appreciating about developers who ship and maintain proper Linux builds. Native support can mean better integration with the desktop, fewer compatibility layers, and potentially easier troubleshooting, although the actual experience depends on the game and how well the port is maintained.

At the same time, a neglected native port can run worse than the Windows version through Proton, so simply having a Linux build isn't automatically a win.

I'd love to see more developers treat Linux as a platform worth testing and supporting properly, rather than just ticking a box on a store page.

For those who've played games with both native Linux and Proton versions, which games genuinely run better natively, and which ones surprised you by working better through Proton?

🎮 Trying to get Diablo IV running on Linux on my PS5 Slim — need some help!

Hi everyone! 👋

I’ve been experimenting with running Linux on my PS5 Slim using the ps5-linux-loader project by SonicIso. I installed Ubuntu on an external USB 3.0 SSD, and now I’m trying to get Diablo IV running through Steam.

It’s been quite a journey so far! The game either fails to launch or reaches the main menu/character selection screen before freezing completely.

Here’s what I’ve tried and discovered so far:

• Tested different Proton versions, including Proton 10, Experimental, Proton-GE and Proton 11, without finding a working solution.
• Checked Vulkan and graphics support. The system detects the AMD GPU using RADV (GFX1013), with Mesa 26.2.5 and Vulkan 1.4.354.
• Investigated the kernel logs and found some concerning graphics memory errors:
  • Failed to pin framebuffer ... -12
  • [drm] Not enough memory for command submission!

I’m still trying to determine whether the problem is related to GPU memory management, graphics drivers, Proton compatibility, or the Ubuntu setup itself.

Has anyone managed to get Diablo IV running on a PS5 with Linux? Would switching from Ubuntu to CachyOS or another gaming-focused distro actually help, or am I likely to run into the same issue?

I’d really appreciate any advice from people working on PS5 Linux. I’m learning as I go, and hopefully we can figure this out together! 🙏🎮

Following AMD’s announcement of FSR Upscaling 4.1 support for Z2 Extreme handhelds, I tested the new amdxcffx64.dll from the official Adrenalin 26.10.1 package on my Legion Go 2 running SteamOS.

I’ve tested it in The Witcher 3, and I’m attaching photos of my results.

The patch automatically installs the locally supplied DLL into each game’s Wine prefix when needed, avoiding manual replacement for every game.

Installation

Prepared specifically for Proton-CachyOS 11.0-20261014-slr.

1. Close the game and switch to Desktop Mode.
2. Back up your existing protonfixes/upscalers.py.
3. Open your selected Proton-CachyOS installation folder, usually under:\~/.local/share/Steam/compatibilitytools.d/
4. Unzip [proton-cachyos-local-fsr4.zip](http://proton-cachyos-local-fsr4.zip) directly inside the Proton-CachyOS folder containing proton, files, and protonfixes. Allow merging folders and replacing files. Don’t create an extra enclosing folder.
5. Use this Steam launch option:FSR4_UPGRADE=1 %command%

That’s the one-time setup. The patched launcher handles the DLL installation for each game afterward.

The new DLL’s driver-library version is 2.4.0.4370, compared with 2.3.0.2913 in the previous download. These numbers are distinct from the in-game FSR version.

This remains experimental. My gameplay testing covers The Witcher 3; it doesn’t establish which internal model was selected or confirm a performance improvement. Proton updates may overwrite the customization.

Patch/details: [https://drive.google.com/file/d/1UdVj9gQtriNdBl7CxjI95Rx3UeK9RrIh/view?usp=drive_link](https://drive.google.com/file/d/1UdVj9gQtriNdBl7CxjI95Rx3UeK9RrIh/view?usp=drive_link))

Has anyone else tested this on a Z2 Extreme handheld? Please share your game, TDP, resolution, and upscaling settings.

EDIT / UPDATE: We found that my earlier Witcher 3 test was using the regular FSR 4 INT8 model—the overlay showed FSR4-i8.

The newer AMD DLL also contains a smaller “Lite” model designed for handhelds, but simply replacing the DLL didn’t make my setup select it.

We’ve now prepared an experimental patch that tells it to choose Lite automatically. Installation is the same: extract proton-cachyos-auto-lite.zip into your Proton-CachyOS folder, merge/replace the files, and keep FSR4_UPGRADE=1 %command%.

cachyos patch: https://drive.google.com/file/d/1o5RGZ0cQL7NO53si-COmVyclvk7gb7qe/view?usp=drive_link

To confirm Lite is active, the watermark should show FSR4L-i8.

A VR mod for Linux with guided installation, compatibility checks, controller guides and diagnostics for games using Steam, Heroic, Proton and WiVRn. https://github.com/BananaNanners/NAnnersVRhub

Disclaimer: NAnnersVRhub was created with AI assistance for coding, documentation and troubleshooting, alongside hands-on user testing and automated

I'm not sure if this is the right place to put this, but I recently updated to Omarchy 4 from Omarchy 3 and ever since then, the shift key in legacy versions of Minecraft has been sticky, and I can't unshift once I press it (no, I do not have toggle-shift enabled, and the shifting persists through menus and typing in chat). I tested on 1.8.9 and 1.12.2, Lunar Client and Prism Launcher, and I'm still running into the same issue. It works perfectly fine on newer versions (like 1.21.8), which leads me to believe that it might have something to do with the new version of Hyprland and the old LWJGL library that legacy Minecraft versions use for input, but I don't know what exactly is causing this let alone how I would patch it. If it's worth noting, I haven't run into any input-related issues with other games on Omarchy 4, so this is specific to Minecraft.

Also, I have tried using gamescope with Minecraft, and while it does resolve the shifting issue, it causes my frames to drop to like 1FPS when I move my mouse, and I can't lower my mouse's polling rate below 1000Hz.

Has anyone else had this issue? Any info would be much appreciated. Thanks in advance.

So, I downloaded the Mods of Mistria Installer for Linux, but when I double click it doesn't open. Worse, it says there is nothing inside. I did got to open it, but it says there is no mod installed when I have two.

Hey!

I guess this is not a Linux specific issue but more related to hardware.
I got a Steam Controller recently...everything was fine more or less (terrible controller outside of Steam but that's not the issue here), a couple of days ago, I started hearing the Steam UI sounds behind the game when using the controller.
I play with Steam Big Picture since I launch game from my TV so you know what sounds I'm talking about.

Bit annoying but I could at least disable those sounds and keep playing.
But since yesterday, the controller straight up does not work in any game.
I tested with all my other controllers (I have 3 8BitDo ones and an Xbox controller) and I have no issue there. It's only with the Steam Controller.

Tried disabling proton wayland since I know Steam Input doesn't play well with it, to no avail.
Disabled SteamRT3 because I know it's new so I thought maybe there was something not working there but same, it just won't work anymore.

Even tried launching Steam inside of Gamescope to reproduce some kind of Steam Deck envrionment with the -steamdeck and -steamos3 flags but nothing.
Still works with my other controllers but the Steam Controller is completely unresponsive in games.

Anyone else having issues with this controller?
It hasn't been a great experience with this controller overall to say the least but at least it was working but right now it's just a brick.

If anyone is wondering, yes Steam detects the controller and I can call the overlay while in game, but the games themselves don't seem to grab the controller anymore.

I don't even know where to start looking for an issue like that T_T.

I installed Linux Mint a while ago on my MSI laptop, no dualbooting, as I didn't want to have the option to go back and because usually when I get comfortable in one place I usually stay there and don't come back.

Thus far I have liked how nice and simple Mint is, etc. I have gotten a lot of stuff to work like I want it to, but at the same time I have had so many issues with Mint.

My laptop is constantly overheating, games as simple as Deltarune run terribly, I installed MControlCenter and constantly have to turn on the cooler boost to get this thing to not crash because of overheating, streaming on twitch or YouTube is a freaking nightmare and, again, I have to have the fans on all the dang time whenever I'm doing that.

I was able to get around it for the most part, but today just running Deltarune and a PNGTube software I usually use gave me 18 FPS in my entire system and so much fucking frustration. I have installed MControlCenter, I have installed autocpu-freq which only helped a bit, my drivers are up to date and the propretary drivers as usually needed, etc.

These are the specs that neofetch gives

I'm not sure of what else to try. I have heard a lot about Linux having better performance than Windows, but I have also heard about MSI laptops not having the best compatibility with Linux. I'm starting to consider either moving to a different distro (I don't know how much that would even help) or even going back to Windows and instead debloating it as much as possible.

I'm just so f-cking tired, and thus far I have been unable to find any good solutions.

im sure this is asked alot so im sorry

im switching to linux and ive seen strictly good things about it, i dont really care for the privacy but i think its cool. I was looking into linux mint but i also saw people talking about using something called bazzite for games. I do play games quite often but people were talking about not being able to use your browser on bazzite which seems kind of annoying. All opinions wanted

also i want to mention i dont mind to learn things so if its possible for mint to be just as good as bazzite as long as you're willing to learn to make it that way i have no problem doing that

I have a generic "DragonRise" USB controller. evtest confirms it works perfectly on Linux, but Steam shows "No active controller" (and the "Begin Setup" mapping doesn't save), and Faugus Launcher doesn't respond to it at all.

I'm on PikaOS + Niri (Wayland). How can I get this working universally for both Steam games and Faugus? Is there a single tool (like SC Controller or AntiMicroX) that works for both, or do I need a udev rule?

Any help is appreciated!