You are not logged in.
Hi folks,
Today, Proton just randomly stopped working properly. Every single game takes a very long time to start up, and then when eventually it loads there's no audio.
Funnily enough, even after I close the game all the other apps afterwards seem a bit sluggish, audio is completely out still (no audio interfaces in the pulseaudio widget dropdown list), and after I try to shutdown/restart my PC it gets stuck on the "journal recover" "/dev/nvmexxxx" blocks message and I have to do a hard reset to get it running (this only happens after I try to run anything through proton, if I don't do that on that session then everything shuts down properly).
I am not on an NTFS partition, I use ext4.
Native linux games don't cause this problem.
here's the proton logs from a game (it's on proton-GE, but same exact issue happens on standard proton)
https://pastebin.com/d7YwzxGA
I run Proton directly through steam, but same problem happens if I try running it on a game through the terminal.
any ideas? I'm at my wits end, and genuinely have no idea how to even troubleshoot this further. Didn't change anything about my setup either recently.
Last edited by Endali (2024-09-10 12:58:57)
Offline
Lots of pulse channel map errors. Are you using wireplumber/pipewire-pulse? The latest release did some changes in the profile loading logic that might bite you here. What output do you get from
sudo fuser -v /dev/snd/*
aplay -lL
pacman -Qs 'pulse|wire'
pactl list cards
pactl list sinksOffline
Lots of pulse channel map errors. Are you using wireplumber/pipewire-pulse? The latest release did some changes in the profile loading logic that might bite you here.
I do, and you are right! Downgrading wireplumber to the previous version (0.5.5) solved the issue, now everything works perfectly ![]()
Thank you so much!! <3
Offline
Probably should report a bug, or do you use any custom config here? Maybe some things logically broke with the profile change. Something that's also often a case is that wireplumber inproperly invalidates it's cache on updates, in which case you might want to check whether removing ~/.local/state/wireplumber helps.
Offline
Nope, I don't use any custom config - when I have a moment though I'll try removing the cache with the latest wireplumber installed and see if it helps anyhow.
Offline
Yup, thank you again!
Clearing cache solved it, and funnily enough it also solved another issue with my audio interface that I just learned to live with (it would merge my Behringer UMC204HD's inputs/outputs into single channels), so my cache must have been really screwed up. ![]()
Offline
That's really up to the wireplumber devs, they don't really seem to have a good mechanism for reinstating/invalidating the cache on incompatible changes...
In any case please mark as [SOLVED] by editing the title in your first post. (might have to shorten it a bit)
Offline