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

[RY Seshan]

Binary package hint: gvfs

no sound and sound driver not working

ProblemType: Crash
Architecture: i386
Date: Thu Dec 10 13:07:52 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/bash
 PATH=(custom, no user)
 LANG=en_IN
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
SegvAnalysis:
 Segfault happened at: 0xfc67da <gdu_pool_get_presentables+26>: mov 0xc(%eax),%eax
 PC (0x00fc67da) 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-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:1757): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1794): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1810): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:1782): IBUS-WARNING **: Connect to unix:abstract=/tmp/dbus-r2TLEBz98Q,guid=78559721a363f53b2f6e1e854af80eb7 failed: Failed to connect to socket /tmp/dbus-r2TLEBz98Q: Connection refused.
 (update-notifier:1798): IBUS-WARNING **: Connect to unix:abstract=/tmp/dbus-r2TLEBz98Q,guid=78559721a363f53b2f6e1e854af80eb7 failed: Failed to connect to socket /tmp/dbus-r2TLEBz98Q: Connection refused.

[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.