After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 716912 - Better management of photo library on a removable media
Better management of photo library on a removable media
Status: RESOLVED OBSOLETE
Product: shotwell
Classification: Other
Component: general
unspecified
Other All
: Low normal
: ---
Assigned To: Shotwell Maintainers
Shotwell Maintainers
: 740038 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-12-12 04:59 UTC by Shotwell Maintainers
Modified: 2021-05-19 12:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-25 21:48:01 UTC


---- Reported by shotwell-maint@gnome.bugs 2010-12-12 08:59:00 -0800 ----

Original Redmine bug id: 2954
Original URL: http://redmine.yorba.org/issues/2954
Searchable id: yorba-bug-2954
Original author: Andrea Carpani
Original description:

I have photos on an external HDD and if I start shotwell and the HDD is
unplpugged all photos become “unavailableâ€. I then have to close it, plug
the HDD and restart shotwell and wait for a complete rescan (20k fotos take
quite some time).

Could it be possible to have a better management of this either by explicitely
flagging the Library location as “removable†in the preferences or by
detecting this somehow?

.a.c.

Andrea Carpani



---- Additional Comments From shotwell-maint@gnome.bugs 2010-12-20 15:08:00 -0800 ----

### History

####

#1

Updated by Adam Dingle almost 3 years ago

Yes, it can take a couple of minutes to mark an entire collection as offline
or online, which is a long time for the user to wait. I agree it would be nice
to improve this somehow.

####

#2

Updated by Andrea Carpani almost 3 years ago

Another issue related to photos on a removble media (not sure if it's a
separate ticket): my collection is on /media/%(=caps)DATA%/Foto where DATA is
the removable device mountpoint.

If I start shotwell and the device is unmounted the collection value in
preference changes to /data/media. I then remount the media and start shotwell
and it starts rescanning the whole /media/data device and not
/media/%(=caps)DATA%/Foto.

####

#3

Updated by Adam Dingle almost 3 years ago

@ancarpan,

Thanks for pointing out this last problem where the library root changes. That
was a previously unknown bug. I've ticketed that separately as#3000.



--- Bug imported by chaz@yorba.org 2013-11-25 21:48 UTC  ---

This bug was previously known as _bug_ 2954 at http://redmine.yorba.org/show_bug.cgi?id=2954

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 set on an open status.
   Dropping resolution 

Comment 1 Jim Nelson 2014-11-14 03:21:41 UTC
*** Bug 740038 has been marked as a duplicate of this bug. ***
Comment 2 edappere 2014-11-25 21:52:38 UTC
Hi,

Thanks Jim for merging my own bug report with this one. 

I am no developer so I really don't know how this issue with library stored on removable drive could be handled. The simple (naive ?) solution would be to mark the library as stored on a removable drive (in Shotwell's settings) and then, at each start of shotwell, check if the removable drive is available or not. The current script that checks if all files exist would not be triggered ... until removable drive is connected to the computer. In "disconnected mode" Shotwell would only display the thumbnails (no click on image for full-size view possible) but this should be explained in some sort of disclaimer in the settings (when checking "Library stored on removable drive").

As I write down all this I realize this would lead to a lot of modifications in Shotwell's code. I don't know if many people need this feature. Maybe there's a workaround that would be easier and faster to implement ? For example I tried to run the command "shotwell --no-runtime-monitoring" as mentionned in the FAQ but to no avail. Or maybe I should try some other options :
- export all my pictures in a small size on my laptop's hard-drive and browse this ?
- use another software than Shotwell ?

Any ideas or suggestions would be interesting.

Best regards,
Comment 3 GNOME Infrastructure Team 2021-05-19 12:23:45 UTC
-- 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/2056.