gvfsd-sftp crashed with SIGSEGV in g_vfs_backend_get_daemon()

Bug #815924 reported by Jeroen Roovers
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Medium
Unassigned

Bug Description

disconnected an ssh mount in Nautilus, then this happened

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs-backends 1.9.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-6.7-generic 3.0.0-rc7
Uname: Linux 3.0.0-6-generic i686
Architecture: i386
CrashCounter: 1
Date: Mon Jul 25 16:24:42 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfsd-sftp
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/lib/gvfs/gvfsd-sftp --spawner :1.1 /org/gtk/gvfs/exec_spaw/7
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x1ae0d7 <g_vfs_backend_get_daemon+7>: mov (%eax),%eax
 PC (0x001ae0d7) ok
 source "(%eax)" (0xaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 g_vfs_backend_get_daemon () from /usr/lib/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/gvfs/libgvfscommon.so
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
Title: gvfsd-sftp crashed with SIGSEGV in g_vfs_backend_get_daemon()
UpgradeStatus: Upgraded to oneiric on 2011-07-12 (12 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jeroen Roovers (jer-gentoo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_vfs_backend_get_daemon (backend=0x817c000) at gvfsbackend.c:281
 unregister_mount_callback (unmount_reply=0x0, error=0x8179350, user_data=0x817d090) at gvfsjobunmount.c:244
 handle_async_reply (pending=<value optimized out>, data=<value optimized out>) at gvfsdbusutils.c:1216
 _dbus_pending_call_complete (pending=0x8190958) at ../../dbus/dbus-pending-call.c:199
 complete_pending_call_and_unlock (connection=0x8174a50, pending=0x8190958, message=0x8196450) at ../../dbus/dbus-connection.c:2301

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gvfs (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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