This was a really ham-handed workaround. The percentage of users with
SSDs has got to be under 1%, and to help them, you're going to risk the
rest of your users losing data b/c they thought their system was
monitoring their drive health and now it's not? Seems pretty stupid to
me, but what do I
Chris,
it's available in Lucid, why is it then invalid in Karmic?
** Changed in: devicekit-disks (Ubuntu)
Status: Invalid = Confirmed
--
palimpsest / gnome-disk-utility stopped working normally from recently -
incorrectly says that SMART is not available !!
I am not sure I understand - it seems that the functionality of the
utility has been entirely lost for a large class of users in order to
fix a hardware problem for another class of users. While it's well
intentioned (assuming the utility was causing damage to the hardware,
even for a small group
Sorry if this is a dumb question, but for those of us without any SSD
disks is there a way to manually re-enable the SMART monitoring?
--
palimpsest / gnome-disk-utility stopped working normally from recently -
incorrectly says that SMART is not available !!
Please see my last comment.
Adding checks for HDD/SSD is fairly unlikely to happen as a SRU for
karmic, but SMART may be re-enabled again once the libatasmart bug is
fixed (bug 445852)
** Changed in: devicekit-disks (Ubuntu)
Status: Confirmed = Invalid
--
palimpsest /
I confirm this problem on HDD.
Please detect if HDD or SDD before to configure devicekits-kits, because
it seems several HDD users has the same problem.
Thanks. :)
** Changed in: devicekit-disks (Ubuntu)
Status: Invalid = Confirmed
--
palimpsest / gnome-disk-utility stopped working
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42781455/Dependencies.txt
--
palimpsest / gnome-disk-utility stopped working normally from recently -
incorrectly says that SMART is not available !!
https://bugs.launchpad.net/bugs/553282
You received this bug notification
Thank you for your bug report. However, this is intentional as a
workaround for bug 445852, and is explained in the changelog for the
last devicekit-disks upload (which should have been viewable in update-
manager when you updated):
devicekit-disks (007-2ubuntu6) karmic-proposed; urgency=low
*