I can not login after "today" steam-linux-clietn update
even after cleaning ~/.steam/steam steam crash after "phone code confirmation"
I can duplicate this on Arch Linux. Originally didn't think I could launch it at all but removing config.vdf did allow me to log in. Also, I was getting this in the logs:
process 25408: arguments to dbus_connection_ref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file dbus-connection.c line 2686.
I had the same issue, starting steam with STEAM_RUNTIME_PREFER_HOST_LIBRARIES=0 works for me.
Thanks, STEAM_RUNTIME_PREFER_HOST_LIBRARIES=0 fixes it for me too.
Steam seems to work OK, but I get an error message in the terminal when running this way though. The following messages keeps repeating every few seconds:
process 3492: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../dbus/dbus-connection.c line 2794.
This is normally a bug in some application using the D-Bus library.
process 3492: arguments to dbus_connection_ref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../dbus/dbus-connection.c line 2656.
This is normally a bug in some application using the D-Bus library.
My installed version of dbus is:
dbus-1.10.20-x86_64-1
dbus-compat32-1.10.20-x86_64-1compat32
Hello @af7567, can you pin the steam runtime variant of libdbus with ln -s ${HOME}/.local/share/Steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/libdbus-1.so.3 ${HOME}/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_32/libdbus-1.so.3 and see if that works as a workaround.
I think I have the same issue in #5102 that fix @kisak-valve has works for me.
I get those messages though.
This is normally a bug in some application using the D-Bus library.
process 8358: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../dbus/dbus-connection.c line 2794.
@kisak-valve Creating that symlink fixes steam startup for me when the password is saved.
I did also try downgrading my nvidia driver to 381.22 again earlier but still got the crash, so this is unrelated to the new nvidia drivers it was just a coincidence.
I'm not sure if this should be a separate bug or not but I'm also getting other random crashing if I don't set STEAM_RUNTIME_PREFER_HOST_LIBRARIES=0 - just tried to launch Pyre and the Steam client crashed before it even got to the game launch. Setting the above variable fixed it, and as I mentioned before I'm also impacted by the 'save password' crash so I suspect it's the same bug and not something different.
No dbus error on this one though, instead:
steam.desktop[7941]: Assert( CClientPipe::BWriteAndReadResult: BWaitResult failed, disconnected ):../common/pipes.cpp:766
kernel: CIPCServer::Thr[8134]: segfault at 657f ip 00000000ed75cf74 sp 00000000ecafedd0 error 4 in steamclient.so[ed611000+1396000]
steam.desktop[7941]: assert_20170728100259_1.dmp[8348]: file ''/tmp/dumps/assert_20170728100259_1.dmp'', upload yes: ''CrashID=bp-4c95419f-d305-46b5-a9a9-c0de62170728''
@kisak-valve Hit the same issue. Symlink fixes things for me as well on slackware-current (32bit) with latest updates and beta opt-in.
Pinning libdbus works for me as well, on Arch Linux x64.
I guess there's quite a large gap between Steam's libdbus 1.4.18 (libdbus-1.so.3.5.8) and Slackware's 1.10.22 (3.14.13).
I do not have a pinned_libs_32 directory so unfortunately that solution would not work for me. Experiencing the same issue however.
Is anyone else who is using the dbus symlink work around getting really long game loading times now? I notice it most with csgo where it shows a black screen for 2 mins before showing the valve logo. Then when I get to the main menu it takes another 10 secs before showing my rank and the hydra menu. It was a lot faster last week, so I wondered if it is something to do with all the dbus warning messages shown in the terminal.
edit: After using gdb to try and work out why csgo is loading slowly it seems to be something to do with the nvidia 384.59 drivers, not this dbus problem.
I can't duplicate that at all, I have the dbus errors after pinning the symlink but CSGO still starts up fast for me.
I am getting errors when loading anything in the CEF though, CSGO's blog page is missing and Steam's store and community pages are just showing a 'Bad Request' http error.
Edit: Can no longer duplicate the above either, probably unrelated.
notice that i also had this problem on slackware, but using mesa drivers (-git versions). the workaround solved the problem
This has not happened for a long time so it seems to be fixed now.
Just happened to me, restarting system usually fixes this.
munir@abc:~/go/src/gksgsrvr$ steam
Running Steam on ubuntu 18.04 64-bit
STEAM_RUNTIME is enabled automatically
Pins up-to-date!
Installing breakpad exception handler for appid(steam)/version(1522709999)
Installing breakpad exception handler for appid(steam)/version(1522709999)
Installing breakpad exception handler for appid(steam)/version(1522709999)
Gtk-Message: 15:52:37.985: Failed to load module "gail"
Gtk-Message: 15:52:37.985: Failed to load module "atk-bridge"
dbus[11148]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
crash_20180417155235_1.dmp[11156]: Uploading dump (out-of-process)
/tmp/dumps/crash_20180417155235_1.dmp
/home/munir/.local/share/Steam/steam.sh: line 927: 11148 Aborted (core dumped) $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"
crash_20180417155235_1.dmp[11156]: Finished uploading minidump (out-of-process): success = yes
crash_20180417155235_1.dmp[11156]: response: CrashID=bp-4cb1117f-5513-490a-88a3-97c142180417
crash_20180417155235_1.dmp[11156]: file ''/tmp/dumps/crash_20180417155235_1.dmp'', upload yes: ''CrashID=bp-4cb1117f-5513-490a-88a3-97c142180417''
@af7567 probably should re-open?
having the exact same problem as @munirehmad after updating my ubuntu 17.10 to 18.04
@af7567 should re-open this
@munirehmad i'm able to open the steam using the following command "STEAM_RUNTIME_PREFER_HOST_LIBRARIES=0 steam"
from here
Same issue. I've installed steam on ubuntu 18.04 and it worked fine for the first time. After that i've installed some packages, tested some steam games under wine (perhaps that's unrelated) and now my native steam fails to launch. Setting that enviroment variable fixes this issue. Tested this on current release and beta release.
UPDATE: I've managed to fix this by deleting "~/.local/share/Steam". After Steam re-downloaded itself everything worked fine. I suppose something gone wrong when i copied my old home folder to to this new installation of ubuntu.
This bug has reappeared as of June 13 2021 on Arch Linux with NetworkManager and Docker running - unable to determine if that's relevant but it's my only other system change.
Your system information
Please describe your issue in as much detail as possible:
Steam is crashing today when trying to login automatically, which is how I normally have it logging in. I have found that if I remove config.vdf then I need to enter my password and steam guard again and steam client starts up OK. If I tell it to remember the password again then the next time I start steam client it crashes again.
Steps for reproducing this issue:
attached minidump and stdout
steamautologcrash.zip
edit:
I did also have some system updates today, in case that could have triggered the problem the updated packages are libidn2-2.0.3, libinput-compat32-1.8.1, gdk-pixbuf2-2.36.7, gdk-pixbuf2-compat32-2.36.7, nvidia-kernel-384.59, nvidia-driver-384.59.