gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables()

[Michael Nagel]

Binary package hint: gvfs

this happened when starting the first time after upgrading from jaunty to karmic. no user interaction involved, happened right after startup

ProblemType: Crash
Architecture: i386
Date: Sun Nov 1 16:17:01 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
Package: gvfs 1.4.1-0ubuntu1
ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor
ProcEnviron:
 SHELL=/bin/zsh
 LC_PAPER=de_DE.UTF-8
 PATH=(custom, user)
 LC_TIME=de_DE.UTF-8
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0xb7fa77da <gdu_pool_get_presentables+26>: mov 0xc(%eax),%eax
 PC (0xb7fa77da) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 gdu_pool_get_presentables () from /usr/lib/libgdu.so.0
 ?? ()
 ?? ()
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
Title: gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:2294): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2383): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2402): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:2382): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 28
 (gnome-panel:2382): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window

[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 #436871, 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.