My panel is laid out from left to right as follows: K Menu, a few launchers, task manager, pager, system tray, clock. When a new icon appears in the system tray, the following happens very quickly: 1) The system tray area briefly expands to the right, becoming superimposed slightly on top of the clock. 2) The panel widgets to the left of the system tray resize to make room for the expanded system tray area. 3) The system tray moves to the left, taking the new elbow room given to it by the resizing widgets. However, after the tray icons all move to the left, the rightmost part of the system tray (usually the popup arrow) is still visible superimposed on top of the clock (see attached screenshot). This graphical glitch does go away when the clock display is updated (usually once every minute when the time changes). Clicking on the clock also chases off the superimposed arrow. Reproducible: Always Steps to Reproduce: 1. Log into KDE. 2. Start an application that causes a new tray icon to appear. For me this would be Thunderbird (brings up message indicator) or anything that causes notifications, such as copying a file. Actual Results: Arrow-impaled clock. Expected Results: Healthy, non-impaled clock. This behavior has been happening for a while, for sure since the KDE 4.10 series and continues to happen with KDE 4.11.1. I've just been too lazy to report it until now ;)
Created attachment 82374 [details] screenshot showing the bug
Duplicate of 317066
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