Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 484510 - KDE panel freeze
Summary: KDE panel freeze
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: Normal major (vote)
Assignee: Gentoo KDE team
URL: https://bugs.kde.org/show_bug.cgi?id=...
Whiteboard: fixed in 4.11.2
Keywords:
Depends on:
Blocks: kde-4.11.2-stable
  Show dependency tree
 
Reported: 2013-09-10 18:49 UTC by Marco Di Fresco
Modified: 2013-10-15 20:57 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Di Fresco 2013-09-10 18:49:11 UTC
I have an issue with the KDE panel that frequently freeze. Any part of it (the task manager, the clock, the system tray, etc.) cannot be interacted with; the rest of the system works fine as I can alt-tab between open apps, I can access the Run window with ALT+F2, etc.

It started few* weeks ago with KDE 4.10.5 and the following upgrade to KDE 4.11.1.

At first I thought of a corrupted config file, but last Saturday I did a totally clean Gentoo install installing directly KDE 4.11.1 using the following keywords:
http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob_plain;f=Documentation/package.accept_keywords/kde-4.11.keywords
and the problem persist

The freeze happens independently of the open programs (for instance, during the night I don't have any program open beside those on the system tray and daemons on background).

Beside that, the freeze is not even constant in term of time: some time it happens after hours and other times after minutes from the previous occurrence.

When it freeze it does not generate any explicit error (except for the one I'll report in a moment) or the usual bug report window.

The only workaround so far is to open Konsole (fortunately I keybinded it) and run: killall plasma-desktop && plasma-desktop
that close and recreate the panel that become functional until the next freeze.

On the Konsole it generate the following output: http://pastebin.com/Btk3ZkTC

and then it repeat that "NETWM: Warning readIcon() needs buffer adjustment!" until it freeze and than it gives:
*** glibc detected *** plasma-desktop: corrupted double-linked list: 0x00000000021fd850 ***

Any idea on how can I fix it?

If you need any other info or logs, just ask.

Thanks.


*at first I thought that the freeze was just a bad coincidence and than a bad mix of personal time constraint and general laziness made me endure it for days by keep using "killall plasma-desktop && plasma-desktop"; eventually now I cannot recall the exact day it started so I cannot correlate it with any specific upgrade of other software as possible cause of the problem.
Comment 1 Michael Palimaka (kensington) gentoo-dev 2013-09-11 16:16:03 UTC
I'm not sure what to suggest sorry. You could try reporting upstream.
Comment 2 Marco Di Fresco 2013-09-11 17:19:36 UTC
I tried to open it upstream.

For reference: https://bugs.kde.org/show_bug.cgi?id=324801

I'll let you know if I get any news from there.
Comment 3 Johannes Huber (RETIRED) gentoo-dev 2013-10-15 18:11:08 UTC
Two comments in upstream bug report saying this problem is gone with 4.11.2.
Comment 4 Marco Di Fresco 2013-10-15 20:48:01 UTC
Sorry if I didn't follow up on this bug; when I originally reported on upstream that the problem seemed to have been fixed (collaterally), I thought to leave a couple of days for further confirmation that the bug disappeared and in case the devs had any further questions on the case.

After so many days I can confirm that after these updated on October 7th:
kde-base/plasma-workspace-4.11.2-r1
kde-base/kdebase-runtime-meta-4.11.2-r1
kde-base/kdeplasma-addons-4.11.2-r1
the problem disappeared.

Thank you. :)
Comment 5 Marco Di Fresco 2013-10-15 20:57:11 UTC
Ops, I didn't finish correctly the first paragraph, I was saying "... I thought to leave a couple of days ... but then I got busy with issues in RL and I couldn't come back to close the bugs. :D