gvfsd-gphoto2 crashed with SIGSEGV in pthread_mutex_destroy().

Bug #957482 reported by Denis Sorn
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu recognized my Galaxy Nexus as Media player or something. After unmounting it, icon was still present in launcher. After clicking on the icon a couple of times gvfsd-gphoto2 crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gvfs-backends 1.11.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Fri Mar 16 23:03:40 2012
ExecutablePath: /usr/lib/gvfs/gvfsd-gphoto2
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120302)
ProcCmdline: /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.6 /org/gtk/gvfs/exec_spaw/5
ProcEnviron:
 SHELL=bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f537e783e50 <pthread_mutex_destroy>: testb $0x10,0x10(%rdi)
 PC (0x7f537e783e50) ok
 source "$0x10" ok
 destination "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 pthread_mutex_destroy () from /lib/x86_64-linux-gnu/libpthread.so.0
 g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
Title: gvfsd-gphoto2 crashed with SIGSEGV in pthread_mutex_destroy()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo

Revision history for this message
Denis Sorn (sorn-denis) 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 #946255, 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.