Bug 3627 - Disconnecting ppp0 from net_applet results in kded4 comsuming high CPU usage
Summary: Disconnecting ppp0 from net_applet results in kded4 comsuming high CPU usage
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Olivier Blin
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-06 00:00 CET by Jin-tong Hu
Modified: 2012-01-27 16:24 CET (History)
1 user (show)

See Also:
Source RPM: drakx-net
CVE:
Status comment:


Attachments

Description Jin-tong Hu 2011-12-06 00:00:56 CET
Description of problem:

With the Mageia 2 Alpha 1 KDE4 Live CD system installed on my hard disk, after I disconnected the ppp0 network connection from net_applet, I found in the system monitor that the kded4 process immediately comsumed 100% of either one of my 2 CPU cores. Moreover, some KDE apps, such as Kwrite and Konqueror, started to respond slower than usual. This situation continued even if I tried reconnecting the ppp0 connection from net_applet. I had to restart the system to get the system recovered.

How reproducible:

Everytime I disconnect the ppp0 connection from net_applet.

PS.: My network uses the ADSL PPPoE connection. When configuring the connection, I checked the two options below: start the connection at system startup and let the user manage the connection.
Comment 1 Marja Van Waes 2012-01-26 21:27:07 CET
Jin-tong Hu,

Thanks for your report and sorry for being so late to respond to it. We are short on triagers.

Could you please attach everything mentioned here that applies to your system:

https://wiki.mageia.org/en/Triage_guide#Networking_issues

Please close this bug if it was solved by an update.

Assigning to drakx-net maintainer.

@

CC: (none) => marja11
Source RPM: (none) => drakx-net

Comment 2 Marja Van Waes 2012-01-26 21:31:18 CET
(In reply to comment #1)

> 
> Assigning to drakx-net maintainer.
> 
> @ Blino

Of course reassign to bugsquad if, from the attachments that'll be provided, it becomes clear that you don't maintain the culprit.

And please explain, then :)

Assignee: bugsquad => mageia

Comment 3 Jin-tong Hu 2012-01-27 16:24:54 CET
In my current Cauldron system, with all updates starting from Mageia 2 Alpha 1 applied, the problem has disappeared, so I close this bug. Thanks for your reply.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.