gvfsd-smb crashed with SIGSEGV in strlen()

[Steve Garton]

Binary package hint: gvfs

Description: Ubuntu intrepid (development branch)
Release: 8.10

apt-cache policy gvfs
gvfs:
  Installed: 1.0.1-0ubuntu3
  Candidate: 1.0.1-0ubuntu3
  Version table:
 *** 1.0.1-0ubuntu3 0
        500 http://ubuntu.positive-internet.com intrepid/main Packages
        100 /var/lib/dpkg/status

Tried to open a samba share in nautilus, and it refused to open the share.

This happens on 2 different machines (both running Intrepid)

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gvfs/gvfsd-smb
Package: gvfs-backends 1.0.1-0ubuntu3
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.4 /org/gtk/gvfs/exec_spaw/3
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 strlen () from /lib/tls/i686/cmov/libc.so.6
 strdup () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libsmbclient.so.0
 ?? () from /usr/lib/libsmbclient.so.0
 ?? () from /usr/lib/libsmbclient.so.0
Title: gvfsd-smb crashed with SIGSEGV in strlen()
Uname: Linux 2.6.24-19-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev pulse pulse-access pulse-rt sambashare vboxusers video

[Apport retracing service (apport)]

StacktraceTop:strlen () from /lib/tls/i686/cmov/libc.so.6
strdup () from /lib/tls/i686/cmov/libc.so.6
?? () from /usr/lib/libsmbclient.so.0
?? () from /usr/lib/libsmbclient.so.0
?? () from /usr/lib/libsmbclient.so.0

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Reassigning to samba the crash is a libsmbclient one

[Joel Goguen (jgoguen)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Joel Goguen (jgoguen)]

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!