https://bugs.kde.org/show_bug.cgi?id=316348
Matias Barletta <m...@lionix.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m...@lionix.com --- Comment #25 from Matias Barletta <m...@lionix.com> --- (In reply to Martin Gräßlin from comment #23) > > Those experiencing the problem need to help us: please gdb into the process > and get a backtrace, so that we can see where it consumes the CPU. This id a gdb bt on kubuntu 15.10 (kernel 4.5) and plasma 4:5.5.4-0ubuntu1~ubuntu15.10~ppa1 #0 0x00007f8689b5e88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f86830ee1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f86830ee2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f868a48c4ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007f868a43350a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007f868a43b5ec in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x000000000040ae87 in main () -- You are receiving this mail because: You are watching all bug changes.