Steam segfaulting upon running, assuming nvidia driver issue?

Hi there,

Hoping I could get some insight/assistance with this. I ran a “sudo pacman -Syyu” and did a full system update, went very smooth. Then I attached my game drive from windows into steam by installing ldmtool, doing a “sudo ldmtool create all” and then adding the appropriate entry into the /etc/fstab as an ntfs drive, and then added the drive to Steam’s library. Then I attempted to run Cyberpunk 2077, which has been running Super well, ever since installing cachy-os (I played it about 6 hours ago, zero issues). But it says loading, does the shader gen and then nothing, doesn’t open a window or anything, and the button in Steam changes from “running” to “Launch”.
I did a “sudo dmesg | tail” to see if there was anything I could see, and this is what I got:
[ 35.741093] input: JBL Charge 5 Wi-Fi (AVRCP) as /devices/virtual/input/input26
[ 51.434218] systemd-journald[760]: Time jumped backwards, rotating.
[ 56.187794] gldriverquery[2743]: segfault at 0 ip 00007ab82b8ae175 sp 00007fff1f823a50 error 4 in libxcb.so.1.1.0[7ab82b8a4000+17000] likely on CPU 23 (core 13, socket 0)
[ 56.187808] Code: 08 0f b7 40 1a 89 83 fc 51 00 00 eb a0 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 56 41 55 41 54 4d 89 cc 55 53 48 83 ec 68 <44> 8b 37 48 8b 19 89 74 24 28 44 89 44 24 20 64 48 8b 04 25 28 00
[ 56.922473] gldriverquery[2809]: segfault at 0 ip 00000000ea582341 sp 00000000ffaedb00 error 4 in libxcb.so.1.1.0[ea579000+17000] likely on CPU 9 (core 11, socket 0)
[ 56.922483] Code: 71 0c 8b 19 89 45 a0 8b 41 08 89 75 b4 89 45 a4 8b 41 10 89 45 b8 8b 41 14 89 45 c0 65 a1 14 00 00 00 89 45 e4 8b 06 89 45 b0 <8b> 03 85 c0 0f 85 cb 05 00 00 8b 45 a4 85 c0 0f 84 a2 07 00 00 8b
[ 701.221993] gldriverquery[27840]: segfault at 0 ip 000075bcc6047175 sp 00007ffe0b541950 error 4 in libxcb.so.1.1.0[75bcc603d000+17000] likely on CPU 20 (core 10, socket 0)
[ 701.222004] Code: 08 0f b7 40 1a 89 83 fc 51 00 00 eb a0 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 56 41 55 41 54 4d 89 cc 55 53 48 83 ec 68 <44> 8b 37 48 8b 19 89 74 24 28 44 89 44 24 20 64 48 8b 04 25 28 00
[ 701.931502] gldriverquery[27958]: segfault at 0 ip 00000000f167c341 sp 00000000fff11ff0 error 4 in libxcb.so.1.1.0[f1673000+17000] likely on CPU 12 (core 0, socket 0)
[ 701.931511] Code: 71 0c 8b 19 89 45 a0 8b 41 08 89 75 b4 89 45 a4 8b 41 10 89 45 b8 8b 41 14 89 45 c0 65 a1 14 00 00 00 89 45 e4 8b 06 89 45 b0 <8b> 03 85 c0 0f 85 cb 05 00 00 8b 45 a4 85 c0 0f 84 a2 07 00 00 8b

As you can see, it’s giving a segmentation fault error everytime I open Steam by the looks of it. Every game has the exact same behavior. Any ideas, folks?

I’d greatly appreciate any help I could get, and thank you so much to the creator of Cachy-OS, this has been the best distro for me, period. Been running it for a few months now and this is the first actual issue.

This is the cachyos-bugreport that was generated. Thanks in advance!

