| Summary: | Touchpad kded module hogs CPU | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Ralf Jung <post> |
| Component: | kcm_touchpad | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | bhush94, kde, nate, plasma-bugs, rajeeshknambiar |
| Priority: | NOR | ||
| Version: | 5.17.5 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Unfortunately I have no clue what is causing this. If touchpad kde daemon is causing high cpu usage, it has got something to do with touchpad enable/disable hotkey. Is it possible to debug kded5, component kded_touchpad? See source code in plasma-desktop: kcms/touchpad/src/kded/kded.cpp and kcms/touchpad/src/kded/kdedactions.cpp I have just had the same exact event. It happened when I logged out from a separate user on the same machine. kded5 kept running and eat up CPU. Hello! This bug report concerns the Synaptics version of the Touchpad page, which is no longer supported in Plasma 6. Can you please see if the issue still happens when using Libinput? If so, please change the status back to "REPORTED." If not, go ahead and change it to "RESOLVED FIXED", or let the bot do it automatically after a month. Thanks! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |
I currently have a kded5 process using one CPU core full-time for almost two hours. Attaching gdb to it shows: Thread 2 (Thread 0x7f0bfb7fe700 (LWP 15144)): #0 0x00007f0c1c14652d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f0c064156b1 in poll (__timeout=-1, __nfds=1, __fds=0x7f0bec026cf0) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 poll_func (ufds=0x7f0bec026cf0, nfds=1, timeout=-1, userdata=0x7f0bf4048c40) at pulse/thread-mainloop.c:69 #3 0x00007f0c06406db1 in pa_mainloop_poll (m=m@entry=0x7f0bf4048b40) at pulse/mainloop.c:844 #4 0x00007f0c0640744e in pa_mainloop_iterate (m=0x7f0bf4048b40, block=<optimized out>, retval=0x0) at pulse/mainloop.c:926 #5 0x00007f0c06407500 in pa_mainloop_run (m=0x7f0bf4048b40, retval=retval@entry=0x0) at pulse/mainloop.c:944 #6 0x00007f0c06415646 in thread (userdata=0x7f0bf4048b00) at pulse/thread-mainloop.c:88 #7 0x00007f0c05962978 in internal_thread_func (userdata=0x7f0bf4048cf0) at pulsecore/thread-posix.c:81 #8 0x00007f0c19ec20a4 in start_thread (arg=0x7f0bfb7fe700) at pthread_create.c:309 #9 0x00007f0c1c14f06d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f0c1c6ec8c0 (LWP 9316)): #0 XRecordKeyboardMonitor::processNextReply (this=0x14b5d90) at ../../../../kcms/touchpad/src/backends/x11/xrecordkeyboardmonitor.cpp:98 #1 0x00007f0c1a7067ba in QMetaObject::activate (sender=sender@entry=0x14b5ef0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff56f77eb0) at kernel/qobject.cpp:3718 #2 0x00007f0c1a706fb7 in QMetaObject::activate (sender=sender@entry=0x14b5ef0, m=m@entry=0x7f0c1a9206e0 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff56f77eb0) at kernel/qobject.cpp:3583 #3 0x00007f0c1a785a0e in QSocketNotifier::activated (this=this@entry=0x14b5ef0, _t1=10) at .moc/moc_qsocketnotifier.cpp:134 #4 0x00007f0c1a712c9b in QSocketNotifier::event (this=0x14b5ef0, e=<optimized out>) at kernel/qsocketnotifier.cpp:296 #5 0x00007f0c1bb369fc in QApplicationPrivate::notify_helper (this=this@entry=0x139f750, receiver=receiver@entry=0x14b5ef0, e=e@entry=0x7fff56f78120) at kernel/qapplication.cpp:3717 #6 0x00007f0c1bb3bec6 in QApplication::notify (this=0x7fff56f78410, receiver=0x14b5ef0, e=0x7fff56f78120) at kernel/qapplication.cpp:3500 #7 0x00007f0c1a6d7c7b in QCoreApplication::notifyInternal (this=0x7fff56f78410, receiver=0x14b5ef0, event=event@entry=0x7fff56f78120) at kernel/qcoreapplication.cpp:965 #8 0x00007f0c1a72e8fd in QCoreApplication::sendEvent (event=0x7fff56f78120, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224 #9 socketNotifierSourceDispatch (source=0x13eb890) at kernel/qeventdispatcher_glib.cpp:101 #10 0x00007f0c199a2c3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x00007f0c199a2f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x00007f0c199a2fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x00007f0c1a72e44b in QEventDispatcherGlib::processEvents (this=0x13e9780, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #14 0x00007f0c1a6d540a in QEventLoop::exec (this=this@entry=0x7fff56f78330, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #15 0x00007f0c1a6dd4cc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #16 0x00007f0c1c41f297 in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kded5.so #17 0x00007f0c1c08ab45 in __libc_start_main (main=0x400720 <main>, argc=1, argv=0x7fff56f78578, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff56f78568) at libc-start.c:287 #18 0x000000000040074e in _start () This is confirmed by "sudo perf top": 24.73% kded_touchpad.so [.] 0x0000000000033df4 18.79% libxcb.so.1.1.0 [.] xcb_poll_for_reply 12.24% kded_touchpad.so [.] 0x0000000000033dec Reproducible: Didn't try This is probably the wrong product, but I had no idea what "kded_touchpad.so" belongs to. It is packaged as part of plasma-desktop in Debian, so I figured this may be a good place to start.