https://bugs.kde.org/show_bug.cgi?id=429331
--- Comment #6 from Harald Sitter <sit...@kde.org> --- Whoops. Hit save too soon. You could have smartd send notifications to journal and then pick them out via trivial scripting. I really don't think the KCM has a role to play here though. As far as we are concerned there is no nuance. Thats a choice of maintainability of the code as much as the user experience. Either the firmware reports status OK or not. If it is not OK we advise the disk be replaced. If the firmware reports OK but it's not OK then that's a firmware problem same as when the firmware reports not OK but the disk is actually ok. At the same time lower level metrics tracking is something smartd has covered well enough already that I don't see the particular use in replacing that. In particular not as a standard plasma feature. -- You are receiving this mail because: You are watching all bug changes.
