The file really should be created with a $PID appended to it, because it is in a shared space where collisions can happen.
The file should be created somewhere in $HOME. Nobody else can delete it. (except root)
Every time I start Steam I am doing "sudo rm -f /tmp/steam_chrome_shmem".
And then when I quit Steam I do it again.
If I forget, my son coming to pc after me won't start Steam properly and have to reboot pc.
It's realy a pain...
Hello STEAM people, is it really so hard to fix it?
Confirm this one for latest stable Steam client.
It's just make Steam UI freeze.
Ping...
Reply.
scaronni píše v Po 25. 05. 2015 v 08:54 -0700:
Ping...
—
Reply to this email directly or view it on GitHub.
sorry if i'm in wrong section, couldn't find mac one
same problem: long steam response, couldn't find steam_chrome_shmem on sierra
any changes on names/routes?
Closing as the file name conflict was fixed some time ago.
Nothing extracted yet.
After exiting Steam, some files are left behind. This prevents other users logging into the system from using Steam.
Details:
This is the error that is printed in the log:
After exiting the client, the Chrome socket is left behind in /tmp with restricted permissions, preventing a new user that subsequently logs in the system from overwriting the file and thus starting the client.
A simple rm command in the Steam startup script should suffice in solving this, as the file it's recreated when starting again the client.
Thanks,
--Simone