shotwell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

Bug #1757002 reported by Brian Murray
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
shotwell (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Crashed after attaching a usb device with photos on it.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: shotwell 0.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 19 13:59:29 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/shotwell
InstallationDate: Installed on 2013-01-16 (1888 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
ProcCmdline: shotwell file:///media/username/3091-0A00
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7faa6644cc31 <g_type_check_instance_is_fundamentally_a+49>: movzbl 0x14(%rdx),%eax
 PC (0x7faa6644cc31) ok
 source "0x14(%rdx)" (0x70000001c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: shotwell
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_ref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_weak_ref_get () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: shotwell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sbuild sudo

Revision history for this message
Brian Murray (brian-murray) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x56496058b9c0, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4026
 g_object_ref (_object=0x56496058b9c0) at ../../../../gobject/gobject.c:3204
 g_weak_ref_get (weak_ref=<optimized out>) at ../../../../gobject/gobject.c:4379
 g_settings_backend_invoke_closure (user_data=0x7faa48005400) at ../../../../gio/gsettingsbackend.c:263
 g_main_dispatch (context=0x56495febb6c0) at ../../../../glib/gmain.c:3177

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in shotwell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in shotwell (Ubuntu):
status: New → Confirmed
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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