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

[Lubos]

Binary package hint: devicekit-disks

This alert appeared after update from 9.04 to 9.10

ProblemType: Crash
Architecture: i386
AssertionMessage: devkit-disks-daemon: atasmart.c:2725: sk_disk_set_blob: Assertion `blob' failed.
CrashCounter: 1
Date: Sat Oct 31 09:17:29 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/devicekit-disks/devkit-disks-daemon
MachineType: Gigabyte Technology Co., Ltd. P35-DS3L
Package: devicekit-disks 007-2ubuntu3
ProcCmdLine: root=UUID=feeea9e2-21c1-4081-a417-8de40e4bc3b7 ro quiet splash
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:

dmi.bios.date: 08/13/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: P35-DS3L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/13/2007:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-DS3L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[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 #477330, 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.