Devicekit-disks crash at system initialization
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devicekit-disks (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: devicekit-disks
Description: Ubuntu 9.10
Release: 9.10
Since replacement of Jaunty Jacklope (Ubuntu 9.04) by Karmic Koala Devicekit-disks crashes at system initialization
This crash has no known impact on the usability of the system, and is reported only because apport crash detection is enabled by default.
ProblemType: Crash
.etc.fstab:
UUID=9b03fde0-
UUID=b5712264-
UUID=0cd3d00e-
UUID=b5f1c2c0-
UUID=4d15d909-
Architecture: amd64
AssertionMessage: devkit-
CrashCounter: 1
CustomUdevRuleF
Date: Mon Nov 2 20:23:01 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
MachineType: System manufacturer System Product Name
NonfreeKernelMo
Package: devicekit-disks 007-2ubuntu3
ProcCmdLine: root=UUID=
ProcCmdline: /usr/lib/
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
Signal: 6
SourcePackage: devicekit-disks
StacktraceTop:
raise () from /lib/libc.so.6
abort () from /lib/libc.so.6
__assert_fail () from /lib/libc.so.6
sk_disk_get_blob () from /lib/libatasmar
?? ()
Title: devkit-
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: admin cdrom fuse scanner
dmi.bios.date: 03/26/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0503
dmi.board.
dmi.board.name: M2N-MX SE Plus
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
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 #451311, 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.