Steam crashes after upgrading NVIDIA driver to 545.29.06

I ran apt upgrade on my laptop today after not using it for a couple of weeks, the main thing was upgrade of NVIDIA driver to 545.29.06, but there was also some change on one of the steam-lib packages (I’m using the Steam deb version, not flatpak). Ever since upgrading, Steam crashes on start.

I tried searching for recently reported issues with the Steam Linux client but can’t find anything. Is this a known issue? Any suggestions on what I can check/do?

=-=-=

Here’s the segfault from syslog, I have a bunch of core files but don’t know if I can get anything useful from them.

Dec  6 17:13:30 computer steam.desktop[5200]: steam.sh[5200]: Running Steam on pop 22.04 64-bit
Dec  6 17:13:30 computer steam.desktop[5200]: steam.sh[5200]: STEAM_RUNTIME is enabled automatically
Dec  6 17:13:30 computer steam.desktop[5321]: setup.sh[5321]: Steam runtime environment up-to-date!
Dec  6 17:13:31 computer steam.desktop[5200]: steam.sh[5200]: Steam client's requirements are satisfied
Dec  6 17:13:31 computer steam.desktop[5392]: 12/06 17:13:31 Init: Installing breakpad exception handler for appid(steam)/version(1701289036)/tid(5392)
Dec  6 17:13:33 computer steam.desktop[5392]: /home/user/.themes/Sweet-Dark-v40/gtk-2.0/main.rc:727: error: unexpected identifier 'direction', expected character '}'
Dec  6 17:13:33 computer steam.desktop[5392]: /home/user/.themes/Sweet-Dark-v40/gtk-2.0/apps/chrome.rc:50: error: invalid string constant "button", expected valid string constant
Dec  6 17:13:33 computer steam.desktop[5392]: /home/user/.themes/Sweet-Dark-v40/gtk-2.0/apps/xfce.rc:79: error: invalid string constant "entry", expected valid string constant
Dec  6 17:13:33 computer steam.desktop[5404]: crash_20231206171333_5.dmp[5404]: Uploading dump (out-of-process)
Dec  6 17:13:33 computer steam.desktop[5404]: /tmp/dumps/crash_20231206171333_5.dmp
Dec  6 17:13:33 computer crash_20231206171333_5.dmp[5404]: Uploading dump (out-of-process)#012/tmp/dumps/crash_20231206171333_5.dmp
Dec  6 17:13:33 computer kernel: [   72.142532] show_signal_msg: 19 callbacks suppressed
Dec  6 17:13:33 computer kernel: [   72.142534] steam[5392]: segfault at 0 ip 00000000f7ab5045 sp 00000000fffb3e8c error 4 in libc.so.6[f7a20000+182000] likely on CPU 4 (core 4, socket 0)
Dec  6 17:13:33 computer kernel: [   72.142544] Code: 40 38 ca 0f 84 4d 01 00 00 80 f9 00 0f 84 71 01 00 00 40 4f 75 14 8a 08 38 ca 0f 84 36 01 00 00 80 f9 00 0f 84 5a 01 00 00 40 &lt;8b> 08 bd ff fe fe fe bf ff fe fe fe 01 cd 31 cd 01 cf 8d 40 04 0f
Dec  6 17:13:33 computer steam.desktop[5200]: /home/user/.local/share/Steam/steam.sh: line 798:  5392 Segmentation fault      (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@"
Dec  6 17:13:35 computer steam.desktop[5404]: crash_20231206171333_5.dmp[5404]: Finished uploading minidump (out-of-process): success = yes
Dec  6 17:13:35 computer steam.desktop[5404]: crash_20231206171333_5.dmp[5404]: response: CrashID=bp-11a3ce92-de87-49ca-8b7c-7e1622231206
Dec  6 17:13:35 computer steam.desktop[5404]: crash_20231206171333_5.dmp[5404]: file ''/tmp/dumps/crash_20231206171333_5.dmp'', upload yes: ''CrashID=bp-11a3ce92-de87-49ca-8b7c-7e1622231206''
Dec  6 17:13:35 computer crash_20231206171333_5.dmp[5404]: Finished uploading minidump (out-of-process): success = yes
Dec  6 17:13:35 computer crash_20231206171333_5.dmp[5404]: response: CrashID=bp-11a3ce92-de87-49ca-8b7c-7e1622231206
Dec  6 17:13:35 computer crash_20231206171333_5.dmp[5404]: file ''/tmp/dumps/crash_20231206171333_5.dmp'', upload yes: ''CrashID=bp-11a3ce92-de87-49ca-8b7c-7e1622231206''
Dec  6 17:13:35 computer systemd[3855]: app-gnome-steam-5200.scope: Consumed 1.187s CPU time.

Community Rules

Follow the Code of Conduct

All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct

Be helpful

Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like “RTM” or links to LMGTFY. Linking to direct sources that answer the asker’s question is fine, but it’s advised to provide some explanation as to how you got to that source.

Critique should be constructive

We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic “It’s bad” or other simple negative comments don’t help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.

This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.

Don’t post malicious “advice”

It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.

Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn’t serious, but a new user might not.

No personal attacks

Posts making a personal attack on any user will not be tolerated.

No hate speech

Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.