gvfsd-gphoto2 crashed with SIGSEGV in pthread_mutex_lock()

Bug #575536 reported by David Fourer
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gvfs

I am not qualified to say if this is same as older bugs, ranging from 202304 up to 522944.
I plugged in my camera to usb after upgrade to Lucid and turned on camera. I see that gthumb 2.10.11 is opened automatically, but I get a report (from apport) that gvfsd-gphoto2 has crashed.
Camera is Canon Powershot A1100 IS.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gvfs-backends 1.6.0+git20100414-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CheckboxSubmission: 7c98a65fd4e0c4aea8b8b7f13f9b4c2b
CheckboxSystem: 6ce041aeed0a2c17b3343b66d157175d
Date: Tue May 4 20:39:45 2010
ExecutablePath: /usr/lib/gvfs/gvfsd-gphoto2
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.8 /org/gtk/gvfs/exec_spaw/3
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x81ef2d <pthread_mutex_lock+29>: mov 0xc(%esi),%edi
 PC (0x0081ef2d) ok
 source "0xc(%esi)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 pthread_mutex_lock ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: gvfsd-gphoto2 crashed with SIGSEGV in pthread_mutex_lock()
UserGroups: adm admin audio cdrom dialout fax fuse lpadmin netdev plugdev sambashare tape video

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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #202304, 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
tags: removed: need-i386-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.