https://bugs.kde.org/show_bug.cgi?id=447245
--- Comment #30 from PK <pieterkristen...@gmail.com> --- I just turned automatic updates off because this bug obviously lives on without my experiences with auto update. So after I turned off automatic updates I let do Discover it's job - there was a lot to do! Without thinking so much I started up Firefox and that responded not so well at all. But I learned quickly that starting up Firefox (or perhaps any other app) asks quite some cpu power. And at that moment it was clear that Firefox and Discover got in each others way. But only ten seconds or less after, Firefox was no real burden to the system anymore and I could normally browse and update at the same time. Even if mine is definitely not a "power computer". It goes against my instincts to make the auto update process depend on whatever condition. But perhaps it could hold a few seconds when the system load exceeds a certain value? I'm looking forward to your solution of this problem. -- You are receiving this mail because: You are watching all bug changes.
