"bwrap: Can't make symlink at /home: File exists" when running flatpak steam on fedora atomic workstation #1278
Comments
|
Sounds similar to #959 |
|
Retested with fedora-workstation:fedora/27/x86_64/workstation flatpak version 0.10.2.1 Error still persists. |
|
I haven't fully tried to debug this but offhand I suspect flatpak (or possibly bwrap) needs to chase symlinks when setting up bind mounts. |
On atomic /home is a symlink to /var/home, so when we bind-mount the persistent directories we need to early-resolve the symlinks to avoid running into issues with /newroot. In most cases we do this already by calling flatpak_bwrap_add_bind_arg, but the persistent dir case did not, because that function required the target to exist, and the persistent directoried might not. However, these days flatpak_bwrap_add_bind_arg is fine if the base dir doesn't exists but the target does, which is the case here, so we can use it now. This fixes e.g. steam: flatpak#1278
On atomic /home is a symlink to /var/home, so when we bind-mount the persistent directories we need to early-resolve the symlinks to avoid running into issues with /newroot. In most cases we do this already by calling flatpak_bwrap_add_bind_arg, but the persistent dir case did not, because that function required the target to exist, and the persistent directoried might not. However, these days flatpak_bwrap_add_bind_arg is fine if the base dir doesn't exists but the target does, which is the case here, so we can use it now. This fixes e.g. steam: #1278 Closes: #1422 Approved by: cgwalters
On atomic /home is a symlink to /var/home, so when we bind-mount the persistent directories we need to early-resolve the symlinks to avoid running into issues with /newroot. In most cases we do this already by calling flatpak_bwrap_add_bind_arg, but the persistent dir case did not, because that function required the target to exist, and the persistent directoried might not. However, these days flatpak_bwrap_add_bind_arg is fine if the base dir doesn't exists but the target does, which is the case here, so we can use it now. This fixes e.g. steam: #1278 Closes: #1422 Approved by: cgwalters
|
Issue solved! Retested with ostree:https://fedora-workstation:fedora/28/x86_64/workstation flatpak --version |
|
On Fedora Workstation 28, when I run flatpak run com.valvesoftware.Steam I get the following error message bwrap: Can't make symlink at /home/username/.local: File exists flatpak --version Error still here. I make a symlink for ~/.local to another driver before. Seems like my symlink cause this error. |
|
Hi. I think this need to be reopened because the updates do not correct issues such as flathub/org.darktable.Darktable#6 . I believe that there are further issues, and this should be examined better. Thanks, |
|
I have the same problem:
Flatpak 0.11.8.3 (Tumbleweed version) |
|
I don't have Atomic, but I still get this error. Why is steam screwing with this, anyway?? |
|
Workaround for Steam, just delete or move the ~/Pictures folder (mine was a symlink) and then restore it after your done playing/using it. |
|
I'm having the same problem on nixOS, it says it wants to symlink |
|
@RossComputerGuy any workarounds |
|
so supposedly in this image there is no filesystem access in the first place and yet it still wants to access my .icons directory steam will not even follow the theme is there a way to just ignore bwrap error and move on containers/bubblewrap#577 |
On Fedora Atomic Workstation, when I run
flatpak run com.valvesoftware.SteamI get the following error message
bwrap: Can't make symlink at /home: File existsThe flatpak version is 0.10.2. I cleanly installed Atomic Workstation and
rpm-ostree statusgives:Version: 27.26 (2017-12-22 14:44:29)
BaseCommit: d0da7129dd883735b91c3c1d2e041974d13689ae53b5da5bb1dc4d3fe07cfd66
I'd like to add that so far with atomic workstation everything else worked like a charm and that all the other flatpaks I've installed run without issues.
The text was updated successfully, but these errors were encountered: