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

Bug #413796 reported by joey.blacksmith
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-disk-utility (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gnome-disk-utility

This is what happens to me every time I log in. Running karmic alpha 4.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Aug 14 22:36:53 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gnome-disk-utility/gdu-notification-daemon
Package: gnome-disk-utility 0.4-0ubuntu1
ProcCmdline: /usr/lib/gnome-disk-utility/gdu-notification-daemon
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0xad4b5e <gdu_pool_get_devices+30>: mov 0xc(%edx),%eax
 PC (0x00ad4b5e) 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
Stacktrace:
 #0 0x00ad4b5e in gdu_pool_get_devices () from /usr/lib/libgdu.so.0
 #1 0x0804ab15 in ?? ()
 #2 0x0804b25f in ?? ()
 #3 0x00c78b56 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #4 0x0804a5c1 in ?? ()
StacktraceTop:
 gdu_pool_get_devices () from /usr/lib/libgdu.so.0
 ?? ()
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: gdu-notification-daemon crashed with SIGSEGV in gdu_pool_get_devices()
Uname: Linux 2.6.31-5-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
joey.blacksmith (joey-blacksmith) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:gdu_pool_get_devices (pool=0x0) at gdu-pool.c:1345
?? ()
?? ()
__libc_start_main (
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gnome-disk-utility (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libcups2: installed version 1.3.11-1ubuntu4, latest version: 1.3.11-1ubuntu6
libpango1.0-common: installed version 1.25.2-0ubuntu2, latest version: 1.25.3-0ubuntu1
libc6: installed version 2.10.1-0ubuntu6, latest version: 2.10.1-0ubuntu7
libpango1.0-0: installed version 1.25.2-0ubuntu2, latest version: 1.25.3-0ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
Revision history for this message
joey.blacksmith (joey-blacksmith) wrote :

I have installed the lastest versions of the packages, Appoort reacting service is not right about this:

"This might be caused by some outdated packages which were installed on your system
at the time of the report:

libcups2: installed version 1.3.11-1ubuntu4, latest version: 1.3.11-1ubuntu6
libpango1.0-common: installed version 1.25.2-0ubuntu2, latest version: 1.25.3-0ubuntu1
libc6: installed version 2.10.1-0ubuntu6, latest version: 2.10.1-0ubuntu7
libpango1.0-0: installed version 1.25.2-0ubuntu2, latest version: 1.25.3-0ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report."

Changed in gnome-disk-utility (Ubuntu):
status: Invalid → New
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Changed in gnome-disk-utility (Ubuntu):
importance: Undecided → Medium
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.