You are not logged in.

#1 2025-02-17 13:55:50

ikorus
Member
Registered: 2025-02-02
Posts: 18

[SOLVED] Steam dumping core every time it starts (gldriverquery)

Hi, I recently noticed that Steam keeps making core dumps every time I launch it. I tried reinstalling it. Upgrading the system to no avail. I searched on Google and here on the forums, but I haven't seen anything similar anywhere. A nudge in the right direction on how to fix this would be much appreciated.

Here is the snippet from journal when the core dumps:

Feb 17 14:31:23 IkorusPC systemd-coredump[2405]: Process 2404 (gldriverquery) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Feb 17 14:31:23 IkorusPC systemd[1]: Created slice Slice /system/drkonqi-coredump-processor.
Feb 17 14:31:23 IkorusPC systemd[1]: Created slice Slice /system/systemd-coredump.
Feb 17 14:31:23 IkorusPC systemd[1]: Started Process Core Dump (PID 2405/UID 0).
Feb 17 14:31:23 IkorusPC systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Feb 17 14:31:23 IkorusPC systemd-coredump[2407]: Process 2404 (gldriverquery) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 2404:
                                                 #0  0x00000000f60fa579 n/a (n/a + 0x0)
                                                 ELF object binary architecture: Intel 80386
Feb 17 14:31:23 IkorusPC systemd[1]: systemd-coredump@0-2405-0.service: Deactivated successfully.
Feb 17 14:31:23 IkorusPC drkonqi-coredump-processor[2408]: "/home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery" 2404 "/var/lib/systemd/coredump/core.gldriverquery.1000.4ded95df7efa49918e8282634e7d72a6.2404.1739799083000000.zst"
Feb 17 14:31:23 IkorusPC systemd[858]: Started Launch DrKonqi for a systemd-coredump crash (PID 2408/UID 0).
Feb 17 14:31:23 IkorusPC systemd[1]: drkonqi-coredump-processor@0-2405-0.service: Deactivated successfully.
Feb 17 14:31:23 IkorusPC drkonqi-coredump-launcher[2417]: Unable to find file for pid 2404 expected at "kcrash-metadata/gldriverquery.4ded95df7efa49918e8282634e7d72a6.2404.ini"
Feb 17 14:31:23 IkorusPC drkonqi-coredump-launcher[2417]: Nothing handled the dump :O
Feb 17 14:31:46 IkorusPC systemd[1]: Starting Time & Date Service...

And here is the full journal:
Journalctl

Last edited by ikorus (2025-02-21 10:34:12)

Offline

#2 2025-02-17 16:28:36

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 24,096

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

A bunch of xe driver crashes... is this GPU in theory still eligible for i915?

lspci -k | grep -A3 'VGA'

other than that what output do you get from

glxinfo -B
eglinfo -B #Both part of mesa-utils

Offline

#3 2025-02-18 02:09:59

Kurobac
Member
Registered: 2018-06-12
Posts: 8

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

I have the same issue.

journal
https://0x0.st/8qVH.txt

lspci -k | grep -A3 'VGA'                                            
0a:00.0 VGA compatible controller: NVIDIA Corporation GA102 [GeForce RTX 3090] (rev a1)
        Subsystem: Shenzhen Colorful Yugong Technology and Development Co. Device 1301
        Kernel driver in use: nvidia
        Kernel modules: nouveau, nvidia_drm, nvidia

       
eglinfo and glxinfo (glxinfo crash, not sure it's related or not)
https://0x0.st/8qVM.txt

I'm not sure when this started happening. The earliest occurrence I found in logs is from Jan 31, but due to some buggy kde widget spammed my logs, I don't have any earlier entries.
For now, I ran chmod -x on it (not sure if it's a good idea). Steam and games seem to be running just fine™, at least no more annoying coredump message.


not a native english speaker

Offline

#4 2025-02-18 07:48:36

R290
Member
Registered: 2025-02-14
Posts: 7

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

Depending on your opinion of flatpak, you could try the flatpak version of Steam?

Offline

#5 2025-02-18 09:17:44

ikorus
Member
Registered: 2025-02-02
Posts: 18

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

V1del wrote:

A bunch of xe driver crashes... is this GPU in theory still eligible for i915?

As for the i915 I don't think it is as the card has a G21 chip
And from what i found here, it isn't listed.
I might be wrong on this one correct me if I am.

Here are the requested outputs

lspci -k | grep -A3 'VGA'
03:00.0 VGA compatible controller: Intel Corporation Battlemage G21 [Arc B580]
	Subsystem: Intel Corporation Device 1100
	Kernel driver in use: xe
	Kernel modules: xe
glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) Graphics (BMG G21) (0xe20b)
    Version: 25.0.0
    Accelerated: yes
    Video memory: 12216MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 12216 MB, largest block: 12216 MB
    VBO free aux. memory - total: 16011 MB, largest block: 16011 MB
    Texture free memory - total: 12216 MB, largest block: 12216 MB
    Texture free aux. memory - total: 16011 MB, largest block: 16011 MB
    Renderbuffer free memory - total: 12216 MB, largest block: 12216 MB
    Renderbuffer free aux. memory - total: 16011 MB, largest block: 16011 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 12216 MB
    Total available memory: 28227 MB
    Currently available dedicated video memory: 12216 MB
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (BMG G21)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
eglinfo -B
GBM platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL core profile version: 4.6 (Core Profile) Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Wayland platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL core profile version: 4.6 (Core Profile) Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

X11 platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL core profile version: 4.6 (Core Profile) Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL core profile version: 4.6 (Core Profile) Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL core profile version: 4.6 (Core Profile) Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Graphics (BMG G21)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #1:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 19.1.7, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 25.0.0-devel (git-bfd29a55e5)
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Offline

#6 2025-02-18 11:30:21

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 24,096

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

Are you intentionally using a mesa-git release and if so what for? If not I'd try to revert that to the stable branch. If intentional, is lib32-mesa-git installed and at the same version as well?

Offline

#7 2025-02-18 11:46:20

ikorus
Member
Registered: 2025-02-02
Posts: 18

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

V1del wrote:

Are you intentionally using a mesa-git release and if so what for? If not I'd try to revert that to the stable branch. If intentional, is lib32-mesa-git installed and at the same version as well?

Yes, I am using the mesa git intentionally. Because the Intel B580 is a new GPU, it has caused a lot of artifacting and texture glitching in many games and sub-optimal performance. It was fixed after the 25 release, but that one is still under testing and not in the official repositories. The official ones are still at 24.3, which has been problematic with the B580. I will migrate to the stable release once it hits version 25.

Also, Yes, I'm using the same version of the lib32 here's

sudo pacman -Q |grep mesa
lib32-mesa-git 25.1.0_devel.201864.9af11bf306c.d41d8cd-1
lib32-mesa-git-debug 25.1.0_devel.201864.9af11bf306c.d41d8cd-1
mesa-git 25.0.0_devel.200512.bfd29a55e5a.d41d8cd-1
mesa-utils 9.0.0-5
R290 wrote:

Depending on your opinion of flatpak, you could try the flatpak version of Steam?

I tried installing the Flatpak version, which doesn't core dump. I will try to uninstall steam and manually remove all residual files. Then install it back. Maybe it will help.

EDIT: It didn't help

Last edited by ikorus (2025-02-18 12:36:01)

Offline

#8 2025-02-18 15:29:46

seth
Member
Registered: 2012-09-03
Posts: 61,589

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

thTflatschpak will likely ship its own mesa?
What if you accept the artifacts, does the repo steam still crash w/ the 24.x mesa version?

Offline

#9 2025-02-18 15:57:00

ikorus
Member
Registered: 2025-02-02
Posts: 18

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

So, as you requested, I migrated back to Mesa 24.3.4 from the "Extra" repositories. But, no luck, steam still coredumps. So far, I at least want to thank you guys for trying to help me.

Here's the latest journal with the mesa 24.3.4 driver
Journalctl -b

glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) Graphics (BMG G21) (0xe20b)
    Version: 24.3.4
    Accelerated: yes
    Video memory: 12216MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 12216 MB, largest block: 12216 MB
    VBO free aux. memory - total: 16011 MB, largest block: 16011 MB
    Texture free memory - total: 12216 MB, largest block: 12216 MB
    Texture free aux. memory - total: 16011 MB, largest block: 16011 MB
    Renderbuffer free memory - total: 12216 MB, largest block: 12216 MB
    Renderbuffer free aux. memory - total: 16011 MB, largest block: 16011 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 12216 MB
    Total available memory: 28227 MB
    Currently available dedicated video memory: 12216 MB
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (BMG G21)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.3.4-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.3.4-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.3.4-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Offline

