protonscr

Can't log in after update

steamopen Steam client
ValveSoftware/steam-for-linux#8837 · opened 2022-10-08 by michaelneverwins · updated 2022-10-22 · 6 comments · github
Mmichaelneverwins 2022-10-08 github

Your system information

  • Steam client version (build number or date): Startup - updater built Oct 6 2022 23:32:04
  • Distribution (e.g. Ubuntu): Linux Mint 20.3
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

I logged into Steam, checked for updates, and installed them. Upon restarting Steam, I saw the new log-in window. I typed my username and password, and got the Steam Guard prompt. When I entered my Steam Guard code, it brought me back to the username/password screen. I entered my username and password again, followed by another Steam Guard code, and now it's stuck like this:
Screenshot from 2022-10-07 22-17-17
I can close it with the "X" button, but if I try to log in again, I get exactly the same result: first Steam Guard attempt puts me back at the log-in window, and second Steam Guard attempt gets me stuck at this loading screen.

If I run steam from a terminal and go through this process, the logging is as follows:

[2022-10-07 22:12:14] Startup - updater built Oct  6 2022 23:32:04
[2022-10-07 22:12:14] Startup - Steam Client launched with: '/home/michael/.steam/debian-installation/ubuntu12_32/steam' '-nominidumps' '-nobreakpad'
[2022-10-07 22:12:14] Loading cached metrics from disk (/home/michael/.steam/debian-installation/package/steam_client_metrics.bin)
[2022-10-07 22:12:14] Using the following download hosts for Public, Realm steamglobal
[2022-10-07 22:12:14] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf'
[2022-10-07 22:12:14] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 10, source = 'update_hosts_cached.vdf'
[2022-10-07 22:12:14] 3. https://cdn.akamai.steamstatic.com, /client/, Realm 'steamglobal', weight was 10, source = 'update_hosts_cached.vdf'
[2022-10-07 22:12:14] 4. http://media.steampowered.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2022-10-07 22:12:14] Verifying installation...
[2022-10-07 22:12:14] Verification complete
[2022-10-07 22:13:15] Background update loop checking for update. . .
[2022-10-07 22:13:15] Checking for available updates...
[2022-10-07 22:13:15] Downloading manifest: https://client-update.akamai.steamstatic.com/steam_client_ubuntu12
[2022-10-07 22:13:15] Manifest download: send request
[2022-10-07 22:13:15] Manifest download: waiting for download to finish
[2022-10-07 22:13:16] Manifest download: finished
[2022-10-07 22:13:16] Download skipped: /steam_client_ubuntu12 version 1665100899, installed version 1665100899, existing pending version 0
[2022-10-07 22:13:16] Nothing to do

The last of the logging appears after entering the second Steam Guard code.

Steps for reproducing this issue:

  1. Try to log into the Steam client.
Mmichaelneverwins 2022-10-08 github

Well this is weird.

I tried doing it one more time, just to make sure I was right about some details. This time, I accidentally typed the second Steam Guard code incorrectly. I briefly saw an error message that looked like the one in #8835, but now I'm logged in.

Mmichaelneverwins 2022-10-08 github

Actually, I just tried closing Steam and opening it again, and now it gives me a connection error and I can only get to offline mode. So I think I might have been in offline mode when it seemed to be working. If this is all related to Steam network issues and not the Linux client, then feel free to close the issue. The way it got stuck at the Steam Guard log-in seemed very strange though. (Original issue doesn't seem network-related after all. See below.)

Mmichaelneverwins 2022-10-08 github

I just renamed my Steam folder (mv ~/.steam ~/.steam_backup) and started Steam again. I entered the username and password, and then the Steam Guard code, and it sent me back to the username/password screen again, but only for a couple of seconds. Then the log-in window closed and my library opened (and not just in offline mode; everything worked). That's still weird, but less broken.

After moving the original Steam folder back into place (mv ~/.steam ~/.steam_test; mv ~/.steam_backup ~/.steam), I entered my username, password, and Steam Guard code again. I had to sit on the username/password screen considerably longer (not quite a minute), but eventually it did close and my library opened (with no more connection error or offline mode, so that was either a red herring or something getting temporarily messed up by my meddling). Maybe if I had waited at the second username/password screen for 30+ seconds the first time, instead of trying to log in again, I wouldn't have gotten stuck trying to enter a second Steam Guard code. If the solution is "wait" then I suppose the problem is solved, but the fact that I can get stuck if I don't know I have to wait is probably a bug.

It's interesting that I don't have to wait as long when I'm using a fresh .steam folder. I guess it's just because nothing was installed there yet.

Ppoohzaza166 2022-10-08 github

i got the same problem on fedora 35

RReShout876 2022-10-08 github

I have a somewhat familiar issue #8835

Mmichaelneverwins 2022-10-22 github

Following a subsequent update, the default Steam Guard authentication method is just to press an "approve" button on my mobile app instead of entering a five-letter code, so this appears to be a non-issue now. However, I'm having trouble confirming whether the bug is actually fixed, because when I do try to use the five-letter code instead of another method, it's telling me the sign-in request is expired, which may be an entirely different issue (assuming I'm not just consistently misspelling the code)...

Nothing extracted yet.