All games fail to launch after recent driver update :: Steam for Linux General Discussions

Steam for Linux

All Discussions Artwork Videos News Guides

Steam for Linux > General Discussions > Topic Details

duncte123

4 Aug @ 1:58am

All games fail to launch after recent driver update

Did not install steam via flatpak, running on ubuntu 24.04 with a 2080TI. Everything worked fine until a recent driver update. I managed to get the following logs from protontricks:

protontricks (WARNING): Steam library folder /media/duncte123/games/SteamLibrary not found. Protontricks might not have access to the directory. protontricks (WARNING): Current Steam Runtime not recognized by Protontricks. x86_64-linux-gnu-capsule-capture-libs: warning: we are assuming "_el_fn_sh_complete" to be private, but it's just a guess x86_64-linux-gnu-capsule-capture-libs: warning: Dependencies of libnvidia-pkcs11.so.535.183.01 not found, ignoring: Missing dependencies: Could not find "libcrypto.so.1.1" in LD_LIBRARY_PATH (unset), ld.so.cache, DT_RUNPATH or fallback /lib:/usr/lib i386-linux-gnu-capsule-capture-libs: warning: we are assuming "_el_fn_sh_complete" to be private, but it's just a guess pressure-vessel-wrap[6766]: N: Not replacing "/etc/vulkan/explicit_layer.d" with tmpfs: Path "/etc" is reserved by the container framework pressure-vessel-wrap[6766]: N: Not replacing "/etc/vulkan/implicit_layer.d" with tmpfs: Path "/etc" is reserved by the container framework pressure-vessel-wrap[6766]: W: Not sharing path --filesystem="/etc" with container because "/etc" is reserved by the container framework pressure-vessel-wrap[6766]: W: Not sharing path --filesystem="/lib32" with container because "/lib32" is reserved by the container framework pressure-vessel-wrap[6766]: N: Not sharing "/libx32" with sandbox: Path "/usr" is reserved by the container framework pressure-vessel-wrap[6766]: W: Not sharing path --filesystem="/sbin" with container because "/sbin" is reserved by the container framework ------------------------------------------------------ warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug. ------------------------------------------------------ ------------------------------------------------------ warning: You apppear to be using Wine's new wow64 mode. Note that this is EXPERIMENTAL and not yet fully supported. If reporting an issue, be sure to mention this. ------------------------------------------------------ Using winetricks 20240105 - sha256sum: 8f28985b06e9e04b5268e2aef3429b2a0f6abd4fd12c4a30472dfe66355128fa with wine-9.0 and WINEARCH=win64 wine: using kernel write watches, use_kernel_writewatch 1. fsync: up and running. 0024:fixme:ntdll:create_logical_proc_info Improve CPU info reporting: system supports 36 logical cores, but only 32 supported! 0024:fixme:ntdll:create_logical_proc_info skipping logical processor 33 0024:fixme:ntdll:create_logical_proc_info skipping logical processor 34 0024:fixme:ntdll:create_logical_proc_info skipping logical processor 35 wine: using kernel write watches, use_kernel_writewatch 1. wine: using kernel write watches, use_kernel_writewatch 1. wine: using kernel write watches, use_kernel_writewatch 1. wine: using kernel write watches, use_kernel_writewatch 1. 0070:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 007c:fixme:wineusb:query_id Unhandled ID query type 0x5. 0070:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0070:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0070:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 wine: using kernel write watches, use_kernel_writewatch 1. wine: using kernel write watches, use_kernel_writewatch 1. wine: using kernel write watches, use_kernel_writewatch 1. wine: using kernel write watches, use_kernel_writewatch 1. 00d8:fixme:ntdll:create_logical_proc_info Improve CPU info reporting: system supports 36 logical cores, but only 32 supported! 00d8:fixme:ntdll:create_logical_proc_info skipping logical processor 33 00d8:fixme:ntdll:create_logical_proc_info skipping logical processor 34 00d8:fixme:ntdll:create_logical_proc_info skipping logical processor 35 wine: using kernel write watches, use_kernel_writewatch 1. XIO: fatal IO error 9 (Bad file descriptor) on X server ":0" after 19 requests (19 known processed) with 0 events remaining. wine: using kernel write watches, use_kernel_writewatch 1. 00e8:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 00e8:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."

I have googled a lot to try and figure out but no solutions work. Installing winehq-staging seems to resolve the wine issues outside of steam. But proton still fails to launch do anything

