update-notifier crashed with SIGSEGV in gdu_device_get_object_path()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-notifier (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: update-notifier
update-notifier crashed with SIGSEGV in gdu_device_
ProblemType: Crash
Architecture: amd64
Date: Fri Jan 29 00:03:36 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20091215)
NonfreeKernelMo
Package: update-notifier 0.92
ProcCmdline: update-notifier --startup-delay=60
ProcEnviron:
PATH=(custom, user)
LANG=en_IN
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7fa8243965f0 <gdu_device_
PC (0x7fa8243965f0) 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
StacktraceTop:
gdu_device_
gdu_pool_new () from /usr/lib/
up_do_hal_init ()
main ()
Title: update-notifier crashed with SIGSEGV in gdu_device_
Uname: Linux 2.6.32-12-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev root sambashare tape vboxusers video
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 #422392, 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.