-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
steam launcher crashes on second run (debian sid in a chroot on debian wheezy) #3501
Comments
Valve note: The failure report is a segfault in dbus by way of glib from libnm. |
Saw a steam client update.
|
I had the exact same issue when running Debian Jessie in a chroot on a Debian Wheezy. Thanks to the "Valve note" above, I think the segfault is related to not having dbus daemon running. Starting dbus seems to help for me (I didn't do any thorough testing though):
|
I can confirm steam runs after starting the dbus daemon inside the chroot |
I'm having this problem in slackware 64 bit with dbus running. I'm not using networkmanager so maybe that's it, but networkmanager really shouldn't be required for anything steam is doing. It worked fine the first time. Backtrace:
|
I don't have NetworkManager running either (not in or outside the chroot). Do you really have the dbus-daemon running inside the chroot? Easy way to check it outside the chroot:
You should see one root owned dbus-daemon pointing to your dbus inside the chroot. |
I'm not using any chroot unless the installer made one, I have the alien multilibs and just extracted the install script from the debian package and ran it. I just had to change the line LAUNCHSTEAMBOOTSTRAPFILE= to the correct location. It shouldn't be able to make a chroot because it doesn't have root permissions.
Anyway I have found a workaround: just don't check "remember my password" when you login. I guess it's trying to communicate with some password manager over dbus and doesn't bother checking if it's actually there. Deleting .local/share/Steam/config allowed me to login again on an existing installation. |
I am still experiencing this issue, on Gentoo GNU/Linux on amd64. I am using the runtime libraries packaged with steam, and, if I issue "steam --reset", steam will start the first time, but after that, it will always segfault on line 729 of steam.sh. starting steam with DEBUGGER=gdb, I can see that the segmentation fault occurs on libdbus-1.so.3, as steam seems to be trying to do something networkmanager-related. I get the same issue even after starting dbus, but I did not try without checking "remember my password". |
njsg: Are you running the Steam client in a chroot? |
I don't think so, unless Steam starts a chroot by default. I'm running steam through /usr/bin/steam, which seems to be a wrapper script made by Valve, which calls the steam.sh under $HOME/.local/share/Steam |
could somebody with a fully working install list their dbus services so we can see what is causing the issue (https://unix.stackexchange.com/questions/46301/a-list-of-available-dbus-services) |
I think I have only the system bus running. |
I suppose we should open a separate bug for the issue that still exists without a chroot? |
Yes. |
Issue 3580 filled: #3580 |
Tried running Steam inside my chroot after some time and decided to test some more based on the insight found in all the comments here, plus #3580. I can run steam fine with "save password" unchecked. If I check it I get the segfault. To avoid steam segfaulting I need to start dbus. I originally closed the issue because I thought it had been fixed with the latest update but I now realize it was just due to the fact I had not checked the "save password" box after "steam --reset". Since steam still cannot run fine with "save password" checked and no dbus daemon I think this issue needs to be re-opened. If steam cannot run inside a chroot or without a dbus daemon running, it should tell the user and not die in a segfault. |
dieeasy, can you please list your dbus services using the command linked by 21isgonnabeagoodyear? I ask because, in my case (while I am not running Steam inside a chroot), I don't get it to stop crashing even after I start dbus, so it would be interesting to know if there is some dbus service (if that's the right name) that I'm missing. If you catch some message with dbus-monitor that looks relevant, can you see what is it being addressed to? |
Here is my list of dbus services. It's the same inside and outside the chroot, both with dbus stopped or started: |
Hmm, could |
Looks like this has fallen out of the Steam radar. With the release of Debian Jessie on April 25th the steam client can be run fine on a Debian stable so the need for a chroot has dropped even more. Please note that, with the advent of systemd, running a service in a chroot is no more possible (see the changing roots post in the "systemd for administrators" series) so lacking dbus goes from very likely to 100% sure on recent systems. Using systemd-nspawn is probably not a solution (fails silently in my test). I still believe this should be addressed, since crashing on a dbus issue looks like a more general issue than saving a password at login time. If that's not the case, this could still benefit from a small explanation about what's the real problem and why it will not get fixed, then closing the issue. @Plagman: would you mind updating the status of this issue? |
I can confirm this issue still happens, for me using a Ubuntu Bionic (18.04) chroot. Launching dbus via Now it crashes instantly on launching a game, according to the logs because of not being able to find an audio device. That's unrelated to this issue though. |
I am running Steam with Docker https://git.nixaid.com/arno/steam/src/branch/master/Dockerfile in Here is what solved my problem:
I am not passing to a container anything If this still does not help you, then you can remove |
Steam using Chromium? It's about NSS ERROR CODE -8018 I think |
I run steam inside a debian sid chroot on a debian wheezy host. Both are 64-bit, but I also tried a 32-bit chroot (running steam with "setarch i386") and I got the same results. I use an nVidia Quadro 600 video card with drivers version 319.82 (319.82-1~bpo70+2 from wheezy-backports).
It all worked for months. After a steam client update it started briefly showing the verification progress bar and suddenly disappearing, giving no other visual feedback. Launching it from the console revealed a segfault. I think I can reproduce it by re-installing the client.
I have steam-launcher package version 1.0.0.49 installed from "http://repo.steampowered.com/steam/ precise/steam amd64". To test a fresh steam launch I moved my ~/.local.share/Steam/SteamApps dir our of the way, removed
and launched steam from the console.
This is what I get:
...
This is where the login window appeared. After a little while I got these other console messages:
This is when I entered the verification code, logged in, got a working steam client (with no installed games of course) and finally logged out:
After the first successful run, just launching it again produces the following console output:
Is there something I can do to help debug the issue? I would appreciate getting rid of this problem and be able to use steam again.
The text was updated successfully, but these errors were encountered: