Hi,
I'm narrowing this down to the Steam Client itself.
I had another crash today and no game was running. Again, the SIGSEV in klog points to libdbus.
There have been other reports of warnings and assertion failures in libdbus with Steam, which point to a bug in either libdbus or code that calls into it. I know SDL has had bugs in the way it interacted with libdbus in the past, so that's one possibility.
Is there anything you can do that causes this to happen more frequently, like interacting with a particular bit of the Steam UI or your desktop environment's UI?
Do you use/have any of these services? ibus, fcitx, rtkit, upower. (Those are the D-Bus services that SDL is known to interact with.)
Another thing you could try is to run Steam from a terminal (Konsole, xterm or similar), and if it crashes, copy its recent output from that terminal into this bug report.
Perhaps also useful: If you export DBUS_FATAL_WARNINGS=1, Steam (and games) will be more likely to crash with a somewhat useful warning if they use libdbus wrong or encounter a libdbus bug, which might help us to understand what's crashing and why.
The crashes are kind of daily now that I've noticed them.
I don't do anything in particular with Steam when they happen. It's usually running foreground or minimized on some other workspace, or I'm playing a game.
I cannot pinpoint a particular thing that I do that reliably triggers the crashes.
I took the habit of opening it in a terminal to try and see if I could catch something.
Last time this was the console output:
(steam:327058): GLib-GObject-CRITICAL **: 18:23:42.714: g_type_instance_get_private: assertion 'instance != NULL && instance->g_class != NULL' failed
Opted-in Controller Mask for AppId 0: 0
Opted-in Controller Mask for AppId 0: 0
Opted-in Controller Mask for AppId 0: 0
[351970]Non-Steam Controller Configs Enabled: 1
Opted-in Controller Mask for AppId 351970: 0
Opted-in Controller Mask for AppId 413080: 0
assert_20200414163841_1.dmp[337539]: Uploading dump (out-of-process)
/tmp/dumps/assert_20200414163841_1.dmp
/home/darkeox/.local/share/Steam/steam.sh : ligne 722 : 327058 Erreur de segmentation (core dumped)$STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"
assert_20200414163841_1.dmp[337539]: Finished uploading minidump (out-of-process): success = yes
assert_20200414163841_1.dmp[337539]: response: CrashID=bp-dd6e57da-fd7e-4b95-889d-ace522200414
assert_20200414163841_1.dmp[337539]: file ''/tmp/dumps/assert_20200414163841_1.dmp'', upload yes: ''CrashID=bp-dd6e57da-fd7e-4b95-889d-ace522200414''
I've noticed it produces dump files, so here's the one for that crash.
I've now started Steam with env var you provided.
First and foremost, I can already report these warnings:
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.947: Trying to remove a child that doesn't believe we're it's parent.
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.948: Trying to remove a child that doesn't believe we're it's parent.
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.948: Trying to remove a child that doesn't believe we're it's parent.
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.948: Trying to remove a child that doesn't believe we're it's parent.
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.948: Trying to remove a child that doesn't believe we're it's parent.
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.948: Trying to remove a child that doesn't believe we're it's parent.
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.948: Trying to remove a child that doesn't believe we're it's parent.
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.948: Trying to remove a child that doesn't believe we're it's parent.
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.948: Trying to remove a child that doesn't believe we're it's parent.
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.948: Trying to remove a child that doesn't believe we're it's parent.
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.948: Trying to remove a child that doesn't believe we're it's parent.
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.948: Trying to remove a child that doesn't believe we're it's parent.
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.948: Trying to remove a child that doesn't believe we're it's parent.
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.948: Trying to remove a child that doesn't believe we're it's parent.
(steam:362824): LIBDBUSMENU-GLIB-WARNING **: 19:44:33.948: Trying to remove a child that doesn't believe we're it's parent.
Though this looks like the kind of messy errors that pops everywhere on Linux Desktop once you start using things through CLI.
I think the LIBDBUSMENU-GLIB-WARNINGs are normal; I'm not sure whether they indicate a bug in libdbusmenu-glib or in Steam or what, but either way they seem harmless.
Another crash today after 4.92 hour of operation at 14:37 doing essentially nothing (no user interaction that is).
(steam:371806): Gtk-WARNING **: 09:47:28.819: gtk_disable_setlocale() must be called before gtk_init()
[0416/102132.807472:WARNING:keyboard_code_conversion_x.cc(1441)] Unknown keycode:108
[500]Non-Steam Controller Configs Enabled: 1
Opted-in Controller Mask for AppId 500: 0
assert_20200416094217_1.dmp[382008]: Uploading dump (out-of-process)
/tmp/dumps/assert_20200416094217_1.dmp
No minidump written, nothing to upload.
No minidump written, nothing to upload.
No minidump written, nothing to upload.
/home/_user_/.local/share/Steam/steam.sh : ligne 722 : 371806 Erreur de segmentation (core dumped)$STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"
assert_20200416094217_1.dmp[382008]: Finished uploading minidump (out-of-process): success = yes
assert_20200416094217_1.dmp[382008]: response: CrashID=bp-bd5689fe-11fe-4d84-914b-7fa292200416
assert_20200416094217_1.dmp[382008]: file ''/tmp/dumps/assert_20200416094217_1.dmp'', upload yes: ''CrashID=bp-bd5689fe-11fe-4d84-914b-7fa292200416''
The LIBDBUS env var didn't catch anything it seems.
I DO have upower service enabled, but I'm not on a laptop.
Hello @DistantThunder - can you test and reproduce this against the Steam beta client? You indicated you are not using beta - which is consistent with your Apr 4th build date. There is a fix that may affect this problem in Steam beta.
Pending confirmation above, will be closing as duplicate of https://github.com/ValveSoftware/steam-for-linux/issues/6911
Hi, I'm not very comfortable with the beta since I've heard horror stories about bugs it may introduce, but for this particular issue, I confirm I haven't crashed ever since switching to Beta.
Your system information
I understand this issue may be closed or ignored due to not running on an officially supported distribution. I still found the issue relevant to report and hopefully get solved.
Apr 4 2020, 00:37System Information
Please describe your issue in as much detail as possible:
I was playing native Rise of The Tomb Raider in multiplayer mode when the application crashed along with the Steam Client unexpectedly in the middle of gameplay.
local/dbus 1.12.16-5Steps for reproducing this issue: