shotwell crashed with SIGSEGV in g_signal_emit_valist()

Bug #1431441 reported by David Jones
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shotwell (Ubuntu)
New
Undecided
Unassigned

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
SegvAnalysis:
 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
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/modules/libunity-gtk-module.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
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

Revision history for this message
David Jones (dwrj87-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :
description: updated
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.