#10 2025-02-18 16:03:53

seth
Member
Registered: 2012-09-03
Posts: 61,589

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

This starts to smell like https://bbs.archlinux.org/viewtopic.php?id=303500 - but you don't seem to have an nvidia GPU around.
And gldriverquery actually aborts, doesn't it print on the console/the steam logs "why"?

Offline

#11 2025-02-18 17:25:59

ikorus
Member
Registered: 2025-02-02
Posts: 18

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

Here's the message steam gives me when I launch it from the terminal.

steam-runtime
steam.sh[12455]: Running Steam on arch rolling 64-bit
steam.sh[12455]: STEAM_RUNTIME is enabled automatically
setup.sh[12510]: Steam runtime environment up-to-date!
steam.sh[12455]: Log already open
steam.sh[12455]: Using supervisor /home/ikorus/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/bin/steam-runtime-supervisor
steam.sh[12455]: Steam client's requirements are satisfied
CProcessEnvironmentManager is ready, 6 preallocated environment variables.
[2025-02-18 17:50:18] Startup - updater built Jan 28 2025 00:50:36
[2025-02-18 17:50:18] Startup - Steam Client launched with: '/home/ikorus/.local/share/Steam/ubuntu12_32/steam' '-srt-logger-opened'
02/18 17:50:18 minidumps folder is set to /tmp/dumps
02/18 17:50:18 Init: Installing breakpad exception handler for appid(steam)/version(1738026274)/tid(12576)
[2025-02-18 17:50:19] Loading cached metrics from disk (/home/ikorus/.local/share/Steam/package/steam_client_metrics.bin)
[2025-02-18 17:50:19] Using the following download hosts for Public, Realm steamglobal
[2025-02-18 17:50:19] 1. https://client-update.fastly.steamstatic.com, /, Realm 'steamglobal', weight was 900, source = 'update_hosts_cached.vdf'
[2025-02-18 17:50:19] 2. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf'
[2025-02-18 17:50:19] 3. https://client-update.steamstatic.com, /, Realm 'steamglobal', weight was 1, source = 'baked in'
[2025-02-18 17:50:19] Verifying installation...
[2025-02-18 17:50:19] Verification complete
UpdateUI: skip show logo
Steam logging initialized: directory: /home/ikorus/.local/share/Steam/logs

XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xe00a6dc0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xe00a5500
steamwebhelper.sh[12607]: Using supervisor /home/ikorus/.steam/root/ubuntu12_32/steam-runtime/amd64/usr/bin/steam-runtime-supervisor
steamwebhelper.sh[12607]: Starting steamwebhelper under bootstrap sniper steam runtime via /home/ikorus/.local/share/Steam/ubuntu12_64/steam-runtime-sniper.sh
steamwebhelper.sh[12607]: Using CEF sandbox \(try with -no-cef-sandbox if this fails\)
steamwebhelper.sh[12607]: Starting steamwebhelper with Sniper steam runtime at /home/ikorus/.local/share/Steam/ubuntu12_64/steam-runtime-sniper/_v2-entry-point
exec ./steamwebhelper -nocrashdialog -lang=en_US -cachedir=/home/ikorus/.local/share/Steam/config/htmlcache -steampid=12576 -buildid=1738026274 -steamid=0 -logdir=/home/ikorus/.local/share/Steam/logs -uimode=7 -startcount=0 -steamuniverse=Public -realm=Global -clientui=/home/ikorus/.local/share/Steam/clientui -steampath=/home/ikorus/.local/share/Steam/ubuntu12_32/steam -launcher=0 -no-restart-on-ui-mode-change --valve-enable-site-isolation --enable-smooth-scrolling --password-store=basic --log-file=/home/ikorus/.local/share/Steam/logs/cef_log.txt --disable-quick-menu --enable-features=PlatformHEVCDecoderSupport --disable-features=SpareRendererForSitePerProcess,DcheckIsFatal,ValveFFmpegAllowLowDelayHEVC
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 12829
bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam
SDL_StretchSurface missing in SDL3 library.
/usr/share/themes/Breeze-Dark/gtk-2.0/widgets/entry:70: error: unexpected identifier 'direction', expected character '}'
/usr/share/themes/Breeze-Dark/gtk-2.0/widgets/styles:36: error: invalid string constant "combobox_entry", expected valid string constant
Desktop state changed: desktop: { pos:    0,   0 size: 5760,1080 } primary: { pos:    0,   0 size: 1920,1080 }
Caching cursor image for , size 32x32, serial 316, cache size = 0
fsync: up and running.
Fossilize INFO: Overriding serialization path: "/home/ikorus/.local/share/Steam/shader_cache_temp_dir_d3d11_64/fozpipelinesv6/steamapprun_pipeline_cache".
fsync: up and running.
Fossilize INFO: Overriding serialization path: "/home/ikorus/.local/share/Steam/shader_cache_temp_dir_d3d12_64/fozpipelinesv6/steamapprun_pipeline_cache".
[2025-02-18 17:51:50] Shutdown

If you need any other logs don't hesitate to say so. I'll send them right away.
Here is the cef_log.txt

