gdu-notification-daemon crashed with SIGSEGV in gdu_pool_get_devices()

Bug #424990 reported by yodaanneaux on 2009-09-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-disk-utility (Ubuntu)

Bug Description

Binary package hint: gnome-disk-utility

I've just launch the live-CD to test karmic...

ProblemType: Crash
Architecture: i386
Date: Sat Sep 5 20:39:12 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gnome-disk-utility/gdu-notification-daemon
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20090902.1)
Package: gnome-disk-utility 0.5-0ubuntu3
ProcCmdline: /usr/lib/gnome-disk-utility/gdu-notification-daemon
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
 Segfault happened at: 0x7963ae <gdu_pool_get_devices+30>: mov 0xc(%edx),%eax
 PC (0x007963ae) ok
 source "0xc(%edx)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-disk-utility
 #0 0x007963ae in gdu_pool_get_devices () from /usr/lib/
 #1 0x0804ab55 in ?? ()
 #2 0x0804b29f in ?? ()
 #3 0x00fd5b56 in __libc_start_main () from /lib/tls/i686/cmov/
 #4 0x0804a601 in ?? ()
 gdu_pool_get_devices () from /usr/lib/
 ?? ()
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/
 ?? ()
Title: gdu-notification-daemon crashed with SIGSEGV in gdu_pool_get_devices()
Uname: Linux 2.6.31-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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 #418300, 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.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers