do not have any idea about the cause...began showing up after upgrade to 9.10

[cb Turner]

Binary package hint: devicekit-disks

Don't know if this has anything to do with it, but my two USB external HD's were showing up on the desktop. I just noticed that they were not there after upgrade to 9.10. I can mount them with no problem, but they didn't "automatically" mount.

ProblemType: Crash
Architecture: i386
AssertionMessage: devkit-disks-daemon: atasmart.c:2725: sk_disk_set_blob: Assertion `blob' failed.
Date: Sun Nov 1 16:52:44 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/devicekit-disks/devkit-disks-daemon
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Acer Aspire T180
NonfreeKernelModules: nvidia
Package: devicekit-disks 007-2ubuntu3
ProcCmdLine: root=UUID=0a8d9b8c-6d90-441e-b899-653a5a26fad4 ro quiet splash
ProcCmdline: /usr/lib/devicekit-disks/devkit-disks-daemon
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.28-16.55-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.28-16-generic i686
UserGroups:

dmi.bios.date: 04/27/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: R01-B4
dmi.board.name: EM61SM/EM61PM
dmi.board.vendor: Acer
dmi.chassis.asset.tag: Asset tag number: at least 22 digits
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrR01-B4:bd04/27/2007:svnAcer:pnAspireT180:pvrR01-B4:rvnAcer:rnEM61SM/EM61PM:rvr:cvn:ct3:cvr:
dmi.product.name: Aspire T180
dmi.product.version: R01-B4
dmi.sys.vendor: Acer

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