shotwell crashed with SIGABRT in g_assertion_message()

Bug #910044 reported by Sameer Morar on 2011-12-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shotwell (Ubuntu)

Bug Description

Shotwell crashes relatively randomly while in use.

I'm not sure if this is a dupe of #837292, as my preferences are to not save metainformation in the files.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: shotwell 0.11.6-0ubuntu0.1 [modified: usr/share/glib-2.0/schemas/gschemas.compiled]
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Fri Dec 30 22:55:18 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/shotwell
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: shotwell
 PATH=(custom, user)
Signal: 6
SourcePackage: shotwell
 g_assertion_message () from /lib/x86_64-linux-gnu/
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/
 ?? ()
 core_tracker_include_uninclude ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/
Title: shotwell crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Sameer Morar (smorar) wrote :
visibility: private → public
Clint Rogers (clinton-yorba) wrote :

Hi, and thank you for reporting this.

Unfortunately, it looks as if you may have uncovered a new bug, rather than a previously-known one, and I'll ticket it on our side shortly.

If you feel comfortable doing so, can you try building Shotwell from source, running with logging enabled and deliberately triggering the crash? The log may provide some clues as to what's happening inside the application right before it crashes.

(If you want to do this, but don't know how and would like assistance, please have a look at and or feel free to respond here.)

Sameer Morar (smorar) wrote :

Hi Clint

It's taken me a while, but I have managed to reproduce the crash using shotwell from git (latest commit: 5ef32dedd7af1f80dd2125167b130fb0e03f3b71).

This bug seemed to be triggered after selecting all photos in an event, and then clicking on somewhere to deselect the selection.

I have attached the shotwell.gdb and shotwell.log files

Sameer Morar (smorar) wrote :
Clint Rogers (clinton-yorba) wrote :


Thank you for this; this should prove to be quite useful. I'll pass this on to the rest of the team and we'll begin working on this as soon as we can.

Clint Rogers (clinton-yorba) wrote :

For those watching this bug, please also see - this is the upstream bug report.

 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x762780 "media_accumulator_real_uninclude", message=0x54d02c0 "assertion failed: (self->total > 0)") at /build/buildd/glib2.0-2.30.0/./glib/gtestutils.c:1425
 g_assertion_message_expr (domain=0x0, file=0x762628 "x86_64-linux-gnu/MediaViewTracker.c", line=487, func=0x762780 "media_accumulator_real_uninclude", expr=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gtestutils.c:1436
 media_accumulator_real_uninclude (base=0x55291c0, object=<optimized out>) at x86_64-linux-gnu/MediaViewTracker.c:487
 core_tracker_include_uninclude (self=0x5b949e0, objects=<optimized out>, cb=0x521cf0 <_core_tracker_accumulator_uninclude_core_tracker_include_uninclude_object>, cb_target=0x55291c0) at x86_64-linux-gnu/core/Tracker.c:432
 g_closure_invoke (closure=0x4dc3d00, return_value=0x0, n_param_values=2, param_values=0x4dfb0a0, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gobject/gclosure.c:774

Changed in shotwell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in shotwell (Ubuntu):
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers