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 736451 - Shotwell crashes about a minute after start-up
Shotwell crashes about a minute after start-up
Status: RESOLVED DUPLICATE of bug 715198
Product: shotwell
Classification: Other
Component: pipeline
0.18.x
Other Linux
: Normal critical
: 0.20
Assigned To: Shotwell Maintainers
Shotwell Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-09-11 05:48 UTC by Michael Hendry
Modified: 2014-09-26 00:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Shotwell's log (242.83 KB, application/octet-stream)
2014-09-11 05:48 UTC, Michael Hendry
Details
GDB output (14.76 KB, application/octet-stream)
2014-09-11 05:49 UTC, Michael Hendry
Details
GDB output relating to crash (14.26 KB, application/octet-stream)
2014-09-17 07:14 UTC, Michael Hendry
Details
Log of shotwell activity leading up to crash (245.96 KB, application/octet-stream)
2014-09-17 07:15 UTC, Michael Hendry
Details
GDB output documenting shotwell crash (14.26 KB, application/octet-stream)
2014-09-17 07:39 UTC, Michael Hendry
Details
GDB output documenting shotwell crash (14.85 KB, application/octet-stream)
2014-09-21 19:31 UTC, Michael Hendry
Details
Shotwell log relating to the crash (248.21 KB, text/x-log)
2014-09-21 19:32 UTC, Michael Hendry
Details

Description Michael Hendry 2014-09-11 05:48:37 UTC
Created attachment 285881 [details]
Shotwell's log

Ubuntu 14.04 running in a Parallels Virtual Machine on iMac running OS X 10.9.4, with 3 GBytes of memory reserved for Ubuntu.

Shotwell starts normally, with the "Updating Library" message. Both at this stage and after the Updating Library phase is over, it's possible to inspect images etc., as normal. After about a minute, Shotwell crashes.
Comment 1 Michael Hendry 2014-09-11 05:49:52 UTC
Created attachment 285882 [details]
GDB output
Comment 2 Michael Hendry 2014-09-13 10:32:42 UTC
Further experimentation reveals that while repeated attempts to run Shotwell after the first crash cause it to crash repeatedly, if I wait a period of time (more than an hour is necessary, two hours is more than enough) shotwell will run without crashing.

Once I've got over this hurdle, I can reboot my Ubuntu 14.04 virtual machine or my entire iMac, and shotwell runs OK for the rest of that day.

After an overnight shutdown, the crashes occur again, as above.
Comment 3 Jim Nelson 2014-09-16 21:12:47 UTC
Is this .gdb file a core file?  I'm unable to load it into GDB.

This is the best way to generate files for inspection:

https://wiki.gnome.org/Apps/Shotwell/ReportingABug
Comment 4 Michael Hendry 2014-09-16 21:58:36 UTC
The two files I submitted were generated according to the link in Comment 3 above, and found in the expected directories.

Unfortunately, I can't get Shotwell to crash this evening, as I've already run it (and caused it to crash) earlier today, and if past experience is anything to go by, I'll need to shut my computer down overnight and have another try in the morning.

I've had a quick look at the .gdb file and found it was binary, not the text I was expecting, so maybe it's been damaged somehow.

I'll try again tomorrow.
Comment 5 Michael Hendry 2014-09-17 07:14:56 UTC
Created attachment 286342 [details]
GDB output relating to crash
Comment 6 Michael Hendry 2014-09-17 07:15:53 UTC
Created attachment 286343 [details]
Log of shotwell activity leading up to crash
Comment 7 Michael Hendry 2014-09-17 07:16:29 UTC
Further crash generated this morning.

.gdb file is now readable plain text.
Comment 8 Michael Hendry 2014-09-17 07:39:40 UTC
Created attachment 286344 [details]
GDB output documenting shotwell crash
Comment 9 Michael Hendry 2014-09-17 07:42:44 UTC
The most recent .GDB file is readable - the one submitted at 2014-09-17 07:14 UTC was copied from Ubuntu to Mac OS before being submitted, and appears to have been corrupted in the process.

The more recent one (2014-09-17 07:39 UTC) is readable text.
Comment 10 Jim Nelson 2014-09-18 20:02:33 UTC
This bug is fixed in master, commit cfcb00.  It will be available in Shotwell 0.20.0 (due to be released in the next few days).
Comment 11 Michael Hendry 2014-09-21 19:31:10 UTC
Created attachment 286752 [details]
GDB output documenting shotwell crash
Comment 12 Michael Hendry 2014-09-21 19:32:11 UTC
Created attachment 286753 [details]
Shotwell log relating to the crash
Comment 13 Michael Hendry 2014-09-21 19:34:33 UTC
(In reply to comment #10)
> This bug is fixed in master, commit cfcb00.  It will be available in Shotwell
> 0.20.0 (due to be released in the next few days).

Initially it looked as though the bug was fixed, but this evening it came back again (or another one, which has the same effect has appeared!).

Attachments already submitted.
Comment 14 Jim Nelson 2014-09-26 00:24:11 UTC

*** This bug has been marked as a duplicate of bug 715198 ***