Bug 363855

Summary:	Widgets positioning on desktop containment gets rearranged when loging in or changing activities
Product:	[Plasma] plasmashell	Reporter:	Alexandre Pereira <pereira.alex>
Component:	Desktop Containment	Assignee:	Sebastian Kügler <sebas>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	nate, notuxius
Priority:	NOR
Version:	5.6.4
Target Milestone:	1.0
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:

Description Alexandre Pereira 2016-06-02 19:20:01 UTC

Hi,

I place some widgets/plasmoids on the desktop containment ( not folderview ) at specified places/corners.

When login in or changing activities, widgets get moved around, up or down.
I suspect its because of the panel, I have the panel on top and "visible but windows on top". The widgets/plasmoids move up or down, based on the panel height. ( if a bigger panel, they move more ).

Also, triggering the panel cashew/configuration makes them move up and down, and most of the time, they don't return to their original positioning.

Reproducible: Sometimes

Steps to Reproduce:
1. Put widget on desktop in a specific place
2. Switch activities or trigger panel cashew/configuration ( with panel on autohide or visible but windows on top )
3. Watch the widgets/plasmoids move up and down and not returning to original position

Comment 1 Alexandre Pereira 2016-06-02 19:39:44 UTC

link to youtube movie with panel making widgets get out of place:

https://youtu.be/Pchad_NEADw

Comment 2 Alexandre Pereira 2016-07-20 11:12:38 UTC

Added another video : https://youtu.be/vr_My6Gg1FE

Now with Plasma 5.7.2

Comment 3 Alexander Mentyu 2017-12-08 15:59:29 UTC

Can't reproduce in:

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.4
Frameworks: 5.41.0
Qt: 5.9.3
Kernel 4.10.0-40-generic
Type: 64-bit

Comment 4 Nate Graham 2020-01-22 18:35:03 UTC


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

Comment 5 Alexandre Pereira 2020-02-21 11:03:22 UTC

Sorry for not checking up on this.
I have been using latte-dock most of the time.

So with 5.18.1 I tried to reproduce this bug like in the video but couldn't.
Seems its fixed.