protonscr

New beta client doesn't remember login details.

steamopen Steam clientDistro Family: Fedora
ValveSoftware/steam-for-linux#6527 · opened 2019-09-26 by joker-119 · updated 2021-02-19 · 7 comments · github
Jjoker-119 2019-09-26 github

Your system information

  • Steam client version (build number or date): Built 9/23/2019 @ 16:07:56
  • Distribution (e.g. Ubuntu): Fedora 30
  • Opted into Steam client beta?: [Yes/No] Yes
  • Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

Everytime I start steam, even with the "Remember Me" box checked, I am prompted for both a username and password.

Steps for reproducing this issue:

  1. Enter login details, with the "Remember Me" box checked.
  2. After logging in, exit steam.
  3. Open steam.

Expected result:
Steam remembers my account info and logs me in automatically.

Kkisak-valve maintainer 2019-09-26 github

Hello @galaxy119, this is most likely a duplicate of #5030 / #5035. Closing in favor of the existing issue reports.

Jjoker-119 2019-09-26 github

That issue is over 2 years old, and this has only started occuring for me since the last beta update (and reverting to the non-beta client solves the issue for me), so I'm not sure if this is really the same issue.

Kkisak-valve maintainer 2019-09-26 github

Fair enough, if anyone else happens across this issue report, please only comment here if you are also not affected when using the pre-Library beta client, otherwise use #5030.

Jjoker-119 2019-09-26 github

I've been doing a little digging around and think I've found the problem.

While many of the others in the previously linked issues seem to have this or a similar issue all the time, the latest 'workaround' they posted does work for me aswell.

What's happening is, when the steam client starts up, it's copying the ~/.steam/registry.vdf file to registry.vdf.old, then deleting the current one. It then re-makes it because it's not there anymore.
Disallowing create/delete files permissions in that folder solves the problem, as steam can no longer delete the currenty registry and re-make it.

However unlike the other issue, I do not have to set the file as read-only, as it doesn't wipe the contents of the file, just deletes the file itself.
So this is an unrelated issue, but their workaround helped me figure out how to work around it myself.

To workaround:

  1. Start steam and login with the "Remember Me" box checked.
  2. Set the permissions for both your user and group for the ~/.steam directory to Access Files only.
  3. When you restart steam you should now automatically login.

Note: Do not set these permissions recursively, otherwise game updates, client updates, etc, will fail. Many games store options and even save files in their steamapps folder aswell, so this could cause other issues if you set this permission recursively.

Another note: If you are still having problems with it remembering who you are, you can use the workaround posted in the other issue, which involves setting the registry.vdf file as read-only.

LLuticus 2021-02-16 github

Just thought I'd throw my 2cents in on this because I've been dealing with this issue for, god, maybe years now and it's been driving me crazy.

I thought it was a steam bug that would eventually get fixed so I kind of just left it alone and never bothered fixing it. Anyway I happened to notice it doesn't happen on a new laptop I got so I figured I'd take a second look.

@galaxy119 seems to be right about the registry.vdf.old being the culprit. However I couldn't think of a good clean way to prevent file deletion without messing with the file ownership and setting a sticky bit on the directory above, or making the file immutable via chattr +i, or by setting the permissions to remove write. None of those sat well with me as I thought they might mess up other things with steam, possibly break updating, or have some side effect or unintended consequence. Fortunately I noticed that the registry.vdf.old file had a file size of '0' and that to me looked... not right. I used cat to view the file's content and sure enough, it was blank. So I deleted the registry.vdf.old file and simply started steam. This seems to have resolved the issue for me.

You can verify this by watching the files change as you launch steam. Use the watch -n 1 "ls -al registry.*" command from inside the ~/.steam directory and launch steam. You can see it create a file registry.vdf000000000 where the 0's represent some random number, it seems. The file will show up and disappear a few times. That's the behavior that was happening when it WORKED, so that's what you want. For some reason the .old file was preventing that... some how.

I have also confirmed that having a symlink for the ~/.steam in my home to create a non hidden version (~/steam) for easy access does cause this problem to occur again for some god awful reason I can't understand. So if you have that, then use unlink ~/steam in your home directory to remove that as well. You should only have a ~/.steam.

I hope this advice helps anyone else facing this issue as it was driving me crazy!

Jjoker-119 2021-02-18 github

For me, after deleting the vdf.old file, the next time I start steam, it just re-creates it, again with 0 bytes, and gives me the all too familiar login screen again.

LLuticus 2021-02-19 github

@galaxy119 , I had that issue too if I had a ~/steam folder or symlink. Try double checking that you only have a ~/.steam folder (hidden). If you have a symlink then use unlink to remove it, otherwise mv the folder from steam to .steam and see if that helps. If that's not your issue then there's obviously something else going on that's outside of what was causing it for me.

Nothing extracted yet.