Adding PROTON_USE_WINED3D=1 fixed it for now, only thing that remains is determining wether it's really a fix or a workaround.

EDIT: Not fixed: It launches, but reduces my fps to under 20 (instead of great, but not measured framerate playing through Lutris before the Steam release) and displays a lot of textures as black.

I'm unable to reproduce this on my end, the game starts fine on both my AMD and Nvidia setups.

@JobeSound Could you try to turn off shader pre-caching in the steam options and see if that changes anything?

@JobeSound Could you try to turn off shader pre-caching in the steam options and see if that changes anything?

It makes the entire map show as black. Only UI elements are still visible.

working fine here as well

It makes the entire map show as black. Only UI elements are still visible.

Thats with dxvk and not wined3d?

With wined3d. Without the wined3d launch option, the error from the main post occurs no matter if I have shader pre-caching on or off. I haven't been able to get the game back to horrible fps but visible map either since i tried disabling shader pre-caching

@JobeSound try clearing the Proton prefix (will erase local state such as settings, replays, maps) and use Proton 7.0-6 to set up a new one.

Using wined3d is not a fix. It's a workaround at best.

I have finally had the time to try all these things (I manually removed all the Proton-related files from my steam library including compatdata) and have had no success.
Bypassing steam completely and installing the game through Ubisoft Connect in Lutris works, however. Could this be because flatpak installs its own version of the Nvidia Driver when installing Lutris?

