vpnc causes kded to consume 100% cpu

[Ritesh Raj Sarraf]

Binary package hint: vpnc

Given that network-manager-vpnc is not supported for Feisty (See Bug #94889), I tried to use vpnc manually.

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.

[Philipp Kern (pkern)]

Dear kdelibs maintainers, as I don't have a clue about KDE: is there network handling in kded?

[Daniel T Chen (crimsun)]

I can't reproduce this symptom in 8.10 alpha/beta.

[Daniel T Chen (crimsun)]

Closing per inactivity.