Last edited by duncte123; 4 Aug @ 7:27am

< >

Showing 1-14 of 14 comments

Kepos

4 Aug @ 2:44am

Hm...did you recently update kernel toward 6.10. ?
I don't know what that all means, but it points a lot toward a kernel missmatch. Kernel 6.10.1 and 6.10.2 are actually reported for causing issues that would be solved on 6.10.3.
Probably you may try another kernel with 6.9.x.

duncte123

4 Aug @ 7:27am

Nope, running kernel 6.8, should probably have included this in the main post. I'll see if I can upgrade to 6.9

duncte123@destroyed-by-UPS -------------------------- OS: Kubuntu 24.04 LTS x86_64 Kernel: 6.8.0-39-generic Uptime: 1 min Packages: 2809 (dpkg), 13 (flatpak), 11 (snap) Shell: fish 3.7.1 Resolution: 1920x1080, 1920x1080 DE: Plasma 5.27.11 WM: KWin Theme: [Plasma], Breeze [GTK2/3] Icons: [Plasma], breeze [GTK2/3] Terminal: konsole CPU: Intel i9-7980XE (36) @ 4.200GHz GPU: NVIDIA GeForce RTX 2080 Ti Rev. A Memory: 2595MiB / 63973MiB

tfk

4 Aug @ 7:44am

There are some errors in the log:

Access error:

protontricks (WARNING): Steam library folder /media/duncte123/games/SteamLibrary not found. Protontricks might not have access to the directory.

Not sure about this one:

protontricks (WARNING): Current Steam Runtime not recognized by Protontricks. x86_64-linux-gnu-capsule-capture-libs: warning: we are assuming "_el_fn_sh_complete" to be private, but it's just a guess

Dependency missing libcrypto:

x86_64-linux-gnu-capsule-capture-libs: warning: Dependencies of libnvidia-pkcs11.so.535.183.01 not found, ignoring: Missing dependencies: Could not find "libcrypto.so.1.1" in LD_LIBRARY_PATH (unset), ld.so.cache, DT_RUNPATH or fallback /lib:/usr/lib

This might need some looking into:

XIO: fatal IO error 9 (Bad file descriptor) on X server ":0" after 19 requests (19 known processed) with 0 events remaining.

Last errors in the log:

00e8:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 00e8:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."

duncte123

4 Aug @ 7:50am

Update: I installed kernel 6.9.12, only one monitor worked after that and it inverted all the colours. Ubuntu was not a fan it seems. I tried going back to kernel 6.8.0-38-generic to see if that would resolve the launching issues but it did not fix anything either

duncte123

4 Aug @ 7:56am

Originally posted by tfk:
There are some errors in the log:

Access error:
protontricks (WARNING): Steam library folder /media/duncte123/games/SteamLibrary not found. Protontricks might not have access to the directory.

Not sure about this one:
protontricks (WARNING): Current Steam Runtime not recognized by Protontricks. x86_64-linux-gnu-capsule-capture-libs: warning: we are assuming "_el_fn_sh_complete" to be private, but it's just a guess

Dependency missing libcrypto:
x86_64-linux-gnu-capsule-capture-libs: warning: Dependencies of libnvidia-pkcs11.so.535.183.01 not found, ignoring: Missing dependencies: Could not find "libcrypto.so.1.1" in LD_LIBRARY_PATH (unset), ld.so.cache, DT_RUNPATH or fallback /lib:/usr/lib

This might need some looking into:
XIO: fatal IO error 9 (Bad file descriptor) on X server ":0" after 19 requests (19 known processed) with 0 events remaining.

Last errors in the log:
00e8:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 00e8:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."

You can ignore that first access error, my stream library is on a different drive mounted under /games.

The libcrypto seems to not be an issue as it's ignoring that.

Those x server errors are also my suspicion but I did not manage to find a solution online, hence me posting it here.

Normal wine had the same issue until I switched to winehq-staging

Xenophobe

4 Aug @ 9:05am

Are your games on an NTFS drive? I ran across the following while reading the linux mint 22 release notes ... https://www.linuxmint.com/rel_wilma.php

NTFS volumes

Kernel 6.8 introduced a regression with NTFS volumes:

https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/2062972
https://github.com/tuxera/ntfs-3g/issues/108

