KRadio starts using 100% CPU after some button are pressed on the remote
Bug #157892 reported by
Slobodan Simić
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kradio (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: kradio
KRadio worked just fine until I decided to enable LIRC support and assign keys of
the remote with kradio's actions in KRadio's Configuration window>LIRC support.
From that point, CPU usage goes on 96-99% for kradio every time I press some remote button.
(Even the one that's not defined in kradio's dialog)
KRadio became unresponable and only KILL helps.
KRadio use his own LIRC support so I think it's definately kradio's problem, since
I use IRKick and lirc without any problems with other KDE and non-KDE apps.
Revision history for this message
| Slobodan Simić (slsimic) wrote | #1 |
| Changed in kradio: | |
| status: | New → Confirmed |
To post a comment you must log in.
Same thing when updated to gutsy.
lirc and irKick works fine but when kradio is started any button pressed on the remote makes kradio uses 99%cpu and became unresponsive altough lirc and irKick control continues to work fine with other apps.
I tried to unload kradio's lirc plugin before pushing any remote button and then cpu usage stays at normal but then of course there is no use of remote control with kradio.