If you have a systemtray as only plasmoid in a panel, you only can resize the panel to size much bigger than the visible part of the systemtray. See attached screenshot. And even after removing the systemtray, you cannot make the panel smaller than that size with the minimum size slider, so the panel seems to remember this size. Reproducible: Always Steps to Reproduce: 1. Add a new empty panel (right-click on desktop, choose "Add Panel"->"Empty Panel" 2. Add a systemtray plasmoid to that panel 3. resize the panel using the minimum size slider Actual Results: The minimum panel size is much bigger than the visible part of the systemtray. Expected Results: Panel size can be made as small as the visible part of the systemtray. It seems to me that the systemtray widget just takes the current panel size as its minimum size. Or is this a bug in the panel? This is reproducible with 4.10.5 and 4.10.90.
Created attachment 80972 [details] Screenshot showing the bug Notice that the systemtray is much smaller than the panel, but the panel size is somewhere between the minimum and maximum set with the sliders.
Sorry, I found out now, that this is not specific to the systemtray. So it's a bug in the panel itself. Reassigned and changed the summary therefore. To recap: 1. Add an empty panel, notice that you can resize it to any size by moving the minimum size slider. 2. Add a plasmoid. Anyone will do, f.e. "Show Desktop". After this, you can't make the panel smaller anymore with the minimum size slider. 3. Remove that plasmoid again (and all others you might have added), so that the panel is empty again. The panel still can't be made smaller with the minimum size slider. So apparently the (empty) panel has no minimum size set. But adding a plasmoid seems to set the current panel's size as minimum.
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