gvfsd-gphoto2 crashed with SIGSEGV in __pthread_mutex_destroy()

Bug #946255 reported by Joel Stanley
144
This bug affects 31 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Confirmed
High
Unassigned

Bug Description

caused chrome to crash

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gvfs-backends 1.11.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-3.8-generic 3.2.0-rc4
Uname: Linux 3.2.0-3-generic x86_64
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Sun Mar 4 21:15:43 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfsd-gphoto2
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.1 /org/gtk/gvfs/exec_spaw/2
SegvAnalysis:
 Segfault happened at: 0x7f0c169abe50 <__pthread_mutex_destroy>: testb $0x10,0x10(%rdi)
 PC (0x7f0c169abe50) 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 (mutex=0x0) at pthread_mutex_destroy.c:28
 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: Upgraded to precise on 2012-01-29 (35 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sudo usrp video

Revision history for this message
Joel Stanley (shenki) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __pthread_mutex_destroy (mutex=0x0) at pthread_mutex_destroy.c:28
 g_mutex_impl_free (mutex=0x0) at /build/buildd/glib2.0-2.31.18/./glib/gthread-posix.c:112
 g_mutex_clear (mutex=<optimized out>) at /build/buildd/glib2.0-2.31.18/./glib/gthread-posix.c:187
 release_device (gphoto2_backend=0x18e80e0) at gvfsbackendgphoto2.c:621
 do_mount (backend=<optimized out>, job=0x18e9800, mount_spec=<optimized out>, mount_source=<optimized out>, is_automount=<optimized out>) at gvfsbackendgphoto2.c:1668

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gvfs (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 gvfs (Ubuntu):
status: New → Confirmed
visibility: private → public
Changed in gvfs (Ubuntu):
importance: Medium → High
tags: added: bugpattern-needed
papukaija (papukaija)
tags: added: metabug
Revision history for this message
Vidvranjek (vidvranjek) wrote :

To me this happens when i connetct my Asus Transformer Prime TF201. It cannot mount via MTP...

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.