Option to rescan library directory
Submitted by an unknown user
Link to original bug (#718493)
Description
---- Reported by shotwell-maint@gnome.bugs 2012-01-07 06:37:00 -0800 ----
Original Redmine bug id: 4572
Original URL: http://redmine.yorba.org/issues/4572
Searchable id: yorba-bug-4572
Original author: Brian Walton
Original description:
It would be advantageous to be able to rescan the library directory for changes during run-time.
I share the photo repository (but not the shotwell database - as recommended) and other users may add, remove or change files (e.g. add tags) in that repository. Such changes are not reflected in other instances until shotwell is restarted. One may also change the content of the library directory from another client (command line / nautilus) which may not show in shotwell until a restart.
I suggest / request a button / menu option to rescan the library directory. Maybe this could be a generic feature to rescan the currently selected tree item and could be presented in the context menu.
Related issues:
- related to shotwell - 2878: Support directory monitoring over network shares (Open)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:47:00 -0700 ----
History
Comment 1
Updated by Adam Dingle almost 2 years ago
- Status changed from Open to 5
- Resolution set to worksforme
This feature already exists. In the Preferences dialog, check the box "Watch library directory for new files". When this box is checked, Shotwell will automatically notice changes in the library directory.
Comment 2
Updated by Brian Walton almost 2 years ago
This is not working for me (I have this option enabled). The library directory is on a nfs share. Does the auto-monitor feature work with such confgiuration? (I am not able to change the status of this issue from "Closed").
If I add files to the directory, a running instance of shotwell does not show these. If I restart that instance of shotwell, it performs an automatic import and subsequently shows the new files. This is also true for deleting and changing.
How often does shotwell check for modifications, additions and removals in the library directory?
Comment 3
Updated by Adam Dingle almost 2 years ago
Brian,
directory monitoring in Shotwell is known not to work over network shares: see #2878 (closed). Further comments are welcome on that ticket.
By the way, Shotwell does not check for modifications, additions and removals periodically. Instead, it asks the underlying GIO library to notify it whenever any change occurs in the library directory.
Comment 4
Updated by Brian Walton almost 2 years ago
Okay, understood. I will look at issue #2878 (closed). There seem to be use cases that support my initial request. If the repository is on a network share or the user had chosen not to enable checking for file changes, the user may want to manually trigger an update. At least until a solution for issue #2878 (closed) is implemented, will you consider adding the feature to manually trigger an update?
Comment 5
Updated by Adam Dingle almost 2 years ago
Feel free to file a separate ticket for that if you like. I don't think it will be a high priority, though, since this affects a relatively small number of users (I think that few users will have their library on a network drive) and there's an easy workaround: simply restart Shotwell to cause another library scan.
Comment 6
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Invalid
--- Bug imported by chaz@yorba.org 2013-11-25 21:57 UTC ---
This bug was previously known as bug 4572 at http://redmine.yorba.org/show_bug.cgi?id=4572
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED INVALID