Shotwell crashes on starting

Asked by Jack Beveridge on 2011-12-13

Can someone help with this? Shotwell crashes on starting. When run from a terminal I get this-

(shotwell:4735): GLib-GIO-CRITICAL **: g_file_hash: assertion `G_IS_FILE (file)' failed

(shotwell:4735): GLib-GIO-CRITICAL **: g_file_hash: assertion `G_IS_FILE (file)' failed
**
ERROR:i686-linux-gnu/core/SourceHoldingTank.c:663:source_holding_tank_internal_notify_altered: assertion failed: (_tmp0_)
Aborted

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu shotwell Edit question
Assignee:
No assignee Edit question
Solved by:
Jack Beveridge
Solved:
2011-12-15
Last query:
2011-12-15
Last reply:
2011-12-14

Can you give the output of:

cat /etc/lsb-release ; apt-cache policy shotwell

Thanks

 cat /etc/lsb-release ; apt-cache policy shotwell
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=11.10
DISTRIB_CODENAME=oneiric
DISTRIB_DESCRIPTION="Ubuntu 11.10"
shotwell:
  Installed: 0.11.6-0ubuntu0.1
  Candidate: 0.11.6-0ubuntu0.1
  Version table:
 *** 0.11.6-0ubuntu0.1 0
        500 http://nz.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages
        100 /var/lib/dpkg/status
     0.11.2-0ubuntu1 0
        500 http://nz.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages

If you make a new user and run the app, does it work ok?

When I log in as a guest it starts and runs ok although it's library is empty. Shotwell has been working well until this evening when I tried to open a tiff file in gimp via shotwell. The file became 'modified' and only one layer would open in the gimp (the resuting picture looked like a black and white checkerboard). Now I have this problem with shotwell.

Thanks.

Ok, I suggest you log in as the original user and rename the shotwell config folder (hidden in your home foler) then rerun and rebuild the library.

Cannot find the shotwell config folder. When I view hidden folders there does not seem to be a shotwell config folder either in the config folder or the shotwell folder.

Thanks

try:

mv ~/.shotwell ~/..shotwell_old

May help

Clint Rogers (clinton-yorba) said : #8

Jack,

I'm part of the Shotwell team here at Yorba. We've seen reports of this particular assertion firing from time to time, but have never been able to reproduce it. If this happens consistently for you, and you feel comfortable doing so, can you email the file ~/.shotwell/data/photo.db (the old one, prior to moving it around like actionparsnip recommended) to <email address hidden>? (I'll treat it as confidential.)

With any luck, it'll trigger the crash for us, too, and there will be some clue as to what causes this.

Thankyou,

 But unfortunately I ran out of patience and have reinstalled the operating system. I had my files backed up on an external drive. At this point everything is working as it should. I have been scanning my slide collection using an epsonV330 scanner with iscan software from Avasys corp. The software is accessed through gimp and the scanner was set to scan at it's highest resolution. The resulting file was saved as a tiff. To be on the safe side I will no longer use the shotwell 'open in external editor' path when working with these tiff files. Let me know if I can still help in anyway.