-
Notifications
You must be signed in to change notification settings - Fork 229
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
bubblewrap refuses to work with an unreachable automount #541
Comments
this was the command i used which had this issue: sudo bwrap \
--die-with-parent \
--ro-bind / / \
--tmpfs /tmp \
--dev-bind /dev/null /dev/null \
/usr/bin/bash But it's also reproducible with all flatpak apps I use. CopyQ to name one. |
The precise condition to reproduce this issue, is to make sure automount unit is active, and mount unit is stuck at mounting state (attempting to mount an unreachable filesystem), then all newly executed bubblewrap will also freeze, until the mount unit is timed out and failed, then bubblewrap will also fail complaining about the bubblewrap will not freeze / throw error if only automount unit is active and mount unit is already failed. And of course it also won't freeze when mount unit is active. |
to make sure mount unit is stuck at mounting state, you can configure firewall to drop all packets. something's probably wrong with bubblewrap's bind mount handling. sorry if the issue looks messy, i was tired trying to troubleshoot the root cause of my flatpak apps not autostarting. |
for now setting automount path to I still don't know why is having automount in |
If you setup a systemd automount similar to this:
And place bwrap/flatpak application desktop file into xdg-autostart directory (~/.config/autostart),(← this is unnecessary. just an unreachable automount is enough to reproduce the issue) it'll stuck for a very long time then give up:For instance, ALL my flatpak apps refuse to autostart just because an automount exists, the same error spams in
journalctl
. Disabling the automount fixes the issue.> bwrap --version bubblewrap 0.5.0
The text was updated successfully, but these errors were encountered: