Almost all of the time (>90%) kremotecontrol doesn't work. In 10% of cases it works. After restarting the computer i have to restart kremotecontrol several times to make it work. lircd works fine (irw shows correct keypresses). kremotecontrol starts fine, notifier logo is shown but no keypresses are handled. restarting kded4 results in kremotecontrol opening lirc and immediately closing it again as shown in /var/log/syslog: Nov 5 10:24:37 firefly lircd-0.9.0[9538]: accepted new client on /var/run/lirc/lircd Nov 5 10:24:37 firefly lircd-0.9.0[9538]: initializing '/dev/eventbt' Nov 5 10:24:37 firefly lircd-0.9.0[9538]: removed client Nov 5 10:24:37 firefly lircd-0.9.0[9538]: closing '/dev/eventbt' (/dev/eventbt is a symlink to /input/eventX with some X created by a udev rule) reloading kremotecontrol using dbus (qdbus org.kde.kded /kded unloadModule kremotecontroldaemon && qdbus org.kde.kded /kded loadModule kremotecontroldaemon) results in the same behavior, kded4 log says only kded(10078)/kded4 Kded::unloadModule: Unloading module "kremotecontroldaemon" kded(10078)/kded4 Kded::loadModule: Successfully loaded module "kremotecontroldaemon" Reproducible: Sometimes Steps to Reproduce: 1. start kremotecontroldaemon Actual Results: kremotecontrol doesn't handle keypresses on remote control Expected Results: kremotecontrol should handle keypresses on remote control # /etc/lirc/hardware.conf # #Chosen Remote Control REMOTE="Linux input layer (/dev/input/eventX)" REMOTE_MODULES="" REMOTE_DRIVER="devinput" REMOTE_DEVICE="/dev/eventbt" REMOTE_SOCKET="" REMOTE_LIRCD_CONF="devinput/lircd.conf.devinput" REMOTE_LIRCD_ARGS="" #Enable lircd START_LIRCD="true" #Don't start lircmd even if there seems to be a good config file #START_LIRCMD="false" #Try to load appropriate kernel modules LOAD_MODULES="true"
I traced the problem to having a high cpu load at the time kded4 is started. I have boinc running on the machine and if i suspend boinc and restart kded4 everything is working. Reloading only kremotecontrol does not help, only restarting the whole of kded4 and when it is working and boinc is started afterwards reloading kremotecontrol does not break it. This could be reproduced quite a few times...
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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!