vpnc causes kded to consume 100% cpu
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdelibs (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
vpnc (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: vpnc
Given that network-
After configuring vpnc manually, I'm able to establish a vpn connection with vpnc. The bug is that as soon as vpnc establishes the vpn connection, kded cpu utilization goes to 90%+ CPU usage.
I think this issue is related to the feature introduced in Feisty where applications only use the network when K Network Manager is Online. Probably kded is not intelligent about vpnc and K Network Manager's vpnc support is broken.
With this, using vpnc on Kubuntu is difficult because Kubuntu relies on K Network Manager and K Network Manager doesn't have vpnc support and (vpnc + kded) has a bug.
Dear kdelibs maintainers, as I don't have a clue about KDE: is there network handling in kded?