You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Flatpak of an app, and portals, I use some file X, then I quit from the app, try to dismount the disk or USB stick or LUKS container that file X resides on, and get a "can't unmount because busy" error. I do something like:
and find out that a portal process still has file X open. I have to kill the process to be able to unmount the drive.
Before you say this is an app bug, go file against the app, I've seen it in multiple apps and distros and DEs, which leads me to think perhaps the portal specification or guidance or API maybe is lacking in this area. Is there a way for an app to tell the portal process to let go of the file ? Is this advertised to app developers ? Today the UX of the overall system can be bad because of this issue. What can be done to improve it ? Thanks.
The text was updated successfully, but these errors were encountered:
Same issue as #689. If someone knows how xdg-document-portal (the FUSE filesystem that makes files available to sandboxed apps) can avoid holding fds open indefinitely, but still work correctly, then pull requests are welcome.
When using Flatpak of an app, and portals, I use some file X, then I quit from the app, try to dismount the disk or USB stick or LUKS container that file X resides on, and get a "can't unmount because busy" error. I do something like:
and find out that a portal process still has file X open. I have to kill the process to be able to unmount the drive.
Before you say this is an app bug, go file against the app, I've seen it in multiple apps and distros and DEs, which leads me to think perhaps the portal specification or guidance or API maybe is lacking in this area. Is there a way for an app to tell the portal process to let go of the file ? Is this advertised to app developers ? Today the UX of the overall system can be bad because of this issue. What can be done to improve it ? Thanks.
The text was updated successfully, but these errors were encountered: