shotwell crashed with SIGSEGV in g_signal_emit_valist()

Bug #1438904 reported by Fabio Monteverde on 2015-03-31
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shotwell (Ubuntu)
Undecided
Unassigned

Bug Description

opening a picture!

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: shotwell 0.20.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 31 22:11:45 2015
ExecutablePath: /usr/bin/shotwell
InstallationDate: Installed on 2014-09-16 (196 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: shotwell /home/username/Scrivania/40790_1539284131106_682007_n.jpg
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f4c5ef7ea40: mov (%rdi),%rax
 PC (0x7f4c5ef7ea40) 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-11 (20 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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