GloriousEggroll ships GE-Proton 11-12, keeping Windows games playable on Linux
The volunteer-run Proton fork piles a massive stack of game fixes on top of Valve's Wine 11 and NTSync support. Valve didn't write any of it. It arguably does the most work of the lot.
GloriousEggroll published GE-Proton 11-12 today. It's a point-release, not a major bump, so the Wine major version stays put. What changed is how much sits on top of it. The community fork isn't made by Valve, but it's arguably doing the heavy lifting.
Running Windows games on Linux still leans on a compatibility layer called Wine, which in turn leans hard on GE-Proton. GloriousEggroll is Thomas Crider, a software maintenance engineer at Red Hat who also leads Nobara Linux. He runs the fork on his own time, tracks Valve's bleeding-edge Proton Experimental build, and stacks on patches that Valve hasn't merged upstream. It's often the only thing between a gamer and a title that simply won't launch. Updates roll out every one or two weeks, so 11-12 landed about three weeks after 11-11.
Why 11-12 is the big one this cycle
The whole 11 series matters because it rides Valve's Proton 11, built on Wine 11 and bringing NTSync support. That's the synchronization code that moves out of Wine's userspace emulation and into the Linux kernel itself, available from kernel 6.14 onward. It trims threading overhead and smooths out frame pacing. NTSync is already the default on current Steam Decks, and GE-Proton follows the same logic, turning it on wherever the host kernel can cope.
So the actual architectural win comes from Valve. GE-Proton's real job is the pile of game-specific patches layered on top. It touches core Wine internals, graphics translation, controllers, Wayland and windowing, video playback, HDR rendering, memory management, and dozens of per-game tweaks.
It's a community effort, not a solo one. The changelog names the volunteers who wrote the actual code: greg2010 on the EVE Online memory-growth fix, aderumier on a batch of arcade and Konami movie patches, and jegglest on Helldivers 2's leaks. That game was bleeding roughly 34 GiB of address space and 360 MiB of RAM every hour. It's cleaned up now.
There's a detail in here worth a mention too. DXVK, D7VK, and VKD3D-Proton built from the GE-patched tree now flag themselves with -GE-Proton(dirty) in their version string. Upstream developers can instantly tell from a bug report whether they're debugging stock Valve Proton or a modified GE build. Triage gets messy fast once you can't tell what you're looking at, so it's a quiet win. You'll also spot a set of component bumps: DXVK at v3.1.1-174, VKD3D-Proton at v3.1, DXVK-NVAPI at v0.9.3, and FEX-Emulator at FEX-2610-116 for the Steam Deck's ARM chips.
Should you actually install it?
The community's straight answer is: stay on Valve's official Proton unless a specific game needs something only GE-Proton provides. Per-game overrides are the move, since a fix that rescues one title can quietly regress another. It's arguably competing with official Proton, in a sense, acting as the innovation lab where fixes get stress-tested before Valve considers them upstream.
If you want to try it, the supported path is ProtonUp-Qt, a free GUI available as a Flatpak, an AppImage, or from the AUR. On the Deck you'd switch to Desktop Mode, open ProtonUp-Qt, click Add version, choose GE-Proton, and install the 400 to 500 MB build. Then restart Steam and force the tool through a game's Properties => Compatibility menu. There's no auto-update, so you run ProtonUp-Qt again when a newer version shows up. Older builds stay on disk, which means you can roll back when a release bites you.
Head here to the GitHub repo for GE-Proton 11-12.
