Bug 195193

Summary:	Icons in panel are randomly rearranged
Product:	[Unmaintained] plasma4	Reporter:	Antonio Rojas <arojas>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	asraniel, fintan, v.kiril, vespas, vpiotr
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Antonio Rojas 2009-06-04 11:49:32 UTC

Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Using KDE 4.2.88

The icons in the panel are randomly rearranged on every logon. Even if they haven been used, just logging out and logging in again makes then appear in a different order.

In case it matters, my icons are in a vertical autohide panel. The only plasmoid in the panel besides the icons is a dictionary. It only seems to affect the lowest 7 icons in the toolbar.

Comment 1 Antonio Rojas 2009-06-04 11:57:45 UTC

Actually it is not so random: If the lowest 7 icons are ordered (from bottom to top): 1,2,3,4,5,6,7, on the next logon they will be rearranged like this: 5,1,6,2,3,7,4. Pretty weird.

Comment 2 Paschalis Veskos 2009-07-01 19:17:55 UTC

Still there in 4.3RC1, also in a vertical autohide panel.

Comment 3 Fintan 2009-07-27 08:06:45 UTC

I can confirm this behavior on kde4.3 RC3

Comment 4 vpiotr 2009-08-23 09:56:49 UTC

Confirmed on: Qt: 4.5.2, KDE: 4.3.00 (KDE 4.3.0), Plasma Workspace: 0.3
Had the same issue with KDE 2.4.x.

It seems that there is a workaround (at least it works for me): you need to leave enough additional unused space for widgets on the panel (experiment with how much "enough" is). _Not_ using spacers helps to achieve that. :-)

Comment 5 vpiotr 2009-08-23 09:57:15 UTC

(In reply to comment #4)
> Had the same issue with KDE 2.4.x.
I mean 4.2.x, sorry.

Comment 6 Kiril Vladimiroff 2009-11-23 06:26:33 UTC

This bug is still available in 4.3.3 and still nobody takes care of it?

Comment 7 Beat Wolf 2009-12-07 14:16:02 UTC


*** This bug has been marked as a duplicate of bug 212041 ***