shotwell crashed with SIGSEGV in g_signal_emit_valist()

Bug #1431441 reported by David Jones on 2015-03-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shotwell (Ubuntu)

Bug Description

Not sure what caused it

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: shotwell 0.20.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
Uname: Linux 3.19.0-8-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 12 16:12:41 2015
ExecutablePath: /usr/bin/shotwell
InstallationDate: Installed on 2014-04-19 (327 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: shotwell /home/username/Pictures/Old\ Images/Picture\ Name.jpeg
 Segfault happened at: 0x7fc5c78d4950: mov (%rdi),%rax
 PC (0x7fc5c78d4950) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: shotwell
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/modules/
 ?? () from /usr/lib/x86_64-linux-gnu/
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/
Title: shotwell crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: Upgraded to vivid on 2015-03-02 (9 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

description: updated

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1431121, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers