GNOME Bugzilla – Bug 792300
Shotwell does not prevent library auto-unmount and follow-up errors in DirectoryMonitor
Last modified: 2021-05-19 15:11:20 UTC
Created attachment 366454 [details]
Log file with lots of DirectoryMonitor loop detected warnings
When the photo library is on an external disk with automount and timeout based auto-unmounting, then the following can be observed:
* after starting and loading the library, shotwell does not keep any file(s) or directory from the library open if it is not used constantly. (this can be checked with lsof)
* once the auto-unmount timeout is reached, the library directory will be unmouted
* then shotwell uses 100% of CPU, becomes unresponsive and fills the log with 'Directory loop detected' Warnings (cf. attachment)
While it's easy to workaround this bug by using a startup-script that does a "cd library-directory' before starting the real shotwell, it would be nice if the shotwell binary can ensure somehow that at least one file (or directory) from the library is always kept open to prevent that auto-unmount happens while shotwell is in use.
-- GitLab Migration Automatic Message --
This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/shotwell/-/issues/4897.