Bug 378316 - High cpu usage in task manager network monitor when "Setting network address" state
Summary: High cpu usage in task manager network monitor when "Setting network address"...
Status: RESOLVED DUPLICATE of bug 356479
Alias: None
Product: plasma-nm
Classification: Plasma
Component: general (show other bugs)
Version: 5.9.4
Platform: Chakra Linux
: NOR minor
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-31 13:19 UTC by Sergio Torres Soldado
Modified: 2017-05-09 08:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sergio Torres Soldado 2017-03-31 13:19:53 UTC 
While trying to establish a connection in "auto" i.e. dhcp while here is no dhcp server the cpu usage for plasmashell maxes out 1 core. I don't know if the animation is responsible or other process. How can I debug this? Thanks.
Comment 1 Christoph Feck 2017-04-01 11:48:22 UTC 
Which plasmashell version? Also, are you really using 'knemo' or Plasma's network monitor widget?
Comment 2 Sergio Torres Soldado 2017-04-02 10:20:26 UTC 
plasmashell 5.9.4

Its the plasmashell process that occupies cpu resources so I guess it is Plasma's network monitor widget
Comment 3 Jan Grulich 2017-05-09 08:11:19 UTC 

*** This bug has been marked as a duplicate of bug 356479 ***