If you're unable to mount an NTFS volume and see 'volume is dirty and "force" flag is not set!' in the dmesg output, launch Disks from the application menu, select your NTFS device, click the cog menu and choose "Repair Filesystem...".

If you're using an NTFS shared drive on kernel 6.8 this may be the problem.

duncte123

4 Aug @ 9:52am

Nope, all my volumes are ext4

Xenophobe

4 Aug @ 2:06pm

was the driver update the nvidia driver? if so, try going back to the prior version that worked.

duncte123

5 Aug @ 12:50am

Originally posted by Xenophobe:
was the driver update the nvidia driver? if so, try going back to the prior version that worked.

I've checked, it seemed to be the mesa drivers from https://launchpad.net/%7Eoibaf/+archive/ubuntu/graphics-drivers (I think those are the nvidia drivers, not 100% sure quite new to all this)

Neither upgrading nor downgrading them worked. I switched to these drivers because the drivers that shipped with ubuntu kept freezing plasma.

Native linux games do run of course

Last edited by duncte123; 5 Aug @ 12:50am

Ratconned

5 Aug @ 6:01am

Originally posted by duncte123:
Originally posted by Xenophobe:
was the driver update the nvidia driver? if so, try going back to the prior version that worked.
I've checked, it seemed to be the mesa drivers from https://launchpad.net/%7Eoibaf/+archive/ubuntu/graphics-drivers (I think those are the nvidia drivers, not 100% sure quite new to all this)

Neither upgrading nor downgrading them worked. I switched to these drivers because the drivers that shipped with ubuntu kept freezing plasma.

Native linux games do run of course

unsure about plasma but nvidia driver 525 worked for me when I was using an older ubuntu version (22.04LTS which uses GNOME) when I switched to Linux last year—during active support for the version. 535 gave me a few problems so I had switcged to 525 and hadn't had problems since with steam proton. Since then I switched to debian which has version 525 which was what I was using anyway, no issue (all this for drivers shipped with distribution).

I did face issues with GNOME freezing in the activities tab but upon checking it was a GNOME bug which has been there for years… with LXDE I haven't had a problem since. It could be a combination (possibly—not definite) of a plasma bug with shipped drivers for your distribution and the version of drivers you then used not working well with your distribution. Or it could simply be ubuntu doing ubuntu things (I have grudging pains and only really recommend ubuntu if you do not do manual stuff. Manual stuff like using a driver not shipped with distribution, for example.)

These are the possibilities I can think of.

Last edited by Ratconned; 5 Aug @ 6:44am

#10

Xenophobe

5 Aug @ 6:54am

Originally posted by duncte123:
Originally posted by Xenophobe:
was the driver update the nvidia driver? if so, try going back to the prior version that worked.
I've checked, it seemed to be the mesa drivers from https://launchpad.net/%7Eoibaf/+archive/ubuntu/graphics-drivers (I think those are the nvidia drivers, not 100% sure quite new to all this)

Neither upgrading nor downgrading them worked. I switched to these drivers because the drivers that shipped with ubuntu kept freezing plasma.

Native linux games do run of course

the mesa drivers are AMD and Intel, the nouveau drivers would the basic linux nvidia drivers. you should have a driver manager somewhere in ubuntu's menus to install the proprietary nvidia drivers, which are best for gaming.
https://itsfoss.com/install-additional-drivers-ubuntu/#installing-additional-drivers-in-ubuntu

Last edited by Xenophobe; 5 Aug @ 7:00am

#11

duncte123

5 Aug @ 7:11am

Originally posted by Xenophobe:
Originally posted by duncte123:
I've checked, it seemed to be the mesa drivers from https://launchpad.net/%7Eoibaf/+archive/ubuntu/graphics-drivers (I think those are the nvidia drivers, not 100% sure quite new to all this)

Neither upgrading nor downgrading them worked. I switched to these drivers because the drivers that shipped with ubuntu kept freezing plasma.

Native linux games do run of course
the mesa drivers are AMD and Intel, the nouveau drivers would the basic linux nvidia drivers. you should have a driver manager somewhere in ubuntu's menus to install the proprietary nvidia drivers, which are best for gaming.
https://itsfoss.com/install-additional-drivers-ubuntu/#installing-additional-drivers-in-ubuntu

I don't have that menu (likely because I am running kubuntu instead of plain ubuntu), I'll remove that repository to see if that fixes anything.

#12