installing 9.10 RC clean & recieved this crash notice
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devicekit-disks (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: devicekit-disks
no further info in the output message
ProblemType: Crash
.etc.fstab:
aufs / aufs rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0
Architecture: i386
Date: Sat Oct 24 10:55:34 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
Lsusb:
Bus 002 Device 002: ID 047d:101f Kensington PocketMouse Pro
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0c45:62c0 Microdia Sonix USB 2.0 Camera
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion dv6000 (GA456UA#ABA)
NonfreeKernelMo
Package: devicekit-disks 007-2ubuntu2
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/lib/
ProcEnviron:
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0xf7af1d <dbus_g_
PC (0x00f7af1d) ok
source "0x10(%esi)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%edi" 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 i686
UserGroups:
dmi.bios.date: 05/31/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.37
dmi.board.name: 30B7
dmi.board.vendor: Quanta
dmi.board.version: 65.28
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dv6000 (GA456UA#ABA)
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.