devkit-disks-helper-ata-smart-collect assert failure: devkit-disks-helper-ata-smart-collect: atasmart.c:2711: sk_disk_get_blob: Assertion `(size_t) ((uint8_t*) p - (uint8_t*) d->blob) == size' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devicekit-disks (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: devicekit-disks
this is a report of a bug on the i386 version of ubuntu version 9.10. it is not the amd bug, but he i386. thought the difference might be important.
ProblemType: Crash
Architecture: i386
AssertionMessage: devkit-
CrashCounter: 1
Date: Thu Nov 5 01:30:49 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
LiveMediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Release i386 (20090420.1)
Lsusb:
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 4971:ce04
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Computer Corporation Inspiron 8200
NonfreeKernelMo
Package: devicekit-disks 007-2ubuntu3
PccardctlIdent:
Socket 0:
no product info available
Socket 1:
no product info available
PccardctlStatus:
Socket 0:
no card
Socket 1:
no card
ProcCmdLine: root=UUID=
ProcCmdline: /usr/lib/
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
Signal: 6
SourcePackage: devicekit-disks
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/
abort () from /lib/tls/
__assert_fail () from /lib/tls/
sk_disk_get_blob () from /lib/libatasmar
Title: devkit-
Uname: Linux 2.6.31-14-generic i686
UserGroups:
dmi.bios.date: 04/04/2002
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A02
dmi.board.name: Inspiron 8200
dmi.board.vendor: Dell Computer Corporation
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComp
dmi.product.name: Inspiron 8200
dmi.sys.vendor: Dell Computer Corporation
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 #451311, 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.