gvfsd-smb crashed with SIGSEGV

[Anthony Lovell]

Binary package hint: gvfs

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

Copying multiple files from server to wireless client

ProblemType: Crash
Architecture: i386
Date: Wed Mar 12 21:36:45 2008
Disassembly: 0x0:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/gvfs/gvfsd-smb
NonfreeKernelModules: cdrom
Package: gvfs-backends 0.2.0.1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.4 /org/gtk/gvfs/exec_spaw/6
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: gvfsd-smb crashed with SIGSEGV
Uname: Linux 2.6.24-12-386 i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev sambashare scanner video

[Apport retracing service (apport)]

StacktraceTop:?? ()
g_vfs_job_run (job=0x80dac48) at gvfsjob.c:198
job_handler_callback (data=0x80dac48, user_data=0x8073a00) at gvfsdaemon.c:142
IA__g_thread_pool_set_max_threads (pool=0x8074220, max_threads=135113800, error=0xb7b40ff4)
IA__g_thread_join (thread=0x80dcdc8) at /build/buildd/glib2.0-2.15.6/glib/gthread.c:723

[Sebastien Bacher (seb128)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=522190

[Sebastien Bacher (seb128)]

upstream comment on the bug

"It seems we're getting a GVfsJob with a NULL run method. I don't see how that
is possible though. If someone can reproduce this in gdb please try
p (char *)g_type_name_from_instance (job) in frame 1 in thread 1.
(i.e. the g_vfs_job_run call)"

can you trigger the bug easily? could you give it a try? I can guide you to do that if required

[Sebastien Bacher (seb128)]

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.