What the hell is the renderer doing using sse2?! That is highly suspicious. If that is sse2 as in the instruction set, that could probably explain some serious problems in trying to run steam. It should be using sse4.2 or avx2.
Edit: Ok so something appears to be going on with xcb. This suggests to me that there is likely an x11 driver issue at play.
These lines here
[ 56.187794] gldriverquery[2743]: segfault at 0 ip 00007ab82b8ae175 sp 00007fff1f823a50 error 4 in libxcb.so.1.1.0[7ab82b8a4000+17000] likely on CPU 23 (core 13, socket 0)
[ 56.187808] Code: 08 0f b7 40 1a 89 83 fc 51 00 00 eb a0 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 56 41 55 41 54 4d 89 cc 55 53 48 83 ec 68 <44> 8b 37 48 8b 19 89 74 24 28 44 89 44 24 20 64 48 8b 04 25 28 00
From what I can deduce, it is trying to load something involving xorg. I made the libxcb.so bold as to draw your attention to where the issue is stemming from. The gldriver query is your system trying to find a GL driver and check on its status. Simply put, it might be trying to load the gpu modules needed to run the application but is failing to establish connection to it. Thus it segfaults as the executed commands cannot reach process cycle completion.

xorg-xwayland was updated today. This could perhaps be it, especially since a .1 release is now in extra-testing (I have not looked into what it fixes).

You could perhaps test the extra-testing package (but I have not looked at if this also needs any other packages rebuilt).

But it definitely looks to be something with nvidia, as I don’t have this issue on AMD (have tested steam & also some other apps running on xcb).

Have you tried in X11?

I really wouldn’t be able to test regular x11 on amd as I configured my system to use zink instead of Radeon’s OpenGL driver. Speaking of which, does nvidia support the zink driver? Because if so, that could be used as a potential main or fall back option if something breaks with nvidia. For those who are unaware, zink is a unique layer gpu driver that abstracts opengl code into vulkan code. This allows for much better performance with applications that only support open gl but not vulkan.

The gldriver segfaults are pretty common since the 555 driver. I have this already reported to nvidia.

But these should actually not stop you running an game. Could you provide the PROTON_LOG ?

Also, you could try a different proton version, since yesterday proton-cachyos got updated based on the latest proton-experimental.

Now that I think about it, x11 might be acting up on amd hardware too. I notice that whenever I try to edit my panel, it segfaults quite often, crashing plasma and restarting it. Perhaps it is mesa related? It was also mentioned that it might be xwayland causing a problem. In that case it may not just be nvidia. I would like to note that the problem I have been experiencing appeared after a minor release update or two for kde plasma 6.1 since it launched. It has improved some what with subsequent updates but it is still an unresolved problem.

xwayland 24.1.1 : fix segment fault in xwl_glamor_gbm_init_main_dev , and several other fixes.

(I don’t know if this is your issue, but XWayland 24.1 brought explicit sync support, and other changes, so it could be).

Mhm, I have pushed xwayland 24.1.1 already.

1 Like

Yes, I just added this info since OP hasn’t replied if it works or not.

1 Like

Firstly, a big “Thank You!” to all of you who posted here. I was completely unaware Cachy-OS had such an outstanding community. Seriously, I didn’t expect an answer at all, let alone all you folks helping out and putting in the time and brainpower. So I really, really appreciate that. It make me feel like I chose the wrong “solution”, which I will explain now.
In the past, I have struggled somewhat in getting live help. Most things you can find with some googling, but for something more complicated that won’t work. And to be honest, these have probably been the best responses I’ve received in my time on Linux-focused forums. Very helpful, insightful, and a complete lack of judgement, criticism, etc. So Thank You!

Yesterday was a rough day for me, you could say, as I had already borked my laptop install of Cachy, (completely my fault though) and had no laptop for most of the day. Then I got home and this happened. At this point all I wanted to do was play some games and put the shit day behind me! So it was incredibly frustrating. After working on different possible fixes for about an hour, involving downgrading different packages and trying combinations of package versions of the packages that I thought were involved, I threw my hands up and said “Ok, moving on!”. Please don’t take this in any way as a disrespectful thing, or having a problem with Cachy either. I was just at my last straw. So I installed Nobara. Basically a gaming-centric distro by Glorious Eggroll, the guy who does Proton-GE, based on Fedora. Not my favorite underlying OS but hey I knew it figured it would work so I could get my game on and forget my day lol.
So needless to say, I don’t have any feedback unfortunately about the fixes suggested. But this thread’s responses have really opened my eyes to the community around Cachy-OS! I think I’m ready to try again. So later today I will be reinstalling Cachy, and if anything comes up I will refer to this thread for possible fixes. Again, thank you so much for all the great ideas and just responding in general! I really thought I was just SOL.

  • Edit - Sorry about the novel, just wanted to explain completely what the situation was. I look forward to using Cachy-OS again, as this has literally been my only problem with it! Very well-done distro. I would definitely recommend!
1 Like