devkit-disks-daemon assert failure: devkit-disks-daemon: atasmart.c:2725: sk_disk_set_blob: Assertion `blob' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devicekit-disks (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: devicekit-disks
I suspect that this is a duplicate of another bug listed, but it wasn't obvious to me which one, hence posting as new.
I did a clean install of Intrepid, updated all, rebooted, upgraded to Jaunty (keeping old kernel image, or else my system wouldn't work at all), updated all and finally upgraded to Karmic. Had sound in Intrepid and after Jaunty updates, but no sound at all in Karmic.
Once again, apologies if I've created more work by posting a duplicate.
ProblemType: Crash
Architecture: i386
AssertionMessage: devkit-
Date: Sun Oct 25 07:54:23 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
MachineType: System manufacturer System Product Name
Package: devicekit-disks 007-2ubuntu3
ProcCmdLine: root=UUID=
ProcCmdline: /usr/lib/
ProcEnviron:
ProcVersionSign
Signal: 6
SourcePackage: devicekit-disks
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/
abort () from /lib/tls/
__assert_fail () from /lib/tls/
sk_disk_set_blob () from /lib/libatasmar
Title: devkit-disks-daemon assert failure: devkit-
Uname: Linux 2.6.31-14-generic i686
UserGroups:
dmi.bios.date: 02/02/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5VD2-MX ACPI BIOS Revision 1012
dmi.board.name: P5VD2-MX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: System Product Name
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 #449446, 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.