Skip to content
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

Closed
PorcelainMouse opened this issue Dec 5, 2018 · 8 comments · Fixed by #5749
Closed

bwrap: Can't make symlink at /home/<username>/Pictures: File exists #2387

PorcelainMouse opened this issue Dec 5, 2018 · 8 comments · Fixed by #5749

Comments

@PorcelainMouse
Copy link

PorcelainMouse commented Dec 5, 2018

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

@ioogithub
Copy link

I have the same problem but with Music

$ flatpak run com.valvesoftware.Steam

bwrap: Can't make symlink at /home/oem/Music: File exists

@strootje
Copy link

strootje commented May 26, 2020

I've have the same with my ~/Music folder.
My Music folder is a symlink which points to an external drive.
I have to rename my ~/Music folder, after which steam starts file. Once steam is started I can rename the Music folder back again.

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:
#1971

I ran xdg-user-dirs-update --set MUSIC /mnt/nas/music

@RossComputerGuy
Copy link

I have the same problem on nixOS except it wants to symlink ~/.nix-profile.

@Justinzobel
Copy link

Still an issue on 1.15.4

@hideki2k02
Copy link

I'm getting a similar problem but its because i made a script that runs at startup to generate a symlink at /run/user/1000/discord-ipc-0

bwrap: Can't make symlink at /run/user/1000/discord-ipc-0: File exists

One thing that is worth noting is that if its a hardlink Flatpak wont complain, so the current workarounds:

  • Delete the Symlink that the program is complaining then run the program again
  • Using a hardlink (In my case i've replaced my startup script to create a hardlink)

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.

@shvetsnikita
Copy link

I have the same problem but with Music
$ flatpak run com.valvesoftware.Steam
bwrap: Can't make symlink at /home/oem/Music: File exists

Is there any way to workaround this by maybe changing something in Flatseal?

@rugk
Copy link

rugk commented Mar 7, 2024

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.

@shvetsnikita
Copy link

@rugk

As I found out replacing symlinks with fstab binds works too, and x-gvfs-hide flag hide it from Nautilus.

smcv added a commit to smcv/flatpak that referenced this issue Mar 27, 2024
* `--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>
smcv added a commit that referenced this issue Mar 27, 2024
* `--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>
GeorgesStavracas pushed a commit to GeorgesStavracas/flatpak that referenced this issue Apr 26, 2024
* `--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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants