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

Bug #413448 reported by Richard Cavell
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-disk-utility (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnome-disk-utility

I updated my second-gen MacBook to Karmic 4 (64-bit) and rebooted. Then this notification appeared during the login sequence.

gnome-disk-utility:
  Installed: 0.4-0ubuntu1

ProblemType: Crash
Architecture: amd64
Date: Fri Aug 14 17:47:44 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_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x7f74ef199d9d <gdu_pool_get_devices+13>: mov 0x18(%rdi),%rax
 PC (0x7f74ef199d9d) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-disk-utility
StacktraceTop:
 gdu_pool_get_devices () from /usr/lib/libgdu.so.0
 ?? ()
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
Title: gdu-notification-daemon crashed with SIGSEGV in gdu_pool_get_devices()
Uname: Linux 2.6.31-5-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Richard Cavell (richardcavell) 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 () from /lib/libc.so.6
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
visibility: private → public
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.