[0218/181222.393753:WARNING:alloy_main_delegate.cc(578)] Alloy bootstrap is deprecated and will be removed in ~M127. See https://github.com/chromiumembedded/cef/issues/3685
[0218/181222.412270:INFO:crash_reporting.cc(238)] Crash reporting enabled for process: browser
[0218/181222.414421:WARNING:task_impl.cc(31)] No task runner for threadId 0
[0218/181222.414941:WARNING:task_impl.cc(31)] No task runner for threadId 0
[0218/181222.481513:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: gpu-process
[0218/181222.615173:WARNING:sandbox_linux.cc(430)] InitializeSandbox() called with multiple threads in process gpu-process.
[0218/181224.209455:INFO:crash_reporting.cc(238)] Crash reporting enabled for process: utility
[0218/181224.247806:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: utility
[0218/181224.281909:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: renderer
[0218/181225.357430:ERROR:atom_cache.cc(229)] Add STEAM_GAME to kAtomsToCache
[0218/181226.919286:ERROR:atom_cache.cc(229)] Add _NET_WM_STATE_KEEP_ABOVE to kAtomsToCache
[0218/181226.922428:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: renderer
[0218/181228.363525:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[0218/181228.374516:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[0218/181228.404912:INFO:crash_reporting.cc(255)] Crash reporting enabled for process: renderer
[0218/181228.412049:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
[0218/181229.598351:ERROR:ffmpeg_common.cc(959)] Unsupported pixel format: -1
[0218/181229.633977:ERROR:ffmpeg_common.cc(959)] Unsupported pixel format: -1

This log has a renderer crash logged.


seth wrote:

but you don't seem to have an nvidia GPU around.

I don't anymore. I did have a gtx 1060 in this system which I swapped mid december~ish. But i removed everything (packages/mkinit hooks/kernel modules) before installing the new gpu.

Edit: As for the console output when launching steam. I don't see anything weird there apart from the GTK 2 theme error.

Last edited by ikorus (2025-02-18 17:31:52)

Offline

#12 2025-02-19 11:03:01

ugjka
Member
From: Latvia
Registered: 2014-04-01
Posts: 1,885
Website

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

Same stuff here

feb 19 12:53:57 ugjka systemd-coredump[3567]: [?] Process 3564 (gldriverquery) of user 1000 dumped core.
                                              
                                              Stack trace of thread 3564:
                                              #0  0x00000000ea0bf579 n/a (n/a + 0x0)
                                              ELF object binary architecture: Intel 80386

System:

Operating System: Arch Linux 
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.2-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 54,7 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUS

https://ugjka.net
"It is easier to fool people, than to convince them that they've been fooled" ~ Dr. Andrea Love

Offline

#13 2025-02-19 16:32:53

seth
Member
Registered: 2012-09-03
Posts: 61,589

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

Try to run "/home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery" manually, it'll likely crash but you can then run it through gdb and strace and maybe get a better idea what's going wrong (eg. just by the invoked libraries) than n/a+0x0 …

Offline

#14 2025-02-19 18:25:35

Kurobac
Member
Registered: 2018-06-12
Posts: 8

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

No crash if I ran gldriverquery manually. Exit with code 0.
Also no crash with steam flatpak.
Maybe I should try different mesa version?
Edit: tried mesa 23.0 and mesa 24.0, still crash.

Last edited by Kurobac (2025-02-19 18:44:23)


not a native english speaker

Offline

#15 2025-02-19 20:01:38

ugjka
Member
From: Latvia
Registered: 2014-04-01
Posts: 1,885
Website

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

I simply installed Flatpak version, not interested in mysteries


https://ugjka.net
"It is easier to fool people, than to convince them that they've been fooled" ~ Dr. Andrea Love

Offline

#16 2025-02-19 22:51:36

seth
Member
Registered: 2012-09-03
Posts: 61,589

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

No crash if I ran gldriverquery manually. Exit with code 0.

Hybrid system?
Does

prime-run gldriverquery

crash?

Offline

#17 2025-02-20 01:13:03

Kurobac
Member
Registered: 2018-06-12
Posts: 8

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

seth wrote:

Hybrid system?

No. Desktop with single gpu.


not a native english speaker

Offline

#18 2025-02-20 10:58:28

ikorus
Member
Registered: 2025-02-02
Posts: 18

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

seth wrote:

Try to run "/home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery" manually, it'll likely crash but you can then run it through gdb and strace and maybe get a better idea what's going wrong (eg. just by the invoked libraries) than n/a+0x0 …

I'm gonna be completely honest. I am not a programmer and this issue has become way bigger than I can handle. Even tho I'm gonna try to follow the instructions given to the best of my abilities.

When i run "/home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery". In the terminal it doesn't output anything just skips to the next line as if command has just finished.

If i cd into the /home/ikorus/.local/share/Steam/ubuntu12_32/ and try to execute it like a bash script  ./gldriverquery it just skips to the next line not giving any output.

If i navigate to the same file location in a graphical file explorer and try "double clicking it" nothing happens.

After that I tried running gbd

run /home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery
Starting program:  /home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery
No executable file specified.
Use the "file" or "exec-file" command.

After that I did

exec-file /home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery

Which didn't give any output.


after that i tried

(gdb) file /home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery
Reading symbols from /home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery...

It skips to a new line after.

and yes the file is executable

ls /home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery -l
-rwxr-xr-x 1 ikorus ikorus 203548 Aug 28 19:28 /home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery

And also no. I am not on a hybrid system.

Offline

#19 2025-02-20 13:52:09

seth
Member
Registered: 2012-09-03
Posts: 61,589

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

When i run "/home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery". In the terminal it doesn't output anything just skips to the next line as if command has just finished.

Means it most likely doesn't crash

/home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery && echo fine

This fits Kurobac's experience and means the problem only arises within the steam context - and apparently it's not for chosing the wrong GL library…

https://bbs.archlinux.org/viewtopic.php?id=303500 was down to vulkan…

pacman -Qs vulkan
vulkaninfo --summary

and see https://wiki.archlinux.org/title/Steam/ … _emulation

Offline

#20 2025-02-20 15:16:37

ikorus
Member
Registered: 2025-02-02
Posts: 18

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

Ok I ran the

/home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery && echo fine

The echo came back that means the gldriverquery did run.

seth wrote:

With this do you want me to switch to the GL renderer ?


seth wrote:

Should I test the command

PROTON_USE_WINED3D=1 %command%

on a few games and see if coredumps occur ?


Here are the:

vulkaninfo --summary
==========
VULKANINFO
==========

Vulkan Instance Version: 1.4.303


Instance Extensions: count = 24
-------------------------------
VK_EXT_acquire_drm_display             : extension revision 1
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_EXT_headless_surface                : extension revision 1
VK_EXT_surface_maintenance1            : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 5
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6
VK_LUNARG_direct_driver_loading        : extension revision 1

Instance Layers: count = 10
---------------------------
VK_LAYER_FROG_gamescope_wsi_x86_64 Gamescope WSI (XWayland Bypass) Layer (x86_64) 1.3.221  version 1
VK_LAYER_INTEL_nullhw              INTEL NULL HW                                  1.1.73   version 1
VK_LAYER_KHRONOS_validation        Khronos Validation Layer                       1.3.296  version 1
VK_LAYER_MANGOHUD_overlay_x86_64   Vulkan Hud Overlay                             1.3.0    version 1
VK_LAYER_MESA_device_select        Linux device selection layer                   1.4.303  version 1
VK_LAYER_MESA_overlay              Mesa Overlay layer                             1.4.303  version 1
VK_LAYER_VALVE_steam_fossilize_32  Steam Pipeline Caching Layer                   1.3.207  version 1
VK_LAYER_VALVE_steam_fossilize_64  Steam Pipeline Caching Layer                   1.3.207  version 1
VK_LAYER_VALVE_steam_overlay_32    Steam Overlay Layer                            1.3.207  version 1
VK_LAYER_VALVE_steam_overlay_64    Steam Overlay Layer                            1.3.207  version 1

Devices:
========
GPU0:
	apiVersion         = 1.4.305
	driverVersion      = 25.0.99
	vendorID           = 0x8086
	deviceID           = 0xe20b
	deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
	deviceName         = Intel(R) Graphics (BMG G21)
	driverID           = DRIVER_ID_INTEL_OPEN_SOURCE_MESA
	driverName         = Intel open-source Mesa driver
	driverInfo         = Mesa 25.1.0-devel (git-765f3b78d5)
	conformanceVersion = 1.4.0.0
	deviceUUID         = 86800be2-0000-0000-0300-000000000000
	driverUUID         = 8f481f37-b929-7802-f2f0-96a0ff0e80b2
GPU1:
	apiVersion         = 1.4.305
	driverVersion      = 0.0.1
	vendorID           = 0x10005
	deviceID           = 0x0000
	deviceType         = PHYSICAL_DEVICE_TYPE_CPU
	deviceName         = llvmpipe (LLVM 19.1.7, 256 bits)
	driverID           = DRIVER_ID_MESA_LLVMPIPE
	driverName         = llvmpipe
	driverInfo         = Mesa 25.1.0-devel (git-765f3b78d5) (LLVM 19.1.7)
	conformanceVersion = 1.3.1.1
	deviceUUID         = 6d657361-3235-2e31-2e30-2d6465766500
	driverUUID         = 6c6c766d-7069-7065-5555-494400000000

and

pacman -Qs vulkan
local/dxvk-bin 2.5.3-1
    A Vulkan-based compatibility layer for Direct3D 9/10/11 which allows running 3D applications on
    Linux using Wine (Windows DLL binary files)
local/lib32-mesa-git 25.1.0_devel.201914.765f3b78d56.d41d8cd-1
    an open-source implementation of the OpenGL specification, git version
local/lib32-vkd3d 1.14-1
    Direct3D 12 to Vulkan translation library By WineHQ
local/lib32-vulkan-icd-loader 1.4.303-1
    Vulkan Installable Client Driver (ICD) Loader (32-bit)
local/mangohud 0.8.0-2
    A Vulkan overlay layer for monitoring FPS, temperatures, CPU/GPU load and more.
local/mesa-git 25.1.0_devel.201914.765f3b78d56.d41d8cd-1
    an open-source implementation of the OpenGL specification, git version
local/qt6-shadertools 6.8.2-1 (qt6)
    Provides functionality for the shader pipeline that allows Qt Quick to operate on Vulkan, Metal,
    and Direct3D, in addition to OpenGL
local/spirv-tools 2024.4.rc2-1 (vulkan-devel)
    API and commands for processing SPIR-V modules
local/vkd3d 1.14-1
    Direct3D 12 to Vulkan translation library By WineHQ
local/vulkan-headers 1:1.4.303-1 (vulkan-devel)
    Vulkan header files
local/vulkan-icd-loader 1.4.303-1
    Vulkan Installable Client Driver (ICD) Loader
local/vulkan-tools 1.4.303-2 (vulkan-devel)
    Vulkan Utilities and Tools
local/vulkan-validation-layers 1.3.296.0-1 (vulkan-devel)
    Vulkan Validation Layers

Offline

#21 2025-02-20 16:46:22

Kurobac
Member
Registered: 2018-06-12
Posts: 8

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

Seems like no more crash with glibc 2.41+r9+ga900dbaf70f0-1.
Also:

kurobac:~/ $ .local/share/Steam/ubuntu12_32/gldriverquery                          [0:30:15]
.local/share/Steam/ubuntu12_32/gldriverquery: error while loading shared libraries: libSDL2-2.0.so.0: cannot open shared object file: No such file or directory
kurobac:~/ $ LD_PRELOAD=/home/kurobac/.local/share/Steam/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu/libSDL2-2.0.so.0 .local/share/Steam/ubuntu12_32/gldriverquery 
kurobac:~/ $ echo $?                                                               [0:34:45]
0

Before glibc update, it will exit with code 0 without LD_PRELOAD.

Last edited by Kurobac (2025-02-20 16:51:56)


not a native english speaker

Offline

#22 2025-02-20 17:00:30

ikorus
Member
Registered: 2025-02-02
Posts: 18

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

Kurobac wrote:

Seems like no more crash with glibc 2.41+r9+ga900dbaf70f0-1.


Meanwhile I'm still here dumping cores like there's no tomorrow sad

Feb 20 17:54:12 IkorusPC steam-runtime-steam-remote[1755]: steam-runtime-steam-remote: Steam is not running: No such device or address
Feb 20 17:54:15 IkorusPC appimagelauncherd[1034]: Executing deferred operations
Feb 20 17:54:15 IkorusPC appimagelauncherd[1034]: Integrating: /home/ikorus/.bash_history
Feb 20 17:54:15 IkorusPC appimagelauncherd[1034]: ERROR: not an AppImage, skipping
Feb 20 17:54:15 IkorusPC appimagelauncherd[1034]: Cleaning up old desktop integration files
Feb 20 17:54:15 IkorusPC appimagelauncherd[1034]: Updating desktop database and icon caches
Feb 20 17:54:15 IkorusPC appimagelauncherd[1858]: which: no gtk-update-icon-cache-3.0 in (/usr/local/bin:/usr/bin)
Feb 20 17:54:15 IkorusPC appimagelauncherd[1866]: which: no update-icon-caches in (/usr/local/bin:/usr/bin)
Feb 20 17:54:19 IkorusPC appimagelauncherd[1034]: Done
Feb 20 17:54:21 IkorusPC rtkit-daemon[1282]: Successfully made thread 1993 of process 1885 owned by '1000' high priority at nice level -10.
Feb 20 17:54:21 IkorusPC rtkit-daemon[1282]: Supervising 8 threads of 5 processes of 1 users.
Feb 20 17:54:21 IkorusPC rtkit-daemon[1282]: Successfully made thread 1994 of process 1885 owned by '1000' high priority at nice level -10.
Feb 20 17:54:21 IkorusPC rtkit-daemon[1282]: Supervising 9 threads of 5 processes of 1 users.
Feb 20 17:54:21 IkorusPC systemd-coredump[2078]: Process 2075 (gldriverquery) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Feb 20 17:54:21 IkorusPC systemd[1]: Created slice Slice /system/drkonqi-coredump-processor.
Feb 20 17:54:21 IkorusPC systemd[1]: Created slice Slice /system/systemd-coredump.
Feb 20 17:54:21 IkorusPC systemd[1]: Started Process Core Dump (PID 2078/UID 0).
Feb 20 17:54:21 IkorusPC systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Feb 20 17:54:21 IkorusPC systemd-coredump[2081]: [?] Process 2075 (gldriverquery) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 2075:
                                                 #0  0x00000000f6415579 n/a (n/a + 0x0)
                                                 ELF object binary architecture: Intel 80386
Feb 20 17:54:21 IkorusPC systemd[1]: systemd-coredump@0-2078-0.service: Deactivated successfully.
Feb 20 17:54:22 IkorusPC drkonqi-coredump-processor[2082]: "/home/ikorus/.local/share/Steam/ubuntu12_32/gldriverquery" 2075 "/var/lib/systemd/coredump/core.gldriverquery.1000.90632e56579f44c795aab94fc96c61ed.2075.1740070461000000.zst"
Feb 20 17:54:22 IkorusPC systemd[1025]: Started Launch DrKonqi for a systemd-coredump crash (PID 2082/UID 0).
Feb 20 17:54:22 IkorusPC systemd[1]: drkonqi-coredump-processor@0-2078-0.service: Deactivated successfully.
Feb 20 17:54:22 IkorusPC drkonqi-coredump-launcher[2114]: Unable to find file for pid 2075 expected at "kcrash-metadata/gldriverquery.90632e56579f44c795aab94fc96c61ed.2075.ini"
Feb 20 17:54:22 IkorusPC drkonqi-coredump-launcher[2114]: Nothing handled the dump :O
Feb 20 17:54:45 IkorusPC systemd[1]: Starting Time & Date Service...
Feb 20 17:54:45 IkorusPC systemd[1]: Started Time & Date Service.
Feb 20 17:54:46 IkorusPC rtkit-daemon[1282]: Supervising 9 threads of 5 processes of 1 users.
Feb 20 17:54:46 IkorusPC rtkit-daemon[1282]: Supervising 9 threads of 5 processes of 1 users.
Feb 20 17:54:46 IkorusPC rtkit-daemon[1282]: Supervising 9 threads of 5 processes of 1 users.
Feb 20 17:54:46 IkorusPC rtkit-daemon[1282]: Supervising 9 threads of 5 processes of 1 users.
Feb 20 17:54:46 IkorusPC rtkit-daemon[1282]: Successfully made thread 2598 of process 2462 owned by '1000' RT at priority 10.
Feb 20 17:54:46 IkorusPC rtkit-daemon[1282]: Supervising 10 threads of 6 processes of 1 users.
sudo pacman -Q |grep glibc
glibc 2.41+r9+ga900dbaf70f0-1
lib32-glibc 2.41+r9+ga900dbaf70f0-1

Offline

#23 2025-02-20 21:10:48

seth
Member
Registered: 2012-09-03
Posts: 61,589

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

@ikorus you're probably the only one on mesa-git?
Have you at least rebuilt it on top of the latest glibc?

Offline

#24 2025-02-21 08:31:30

ikorus
Member
Registered: 2025-02-02
Posts: 18

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

You're right. I didn't do a rebuild at the time. Well, after I rebuilt. It didn't help anyway, neither did migrating back to 24.3. As it seems that the larger issue for the majority of people has been solved by the glibc update, and it's highly possible that I just f up something on my system should I mark this thread as solved ?

Offline

#25 2025-02-21 10:33:46

ikorus
Member
Registered: 2025-02-02
Posts: 18

Re: [SOLVED] Steam dumping core every time it starts (gldriverquery)

Ok. It didn't seem right to me so I kept digging around. Got mad and decided to clean up my system. I uninstalled mesa-git as the version 25 is released as of now. Just haven't been pushed to the official repositories yet. And followed https://wiki.archlinux...Removing_unused_packages and https://wiki.archlinux...Detecting_more_unneeded_packages. Restarted my PC and behold no more core-dumping from steam. Marking this Post as solved.

P.S
I want to thank you guys for taking the time to help.
Not just now but in many posts before me.
I haven't seen many people have the patience of gods some of you have.
Thanks.

Offline

Board footer

Powered by FluxBB