For me, the restart prompt is triggered every time I press OK in the Settings dialog.
Steps for reproducing:
I can confirm @Leeo97one's simpler repro.
same pb here, I though it was only my settings which were corrupted
Same here on Arch Linux with latest Steam runtime.
Information: https://gist.github.com/ml-/5cfc0530b114a0a835a53aae03c2b0a6
Arch Linux as well.
I see Arch (+Manjaro) people reporting this issue in here. Is this solely an Arch issue or can someone with another distribution also reproduce?
Distro independant.
Even in the beta client.
Yeah, I'd like to chime in that this issue is quite annoying. Especially for new users.
Fixed in next Beta.
Fixed in next Beta.
What do you mean by "next Beta"? The problem persists even after yesterday's update.
Same in the last update.
Maybe they are talking about the clean 64bits steam client, the one which is
properly packaged with most of its dependencies and does not expect a huge
mainstream distro?
(irony inside)
The safe assumption here is that there's a fix queued in the next beta branch off of the developer's version of Steam. Keep an eye out for a Steam client beta update with a larger set of patch notes compared to the small fixes that regularly get pushed.
OK, thanks for the clarification.
Per "Fixed settings dialog incorrectly always prompting for a client restart" in the 2019-01-16 Steam client beta update, please opt into the beta and retest this issue.
Yes, it's fixed now. You can add that to the long list of fixes in this patch
Thanks for retesting, fix has gone into the stable client as well.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
Nickname change in Settings triggers a Steam restart prompt. If Ok is pressed, Steam restarts, but with the old name, i.e. without changes. If Cancel is pressed (postponing the restart), the nickname is changed immediately, not requiring a restart. After a directly following manual restart the new nickname remains preserved.
The restart prompt should not appear in the first place. If it's required now, after the restart the nickname should be changed.
Steps for reproducing this issue: