Bug 432001

Summary:	Widgets resize to random size at reboot
Product:	[Plasma] plasmashell	Reporter:	mnrbn <rubenxinternet>
Component:	Containment	Assignee:	Marco Martin <notmart>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kdelibs-bugs, nate, plasma-bugs
Priority:	NOR
Version:	5.20.0
Target Milestone:	1.0
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description mnrbn 2021-01-23 17:57:18 UTC

If I set a widget in the desktop with a size smaller than X (every widget seems to have a different X), at reboot the widget appears with the size X again, so I can´t have widgets smaller than some random X size in the desktop.
If the size of the widget is bigger than X the position and size are remembered on reboot.



STEPS TO REPRODUCE
1. Place any widget and resize it to minimum size
2. Reboot


OBSERVED RESULT
The widget changes size to some random size

EXPECTED RESULT
The widget should keep the size whatever is it

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Manjaro
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78
Qt Version: 5.15.2

ADDITIONAL INFORMATION

Comment 1 Nate Graham 2021-01-26 03:31:50 UTC


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

Comment 2 mnrbn 2021-01-31 21:05:50 UTC

(In reply to Nate Graham from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 360478 ***

It´s not the same bug, I didn´t mention any game or fullscreen, my problem is different from this one.

Comment 3 Nate Graham 2021-02-01 15:08:44 UTC

Hmm, could be Bug 419590 then...

Comment 4 mnrbn 2021-02-01 22:53:59 UTC

(In reply to Nate Graham from comment #3)
> Hmm, could be Bug 419590 then...

I don´t think so. My problem can be reproduced by just setting the size of a widget to minimum (or smaller than some random different value that every widget has) and reboot (or kill and restart plasmashell).
And I have to say that I can reproduce the Bug you mentioned, so it´s also there for sure, but my bug is another one.

Comment 5 Nate Graham 2021-08-08 17:22:37 UTC


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