https://bugs.kde.org/show_bug.cgi?id=417592
--- Comment #9 from bug2...@wolke7.net --- Since my reboot on the 23rd I could not reproduce that problem with 4 resume cycles. I had no relevant updates, so the same machine might or might not reproduce the problem. One question is: Does it needs to be triggered on the first resume cycle? -- You are receiving this mail because: You are watching all bug changes.
