GNOME Bugzilla – Bug 745195
Gnome-shell writes to journald every second due to system monitors extension
Last modified: 2018-02-24 02:37:36 UTC
I have dual-core processor. ArchLinux, gnome-shell 3.14.3 from official repositories After disconnecing one core to save power (echo 0 > /sys/devices/system/cpu/cpu1/online) gnome-shell every second writes to journal: feb 26 10:32:14 awildnote gnome-session[9460]: glibtop: 'cpu2 33752 3452 9803 69508 267 0 16 0 0 0 feb 26 10:32:14 awildnote gnome-session[9460]: intr 1116285 26 5289 0 0 0 0 0 0 1 3958 0 0 0 0 0 0 0 0 3342 0 0 0 0 123 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 88125 28 17 96186 54942 16 708 0 0 0 0 0 feb 26 10:32:14 awildnote gnome-session[9460]: ctxt 4557313 feb 26 10:32:14 awildnote gnome-session[9460]: btime 1424933441 feb 26 10:32:14 awildnote gnome-session[9460]: processes 39491 feb 26 10:32:14 awildnote gnome-session[9460]: procs_running 3 feb 26 10:32:14 awildnote gnome-session[9460]: procs_blocked 0 feb 26 10:32:14 awildnote gnome-session[9460]: softirq 1025465 50 353124 991 9822 95758 4 22841 200560 949 341366 feb 26 10:32:14 awildnote gnome-session[9460]: ' does not start with 'cpu1': Resource temporarily unavailable feb 26 10:32:15 awildnote gnome-session[9460]: glibtop: 'cpu2 33755 3452 9804 69555 267 0 16 0 0 0 feb 26 10:32:15 awildnote gnome-session[9460]: intr 1116498 26 5299 0 0 0 0 0 0 1 3958 0 0 0 0 0 0 0 0 3342 0 0 0 0 123 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 88133 28 17 96186 54942 16 708 0 0 0 0 0 feb 26 10:32:15 awildnote gnome-session[9460]: ctxt 4558429 feb 26 10:32:15 awildnote gnome-session[9460]: btime 1424933441 feb 26 10:32:15 awildnote gnome-session[9460]: processes 39491 feb 26 10:32:15 awildnote gnome-session[9460]: procs_running 3 feb 26 10:32:15 awildnote gnome-session[9460]: procs_blocked 0 feb 26 10:32:15 awildnote gnome-session[9460]: softirq 1025585 50 353167 991 9822 95758 4 22851 200605 949 341388 feb 26 10:32:15 awildnote gnome-session[9460]: ' does not start with 'cpu1': Resource temporarily unavailable feb 26 10:32:15 awildnote gnome-session[9460]: glibtop: 'cpu2 33759 3452 9805 69598 267 0 16 0 0 0 feb 26 10:32:15 awildnote gnome-session[9460]: intr 1116777 26 5308 0 0 0 0 0 0 1 3958 0 0 0 0 0 0 0 0 3342 0 0 0 0 123 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 88159 28 17 96186 54942 16 708 0 0 0 0 0 feb 26 10:32:15 awildnote gnome-session[9460]: ctxt 4559735 feb 26 10:32:15 awildnote gnome-session[9460]: btime 1424933441 feb 26 10:32:15 awildnote gnome-session[9460]: processes 39491 feb 26 10:32:15 awildnote gnome-session[9460]: procs_running 1 feb 26 10:32:15 awildnote gnome-session[9460]: procs_blocked 0 feb 26 10:32:15 awildnote gnome-session[9460]: softirq 1025706 50 353213 991 9822 95758 4 22860 200650 949 341409 feb 26 10:32:15 awildnote gnome-session[9460]: ' does not start with 'cpu1': Resource temporarily unavailable feb 26 10:32:16 awildnote gnome-session[9460]: glibtop: 'cpu2 33762 3452 9807 69643 267 0 16 0 0 0 feb 26 10:32:16 awildnote gnome-session[9460]: intr 1116994 26 5313 0 0 0 0 0 0 1 3958 0 0 0 0 0 0 0 0 3342 0 0 0 0 123 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 88179 28 17 96186 54942 16 708 0 0 0 0 0 feb 26 10:32:16 awildnote gnome-session[9460]: ctxt 4560874 feb 26 10:32:16 awildnote gnome-session[9460]: btime 1424933441 feb 26 10:32:16 awildnote gnome-session[9460]: processes 39491 feb 26 10:32:16 awildnote gnome-session[9460]: procs_running 2 feb 26 10:32:16 awildnote gnome-session[9460]: procs_blocked 0 feb 26 10:32:16 awildnote gnome-session[9460]: softirq 1025821 50 353257 991 9822 95758 4 22865 200693 950 341431 feb 26 10:32:16 awildnote gnome-session[9460]: ' does not start with 'cpu1': Resource temporarily unavailable
(In reply to uselessfire from comment #0) > feb 26 10:32:14 awildnote gnome-session[9460]: glibtop: 'cpu2 33752 3452 > 9803 69508 267 0 16 0 0 0 Are you using the system monitors extension?
Yes, and no more errors after i turned it off. This is the same issue with indicator-multiload: https://bugs.launchpad.net/indicator-multiload/+bug/877420/+activity I changed the category to "extensions"
You should contact the authors of the extensions. Reporting it here don't help because there is no guarantee that the extension author even sees this bug. The extension component is mostly for extension shipped in gnome-shell-extensions.
(In reply to drago01 from comment #3) > The extension component is mostly for extension shipped in > gnome-shell-extensions. It's not part of classic-mode or anything, but it is actually part of the gnome-shell-extensions module (for now) ...
Created attachment 298583 [details] [review] extensions: Remove systemMonitor extension The systemMonitor extension extends the message tray with its UI, which obviously broke when the bottom tray was removed. It has also been the source for various performance/memory issues in the past and is part of the semi-random collection that pre-dates the extension.gnome.org site rather than the set of classic-mode/endorsed extensions, so just remove it from the module. Hopefully this will motivate someone who actually cares about it to pick it up ...
Attachment 298583 [details] pushed as c9a6421 - extensions: Remove systemMonitor extension
I am astounded that this hasn't been repaired yet. That's a funny use of the term 'fixed'. Anyway, give me a 101 course on writing gnome extensions, I'll see if I can manage not to make it worse. FYI, I installed this extension 2 days ago in Leap, and it worked perfectly after I rebooted. Now in Tumbleweed, it's giving me an error on download. :(
(In reply to crogonint from comment #7) > FYI, I installed this extension 2 days ago in Leap, and it worked perfectly > after I rebooted Unless Leap ships a very old GNOME version, you installed a different extension. The one that was removed added itself to a UI element that was removed in 3.16 ...
Well, I sincerely apologize. I can't imagine why only one extension or the other showed up when I searched for it, but you are correct. :/