You are not logged in.

#1 2021-02-10 18:43:30

SilverMight
Member
Registered: 2017-11-20
Posts: 25

Steam completely sandboxed to ~/.local/share/Steam

Hello,

Recently I was forced to reinstall Steam, (deleting .steam and .local/share/Steam), however I've noticed that Steam is now completely sandboxed to it's own directory. I can't get out of it using any of Steam's file dialogs, and adding a new library presents me only with a blank screen that shows "/", which must be some fake drive, because attempting to create a folder in it creates that it is read-only.

I had been using Flatpak to temporarily remedy a situation before, but even after completely uninstalling that it hasn't changed anything. It's definitely not using Flatpak to run. I've tried using steam --reset, repeatedly deleting the ~/.local/share/Steam and ~/.steam files, uninstalling and reinstalling the Steam package, etc.

Offline

#2 2021-02-10 23:41:56

SilverMight
Member
Registered: 2017-11-20
Posts: 25

Re: Steam completely sandboxed to ~/.local/share/Steam

Something else I noticed... Wine has the same issue.
Opening wine cmd and trying to run dir in the root of the directory presents this

wine: Read access denied for device L"\\??\\Z:\\", FS volume label and serial are not available.
0114:fixme:file:errno_to_status Converting errno 75 to STATUS_UNSUCCESSFUL
0114:fixme:file:errno_to_status Converting errno 75 to STATUS_UNSUCCESSFUL
Volume in drive Z has no label.
Volume Serial Number is 0000-0000

Directory of Z:\

File not found.

Offline

#3 2021-04-02 21:22:15

rmcgu
Member
Registered: 2021-04-02
Posts: 1

Re: Steam completely sandboxed to ~/.local/share/Steam

SilverMight wrote:

Something else I noticed... Wine has the same issue.
Opening wine cmd and trying to run dir in the root of the directory presents this

wine: Read access denied for device L"\\??\\Z:\\", FS volume label and serial are not available.
0114:fixme:file:errno_to_status Converting errno 75 to STATUS_UNSUCCESSFUL
0114:fixme:file:errno_to_status Converting errno 75 to STATUS_UNSUCCESSFUL
Volume in drive Z has no label.
Volume Serial Number is 0000-0000

Directory of Z:\

File not found.

I was getting the

fixme:file:errno_to_status Converting errno 75 to STATUS_UNSUCCESSFUL

failure from wine too, but just for my home directory. Listing z:\ was fine, but my home directory was invisible and unbrowsable.

Errno 75 is:

$ errno 75
EOVERFLOW 75 Value too large for defined data type

I dug into it with gdb, and it turned out glibc was raising that error while converting timestamps from 64-bit to 32-bit. My home directory had somehow ended up with an atime in the year 2040, which meant the value could no longer be represented as a 32-bit time[1]. Wine is the only 32-bit program I have on my system.

You can check the timestamps with:

stat /path

and update access/modification times to now with:

touch /path

In your case it looks like your root directory could be affected by the same thing.

[1] https://en.wikipedia.org/wiki/Year_2038_problem

Offline

#4 2021-04-23 19:26:01

Wang
Member
Registered: 2016-01-23
Posts: 10

Re: Steam completely sandboxed to ~/.local/share/Steam

I had the exact same problem as @SilverMight (also after re-installation and flatpak). Indeed @rmcgu is right,

stat /

gives me

File: /
Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 10304h/66308d   Inode: 2           Links: 18
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2115-12-18 14:28:49.604609696 +0100
Modify: 2021-01-21 11:46:28.095624324 +0100
Change: 2021-01-21 11:46:28.095624324 +0100
Birth: 2016-06-27 08:31:48.000000000 +0200

After I update the time with

sudo touch /

the 'Acess' date is updated and Steam is able to read all the directories! Thanks to @SilverMight and @rmcgu, I would never be able to solve the problem by myself smile.

Offline

#5 2021-06-09 10:36:10

krnlpk
Member
Registered: 2010-01-03
Posts: 25

Re: Steam completely sandboxed to ~/.local/share/Steam

I just had this same issue with my home directory having an atime in February 2040, which I also solved by `touch`ing it. Did you guys ever find out what was causing this issue?

Do you perhaps also use ZFS on your root partition, like I do?

Offline

Board footer

Powered by FluxBB