Unassigning, I'm not working on that one. Looking a bit to it I can
confirm what Ken wrote, in some cases there is a low level event spam,
seems like rather a kernel/udev/... issue, it just happens that u-s-s
reacts to those events and the callback uses some cpu, so calling it in
loop leads to the cpu usage
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: Sebastien Bacher (seb128) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337200
Title:
U-S-S sluggish after some hours, high CPU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1337200/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
