gvfsd-smb crashed with SIGSEGV in g_vfs_daemon_queue_job

[Roland]

Binary package hint: gvfs

I opened a smb share window yesterday, left it open, and hibernated the E6400 dell latitude.

Today, I woke it up. I clicked on the smb share window and it reported that it can't connect to that share (which is fine, I would guess the session timed out during the time).

So I started to browse the LAN again, and as I clicked on "Windows Network" it crashed.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gvfs/gvfsd-smb
NonfreeKernelModules: nvidia
Package: gvfs-backends 1.0.1-0ubuntu3
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.7 /org/gtk/gvfs/exec_spaw/10
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /usr/lib/libsmbclient.so.0
 ?? () from /usr/lib/libsmbclient.so.0
 ?? () from /usr/lib/libsmbclient.so.0
 ?? () from /usr/lib/libsmbclient.so.0
 ?? () from /usr/lib/libsmbclient.so.0
Title: gvfsd-smb crashed with SIGSEGV
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

[Sebastien Bacher (seb128)]

the crash is a libsmbclient one

[Apport retracing service (apport)]

StacktraceTop:event_add_to_select_args () from /usr/lib/libsmbclient.so.0
event_loop_once () from /usr/lib/libsmbclient.so.0
cli_pull () from /usr/lib/libsmbclient.so.0
cli_read () from /usr/lib/libsmbclient.so.0
SMBC_read_ctx () from /usr/lib/libsmbclient.so.0

[Mark Ellse (markellse)]

Please see the bug below showing similar behaviour on Intrepid, together with some steps to isolate the problem.

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/316862

[Pedro Villavicencio (pedro)]

It looks like bug https://bugzilla.samba.org/show_bug.cgi?id=5707 which is fixed now, could you try with newest package and report back? thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.