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" ];

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.

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

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?

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.

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.

It all of the sudden ended up this way.

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

Hi there guys.

I was hoping that you could help with with an issue that I've been experiencing.

Background / History:

I've just gotten around to installing Marvels Spider-Man 1

running on Linux via Steam and Proton.

And (when it's briefly worked) I've been loving it.

However it's now crashing very regularly.

When I first played the game, (I was in a rush) and just clicked play

(without selecting or noting the compatibility layers or version of Proton).

To my surprise the game launched, and I was able to begin the game properly.

However it was crashing regularly (every 5-10-20 mins) for the first couple of days.

Things seemed to settle down, and I was able to play the game for about 1 hr

before it crashed. (Frustrating but better than the original every 5-10 mins).

All these new issues / frequent crashes appear to have started on Monday 2026-10-19

I was playing the game for quite a while

Half way through a base mission (Fisk / King pin) base mission

(3x stealth take downs, then 10x perfect doges)

The game crashed (I'd been playing for about 1hr)

But I had to force close the game from the main steam app.

When I tried to load the game tonight (2026-10-20)

Initially it said that the - Cloud Status was "Out of sync" and would not load

I Had to force close steam from the CLI (HTOP)

Steam auto-reloaded (but the Cloud Sync was now (Up to date / back in sync)

However now the game keeps crashing on multiple different versions of Proton.

Troubleshooting:

1. I've tried multiple different version of Proton

(See details further below)

1. Tried creating a brand new save game / profile =

Got past the intro cinematic, into the very beggining of the game then crashed.

1. I've uploaded the .log file to pastebin

however as it's 2.3 MB in size, I've had to split it down to sub-512 Kb

text files so that it would fit into separate pastes.

Links to the pastebin =

1.

https://pastebin.com/fY6JT60w

2.

https://pastebin.com/PM3w3Ltp

3.

https://pastebin.com/zzc8ARDe

4.

https://pastebin.com/XvyNu7Nw

5.

https://pastebin.com/VGT8AqEq

6.

https://pastebin.com/C8auuDES

Part 6 seems to have some interesting error messages.

1. I originally ran the game via Wayland (the new Linux GFX compositor)

However as this conflicts with Nvidia's Linux GFX drivers

I'm now running X11 as my graphics compositor, as this allows me to set the

GPU fan speed directly.

Various versions of Proton and their results

Proton version: 11.0-2

Issue: Game crashed after a few mins

Proton version: 10.0-4

Issue: crashed after a few mins

Proton version: 9.0-4

Issues: doesn't recognize my game pad

Proton version: 8.0-5

Issue: Game appears to freeze or crash on initial PS "advert" screen

Proton version: 7.0-6

Issue: Wouldn't even load. Steam appeared to crash when it was re-compiling

the Vulkan shaders (got to 50% approx)

Questions:

1. Does anyone know why my game keeps crashing ?

2. How can I stop / prevent these crashes from happening

(either so frequently or at all).

TIA for any help or advice.

Details:

Proton version: Stable 11.0-2

Steam version: Snap

Steam Beta Branch: Stable Client

Steam Version: 1791918634

Steam Client Build Date: Tue, Oct 13, 2026 19:44 UTC +01:00

Steam Web Build Date: Tue, Oct 13, 2026 19:45 UTC +01:00

Steam API Version: SteamClient023

OS: Linux = Kubuntu 26.04.1 LTS (Resolute Raccoon) x86_64

Kernel: Linux 7.0.0-38-generic

Display (DELL P2422H): 1920x1080 in 24", 60 Hz [External] *

Display (DEL4048): 1280x1024 in 19", 60 Hz [External]

DE: KDE Plasma 6.6.6

WM: KWin (X11)

CPU: AMD Ryzen 5 5600X (12) @ 5.28 GHz

GPU: NVIDIA GeForce GTX 1070 [Discrete]

Memory: 3.25 GiB / 31.25 GiB (10%)

I've spent the last hour trying to get it to work, watched several videos and nothing. I want to run seamless co-op and randomizer at the same time, which already using proton makes it EVEN MORE complicated. So I put the contents of both seamless co op and randomizer into the mod folder next to the game exe, and also ran the randomizer. But after setting the launcher .bat as a non-steam game, the play button turns to stop, and CMD box pops up briefly then it just goes back to play again so the game won't launch. It seems getting two mods running simultaneously is really hard, and even harder when trying to use linux.

ERROR: ld.so: object '/home/me/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOA
D cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
pressure-vessel-wrap[649]: E: Child process exited with code 1: bwrap: Can't bind mount /etc on /et
c: mount_setattr() failed at "/newroot/etc": Operation not permitted

Do you think my /etc/ permission might be messed up? It's set as:

drwxr-xr-x 113 root root 12288 Oct 21 21:42 /etc/

I tried completely removing and reinstalling Steam. Ran verify on games. Disabled overlay. Rolled back Arch's update to two weeks ago. Same issue.

I know you're probably sick of hearing about this, but you're gonna want to hear this. Epic themselves have described this as more of a stop-gap measure than their long-term plan. What is their long term plan?

The ideal solution for a cheat-free gaming environment is one where the operating system provides assurances to players that their data remains isolated from both anticheat and game companies while also ensuring that the gameplay cannot be tampered with. There have been many efforts over the years to build solutions like this including virtualization techniques to enable cheat free gaming, but to date they haven't gained traction. We hope they soon will, and we'll work with all willing companies in the industry to make this happen in the future. This includes continuing the Easy Anti-Cheat team's open line of communications with Valve to support Steam Hardware devices to the maximum extent technically possible.

I'll be honest, I have no idea what that actually means. What I do know is that what they just announced last week isn't actually their long-term goal. The section where they describe EAC 2.0 is titled "The Immediate Solution." Long-term, it seems some kind of secure container or something is the goal?

What this MIGHT possibly mean is that in the long run you won't have to have your system locked down to a certain whitelisted kernel.

I admit this is incredibly vague and doesn't actually say anything. So why am I bringing it up? Because even those in favor of the current solution will admit that it's a bit messy. And it seems that, for better or for worse, Epic doesn't want this messy solution to be their long-term solution.

Here's the source link in case somebody wants to fact check me.

This is the trailer of a game I'm releasing on November 10, and in the mean time, its demo is available during Steam Next Fest this week.

The rules are the same as standard chess, the difference is the board, which is made on an irregular grid. It is still made of quads, and each quad still has 1 neighbour per side, but it can have more than 1 quad sharing a corner. It can also have none.

This makes rooks' lines bend and bishop's lines fork.

I'm developing on linux (PopOS), so it should hopefully work just fine on most distributions. When I started its development, I was on X11 and now am on Wayland, so both should be supported (it's using wgpu/webgpu for the graphic api).

And it's written in the language jai, which is still in beta.

• Steam: https://store.steampowered.com/app/2775560/Chess_Twist/?utm_campaign=chess-twist-trailer&utm_medium=short&utm_source=reddit
• Web: https://polyreplay.com/chesstwist

It fails to launch every game i try it with, and the games launch just fine without it.
Problem is, gnome scaling makes games think my monitor is 4k, and they look blurry at native resolution as a result, so i'm trying gamescope to fix it.

This is what i get when i want to launch vkcube :

❯ gamescope -b -W 1920 -H 1080 -r 60 -- vkcube
[gamescope] [Info]  console: gamescope version 3.16.25 (gcc 16.2.1)
No CAP_SYS_NICE, falling back to regular-priority compute and threads.
Performance will be affected.
[gamescope] [Info]  scriptmgr: Loading scripts from: '/usr/share/gamescope/scripts'
[gamescope] [Info]  scriptmgr: Loading scripts from: '/usr/share/gamescope/scripts/00-gamescope'
[gamescope] [Info]  scriptmgr: Loading scripts from: '/usr/share/gamescope/scripts/00-gamescope/common'
[gamescope] [Info]  scriptmgr: Running script file '/usr/share/gamescope/scripts/00-gamescope/common/inspect.lua' (id: 0)
[gamescope] [Info]  scriptmgr: Running script file '/usr/share/gamescope/scripts/00-gamescope/common/modegen.lua' (id: 1)
[gamescope] [Info]  scriptmgr: Running script file '/usr/share/gamescope/scripts/00-gamescope/common/util.lua' (id: 2)
[gamescope] [Info]  scriptmgr: Loading scripts from: '/usr/share/gamescope/scripts/00-gamescope/displays'
[gamescope] [Info]  scriptmgr: Running script file '/usr/share/gamescope/scripts/00-gamescope/displays/asus.rogally.lcd.lua' (id: 3)
[gamescope] [Info]  scriptmgr: Running script file '/usr/share/gamescope/scripts/00-gamescope/displays/deckhd.steamdeck.deckhd-lcd.lua' (id: 4)
[gamescope] [Info]  scriptmgr: Running script file '/usr/share/gamescope/scripts/00-gamescope/displays/gpd.win4.lcd.lua' (id: 5)
[gamescope] [Info]  scriptmgr: Running script file '/usr/share/gamescope/scripts/00-gamescope/displays/lenovo.legiongo.lcd.lua' (id: 6)
[gamescope] [Info]  scriptmgr: Running script file '/usr/share/gamescope/scripts/00-gamescope/displays/lenovo.legiongos.lcd.lua' (id: 7)
[gamescope] [Info]  scriptmgr: Running script file '/usr/share/gamescope/scripts/00-gamescope/displays/onexplayer.f1.oled.lua' (id: 8)
[gamescope] [Info]  scriptmgr: Running script file '/usr/share/gamescope/scripts/00-gamescope/displays/valve.steamdeck.lcd.lua' (id: 9)
[gamescope] [Info]  scriptmgr: Running script file '/usr/share/gamescope/scripts/00-gamescope/displays/valve.steamdeck.oled.lua' (id: 10)
[gamescope] [Info]  scriptmgr: Running script file '/usr/share/gamescope/scripts/00-gamescope/displays/zotac.zone.oled.lua' (id: 11)
[gamescope] [Info]  scriptmgr: Loading scripts from: '/etc/gamescope/scripts'
[gamescope] [Warn]  scriptmgr: Directory '/etc/gamescope/scripts' does not exist
[gamescope] [Info]  scriptmgr: Loading scripts from: '/home/veprovina/.config/gamescope/scripts'
[gamescope] [Warn]  scriptmgr: Directory '/home/veprovina/.config/gamescope/scripts' does not exist
WARNING: radv is not a conformant Vulkan implementation, testing use only.
[gamescope] [Info]  vulkan: selecting physical device 'AMD Radeon RX 9070 (RADV GFX1201)': queue family 1 (general queue family 0)
[gamescope] [Info]  vulkan: physical device supports DRM format modifiers
[gamescope] [Info]  wlserver: [backend/headless/backend.c:60] Creating headless backend
[gamescope] [Info]  xdg_backend: Seat name: seat0
[gamescope] [Info]  xdg_backend: Initted Wayland backend
[gamescope] [Info]  vulkan: supported DRM formats for sampling usage:
[gamescope] [Info]  vulkan:   AR24 (0x34325241)
[gamescope] [Info]  vulkan:   XR24 (0x34325258)
[gamescope] [Info]  vulkan:   AB24 (0x34324241)
[gamescope] [Info]  vulkan:   XB24 (0x34324258)
[gamescope] [Info]  vulkan:   RG16 (0x36314752)
[gamescope] [Info]  vulkan:   NV12 (0x3231564E)
[gamescope] [Info]  vulkan:   AB4H (0x48344241)
[gamescope] [Info]  vulkan:   XB4H (0x48344258)
[gamescope] [Info]  vulkan:   AB48 (0x38344241)
[gamescope] [Info]  vulkan:   XB48 (0x38344258)
[gamescope] [Info]  vulkan:   AB30 (0x30334241)
[gamescope] [Info]  vulkan:   XB30 (0x30334258)
[gamescope] [Info]  vulkan:   AR30 (0x30335241)
[gamescope] [Info]  vulkan:   XR30 (0x30335258)
[gamescope] [Info]  wlserver: Using explicit sync when available
[gamescope] [Info]  wlserver: Running compositor on wayland display 'gamescope-0'
[gamescope] [Info]  wlserver: [backend/headless/backend.c:17] Starting headless backend
[gamescope] [Info]  wlserver: Successfully initialized libei for input emulation!
[gamescope] [Info]  wlserver: [xwayland/server.c:107] Starting Xwayland on :2
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Multiple symbols for level 1/group 1 on key <FK23>
>                   Using F23, ignoring XF86TouchpadOff
> Warning:          Symbol map for key <FK23> redefined
>                   Using last definition for conflicting fields
> Warning:          Symbol map for key <FK24> redefined
>                   Using last definition for conflicting fields
Errors from xkbcomp are not fatal to the X server
[gamescope] [Info]  pipewire: stream state changed: connecting
[gamescope] [Info]  pipewire: stream state changed: paused
[gamescope] [Info]  pipewire: stream available on node ID: 82
[gamescope] [Info]  xdg_backend: HDR INFO
[gamescope] [Info]  xdg_backend:   cv_hdr_enabled: false
[gamescope] [Info]  xdg_backend:   uMaxLum: 80, uRefLum: 80
[gamescope] [Info]  xdg_backend:   bExposeHDRSupport: false
[gamescope] [Info]  edid: Patching res 800x1280 -> 1920x1080
[gamescope] [Info]  vblank: Using timerfd.
[gamescope] [Info]  xdg_backend: Post-Initted Wayland backend
Selected WSI platform: wayland
[Gamescope WSI] Application info:
  pApplicationName: vkcube
  applicationVersion: 0
  pEngineName: vkcube
  engineVersion: 0
  apiVersion: 4194304
[Gamescope WSI] Executable name: vkcube
WARNING: radv is not a conformant Vulkan implementation, testing use only.
[Gamescope WSI] Failed to get Wayland objects
[gamescope] [Info]  launch: Primary child shut down!
(EE) failed to read Wayland events: Broken pipe

Using CachyOS. I was on Fedora til yesterday, distrohopped to try the new gnome thing. I'm going back to Fedora when 45 drops, but if i can't fix games on gnome with gamescope, i'm going back to KDE.

Any ideas?