Re: High CPU load caused by plasmashell
On Wednesday, 2016-06-15, 09:05:16, Marc Haber wrote: > I have two desktop machines and two laptops running current unstable > with KDE. Both desktops do have the issue that plasmashell suddenly > begins taking a full CPU core while staying fully responsive. This > especially happens after suspend or when the system was idle for some > time, for example when I go to lunch and return an hour later. > > X itself takes about 50 % CPU if this happens. > > Killing off plasmashell and starting a new one solves the issue. > > Is this a common issue? Is it already known what causes the issue? > What can I do to find out what happens? When I see this behavior it usually involves some applet or symbol in the notification area doing something animated. E.g. I get this during file copy operations when the notification icon shows a spin animation, or when the network applet shows a spin animation when it tries to connect to a network that doesn't react promptly, or when Kopete has "pulses" its icon. Cheers, Kevin signature.asc Description: This is a digitally signed message part.
Re: High CPU load caused by plasmashell
On Wed, Jun 15, 2016 at 01:39:37PM +0200, Diederik de Haas wrote: > You do need to manually install them, but you don't have to guess your > suspects. When things crash you should get a window with debugging info > (DrKonqi?) and then you can see whether you get a useful backtrace. Unfortuantely, things don't crash, they just run around in circles. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Re: High CPU load caused by plasmashell
On woensdag 15 juni 2016 13:31:20 CEST Marc Haber wrote: > > These are the debug lines I have in my sources.list: > > deb http://debug.mirrors.debian.org/debian-debug unstable-debug main > > contrib non-free > > > > deb http://debug.mirrors.debian.org/debian-debug experimental-debug main > > contrib non-free > > And I need to manually install those belonging to the packages that I > suspect to be at fault? You do need to manually install them, but you don't have to guess your suspects. When things crash you should get a window with debugging info (DrKonqi?) and then you can see whether you get a useful backtrace. If you get paths with linenumbers then you have good one. If it only shows an object name (*.so usually) you can usually find the corresponding package with: dpkg -S $(which ) and then search for a corresponding -dbg or -dbgsym package and install that. Once you've done that, reload the stacktrace and then it should be able to further specify the backtrace. Repeat this as often as needed/useful.
Re: High CPU load caused by plasmashell
On Wed, Jun 15, 2016 at 01:18:28PM +0200, Diederik de Haas wrote: > On woensdag 15 juni 2016 09:33:31 CEST Martin Steigerwald wrote: > > > Do the current unstable KDE packages have debugging symbol > > > counterparts? I am a bit outdated on the availability of debugging > > > symbols for Debian packages, there was a change in their generation > > > last year, I think I remember, right? > > > > I think these are now in dbgsym packages and you need an extra line in > > sources.list to get these. I do not fully remember what this line looks > > like but it had something along with "debug" in it. > > These are the debug lines I have in my sources.list: > deb http://debug.mirrors.debian.org/debian-debug unstable-debug main contrib > non-free > > deb http://debug.mirrors.debian.org/debian-debug experimental-debug main > contrib non-free And I need to manually install those belonging to the packages that I suspect to be at fault? Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Re: High CPU load caused by plasmashell
On woensdag 15 juni 2016 09:33:31 CEST Martin Steigerwald wrote: > > Do the current unstable KDE packages have debugging symbol > > counterparts? I am a bit outdated on the availability of debugging > > symbols for Debian packages, there was a change in their generation > > last year, I think I remember, right? > > I think these are now in dbgsym packages and you need an extra line in > sources.list to get these. I do not fully remember what this line looks > like but it had something along with "debug" in it. These are the debug lines I have in my sources.list: deb http://debug.mirrors.debian.org/debian-debug unstable-debug main contrib non-free deb http://debug.mirrors.debian.org/debian-debug experimental-debug main contrib non-free
Re: High CPU load caused by plasmashell
On Wed, Jun 15, 2016 at 09:48:23AM +0200, Martin Steigerwald wrote: > On Mittwoch, 15. Juni 2016 09:37:46 CEST Marc Haber wrote: > > On Wed, Jun 15, 2016 at 09:33:31AM +0200, Martin Steigerwald wrote: > > > Another thing would be: Does it loop any message when it utilizes CPU > > > heavily? > > No. That would be an obvious hint. > > > > Greetings > > Marc, not too excited about having to ditch my carefully crafted > > configuration for a Heisenbug. > > No need to ditch it, I´d say. You can backup it if you find out where it is > stored. I'm going to try a new account on one of the desktops. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Re: High CPU load caused by plasmashell
On Mittwoch, 15. Juni 2016 09:37:46 CEST Marc Haber wrote: > On Wed, Jun 15, 2016 at 09:33:31AM +0200, Martin Steigerwald wrote: > > Another thing would be: Does it loop any message when it utilizes CPU > > heavily? > No. That would be an obvious hint. > > Greetings > Marc, not too excited about having to ditch my carefully crafted > configuration for a Heisenbug. No need to ditch it, I´d say. You can backup it if you find out where it is stored. My bet would be: - plasmashellrc - plasma-org.kde.plasma.desktop-appletsrc from looking at: martin@merkaba:~/.config> ls -l plasma* -rw-r--r-- 1 martin martin55 Okt 8 2015 plasma-localerc -rw-r--r-- 1 martin martin 242 Okt 8 2015 plasma-locale-settings.sh -rw--- 1 martin martin 12871 Jun 14 18:05 plasma-org.kde.plasma.desktop- appletsrc -rw--- 1 martin martin54 Feb 21 11:55 plasmarc -rw--- 1 martin martin 2427 Jun 15 09:44 plasmashellrc -rw--- 1 martin martin 246 Mai 27 18:41 plasmawindowed-appletsrc -rw--- 1 martin martin 114 Mai 27 18:57 plasmawindowedrc -rw--- 1 martin martin 648 Feb 21 11:40 plasma_workspace.notifyrc The plasmawindowed* files do not appear to be needed, I removed them and restarted plasmashell and they are still gone for good. Ciao, -- Martin
Re: High CPU load caused by plasmashell
On Wed, Jun 15, 2016 at 09:33:31AM +0200, Martin Steigerwald wrote: > Another thing would be: Does it loop any message when it utilizes CPU heavily? No. That would be an obvious hint. Greetings Marc, not too excited about having to ditch my carefully crafted configuration for a Heisenbug. -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Re: High CPU load caused by plasmashell
On Mittwoch, 15. Juni 2016 09:05:16 CEST Marc Haber wrote: > I have two desktop machines and two laptops running current unstable > with KDE. Both desktops do have the issue that plasmashell suddenly > begins taking a full CPU core while staying fully responsive. This > especially happens after suspend or when the system was idle for some > time, for example when I go to lunch and return an hour later. > > X itself takes about 50 % CPU if this happens. Could be one of the plasma applets you are using. They are running in process and if one of these things go crazy… Do you use any additional applets? > Killing off plasmashell and starting a new one solves the issue. > > Is this a common issue? Is it already known what causes the issue? > What can I do to find out what happens? I didn´t see this kind of behaviour since a long time. > Do the current unstable KDE packages have debugging symbol > counterparts? I am a bit outdated on the availability of debugging > symbols for Debian packages, there was a change in their generation > last year, I think I remember, right? I think these are now in dbgsym packages and you need an extra line in sources.list to get these. I do not fully remember what this line looks like but it had something along with "debug" in it. > I am not using many fancy plasma things, I have a single panel with a > quick launch applet, a desktop pager, a task bar, a tray and a clock. > And two additional clocks on the desktop. Hm, maybe one of those clocks? Did you also test with a standard configuration? > What might be going wrong here? Wonderful question. I don´t have any good answers on how to efficiently find it out, except trying with a standard configuration and then applying change after change until finding out what causes the issue. > P.S.: This is what a freshly started plasmashell writes on its > terminal, is there anything I should be worried about? > > kscreen: starting external backend launcher for "" > org.kde.plasma: unversioned plugin detected, may result in instability [… more of these …] > No metadata file in the package, expected it at: > "/home/e13itfe/.config/pic//metadata.desktop" No metadata file in the > package, expected it at: "/home/e13itfe/.config/pic//metadata.desktop" No > metadata file in the package, expected it at: > "/home/e13itfe/.config/pic//metadata.desktop" QFont::setPointSizeF: Point > size <= 0 (0.00), must be greater than 0 No metadata file in the > package, expected it at: "/home/e13itfe/.config/pic//metadata.desktop" No > metadata file in the package, expected it at: > "/home/e13itfe/.config/pic//metadata.desktop" No metadata file in the > package, expected it at: "/home/e13itfe/.config/pic//metadata.desktop" > file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents > /ui/CompactBarMonitor.qml:45:20: Unable to assign [undefined] to QColor > : [… tons more of debug output …] plasmashell outputs a ton of debug output. And frankly I have no idea on whether anything of this mentions the cause of your issue. Excessive plasmashell debug output is known by upstream and I think there have been some attempts to mitigate it. I think it would be good if it only outputs when it really has a problem that affects the user by default and only outputting developer debug information on request. You could try to disable debug output via kdebugdialog and then restart plasmashell on console again, to see whether it outputs anything it considers to be an error. Not sure how helpful it is tough. Another thing would be: Does it loop any message when it utilizes CPU heavily? Thanks, -- Martin
High CPU load caused by plasmashell
I have two desktop machines and two laptops running current unstable with KDE. Both desktops do have the issue that plasmashell suddenly begins taking a full CPU core while staying fully responsive. This especially happens after suspend or when the system was idle for some time, for example when I go to lunch and return an hour later. X itself takes about 50 % CPU if this happens. Killing off plasmashell and starting a new one solves the issue. Is this a common issue? Is it already known what causes the issue? What can I do to find out what happens? Do the current unstable KDE packages have debugging symbol counterparts? I am a bit outdated on the availability of debugging symbols for Debian packages, there was a change in their generation last year, I think I remember, right? I am not using many fancy plasma things, I have a single panel with a quick launch applet, a desktop pager, a task bar, a tray and a clock. And two additional clocks on the desktop. What might be going wrong here? Greetings Marc P.S.: This is what a freshly started plasmashell writes on its terminal, is there anything I should be worried about? kscreen: starting external backend launcher for "" org.kde.plasma: unversioned plugin detected, may result in instability org.kde.plasma: unversioned plugin detected, may result in instability org.kde.plasma: unversioned plugin detected, may result in instability org.kde.plasma: unversioned plugin detected, may result in instability org.kde.plasma: unversioned plugin detected, may result in instability org.kde.plasma: unversioned plugin detected, may result in instability org.kde.plasma: unversioned plugin detected, may result in instability org.kde.plasma: unversioned plugin detected, may result in instability org.kde.plasma: unversioned plugin detected, may result in instability org.kde.plasma: unversioned plugin detected, may result in instability org.kde.plasma: unversioned plugin detected, may result in instability org.kde.plasma: unversioned plugin detected, may result in instability org.kde.plasma: unversioned plugin detected, may result in instability org.kde.plasma: unversioned plugin detected, may result in instability org.kde.plasma: unversioned plugin detected, may result in instability No metadata file in the package, expected it at: "/home/e13itfe/.config/pic//metadata.desktop" No metadata file in the package, expected it at: "/home/e13itfe/.config/pic//metadata.desktop" No metadata file in the package, expected it at: "/home/e13itfe/.config/pic//metadata.desktop" QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0 No metadata file in the package, expected it at: "/home/e13itfe/.config/pic//metadata.desktop" No metadata file in the package, expected it at: "/home/e13itfe/.config/pic//metadata.desktop" No metadata file in the package, expected it at: "/home/e13itfe/.config/pic//metadata.desktop" file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/CompactBarMonitor.qml:45:20: Unable to assign [undefined] to QColor : Could not resolve property : radialGradient4857 Could not resolve property : radialGradient4857 Could not resolve property : radialGradient4857 Could not resolve property : radialGradient4857 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:106:17: Unable to assign [undefined] to QObject* file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:85: TypeError: Cannot read property 'effectivePressed' of undefined file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:106:17: Unable to assign [undefined] to QObject* file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:85: TypeError: Cannot read property 'effectivePressed' of undefined file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:106:17: Unable to assign [undefined] to QObject* file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:85: TypeError: Cannot read property 'effectivePressed' of undefined file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:220: TypeError: Cannot read property '0' of undefined file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:209: TypeError: Cannot read property '0' of undefined file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:106:17: Unable to assign [undefined] to QObject* file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null
