vevickit crashes after usb device wakes up, called by system

[Axel Rogat]

Binary package hint: devicekit-disks

?

ProblemType: Crash
Architecture: amd64
AssertionMessage: devkit-disks-daemon: atasmart.c:2725: sk_disk_set_blob: Assertion `blob' failed.
CrashCounter: 1
CustomUdevRuleFiles: gnupg-ccid.rules smart_card.rules
Date: Sun Nov 1 18:55:40 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/devicekit-disks/devkit-disks-daemon
MachineType: HP-Pavilion FL321AA-ABD a6652de
NonfreeKernelModules: fglrx
Package: devicekit-disks 007-2ubuntu3
ProcCmdLine: root=UUID=74b485db-8cdb-48d2-bceb-9050113d7c54 ro splash vga=794
ProcCmdline: /usr/lib/devicekit-disks/devkit-disks-daemon
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
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_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 x86_64
UserGroups: amavis clamav
dmi.bios.date: 10/09/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.17
dmi.board.name: NARRA3
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 3.02
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.17:bd10/09/2008:svnHP-Pavilion:pnFL321AA-ABDa6652de:pvr:rvnPEGATRONCORPORATION:rnNARRA3:rvr3.02:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: FL321AA-ABD a6652de
dmi.sys.vendor: HP-Pavilion

[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.