Ubuntu
gvfs package

gvfsd-sftp crashed with SIGSEGV in strlen()

Bug #403223 reported by Sebastien Bacher
42
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gvfs
Fix Released
Critical
gvfs (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

crash after connection to an unknown server

ProblemType: Crash
Architecture: i386
Date: Wed Jul 22 22:59:10 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gvfs/gvfsd-sftp
Package: gvfs-backends 1.3.2-0ubuntu4
ProcCmdline: /usr/lib/gvfs/gvfsd-sftp --spawner :1.9 /org/gtk/gvfs/exec_spaw/3
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SegvAnalysis:
 Segfault happened at: 0xb55e63 <strlen+51>: mov (%eax),%ecx
 PC (0x00b55e63) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 strlen () from /lib/tls/i686/cmov/libc.so.6
 marshal_string (str=0x8a3f220, insert_at=346, type=115,
 _dbus_marshal_write_basic (str=0x8a3f220, insert_at=346, type=115,
 _dbus_type_writer_write_basic_no_typecode (
 _dbus_type_writer_write_basic (writer=0xb7efa9ec, type=115,
Title: gvfsd-sftp crashed with SIGSEGV in strlen()
Uname: Linux 2.6.31-3-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in gvfs (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → High
status: New → Triaged
visibility: private → public
Bug Watch Updater (bug-watch-updater)
Changed in gvfs:
status: Unknown → New
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:strlen () at ../sysdeps/i386/i486/strlen.S:69
_dbus_marshal_write_basic (str=0x8a3f220, insert_at=346,
_dbus_type_writer_write_basic (writer=0xb7efa9ec, type=115,
dbus_message_iter_append_basic (iter=0xb7efa9e4, type=115,
_g_dbus_message_iter_append_args_valist (iter=0xb7efaa58,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gvfs (Ubuntu):
importance: High → Medium
tags: removed: need-i386-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug has been fixed upstream now

Changed in gvfs (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gvfs - 1.3.4-0ubuntu1

---------------
gvfs (1.3.4-0ubuntu1) karmic; urgency=low

  * New upstream version:
    - ftp: Make large FTP transfers work
    - gphoto: use udev instead of hal
    - Fix build on FreeBSD
    - Bugs fixed: 588187, 589915, 573994, 590793, 576229, 589434
      (lp: #403223, #404490, #291259, #364084, #395216)
  * debian/patches/02-port-gphoto2-backend-and-monitor-to-gudev.patch:
    - the change is in the new version
  * debian/patches/90_relibtoolize.patch:
    - new version update

 -- Sebastien Bacher <email address hidden> Mon, 10 Aug 2009 22:24:25 +0200

Changed in gvfs (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Mathieu Leplatre (mathieu.leplatre) wrote :

In Karmic, nautilus crashes if a remote identification has changed.

If I access the remote host by ssh in a terminal, I get the usual :
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!

With nautilus, it just crashes.

After editing the .ssh/known_hosts file, it works well of course.

Revision history for this message
Krzysztof Klimonda (kklimonda) wrote :

You will have to open a new bug about it. The easiest way is to enable apport by doing
sudo force_start=1 /etc/init.d/apport start
and then make nautilus crash. Then you can send a full report which will help us (or rather upstream) to fix it.

Bug Watch Updater (bug-watch-updater)
Changed in gvfs:
importance: Unknown → Critical
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.