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 717174 - "Ghost" Events after deleting photos
"Ghost" Events after deleting photos
Status: RESOLVED DUPLICATE
Product: shotwell
Classification: Other
Component: general
unspecified
Other All
: Low normal
: ---
Assigned To: Shotwell Maintainers
Shotwell Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-01-15 04:49 UTC by Shotwell Maintainers
Modified: 2013-05-01 06:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-25 21:49:30 UTC


---- Reported by shotwell-maint@gnome.bugs 2011-01-14 20:49:00 -0800 ----

Original Redmine bug id: 3101
Original URL: http://redmine.yorba.org/issues/3101
Searchable id: yorba-bug-3101
Original author: Sat Garcia
Original description:

During backup I only saved the shotwell db file, not realizing I needed the
thumbnails also. As a result, most of my photos showed up only as gray boxes.

The only solution (for now) provided on the mailing list was to remove the
photos and re-import (unfortunately losing an edits I made to the photos).
Well, I did this and for some photos it worked fine but others seem to have
“ghosts†hanging around. For example, in one of my events, I selected all
photos and performed a “Remove from Library.†I no longer see any photos
in the event but the event still exists and Shotwell says there are some
photos left in the event (not as many as were originally in there though).



---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:47:00 -0700 ----

### History

####

#1

Updated by Lucas Beeler almost 3 years ago

hi elsaturnino,

Did you delete your shotwell database before you re-imported? I suggest this
because when you re-import, you're going to lose most of what's stored in the
database anyway (edits, etc.). So there's really not much of a reason to keep
the old database around. Hence it's good to start with a new, fresh database
to avoid any problems like this. Just my two cents, though.

Take care,

Lucas

####

#2

Updated by Sat Garcia almost 3 years ago

Yeah, that would have been the smart thing to do. I wish I were smart ;)

####

#3

Updated by Jim Nelson almost 3 years ago

  * **Status** changed from _Open_ to _5_
  * **Resolution** set to _duplicate_
  * **% Done** changed from _0_ to _100_

This is a duplicate of #2889.

####

#4

Updated by Sat Garcia almost 3 years ago

I fail to see how this is a duplicate of #2889. When there aren't thumbnails,
there is a gray box but here there is no indication of photos at all.

####

#5

Updated by Jim Nelson almost 3 years ago

You said in your ticket that when you backed up you only backed up the
database file. When you restarted Shotwell, you got a series of gray boxes.

What I'm saying is, this problem could've been solved if the startup scan
regenerated the thumbnails. Re-importing was an idea, but is not an ideal way
to fix this problem. As Lucas said, starting from a fresh database is a better
way, but you lose all your data.

As far as the ghost events goes, we can debug this. I would need to see the
database with the ghost events. If you still have that, or can reproduce this,
I'm more than happy to re-open the ticket to investigate. I closed the ticket
because #2889 would've solved this problem before it reached this point.

####

#6

Updated by Charles Lindsay 7 months ago

  * **Status** changed from _5_ to _Duplicate_



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

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

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.