devicekit-disks crashes apruptply

[dingsi]

Binary package hint: devicekit-disks

none

ProblemType: Crash
Architecture: i386
AssertionMessage: devkit-disks-daemon: atasmart.c:2725: sk_disk_set_blob: Assertion `blob' failed.
CustomUdevRuleFiles: z80_user.rules
Date: Thu Nov 5 18:00:51 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/devicekit-disks/devkit-disks-daemon
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: devicekit-disks 007-2ubuntu3
ProcCmdLine: root=UUID=b80a3b94-b1cb-4f30-a537-ae4541bdfcdb ro quiet splash ipv5.disabled=1
ProcCmdline: /usr/lib/devicekit-disks/devkit-disks-daemon
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 6
SourcePackage: devicekit-disks
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 __assert_fail () from /lib/tls/i686/cmov/libc.so.6
 sk_disk_set_blob () from /lib/libatasmart.so.4
Title: devkit-disks-daemon assert failure: devkit-disks-daemon: atasmart.c:2725: sk_disk_set_blob: Assertion `blob' failed.
Uname: Linux 2.6.31-14-generic i686
UserGroups: fuse root tape
dmi.bios.date: 11/14/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1017.002
dmi.board.name: A8V Deluxe
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1017.002:bd11/14/2005:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnA8VDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Apport retracing service (apport)]

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.