devkit-disks-daemon assert failure: devkit-disks-daemon: atasmart.c:2725: sk_disk_set_blob: Assertion `blob' failed.

[A. Leon]

Binary package hint: devicekit-disks

Apport caught this bug...

ProblemType: Crash
Architecture: i386
AssertionMessage: devkit-disks-daemon: atasmart.c:2725: sk_disk_set_blob: Assertion `blob' failed.
Date: Wed Oct 21 23:03:52 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/devicekit-disks/devkit-disks-daemon
MachineType: Gateway MC7833U
Package: devicekit-disks 007-2ubuntu2
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-14-generic-pae root=/dev/mapper/system-root ro quiet splash
ProcCmdline: /usr/lib/devicekit-disks/devkit-disks-daemon
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae
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-pae i686
UserGroups:

dmi.bios.date: 12/01/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 99.06
dmi.board.vendor: Gateway
dmi.board.version: 99.06
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 8
dmi.chassis.vendor: Gateway
dmi.chassis.version: Rev.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr99.06:bd12/01/2008:svnGateway:pnMC7833U:pvrRev1:rvnGateway:rn:rvr99.06:cvnGateway:ct8:cvrRev.1:
dmi.product.name: MC7833U
dmi.product.version: Rev 1
dmi.sys.vendor: Gateway

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