Segfault in gvfsd-ftp after copy a file by FTP on a server

[d-snake]

Binary package hint: gvfs

While copy a file on FTP server the connection crashed. I just can stop the copy process/dialog by killing nautilus. I've repeated the process several times , everytime the same result.

I've found following entry in /var/log/syslog:
May 2 08:35:49 rnaumann-laptop kernel: [ 1026.867026] gvfsd-ftp[2875]: segfault at 0 ip (null) sp 00007fb5ac71dd88 error 14 in gvfsd-ftp[400000+30000]

It seems to be an error in the package 'gvfs-backends'.

This bug seems to be very critical!

Here are some infos of my system:
lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

Installed Versions:
gvfs: 1.8.0-0ubuntu2
gvfs-backends: 1.8.0-0ubuntu2
gvfs-fuse: 1.8.0-0ubuntu2

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gvfs-backends 1.8.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon May 2 09:26:58 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
ProcEnviron:
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.