[Karmic] update-notifier crashed with SIGSEGV in gdu_pool_get_devices()

[pdaemon]

Binary package hint: update-notifier

Description: Ubuntu karmic (development branch)
Release: 9.10

update-notifier:
  Installed: 0.87
  Candidate: 0.87
  Version table:
 *** 0.87 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

I expected update-notifier to work and not crash!

ProblemType: Crash
Architecture: amd64
Date: Fri Jul 17 17:49:57 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/update-notifier
NonfreeKernelModules: nvidia
Package: update-notifier 0.87
ProcCmdline: update-notifier --startup-delay=60
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SegvAnalysis:
 Segfault happened at: 0x7fa8fb59ad9d <gdu_pool_get_devices+13>: mov 0x18(%rdi),%rax
 PC (0x7fa8fb59ad9d) 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: update-notifier
Stacktrace:
 #0 0x00007fa8fb59ad9d in gdu_pool_get_devices () from /usr/lib/libgdu.so.0
 #1 0x000000000040b7ef in up_device_changed () from /usr/bin/update-notifier
 #2 0x000000000040b86f in up_check_mounted_devices ()
    from /usr/bin/update-notifier
 #3 0x0000000000406a62 in main () from /usr/bin/update-notifier
StacktraceTop:
 gdu_pool_get_devices () from /usr/lib/libgdu.so.0
 up_device_changed () from /usr/bin/update-notifier
 up_check_mounted_devices ()
 main () from /usr/bin/update-notifier
Title: update-notifier crashed with SIGSEGV in gdu_pool_get_devices()
Uname: Linux 2.6.31-3-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? ()

[Nick Ellery (nick.ellery)]

Got this to from version 0.87 in Karmic.

[dava4444 (dava4444)]

hi
I have the i368 upgrade to karmic and got this.

it was when i started spotify in wine.

[Pedro Villavicencio (pedro)]

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.