gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()

Bug #240866 reported by ingo
6
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gvfs

I know it is probably a duplicate of bug 235698.
It happened just after login, have just started only Thunderbird to fetch my mail and Apport popped up.
So it will be difficult to trace because as soon as you perform one action after login - i.e. setup fpr tracing - it happems already.
Lateron it is unlikely to happen again.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Jun 17 23:25:51 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/gvfs/gvfs-fuse-daemon
NonfreeKernelModules: nvidia
Package: gvfs-fuse 0.2.4-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: /usr/lib/gvfs//gvfs-fuse-daemon /home/username/.gvfs
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 pthread_mutex_lock () from /lib/libpthread.so.0
 g_main_loop_quit () from /usr/lib/libglib-2.0.so.0
 ?? ()
 fuse_fs_destroy () from /lib/libfuse.so.2
 ?? () from /lib/libfuse.so.2
Title: gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
Uname: Linux 2.6.24-19-generic x86_64
UserGroups: adm admin audio cdrom dip floppy fuse lpadmin plugdev uml-net vboxusers video

Revision history for this message
ingo (ingo-steiner) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:pthread_mutex_lock () from /lib/libpthread.so.0
IA__g_main_loop_quit (loop=0x655db0)
?? ()
fuse_fs_destroy (fs=0x610fa0) at fuse.c:1347
fuse_lib_destroy (data=0x610e80) at fuse.c:1360

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

No worries, marking it as dup, thanks.

Changed in gvfs:
status: New → Invalid
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.