shotwell crashed with SIGSEGV in g_cclosure_marshal_VOID__VOIDv()

Bug #1429704 reported by Alan
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shotwell (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crash when closes.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: shotwell 0.20.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu1
Architecture: i386
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Mar 9 00:37:23 2015
ExecutablePath: /usr/bin/shotwell
InstallationDate: Installed on 2014-11-28 (101 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
ProcCmdline: shotwell /home/username/Escritorio/A\ mi\ rancho\ -\ f.jpg
SegvAnalysis:
 Segfault happened at: 0xb656ee77: mov (%eax),%edx
 PC (0xb656ee77) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: shotwell
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/gtk-3.0/modules/libunity-gtk-module.so
 g_cclosure_marshal_VOID__VOIDv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: shotwell crashed with SIGSEGV in g_cclosure_marshal_VOID__VOIDv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev robots sambashare sudo

Revision history for this message
Alan (alanjas) wrote :
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 #1429514, 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-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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