MangoHud
MangoHud copied to clipboard
flightlessmango
dxvk crashes with segfault when trying to quit Team Fortress 2 with mangohud enabled
When Team Fortress 2 (tf2) is launched with mangohud, i.e. by setting the launch args in steam to mangohud %command%, the game will crash when it is closed. At the moment its just a minor annoyance, since the game still closes when i wanted it to, but the OS reports it as a crash each time which gets annoying.
Fedora 41, Gnome 47.3 + Wayland mangohud -- version shows 0.7.1 but rpm shows mangohud 0.7.2-3 AMD Ryzen 7 7800X3D AMD Radeon RX 6900 XT
Steps to reproduce the behavior:
- Add
mangohud %command%to tf2 launch args in steam - Launch tf2 through steam
- Wait for the game to load
- Quit the game (any method -- using the GUI or using the console)
Expected behavior
- The game closes
Actual behavior
- The game closes
- dxvk segfaults
- OS reports a crash
If mangohud %comand% is removed from the launch args, the game quits like normal without crashing.
Some logs from journalctl:
while launching:
Feb 03 16:44:40 cow-lan1 gnome-shell[2698]: g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failed
Feb 03 16:44:55 cow-lan1 xdg-desktop-por[3500]: Backend call failed: GDBus.Error:org.gnome.SessionManager.GeneralError: Application ID not specified
Feb 03 16:45:05 cow-lan1 gnome-shell[2698]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00002 (Team Fortress 2 - Vulkan - 64 Bit)
Feb 03 16:45:06 cow-lan1 rtkit-daemon[1171]: Successfully made thread 18813 of process 18749 (/home/spot/.local/share/Steam/steamapps/common/Team Fortress 2/tf_linux64) owned by '1000' high priority at nice level -15.
Feb 03 16:45:12 cow-lan1 rtkit-daemon[1171]: Successfully made thread 18839 of process 18749 (/home/spot/.local/share/Steam/steamapps/common/Team Fortress 2/tf_linux64) owned by '1000' high priority at nice level -15.
while quitting:
Feb 03 16:45:17 cow-lan1 audit[18749]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=18749 comm="dxvk-submit" exe=2F686F6D652F73706F742F2E6C6F63616C2F73686172652F537465616D2F737465616D617070732F636F6D6D6F6E2F5465616D20466F72747265737320322F74665F6C696E75783634 sig=11 res=1
Feb 03 16:45:18 cow-lan1 systemd-coredump[18858]: Process 18749 (tf_linux64) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Feb 03 16:45:18 cow-lan1 audit: BPF prog-id=204 op=LOAD
Feb 03 16:45:18 cow-lan1 audit: BPF prog-id=205 op=LOAD
Feb 03 16:45:18 cow-lan1 audit: BPF prog-id=206 op=LOAD
Feb 03 16:45:18 cow-lan1 systemd[1]: Started [email protected] - Process Core Dump (PID 18858/UID 0).
Feb 03 16:45:18 cow-lan1 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@7-18858-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 16:45:18 cow-lan1 abrt-dump-journal-core[1302]: Failed to obtain all required information from journald
Feb 03 16:45:21 cow-lan1 systemd-coredump[18859]: [🡕] Process 18749 (tf_linux64) of user 1000 dumped core.
Module libzstd.so.1 from rpm zstd-1.5.6-2.fc41.x86_64
Module liblzma.so.5 from rpm xz-5.6.2-2.fc41.x86_64
Stack trace of thread 18820:
#0 0x00007fc459b9d2a0 n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64
Feb 03 16:45:21 cow-lan1 systemd[1]: [email protected]: Deactivated successfully.
Feb 03 16:45:21 cow-lan1 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@7-18858-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 16:45:21 cow-lan1 systemd[1]: [email protected]: Consumed 3.278s CPU time, 2.2G memory peak.
Feb 03 16:45:21 cow-lan1 audit: BPF prog-id=206 op=UNLOAD
Feb 03 16:45:21 cow-lan1 audit: BPF prog-id=205 op=UNLOAD
Feb 03 16:45:21 cow-lan1 audit: BPF prog-id=204 op=UNLOAD
Feb 03 16:45:21 cow-lan1 abrtd[1269]: Size of '/var/spool/abrt' >= 5000 MB (MaxCrashReportsSize), deleting old directory 'ccpp-2025-01-17-21:39:22.927270-16730'
Feb 03 16:45:21 cow-lan1 abrt-server[18873]: Unsupported container technology
Feb 03 16:45:21 cow-lan1 abrt-server[18873]: Lock file '.lock' was locked by process 18876, but it crashed?
Feb 03 16:45:23 cow-lan1 abrt-applet[3170]: g_app_info_should_show: assertion 'G_IS_APP_INFO (appinfo)' failed
Feb 03 16:45:23 cow-lan1 abrt-notification[18924]: [🡕] Process 18749 (tf_linux64) crashed in ??()
