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

[Gabriel Bauman]

Binary package hint: gvfs

Logged in this morning, apport mentioned that an application had crashed in the past.

The day before, I had used the sftp protocol to do some browsing.

Ubuntu 8.04
gvfs 0.2.4-0ubuntu1

ProblemType: Crash
Architecture: amd64
Date: Wed Jun 4 17:06:37 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=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /lib/libc.so.6
 malloc () from /lib/libc.so.6
 vasprintf () from /lib/libc.so.6
 asprintf () from /lib/libc.so.6
 __assert_fail () from /lib/libc.so.6
Title: gvfs-fuse-daemon crashed with SIGSEGV in malloc()
Uname: Linux 2.6.24-18-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare staff video

[Apport retracing service (apport)]

StacktraceTop:_int_malloc () from /lib/libc.so.6
malloc () from /lib/libc.so.6
vasprintf () from /lib/libc.so.6
asprintf () from /lib/libc.so.6
__assert_fail () from /lib/libc.so.6

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Hew (hew)]

I'm getting this as well on Intrepid. I'm not sure how to use valgrind in this situation, as I don't know the command to use to launch the program (/usr/lib/gvfs/gvfs-fuse-daemon complains with 'fuse: missing mountpoint'). In addition, most times on startup everything is fine; only occasionally does this problem occur, with a seemingly random cause.

gvfs/intrepid uptodate 0.99.1-0ubuntu3

[Sebastien Bacher (seb128)]

could you try again if that's an issue when the next version is uploaded? could be bug #235698

[Sebastien Bacher (seb128)]

the new version is in intrepid now, could you try if that's still an issue?

you can start "/usr/lib/gvfs/gvfs-fuse-daemon .gvfs" too if it's not already running

[Hew (hew)]

I haven't had this error for a while, so marking it as fixed. I seem to have two copies of gvfs-fuse-daemon running though. I'll reopen this report if I get it again. I'm still getting bug #235698 and other gvfs issues, but I'll keep the details to their respective reports.

[Juksu (jluostar)]

Just got this error/crash when starting my laptop (hardy 8.04 with -.20 kernel with today's updates)

[Hew (hew)]

This bug has been fixed with gvfs 0.99.3-0ubuntu1 in Intrepid. If you (or anyone) can reproduce the error in this version or later, then please reopen the bug. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#head-a7a957d3d691c2754ba24e5085481107ed703b49

[Juksu (jluostar)]

Still not fixed in Hardy. I have "reproduced" this bug several times now. This new launchpad system is ridiculous when it is impossible to file a bug to the current release, which, to my knowledge, is Hardy Heron.
My info is in the "duplicates to this bug".

[Hew (hew)]

This bug has been marked as fixed since it is fixed in the current development release, Intrepid Ibex. We know that this bug affects Hardy, and it has already been nominated for that release as you can see at the top of the page. If you are unfamiliar with the SRU process, please read https://wiki.ubuntu.com/StableReleaseUpdates . Since the specific patch that fixes this issue is not known at this stage, it may be difficult to take the fix to Hardy.