Hello @cpiber, iris_dri.so is part of the mesa project and your video driver for Intel hardware. Crashes in the video driver should be investigated on the driver side.
The easiest thing you can test is if a newer mesa build helps by using a PPA like oibaf or kisak-mesa and also mention your issue to your video driver vendor.
I use the kisak-mesa repo (tested before and after)
Which repo would you recommend me to post this? And how would I gather more data? This is all dmesg shows
You can look for similar mesa issues at https://gitlab.freedesktop.org/mesa/mesa/-/issues and Intel's xorg ddx is at https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/-/issues.
Hello @cpiber, are you still experiencing this issue on an up to date system?
I'm on different hardware now, so I can't be sure. For reference, here is the bug I filed on your recommendation: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3570
I tried it now on another laptop with Ubuntu 22.04 and steam starts fine on DWM. I guess we can close it? I can try to setup the older laptop again if you think it's important.
Thanks for the feedback.
At this time I don't think that there's an actionable detail for a Valve dev to ponder here. If the driver sided investigation makes progress with a hint that there's an application-sided issue, then please add a note here and I can re-open this issue report.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
Can't start steam in desktop environments other than Gnome. Also works in KDE Plasma on Kubuntu (not tested in Plasma on Ubuntu).
Got SEGFAULT:
Possibly related:
https://discourse.ubuntu.com/t/call-for-testing-steam-in-focal-fossa/14490/9
Steps for reproducing this issue:
Tested on LXDE and i3-gaps (both with and without compositor)
Edit: Purging
xserver-xorg-video-inteland rebooting worked. As mentioned in the link above, this might be because steam relies on the gnome appindicator. On my kubuntu install I have no problems with the package using Plasma or i3, possibly a wrong check?