https://bugs.kde.org/show_bug.cgi?id=438539
--- Comment #2 from Harald Sitter <sit...@kde.org> --- It's tricky to be sure. We don't actually know, or rather we don't care because it'd cost a whole lot code maintenance, how exactly things are failing. If smartctl says there are errors in the logs we just take that information and run with it. Having the ability to acknowledge "yo, I've seen the error and this error isn't an error, go away" is exceptionally tricky to implement because we don't know what "this error" actually is in terms of raw data. I wonder if it might be sufficient to add an option to ignore these "soft" errors? They are not actually indicative of the firmware saying something is wrong but rather something may be wrong but the firmware thinks it's not a biggie, so depending on how much you trust the firmware you could ignore the "soft" errors. In fact, when this feature was added I did ponder that we could simply disable the notification if we find it raises false positives. Going slightly over temperature limits seems like a false positive to me. That is: we could disable the notification but if you open kinfocenter manually it'd tell you that there may be signs of problems. -- You are receiving this mail because: You are watching all bug changes.
