gvfsd-gphoto2 crashed with SIGSEGV in g_object_unref()

Bug #909867 reported by Carla Sella
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

I had just opened shotwell after attaching my Nikon DSC coolpix S5100-PTP on the USB port.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gvfs-backends 1.10.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
Uname: Linux 3.2.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Thu Dec 29 20:48:51 2011
ExecutablePath: /usr/lib/gvfs/gvfsd-gphoto2
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.1 /org/gtk/gvfs/exec_spaw/10
SegvAnalysis:
 Segfault happened at: 0x7f1e4896849f: mov 0x20(%rax),%rax
 PC (0x7f1e4896849f) ok
 source "0x20(%rax)" (0xaaaaaaaaaaaaaaca) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_value_unset () 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: gvfsd-gphoto2 crashed with SIGSEGV in g_object_unref()
UpgradeStatus: Upgraded to precise on 2011-12-02 (27 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare video

Revision history for this message
Carla Sella (carla-sella) 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 #819310, 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.

visibility: private → public
visibility: 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.