https://bugs.kde.org/show_bug.cgi?id=493519
--- Comment #4 from Matt Fagnani <matt.fagn...@bell.net> --- I've seen this problem on bare metal as well as I mentioned. The threshold might have been set but the pointer stopThresholdIt might've been corrupted or pointed to an inaccessible address. I looked at a few of the reports in the search of Nate in comment 1, but I didn't see ChargeThresholdHelper::getthreshold in their comments. When I searched for ChargeThresholdHelper::getthreshold nothing was found a couple days ago. Thanks. -- You are receiving this mail because: You are watching all bug changes.
