gvfs-gdu-volume-monitor crashed with SIGABRT in __kernel_vsyscall() shortly after login

[Mike Ayers]

Binary package hint: gvfs

Description: Ubuntu Natty (development branch)
Release: 11.04

gvfs:
  Installed: 1.8.0-0ubuntu1
  Candidate: 1.8.0-0ubuntu2
  Version table:
     1.8.0-0ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
 *** 1.8.0-0ubuntu1 0
        100 /var/lib/dpkg/status

Problem occurred during startup - I don't believe I was "doing" anything yet.

Hardware: Lenovo S10-3t with Ubuntu in an extended partition.
I have Windows 7 in the primary, and a memory card allocated to ReadyBoost.
This installation was upgraded from 10.10.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gvfs 1.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: wl
Architecture: i386
CrashCounter: 1
Date: Mon Apr 25 21:18:32 2011
ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gvfs-gdu-volume-monitor crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to natty on 2011-04-15 (10 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #738241, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.