Created attachment 68573 [details] Screenshot of panel after bug appeared. Version: unspecified (using KDE 4.8.0) OS: Linux Removing the system tray and re-adding it to the panel makes it take up a lot more space. Reproducible: Always Steps to Reproduce: 1. Delete system tray from panel 2. Add system tray to panel Actual Results: System tray taking over twice the size it needs. Expected Results: System tray taking up its normal size. Screenshot in attachment. System is Kubuntu 11.10 with the KDE 4.8 PPA.
Created attachment 68574 [details] Bug's manifestation in two rows system tray
Created attachment 68575 [details] Bug in two rows
I can confirm this bug on Kubuntu 11.10 with the KDE 4.8 PPA. It seems to be also triggered when (for some reasons) plasma recovers from a crash, the system tray widgets gets twice the size from the way it was before the crash
A quick search (I could have missed others) it seems this problem has been reported (and marked as RESOLVED) several times in the last years, and in different versions: https://bugs.kde.org/show_bug.cgi?id=300005 4.8.3 https://bugs.kde.org/show_bug.cgi?id=290982 4.8rc2 https://bugs.kde.org/show_bug.cgi?id=293472 4.8.0 https://bugs.kde.org/show_bug.cgi?id=240347 4.4.8
*** Bug 300005 has been marked as a duplicate of this bug. ***
Confirmed in current 4.9 beta2, it still happens after a plasma crash.
*** Bug 240347 has been marked as a duplicate of this bug. ***
*** Bug 290982 has been marked as a duplicate of this bug. ***
*** Bug 302231 has been marked as a duplicate of this bug. ***
I have this issue with KDE 4.7.2. Nasty workaround to remove these ghost entries from the system tray: Restarting the kded4 daemon -> killall kded4 && sleep 2 && kded4 &0
Still happening on 4.9.1. Here's a snapshot: http://imageshack.us/a/img692/9751/kdetraybug.jpg
Created attachment 74238 [details] Snapshot
I have the same problem since upgrading to KDE 4.8. Also occurs in KDE 4.9.
Dupe of this? https://bugs.kde.org/show_bug.cgi?id=289537
I can confirm this (KUbuntu 12.10, KDE 4.9.2). The systemtray gets flooded with statusnotifieritems. Workaround: System Tray Settings -> Entries and set them to "hidden".
Hi, also have the bug, because each 3-5 days I must restart plasma-desktop that consumes too much misc pixmaps. The workaround is fine, but very annoying when you have dozens of icons nto deactivate ... Is there a "shell" way to put icons from auto to hidden ? And last, is there a way to define the default show policy for systray icons ? (using a regexp, or not) maybe a global policy ? Thanks in advance. PS: bug since Kubuntu 12.04
> The workaround is fine, but very annoying when you have dozens of icons nto > deactivate ... > > Is there a "shell" way to put icons from auto to hidden ? > > And last, is there a way to define the default show policy for systray icons > ? (using a regexp, or not) maybe a global policy ? Don't do it manually. When the KDE4 daemon is restarted, the ghost entries disappear. The best workaround to create a script with the following content: killall kded4 && sleep 2 && kded4 &0 And add a global shortcut (e.g Windows key+F3) in KDE to launch this script.
is that a trailing 0? Shouldn't it be: killall kded4 && sleep 2 && kded4 &
(In reply to comment #18) > is that a trailing 0? Shouldn't it be: > killall kded4 && sleep 2 && kded4 & No, it is meant to end with &0
I don't think it is meant to end in just plain &0 because bash parses that as a command. Has the command been bitten by a missing angle bracket perhaps ? [/testing: leveret@george ~]$ killall kded4 && sleep 2 && kded4 &0 [2] 30401 bash: 0: command not found [/testing: leveret@george ~]$ Experiment and logic suggest that "greaterthan ampersand zero" may be what was originally typed before BZ mangling. Thankyou for this workaround.
My Bash isn't strong enough to really understand what >&0 (greaterthan ampersand zero) means here. Doesn't this mean to redirect standard output to the same place handle 0 (i.e. stdin) goes? But in this case stdin is just the terminal? So it this case it would do nothing?
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham