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
I did some further debugging and found that disabling the battery plugin
in ubuntu-system-settings does keep system-settings from causing the
load. However, when the device wakes after sleeping on 100% battery
while charging, I see dbus-daemon spewing device changed signals from
upower. Without
Good news. The phone running devel was hanging, but the one running
proposed (#189) was fine. So it's possible this is now no longer an
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337200
Reproduced on a krilin running 185
I opened the battery and brightness panels before turning the the main settings
panel, although Popey says he has not been doing that. strace attached showing
dbus calls with powerd.
seeing this on dbus continuously
signal sender=:1.31 - dest=(null
Seb mind taking a quick look?
Battery and brightness plugins are the only code connecting to powerd
The unit should really be suspended so not sure why settings would consume cpu
on wake, unless the unit does not suspend but the app is backgrounded by app
lifecyle. Still dont see anything
I may well be doing something dumb.
As a test I have just rebooted two phones, one devel, one proposed. I
have started system settings, gone to updates screen. Neither show any
updates. I tapped the power button and have sat them down to charge, so
they'll be on overnight. I'll check them again
Not sure if that's related or maybe expected behaviour, the strace
contains \35\0\0\0org.freedesktop.UPower.Devic… strings which seem to
indicate that something in system settings repeatedly calls the upower
dbus API. If these dbus calls are not expected (for example to refresh
battery info
I think so, yes. Will try again tonight with two devices. One on
updates, one not.
I usually check for updates before bed, then lock screen and stick it on
charge.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tried today while I was out.
Left #133 mako on updates screen.
Left #146 mako on settings main screen.
Locked both and left for 7 hours.
When I returned 133 was usable. 146 was unusable.
Will try again overnight once 146 phone is updated to latest.
--
You received this bug notification
@popey are you always on the system update page?
From the paste it looks like something lower level is in a tight loop polling
a socket or something
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
thanks popey, you did the gdb one wrong it seems. you need to type
continue to resume the code before doing ctrl-C
--
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
As I recall I had no opportunity to type anything after continue as it
was running and had no prompt.
I am afk now until the weekend. Can someone else reproduce this with gdb
debugging? It's really easy to reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Tried getting a gdb backtrace via
https://wiki.ubuntu.com/Backtrace#Already_running_programs but it didn't
work as the app didn't hang and when I did ctrl+c it killed gdb.
** Attachment added: gdb-system-settings.txt
** Tags added: lt-category-visible lt-prio-low
--
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:
This is what I see when I strace the running process
http://paste.ubuntu.com/7807924/
This was while it was sat in the updates screen, doing nothing, but
eating 100% cpu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Be nice if you could attach with gdb and see what its doing
** Changed in: ubuntu-system-settings (Ubuntu)
Status: New = Triaged
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: (unassigned) = Jonas G. Drange (jonas-drange)
--
You received this bug notification because you
** Changed in: ubuntu-system-settings (Ubuntu)
Importance: Undecided = Low
** Changed in: ubuntu-system-settings (Ubuntu)
Importance: Low = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Had this again this morning. Left phone overnight and it's still got
system settings running but is wedged at 100% cpu
top - 11:26:33 up 1 day, 19:36, 2 users, load average: 1.24, 1.08, 1.02
Tasks: 255 total, 2 running, 245 sleeping, 8 stopped, 0 zombie
%Cpu(s): 52.5 us, 3.4 sy, 0.0 ni,
18 matches
Mail list logo
