New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bwrap: Can't make symlink at /home/<username>/Pictures: File exists #2387
Comments
I have the same problem but with Music $ flatpak run com.valvesoftware.Steam bwrap: Can't make symlink at /home/oem/Music: File exists |
I've have the same with my ~/Music folder. I've read somewhere, and I'm sorry I cannot find the source anymore, that this is an issue with symlinks in ~ where ~ is persisted. This seems to have fixed this: I ran |
I have the same problem on nixOS except it wants to symlink |
Still an issue on 1.15.4 |
I'm getting a similar problem but its because i made a script that runs at startup to generate a symlink at
One thing that is worth noting is that if its a hardlink Flatpak wont complain, so the current workarounds:
PS: Maybe a way to fix this is to just clear all symlinks once the program closes/Just ignore the symlink if it already exists for some reason. |
Is there any way to workaround this by maybe changing something in Flatseal? |
Well… even removing the permissions does not work, see flathub/com.valvesoftware.Steam#887 However, there are obvious workarounds like removing the symbolic link or renaming it. See also #4894 (comment) for a wild idea that is said to partially work. |
As I found out replacing symlinks with fstab binds works too, and x-gvfs-hide flag hide it from Nautilus. |
* `--symlink` is now idempotent, meaning it succeeds if the symlink already exists and already has the desired target (containers/bubblewrap#549, flatpak#2387, flatpak#3477, flatpak#5255) * Report a better error message if `mount(2)` fails with `ENOSPC` (containers/bubblewrap#615, ValveSoftware/steam-runtime#637) * Fix a double-close on error reading from `--args`, `--seccomp` or `--add-seccomp-fd` argument (containers/bubblewrap#558) * Improve memory allocation behaviour (containers/bubblewrap#556, containers/bubblewrap#624) * Silence various compiler warnings (containers/bubblewrap#559) Resolves: flatpak#2387 Resolves: flatpak#3477 Resolves: flatpak#5255 Signed-off-by: Simon McVittie <smcv@collabora.com>
* `--symlink` is now idempotent, meaning it succeeds if the symlink already exists and already has the desired target (containers/bubblewrap#549, #2387, #3477, #5255) * Report a better error message if `mount(2)` fails with `ENOSPC` (containers/bubblewrap#615, ValveSoftware/steam-runtime#637) * Fix a double-close on error reading from `--args`, `--seccomp` or `--add-seccomp-fd` argument (containers/bubblewrap#558) * Improve memory allocation behaviour (containers/bubblewrap#556, containers/bubblewrap#624) * Silence various compiler warnings (containers/bubblewrap#559) Resolves: #2387 Resolves: #3477 Resolves: #5255 Signed-off-by: Simon McVittie <smcv@collabora.com>
* `--symlink` is now idempotent, meaning it succeeds if the symlink already exists and already has the desired target (containers/bubblewrap#549, flatpak#2387, flatpak#3477, flatpak#5255) * Report a better error message if `mount(2)` fails with `ENOSPC` (containers/bubblewrap#615, ValveSoftware/steam-runtime#637) * Fix a double-close on error reading from `--args`, `--seccomp` or `--add-seccomp-fd` argument (containers/bubblewrap#558) * Improve memory allocation behaviour (containers/bubblewrap#556, containers/bubblewrap#624) * Silence various compiler warnings (containers/bubblewrap#559) Resolves: flatpak#2387 Resolves: flatpak#3477 Resolves: flatpak#5255 Signed-off-by: Simon McVittie <smcv@collabora.com>
Linux distribution and version
Fedora 29
Flatpak version
1.0.6
Description of the problem
Cannot start steam, has worked in the past.
I've seen this before, and then it went away or I deleted the symlink and let steam recreate it or something. Why does this keep coming up? Why does steam care about these directories that my Desktop Env manages? This is non-standard behavior. Steam is already using .local/share/flatpak/app/... . Why does steam care about anything in $HOME?
Several other similar bugs exist, but the closest one is bug #1278, which is closed, yet he problem still exists.
Steps to reproduce
$ flatpak run com.valvesoftware.Steam
bwrap: Can't make symlink at /home/pdestefa/Pictures: File exists
The text was updated successfully, but these errors were encountered: