shotwell crashed with SIGABRT in g_assertion_message()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Shotwell |
New
|
Undecided
|
Unassigned | ||
shotwell (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
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/
ProcVersionSign
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
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, user)
LANG=en_AU.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: shotwell
StacktraceTop:
g_assertion_
g_assertion_
?? ()
core_tracker_
g_closure_invoke () from /usr/lib/
Title: shotwell crashed with SIGABRT in g_assertion_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
Changed in shotwell (Ubuntu): | |
status: | New → Triaged |
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 http:// redmine. yorba.org/ projects/ shotwell/ wiki/ShotwellFA Q#I-found- a-bug-in- Shotwell- How-can- I-report- it and http:// yorba.org/ shotwell/ install/ or feel free to respond here.)