https://bugs.kde.org/show_bug.cgi?id=525349
Nate Graham <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Nate Graham <[email protected]> --- Just noticed something else: reproducing the bug results in two kscreenlocker_worker processes spawning, staying open, and each consuming 100% CPU time. Each has different arguments: nate 19261 1691 99 08:49 ? 00:01:08 /usr/lib/kscreenlocker_worker kde-fingerprint nate nate 19263 1691 99 08:49 ? 00:01:08 /usr/lib/kscreenlocker_worker kde nate In case it's relevant, the computer does not have a fingerprint reader. A backtrace of what one of them is doing at the time is not very helpful, but here you go anyway: #0 0x00007f61c902f80a in std::basic_ios<char, std::char_traits<char> >::clear(std::_Ios_Iostate) () from /usr/lib/libstdc++.so.6 #1 0x00007f61c8fca268 in std::basic_istream<char, std::char_traits<char> >& std::getline<char, std::char_traits<char>, std::allocator<char> >(std::basic_istream<char, std::char_traits<char> >&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, char) () from /usr/lib/libstdc++.so.6 #2 0x0000565449336e3d in main () Raising priority accordingly. -- You are receiving this mail because: You are watching all bug changes.