I have abnormally high memory usage that grows over time in game while playing with the ubisoft overlay enabled. Using htop I can see that winedevice.exe memory usage starts growing (2GBs in like 1hour, when normally it's under 100MB). I can reproduce both on my desktop PC and on my Steam Deck. It doesn't happen while idle in the menu, only when playing any map

Log:
steam-2225070.tar.gz

Replying to https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-1493299894

can you install this game through a custom wine patched with https://gitlab.winehq.org/wine/wine/-/merge_requests/2439 ?

Replying to https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-1493402967

I will try doing that tomorrow, should I just patch proton wine and then build proton? (I also forgot to mention that I'm using proton experimental as of today, 7.0-6 straight up crashes with the overlay enabled)

Replying to https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-1493409541

yeah that should work, if there's some conflicts/issues, I would just copy the logic over

Replying to https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-1493522495

I just built a custom proton version using proton experimental as a base with that patch applied, seems to completely fix the issue (thanks!)

Possible regression? Game doesn't start, just see an shadow outline of the ubisoft connect/uplay window and nothing else happens. Seems to affect others recently too. Arch i7 9700 RX580 Gnome Wayland Proton Experimental and Proton GE 8.3.
steam-2225070.log

Possible regression? Game doesn't start, just see an shadow outline of the ubisoft connect/uplay window and nothing else happens. Seems to affect others recently too. Arch i7 9700 RX580 Gnome Wayland Proton Experimental and Proton GE 8.3. steam-2225070.log

it's working fine for me
try bleeding edge beta of proton experimental

edit: game crashes with RADV GPL on mesa-git, RADV_DEBUG=nogpl disables GPL and avoids the crash while we wait for mesa devs to fix it
edit2: works on mesa stable (no workarounds needed)

it's working fine for me try bleeding edge beta of proton experimental

Good to know... I'm on mesa stable btw. Tried the RADV gpl command anyway but no difference.

bleeding edge beta didn't solve it unfortunately.

steam-2225070.log

it's working fine for me try bleeding edge beta of proton experimental

Good to know... I'm on mesa stable btw. Tried the RADV gpl command anyway but no difference.

bleeding edge beta didn't solve it unfortunately.

steam-2225070.log

Try Deleting the compatdata folder for the game

(Note that this deletes settings, player profiles and custom tracks. Make backups first.)

Thanks, already did that by uninstalling the game and checking the compatdata folder to make sure 2225070 wasn't in there anymore, before switching to the bleeding edge beta. Should have mentioned that before, sorry.

Possible regression? Game doesn't start, just see an shadow outline of the ubisoft connect/uplay window and nothing else happens. Seems to affect others recently too. Arch i7 9700 RX580 Gnome Wayland Proton Experimental and Proton GE 8.3. steam-2225070.log

I suddenly got this today on Fedora on mesa stable.
RADV_DEBUG=nogpl seems to be the only fix

Possible regression? Game doesn't start, just see an shadow outline of the ubisoft connect/uplay window and nothing else happens. Seems to affect others recently too. Arch i7 9700 RX580 Gnome Wayland Proton Experimental and Proton GE 8.3. steam-2225070.log

I suddenly got this today on Fedora on mesa stable.
RADV_DEBUG=nogpl seems to be the only fix

That's because by the time you applied your env variable the devs had uploaded a new proton experimental build with the issue fixed :)

Just remove that variable, it's actively hurting performance

It stopped working for me again about a week ago; launching Trackmania from the Steam Library opens the Ubisoft Connect library instead of the game. Launching the Trackmania (Steam) entry from Ubisoft Connect then switches back to Steam, which then "launches Trackmania" by switching back to Ubisoft Connect. Tried with Bleeding Edge, Experimental, 8-03 and a few GE versions. Log file is from Bleeding Edge:
steam-2225070.zip

It also takes very long to open Ubisoft Connect at all, I'm pretty sure it used to launch the actual game faster. I actually thought at first I had the same issue as described by bradgy because Ubisoft took so long to launch.

@JobeSound it just launched fine for me using Proton Experimental.

Proton-GE prefixes can often be incompatible with regular Proton. Try renaming compdata (rename not delete since it contains settings, replays and more things you probably want to keep).

Issue persists, I've tried reinstalling the game completely as well, no change

On Proton 8, launching the game now nets the launcher crap thingy to not load properly; all I see is a black outline. In the log I can see that it's launching a slew of processes every 2s but it does that seemingly forever.

Getting a bunch of these in the log:

9577.402:0178:01c4:warn:debugstr:OutputDebugStringA "D:\\JenkinsWorkspace\\workspace\\client_build_installer\\client\\shared\\libs\\ceffacade\\mg\\ceffacade\\CefClientHandler.cpp(1051) : CEF render process crashed\n"

Proton Experimental and hotfix work but I get like 15fps at 100% GPU usage on a 6800XT and it's even at 100% in the menus which just isn't right. This wasn't the case a few weeks ago as evidenced by the comment above.

Replying to https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-1730775127

It works perfectly here on proton experimental... (RX 6800)
I will retest today, but this was the case 2 weeks ago i think

Can confirm I am experiencing the same problem on a computer that hasn't had Trackmania installed before. It still runs fine on a computer where I installed it several months ago; the problem seems to be in the install routine.

I tried to launch game after several months, it stopped working for me, after successfully loading ubisoft connect and going into game it shows black fullscreen for a second and then crash. I tested both steam-native and steam-runtime (on Arch Linux, both discrete Nvidia card and integrated Intel), different versions of Proton (8.0-4, Experimental, GE). After crash I have to press "Stop" button in Steam. Entire output:

wine: Using setpriority to control niceness in the [-10,10] range
/bin/sh\0-c\0prime-run /home/flowneee/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=2225070 -- /home/flowneee/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/home/flowneee/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/home/flowneee/.local/share/Steam/steamapps/common/Proton - Experimental'/proton waitforexitandrun  '/home/flowneee/.local/share/Steam/steamapps/common/Trackmania/Trackmania.exe' -upc_steam_free_package_id 62710  -uplay_steam_mode\0
chdir "/home/flowneee/.local/share/Steam/steamapps/common/Trackmania"
ERROR: ld.so: object '/home/flowneee/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/flowneee/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/flowneee/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/flowneee/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/flowneee/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/flowneee/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
fsync: up and running.
wine: Using setpriority to control niceness in the [-10,10] range
Setting breakpad minidump AppID = 2225070
Steam_SetMinidumpSteamID:  Caching Steam ID:  76561198004862369 [API loaded no]

@Flowneee Set PROTON_LOG=1 and paste the log from your home dir into a gist.

https://gist.github.com/Flowneee/40dbded912cb71cae14d68e9570841bf on native runtime and Proton Experimental

i can´t find my log but just updating as im currently facing the same issue.

With Proton 8, neither the game nor Ubisoft Connect terminate when I exit the game. I always have to forcefully stop the game from the Steam interface, and run pkill -f Ubisoft to terminate Ubisoft Connect. If I forget to do this, nothing happens when I try to boot up the game the next time. Very annoying.

Currently, the game is unplayable because Ubisoft Connect fails to start and claims that it isn't installed.
This is after a fresh install, verifying the game files doesn't do anything. Other games run fine etc. etc…
Tried Proton 9, 8, GE 9-5, Experimental.

Replying to https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-2118370685

you just have to manually install ubisoft connect, it works after that

Or remove the compatdata folder for the game usually works for me, instead of having to manually install Ubisoft Connect. Any time you switch to another major version of Proton, Ubisoft Connect breaks and you'll have to repeat the process.

On Sat, 18 May 2024, at 00:06, Etaash Mathamsetty wrote:

Currently, the game is unplayable because Ubisoft Connect fails to start and claims that it isn't installed. This is after a fresh install, verifying the game files doesn't do anything. Other games run fine etc. etc… Tried Proton 9, 8, GE 9-5, Experimental. Error Screenshot https://private-user-images.githubusercontent.com/91573410/331728049-a7a1fc88-46b7-407f-9e49-db6472f7da9a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTU5ODc0NTIsIm5iZiI6MTcxNTk4NzE1MiwicGF0aCI6Ii85MTU3MzQxMC8zMzE3MjgwNDktYTdhMWZjODgtNDZiNy00MDdmLTllNDktZGI2NDcyZjdkYTlhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA1MTclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNTE3VDIzMDU1MlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTlhOTU5ZGUwOWM2ZDEyMmYwOTBiZTVkOGVjNjFmYjMxYTg3Mzk5YjRhM2E5OTE2YWZlZDEzZmQ0MThmMGUyMzkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.RkE41DaDbrvcWav0gOBx4gy3HyJKUCbrm8jfUhq5UrA

you just have to manually install ubisoft connect, it works after that

—
Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-2118474148, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFIPSDTKATG25TNGS5SOULZC2EP5AVCNFSM6AAAAAAUUMKPTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYGQ3TIMJUHA.
You are receiving this because you commented.Message ID: @.***>

I can confirm that the latest Proton Experimental fixes the Ubisoft Connect not starting issue and the game now works, although it didn't when I initially updated the day the changelog came out.

For anyone else annoyed that the game remains in "Playing..." state after quitting, it's because of the Ubisoft Connect launcher keeps running in background and is impossible to quit if you're running GNOME, as it does not appear in the tray. In that case, you might want to try the following launch command:

bash -c 'while ! pgrep -x MainThread; do sleep 1; done; while pgrep -x MainThread; do sleep 1; done; sleep 1; pkill -f upc.exe; pkill -f UplayWebCore.exe' & %command%

This incantation waits until the Trackmania process starts (to give time to Ubisoft Connect to do its nonsense at startup), and once the game starts, it waits until you quit to finally kill the launcher.

In general, many issues in starting the game are due to the fact that the launcher from a previous start is still running in background, or somehow gets stuck. Killing the upc.exe process is the only solution when that happens.

Reporting breakage after switching from Radeon 5700XT to Intel Arc B580, Ubisoft Connect is fine but when the Trackmania window spawns, it's black for a couple frames and then terminates.
steam-2225070.log
System info: https://gist.github.com/widlarizer/5ee8d07b2b264adfddc89b7164c1683f
Mesa 24.3.3 Linux 6.12.8 Proton Experimental

Hello, im on steam deck OLED (stable). Trackmania worked great for like ever. Last time I played was on the 8th of January. (afaik, there was no Ubisoft connect or Trackmania update since then)
Now I start, ubisoft connect turns on and when the game should start, it black screens and turns off, I enabled proton logs.
After enabling them, the game didn't turn off, but I only had blackscreen, I forced quit the game.
Proton log file is over 1GB big, after maybe 1 minute of blackscreen "running".

This error is repeated over and over and over again.

1228.141:0430:0434:warn:seh:dwarf_virtual_unwind backtrace: 0x7f95ac44b38a: Z:\home\deck.local\share\Steam\steamapps\common\Trackmania\Trackmania.exe + 0x138a (_start + 0x2a).
1228.141:0430:0434:trace:unwind:execute_cfa_instructions 7f95ac44b360: DW_CFA_def_cfa %rsp, 8
1228.141:0430:0434:trace:unwind:execute_cfa_instructions 7f95ac44b360: DW_CFA_offset %rip, -8
1228.141:0430:0434:trace:unwind:execute_cfa_instructions 7f95ac44b360: DW_CFA_undefined %rip
1228.141:0430:0434:trace:unwind:dwarf_virtual_unwind fde 0x7f95ac44c140 len 14 personality (nil) lsda (nil) code 7f95ac44b360-7f95ac44b38b
1228.141:0430:0434:trace:unwind:dwarf_virtual_unwind next function rip=00007f95ac44b38a
1228.141:0430:0434:trace:unwind:dwarf_virtual_unwind rax=0000555558224cbc rbx=0000000000000000 rcx=000000000000006f rdx=0000555558224940
1228.141:0430:0434:trace:unwind:dwarf_virtual_unwind rsi=0000000000000038 rdi=0000555558224940 rbp=0000000000000000 rsp=00007ffd52417ce0
1228.141:0430:0434:trace:unwind:dwarf_virtual_unwind r8=0000000000000000 r9=0000000000000001 r10=0000000000000003 r11=0000000000000001
1228.141:0430:0434:trace:unwind:dwarf_virtual_unwind r12=00007f95ac44b360 r13=00007ffd51d37430 r14=0000000000000000 r15=0000000000000000
1228.141:0430:0434:trace:unwind:dwarf_virtual_unwind function 7f95ac44b38a base 0x7f95ac44b360 cie 0x7f95ac44c128 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip

Edit: I tested so much, even reinstalled everything and new prefix etc.

The only thing that got it working was switching to steamOS beta. (in the OLED model, 2 other people in discord also had this issue on the OLED, steamOS beta worked there too, one guy had an LCD and there the game works with stable)

@1basti1 I couldn't reproduce your issue. I tried on steamos main and stable with default proton and it worked fine after multiple attempts and prefix wipes. If you go back to steamos stable do you see the issue again?

@1basti1 I couldn't reproduce your issue. I tried on steamos main and stable with default proton and it worked fine after multiple attempts and prefix wipes. If you go back to steamos stable do you see the issue again?

Hey sorry, I forgot to edit my comment.
For whatever reason one day later I switched back to stable and the game was working again.

Told that to 2 other people in discord and it worked for them too. I really don't know what happend (but I would love to know), but it's working again.

Reporting breakage after switching from Radeon 5700XT to Intel Arc B580, Ubisoft Connect is fine but when the Trackmania window spawns, it's black for a couple frames and then terminates.

I have retried this after software upgrades (still mesa 24.3.3 but linux 6.13.0) and the issue is now different. The game launches but uses my integrated AMD graphics by default. I select the Intel Arc B580 (shown as G21) as the display device and restart the game, I get a popup saying that the display device doesn't have any outputs, and if I want to proceed anyway. If I do, the game doesn't launch.

Or remove the compatdata folder for the game usually works for me, instead of having to manually install Ubisoft Connect. Any time you switch to another major version of Proton, Ubisoft Connect breaks and you'll have to repeat the process.
…

I closed steam, deleted .var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/compatdata/2225070, and relaunched steam. I was happy to see "Running install script (Ubisoft Connect Installer)" next to the "PLAY" button, but it still didn't work. The game does not lauch, and the blue "CANCEL" button turns back the green "PLAY" button.

I can confirm that the latest Proton Experimental fixes the Ubisoft Connect not starting issue and the game now works, although it didn't when I initially updated the day the changelog came out.

I also tried it with the current experimental version, and it didn't work. (I thought this comment was from today, but its actually from exactly 1 year ago. Amazing.)

Replying to https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-2905937488

I have the same issue. I tried to use other versions of proton and remove the compdata directory, but it still wont launch. It wont even show "Running install script".

Getting the same error. Using Steam Flatpak on OpenSUSE Tumbleweed. I tried multiple Proton versions:

• Default
• Experimental
• 10.0.1
• 9.0-4
• GE-Proton9-27
• GE-Proton10-3

Every version has the same problem of not installing thus not detecting Ubisoft Connect when launching. Even installing UC via protontricks does not do the trick this time.

Is working fine for me now.

For anyone still having issues you can try this fix (i am using Proton 9.0-4) :

Install the "Steamworks Common Redistributables" from the Steam Store (it's like 0KB smh)

Restart Steam as a whole, Trackmania should update.

After that Trackmania was running the Installer for Ubisoft Connect fine.

I have another issue with the game. After bringing up the ubisoft overlay and alt tabbing, my pad input in game doesn't work until I open and close the ubisoft overlay again.

In the past this actually required closing the overlay in a specific way but it seems that at least that works now (so for example on the steam deck where you don't alt tab this isn't an issue).

On windows it works properly.

Unfortunately the game requires the ubisoft overlay to join matchmaking teams (well there's a plugin but that doesn't work with console players so it's still a good thing to have working)

@AlchemiistCreative things like game log being empty, and things like Gamestarter must be initialized before game can be launched. are actually red herrings, as I get the same with the game starting normally. As you've gone through so many proton versions, it'd be best to wipe the prefix before grabbing a new log with proton experimental.

@simifor I've also tried removing the prefix almost before each attempt.
Another lead: the Proton log shows a stack overflow (STATUS_STACK_OVERFLOW / c00000fd). I also tried with taskset -c 0-15 %command% to limit visible cores to 16 but the stack overflow persists at the same address.
Additionally, when the game tries to launch, the log shows:
fixme:process:CreateProcessInternalW Unsupported attribute 0x20007.

New log attached.

steam-2225070-new.tar.gz

File located below
/home/charles/.steam/root/steamapps/compatdata/2225070/pfx/drive_c/Program Files (x86)/Ubisoft/Ubisoft Game Launcher/logs/launcher_log.txt

this seems to be a problem with the application not registering in proton and not updating itself.

launcher_log.txt

Trackmania has a URL Protocol handler for launching maps and joining servers trackmania://, but I cant call it successfully on a running instance of the game. If I attempt something with e.g. protontricks after the game has started normally, the URL handler does get called, but not on the running instance of the game; instead, it starts up a new instance of the game. I believe this is something to do with a pressure vessel, or some part of the steam Linux runtime stack, and I'm not sure what the workaround would be.

My Ubisoft connect launches, but right when trackmania should launch in like 90% of all tries steam restarts for me on the steam deck.
I don't know what is happening.

Sometimes it launches fine though. I tried several proton versions..

To come back to my issue:

On latest Stable, launching Trackmania soft-reboots the Deck. Gamescope log shows a Broken pipe and drm: drmModeRmFB failed: Bad file descriptor right at the crash point.

I have this problem on other Ubisoft games too.
One user on e Reddit has the same: https://www.reddit.com/r/SteamDeck/s/u85h1mwZQa (although not trackmania)
I don't know what to do...
Seems like gamescope crashes..

Longer log:

Aug 08 12:36:58 steamdeck gamescope-session[1584]: [gamescope] [Info]  pipewire: stream state changed: paused
Aug 08 12:37:02 steamdeck gamescope-session[1584]: [gamescope] [Warn]  xwm: got the same buffer committed twice, ignoring.
Aug 08 12:37:02 steamdeck steam[13035]: [Gamescope WSI] Application info:
Aug 08 12:37:02 steamdeck steam[13035]: [Gamescope WSI] Executable name: steamsysinfo
Aug 08 12:37:03 steamdeck gamescope-session[1584]: [gamescope] [Info]  binding: (VolumeUp) -> Adding new trigger [XF86AudioRaiseVolume].
Aug 08 12:37:03 steamdeck gamescope-session[1584]: [gamescope] [Info]  binding: (VolumeDown) -> Adding new trigger [XF86AudioLowerVolume].
Aug 08 12:37:04 steamdeck steam[13035]: [Gamescope WSI] Application info:
Aug 08 12:37:04 steamdeck steam[13035]: [Gamescope WSI] Executable name: vulkandriverquery
Aug 08 12:37:04 steamdeck steam[13035]: [Gamescope WSI] Forcing on VK_EXT_swapchain_maintenance1.
Aug 08 12:37:05 steamdeck steam[13035]: [Gamescope WSI] Application info:
Aug 08 12:37:05 steamdeck steam[13035]: [Gamescope WSI] Executable name: vulkandriverquery
Aug 08 12:37:05 steamdeck steam[13035]: [Gamescope WSI] Forcing on VK_EXT_swapchain_maintenance1.
Aug 08 12:37:07 steamdeck gamescope-session[1584]: [gamescope] [Info]  binding: (GRMarker) -> Adding new trigger [F12 + Control_L].
Aug 08 12:37:07 steamdeck gamescope-session[1584]: [gamescope] [Info]  binding: (GRBackgroundRecordingToggle) -> Adding new trigger [F11 + Control_L].
Aug 08 12:37:07 steamdeck gamescope-session[1584]: [gamescope] [Info]  binding: (GuideKeyboardHotkey) -> Adding new trigger [Tab + Shift_L].
Aug 08 12:37:07 steamdeck gamescope-session[1584]: [gamescope] [Info]  binding: (QAMKeyboardHotkey) -> Adding new trigger [Tab + Control_L + Shift_L].
Aug 08 12:37:07 steamdeck gamescope-session[1584]: radv: Updated the per-vertex VRS rate to '0'.
Aug 08 12:37:10 steamdeck steam[13035]: CDesktopCapturePipeWire: setting stream node path: gamescope
Aug 08 12:37:18 steamdeck systemd[1369]: Stopped target Gamescope Session.
Aug 08 12:37:18 steamdeck systemd[1369]: Stopping Xbindkeys for Gamescope session...
Aug 08 12:37:18 steamdeck systemd[1369]: Stopping Portal service (gamescope implementation)...
Aug 08 12:37:18 steamdeck deck[14348]: Gamescope Session Ended - Performing Final Cleanup
Aug 08 12:37:18 steamdeck systemd[1369]: Stopped Xbindkeys for Gamescope session.
Aug 08 12:37:18 steamdeck systemd[1369]: gamescope-mangoapp.service: Consumed 3.043s CPU time, 25.5M memory peak.
Aug 08 12:37:18 steamdeck systemd[1369]: Stopped Portal service (gamescope implementation).
Aug 08 12:37:22 steamdeck systemd[1369]: Stopping Gamescope Session...
Aug 08 12:37:22 steamdeck gamescope-session[1584]: [gamescope] [Info]  wlserver: [xwayland/server.c:217] Restarting Xwayland
Aug 08 12:37:22 steamdeck gamescope-session[1584]: [gamescope] [Info]  wlserver: [xwayland/server.c:217] Restarting Xwayland
Aug 08 12:37:22 steamdeck gamescope-session[14510]: [gamescope] [Info]  wlserver: [xwayland/server.c:107] Starting Xwayland on :1
Aug 08 12:37:22 steamdeck gamescope-session[14512]: [gamescope] [Info]  wlserver: [xwayland/server.c:107] Starting Xwayland on :0
Aug 08 12:37:22 steamdeck gamescope-session[1584]:  EIS: 12:37:22 | WARN | Client error: socket disconnected
Aug 08 12:37:22 steamdeck gamescope-session[14534]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Aug 08 12:37:22 steamdeck gamescope-session[14534]: > Warning:          Could not resolve keysym XF86RefreshRateToggle
Aug 08 12:37:22 steamdeck gamescope-session[14534]: > Warning:          Could not resolve keysym XF86Accessibility
Aug 08 12:37:22 steamdeck gamescope-session[14534]: > Warning:          Could not resolve keysym XF86DoNotDisturb
Aug 08 12:37:22 steamdeck gamescope-session[14533]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Aug 08 12:37:22 steamdeck gamescope-session[14533]: > Warning:          Could not resolve keysym XF86RefreshRateToggle
Aug 08 12:37:22 steamdeck gamescope-session[14533]: > Warning:          Could not resolve keysym XF86Accessibility
Aug 08 12:37:22 steamdeck gamescope-session[14533]: > Warning:          Could not resolve keysym XF86DoNotDisturb
Aug 08 12:37:22 steamdeck gamescope-session[14534]: Errors from xkbcomp are not fatal to the X server
Aug 08 12:37:22 steamdeck gamescope-session[14533]: Errors from xkbcomp are not fatal to the X server
Aug 08 12:37:22 steamdeck gamescope-session[14535]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Aug 08 12:37:22 steamdeck gamescope-session[14536]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Aug 08 12:37:22 steamdeck gamescope-session[14535]: >
Aug 08 12:37:22 steamdeck gamescope-session[14536]: >
Aug 08 12:37:22 steamdeck gamescope-session[14535]: Warning:
Aug 08 12:37:22 steamdeck gamescope-session[14536]: Warning:          Unsupported maximum keycode 708, clipping.
Aug 08 12:37:22 steamdeck gamescope-session[14535]: Unsupported maximum keycode 708, clipping.
Aug 08 12:37:22 steamdeck gamescope-session[14536]: >
Aug 08 12:37:22 steamdeck gamescope-session[14535]: >
Aug 08 12:37:22 steamdeck gamescope-session[14536]:                   
Aug 08 12:37:22 steamdeck gamescope-session[14535]:                   
Aug 08 12:37:22 steamdeck gamescope-session[14536]: X11 cannot support keycodes above 255.
Aug 08 12:37:22 steamdeck gamescope-session[14535]: X11 cannot support keycodes above 255.
Aug 08 12:37:22 steamdeck gamescope-session[14536]: > Warning:          Could not resolve keysym XF86RefreshRateToggle
Aug 08 12:37:22 steamdeck gamescope-session[14535]: > Warning:          Could not resolve keysym XF86RefreshRateToggle
Aug 08 12:37:22 steamdeck gamescope-session[14536]: > Warning:          Could not resolve keysym XF86Accessibility
Aug 08 12:37:22 steamdeck gamescope-session[14536]: > Warning:          Could not resolve keysym XF86DoNotDisturb
Aug 08 12:37:22 steamdeck gamescope-session[14535]: > Warning:          Could not resolve keysym XF86Accessibility
Aug 08 12:37:22 steamdeck gamescope-session[14535]: > Warning:          Could not resolve keysym XF86DoNotDisturb
Aug 08 12:37:22 steamdeck gamescope-session[14536]: Errors from xkbcomp are not fatal to the X server
Aug 08 12:37:22 steamdeck gamescope-session[14535]: Errors from xkbcomp are not fatal to the X server
Aug 08 12:37:22 steamdeck gamescope-session[14512]: (EE) failed to read Wayland events: Broken pipe
Aug 08 12:37:22 steamdeck gamescope-session[14510]: (EE) failed to read Wayland events: Broken pipe
Aug 08 12:37:22 steamdeck gamescope-session[1584]: [gamescope] [Error] drm: drmModeRmFB failed: Bad file descriptor
Aug 08 12:37:22 steamdeck gamescope-session[1584]: [gamescope] [Error] drm: drmModeRmFB failed: Bad file descriptor
Aug 08 12:37:22 steamdeck gamescope-session[1584]: [gamescope] [Error] drm: drmModeRmFB failed: Bad file descriptor
Aug 08 12:37:22 steamdeck gamescope-session[1584]: [gamescope] [Error] drm: drmModeRmFB failed: Bad file descriptor
Aug 08 12:37:24 steamdeck systemd[1369]: Stopped Gamescope Session.
Aug 08 12:37:24 steamdeck systemd[1369]: gamescope-session.service: Consumed 46.432s CPU time, 333.4M memory peak.
Aug 08 12:37:24 steamdeck deck[14556]: Gamescope Session Ended - Cleanup Complete

Edit: Wait, looking closer at the logs, the Gamescope session is already stopped by systemd at 12:37:18—four seconds BEFORE the drmModeRmFB Bad file descriptor error happens at 12:37:22. The crash actually triggers right after CDesktopCapturePipeWire initializes at 12:37:10.

Also this right when the error happens, maybe it helps, I don't know (also when I put this in code format, there's much missing, this why it's like this, sorry):

Aug 08 12:37:18 steamdeck steam[13035]: i386-linux-gnu-capsule-capture-libs: warning: Dependencies of /usr/lib32/libMangoHud.so not found, ignoring: Missing dependencies: Could not find "libxkbcommon.so.0" in LD_LIBRARY_PATH "/home/deck/.local/share/Steam/ubuntu12_32:/home/deck/.local/share/Steam/ubuntu12_32/panorama:/usr/lib32:/usr/lib/perf:/usr/lib", ld.so.cache, DT_RUNPATH or fallback /lib/i386-linux-gnu:/usr/lib/i386-linux-gnu:/usr/i686-pc-linux-gnu/lib:/lib32:/usr/lib32:/lib:/usr/lib Aug 08 12:37:19 steamdeck steam[13035]: fsync: up and running. Aug 08 12:37:19 steamdeck steam[13035]: wine: RLIMIT_NICE is <= 20, unable to use setpriority safely Aug 08 12:37:22 steamdeck steam[13035]: [2026-08-08 12:37:22] Shutdown Aug 08 12:37:30 steamdeck steam[15169]: steam.sh[15097]: Running Steam on steamos rolling 64-bit Aug 08 12:37:30 steamdeck steam[15169]: steam.sh[15097]: STEAM_RUNTIME is enabled automatically Aug 08 12:37:30 steamdeck steam[15169]: setup.sh[15307]: Steam runtime environment up-to-date! Aug 08 12:37:30 steamdeck steam[15169]: steam.sh[15097]: Log already open

Im just an end-user but looking closely at the logs, I think game recording might be the culprit. Because I now turned it off and it starts fine everytime. (tried now 5 boots after another, no issues anymore)

So probably a steam deck / steamos issue...?

Edit: Turning off game recording also helped the guy on reddit for his Ubisoft games:
https://www.reddit.com/r/SteamDeck/s/n9dg0HiNpG

This finding should probably posted somewhere else, but I don't know where. Hopefully someone from valve sees this and can do something about it.

I use a Steam Deck OLED with stable Steam and stable SteamOS.