I have a quicklaunch widget on my desktop with about 10 launch icons in it. I can change the size and shape of the quicklaunch to fit nicely around the icons, but whenever I restart my desktop the widget resizes itself to be quite large (about 4x the height). A picture paints a thousand words so I've linked a screenshot. Reproducible: Always Steps to Reproduce: 1. Add a quicklauncher widget. 2. Add some icons and resize the widget 3. Restart KDE Actual Results: Qucklauncher automagically resizes itself Expected Results: To be the same size as you set it to be.
I cannot reproduce here with 6 icons in my QuickLaunch. Can you add your KDE version and add your screenshot please?
Hi there, KDE version is 4.8.3 Screenshot: http://www.gedda.info/wp-content/uploads/quicklaunch_resize.jpg
Hi Rodney, please attach the screenshot to the bug report using "Add an attachement", thanks!
Created attachment 71505 [details] Quicklaunch resizing itself after plasma restart Pic of quicklaunch automagically resizing itself.
HI, i just tested against master. I added 7 icons. But i cannot reproduce this. I you have a chance to use master or KDE/4.9 branch, please try.
I confirm, on Sabayon 10 with KDE > 4.9.2. Sometimes it shows big icons (I guess it is the default size), so partly goes out of the desktop.
I was testing. I have 39 icons. If I try to arrange them on 2 rows, the applet becomes as described above - it shows big icons (I guess it is the default size), so partly goes out of the desktop. If I arrange it on 3 rows of 13 icons, it resizes itself on 2 rows, having 29 icons on the first row and 10 icons on the second row, the icons keeping their original sizes (small). It seems to stabilize at this configuration.
This still happens in KDE 4.10 (Mageia 3) I am using Folder View and running these additional widgets PyCashew LCD Weather Station CPU Monitor Memory Status Network Monitor and of course Quicklaunch. I have 15 launchers in the Quicklaunch widget.
I don't know if it will help or not but this is the relevant snippet from /home/richard/.kde4/config/plasma-desktop-appletsrc before logging out: [Containments][13][Applets][20] geometry=1091,-11,845,119 immutability=1 plugin=quicklaunch zvalue=118 and this is after logging in again: [Containments][13][Applets][20] geometry=1091,-11,845,352 immutability=2 plugin=quicklaunch zvalue=118 Note the geometry and immutability has changed.
I'm actually facing the same problem here, with a SuSE 13.1 w. KDE 4.11 installed. I've tested, if this is dependent on a specific icon, but for me it is not. After all, it seems to be dependent on icon count in general. Deleting one icon per login and then logout again, brought to me, that the effect is notably decreasing for icon count < 4. With three icons it barely expands, finally with two icons not at all. I guess, there is a function reserving space for additional rows depending on icon count. Since multiple rows aren't implemented yet, I think this is, where the bug has its root.
Just played along with toggling Icon/Starter names. When I activate titles and then deactivate them again, the quicklauncher stays exactly at the (wrong) size it has after login. Maybe simply the class/widget is constructed with "showtitles" set to true for default and then receives the "showtitles=false" value by loading further user-config, but has overwritten size info already at this point.
I experience the same issue. Exactly as described above by Rodney Gedda. Linux mu 3.14.14-gentoo #1 SMP Sat Aug 2 15:59:53 CEST 2014 x86_64 Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz GenuineIntel GNU/Linux KDE-14.12.5
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 has already been 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