devkit-disks-daemon crashed with SIGSEGV in dbus_g_method_return_error()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devicekit-disks (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: devicekit-disks
Tried to install Ubuntu 9.10 amd64 on HP8510w with several partition already installed (Windows XP & Ubuntu 9.10beta/9.04)
ProblemType: Crash
.etc.fstab:
aufs / aufs rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0
/dev/sda6 swap swap defaults 0 0
Architecture: amd64
Date: Thu Oct 29 23:33:55 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Hewlett-Packard HP Compaq 8510w
Package: devicekit-disks 007-2ubuntu3
PccardctlStatus:
Socket 0:
no card
Socket 1:
3.3V 16-bit PC Card
Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/lib/
ProcEnviron:
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7ff490bbd07e <dbus_g_
PC (0x7ff490bbd07e) ok
source "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed readable region)!
destination "%r8d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: devicekit-disks
StacktraceTop:
dbus_g_
?? ()
?? ()
?? ()
?? ()
Title: devkit-disks-daemon crashed with SIGSEGV in dbus_g_
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:
dmi.bios.date: 12/02/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MVD Ver. F.15
dmi.board.name: 30C5
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.36
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Compaq 8510w
dmi.product.
dmi.sys.vendor: Hewlett-Packard
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 #452208, 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.