Open lufia opened 3 weeks ago
Hello @lufia, your symptoms resemble the discussion on #9776. Please give that issue report a read and see if it's relevant to you.
Hi @kisak-valve
I had read that issue you mentioned, I think that issue is very similar to this. However, I couldn't understand what I should do to fix this because that's author commented:
I'm not sure what did it to be exact...
I checked mounts
$ grep /run/user /proc/$(pidof -s steam)/mounts
tmpfs /run/user/60331 tmpfs rw,nosuid,nodev,relatime,size=3255252k,nr_inodes=813813,mode=700,uid=60331,gid=60331,inode64 0 0
$ grep /doc /proc/$(pidof -s steam)/mounts
portal /run/flatpak/doc fuse.portal rw,nosuid,nodev,relatime,user_id=60331,group_id=60331 0 0
Today I noticed that /run/user/60331/doc is symbolic link refers to /run/flatpak/doc.
Therefore, I now suspect XDG Desktop Portal wouldn't implement flock
operation yet if the error message is correct.
Current versions in my Arch Linux box:
@kisak-valve
I'm not sure whether it will be merged or not, I created a PR to xdg-desktop-portal repository to merge a patch that is to fix this issue. https://github.com/flatpak/xdg-desktop-portal/pull/1353
But, the patch would add only non-blocking operations of flock(2) because blocking ops could block entire xdg-document-portal filesystem.
I have a question: Steam client might involve flock(2) with blocking operation?
For now, Steam works well with an external drive.
Your system information
Please describe your issue in as much detail as possible:
My host have an external USB SSD that usually mounted on /run/media/lufia/games.
A few days ago, because my laptop's storage is almost full, I moved large games by
Steam > Settings > Storage
tool.After Steam client was restarted I noticed that Steam does not recognize the games I moved to external USB SSD; they are not installed. Also Steam client can't install new game I bought to the external USB SSD. Both these two cases above Steam client prints the same errors "flock (FILE) LOCK_SH failed. errno = 38"
(FILE) is such as:
Flatpak's permissions
I have tried
I have tried to get shared lock on the host directly, it worked:
I also tried to get shared lock within flatpak, it failed:
Steps for reproducing this issue: