Bug 360491

Summary:	Panel resets size, width, height when display resolution changes
Product:	[Plasma] plasmashell	Reporter:	Jon <jon>
Component:	Panel	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	alpeterson, chocolatesocket, kde, notmart, stronger1234
Priority:	NOR
Version First Reported In:	5.5.5
Target Milestone:	1.0
Platform:	Kubuntu
OS:	Linux
URL:	https://www.dropbox.com/s/8cnh6ujeo3t6rl6/KDE%20Panel.mp4?dl=0
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Jon 2016-03-13 22:04:24 UTC

The Panel's dimensions (width, height) will be reset back to minimum or a default whenever the display resolution is changed.

Reproducible: Always

Steps to Reproduce:
1. Install Kubuntu 15.10 or Arch with Plasma 5 in a VMware Fusion 8.1.0 virtual machine
2. Install open-vm-tools and open-vm-tools-desktop using the respective package managers
* Reboot as needed
3. When logged in, confirm that the system resolution automatically changes when the Fusion window is resized.
4. Customize the panel in some way, such as changing it's width and height. 
5. Change the VM window size [thus triggering a resolution change inside the guest VM]. Or, you can also change the resolution directly within Plasma through settings with the same affect.

I reproduced this issue with Kubuntu 15.10 running Plasma 5.4.2 and Arch Linux running 5.5.5. The test platform are virtual machines running on VMware Fusion 8.1.0 on an OS X host. 

Actual Results:  
The Panel is reset to a minimum or default size. Any customizations such as height, width, positioning relative to the screen edge will be lost.

Expected Results:  
I expect the Panel to scale proportionally with the screen size. 

Screen capture of the issue occurring can be snagged from Dropbox here: https://www.dropbox.com/s/8cnh6ujeo3t6rl6/KDE%20Panel.mp4?dl=0

Comment 1 Marco Martin 2016-03-14 13:44:20 UTC

the panel sizes are saved per screen resolution, relative sizing is not supported nor can work.

Comment 2 David Edmundson 2016-07-07 13:57:12 UTC

@Marco, then close the bug.

Comment 3 Jon 2016-07-07 16:46:59 UTC

Is this a flat out "never going to happen" and won't be considered as a feature request or wishlist?

Comment 4 Aaron Peterson 2017-11-15 10:42:29 UTC

I am amazed that maintaining basic functionality of the system is marked "won't fix"

This results in an unusable system.

To do a work arround for a client I had to basically copy and paste 1920 configurations into a config file to keep the settings roughly the same...  and now with 4k displays that number doubles!

Just make it so it's saved universally, and that people CAN enable per resolution settings if they really want to edit the configuration file themselves... but the default absolutely needs to be a pixel width.. and if you want to be really cleaver.. you might be able to do a screen percentage..

but I'll fund a patch for this.. or do it myself.. I just need to make sure it gets incorporated. But with a big glaring WONTFIX on a critical error that makes the system... WORSE than windows 10?!?!    (that's hard to do)  wow.. theatrics and pointing and screaming are in order here.

Comment 5 czz 2021-03-30 10:10:06 UTC

May I vote for this bug?

It would be more reasonable if it changes to recording the panel's thickness per vertical height instead of per horizontal width, if it's too difficult to implement a relative sizing.

However, recording the panel's thickness per DPI instead of per screen resolution width/height should be the best choice, of course.

Comment 6 David Edmundson 2021-03-30 11:45:34 UTC

>It would be more reasonable if it changes to recording the panel's thickness

Panel thickness is already independent of screen sizes.

Comment 7 czz 2021-03-30 14:23:09 UTC

(In reply to David Edmundson from comment #6)
> Panel thickness is already independent of screen sizes.

I installed Debian 10.8 with KDE Plasma version 5.14.5 in VMware, and the problem still there, resizing the screen will cause the panel thickness reset to the default value. Would you tell me which version of KDE that fixed this problem?