Open neildarlow opened 2 years ago
Is there another instance of GNOME Boxes stuck in the background?
flatpak ps
and flatpak kill org.gnome.Boxes
No. The issue is evident after a fresh boot and login. The Boxes UI is shown and you can quit the application but then an instance is left running and flatpak ps shows this.
I noticed some issues with qemu locking the backing file and the xdg-desktop-portal document portal. By enabling --filesystem=host this issues seem to go away. I sent a flathub update to poke that hole in the sandbox for now until I can find a proper solution that works down the stack. Please, let me know if that fixes your issue too (after updating).
Hi Felipe,
More complex than I thought. I did have a concern that the issue might be related to home directories on Silverblue being under /var/home by default.
For Silverblue, filesystem=host probably isn't a great concern but it could be for less hardened distributions.
Thank you for your fast response on this. Yes, the change does fix the issue.
After updating Boxes to 42.0 and libosinfo 1.9 I have lost access to my virtual machine. Running Boxes at the command line reports:
The directory indicated does exist in my home directory and has sifficient read access e.g.: