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

[ingo]

Binary package hint: gvfs

I just booted up Hardy-amd64 after having prior worked with Debian-Lenny-amd64 on the same disk (but different partitition;-).

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 1 17:56:58 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/gvfs/gvfs-fuse-daemon
NonfreeKernelModules: nvidia
Package: gvfs-fuse 0.2.5-0ubuntu2
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

[Andreas Moog (ampelbein)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 261793, so it 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. Feel free to continue to report any other bugs you may find.