Mimics may not be deleted properly
Submitted by Jim Nelson
Link to original bug (#716813)
Description
---- Reported by jim@yorba.org 2010-09-24 13:47:00 -0700 ----
Original Redmine bug id: 2596
Original URL: http://redmine.yorba.org/issues/2596
Searchable id: yorba-bug-2596
Original author: Jim Nelson
Original description:
Working with a user, I believe there's a situation with the mimic manager. If a photo with a mimic is destroyed and Shotwell is immediately closed, or the user begins importing right away, there's a possibility some of the old mimic files won't be deleted (especially if there's a lot of them). This leads to a situation where the old mimics are used for newer files.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:40:00 -0700 ----
History
Comment 1
Updated by Lucas Beeler over 2 years ago
- Status changed from Open to 5
- Resolution set to fixed
- % Done changed from 0 to 100
From my testing, this was fixed with the commit that fixed #3501 (closed). Please re- open if this bug rears its ugly head again.
Comment 2
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:47 UTC ---
This bug was previously known as bug 2596 at http://redmine.yorba.org/show_bug.cgi?id=2596
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 FIXED