Bug 393661 - Panels loose configuration and reset when resolution changes
Summary: Panels loose configuration and reset when resolution changes
Status: RESOLVED DUPLICATE of bug 392642
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (other bugs)
Version First Reported In: master
Platform: Kubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-30 00:28 UTC by myusualnickname@gmail.com
Modified: 2018-09-25 07:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description myusualnickname@gmail.com 2018-04-30 00:28:37 UTC
There needs to be a way to specify the width or height of a panel regardless of current screen configuration..

Panels loose configuration and are generally unusable if there is a resolution change.

https://imgur.com/HSXzt7f
Comment 1 David Edmundson 2018-04-30 09:30:07 UTC
Yes, this is deliberate.
Comment 2 Aaron Peterson 2018-09-12 21:41:09 UTC
David Edmundson,  This makes the panels not work... It makes users not be able to use the product..

I've sat with users... I've had service calls because of this issue...
I am willing to pay to have this be fixed..
It is the difference between using windows10 and KDE...  I cannot use software that breaks so catastrophically when a client switches monitors.

It really is horrible..
it's terrible...
the buttons all get small and warped to another location... 

Are you, David, saying that this was designed intentionally to be broken?

If you want to have things break at high stress times, please just light your computer on fire.

This was _the reason_ why KDE cannot be deployed to hundreds of people..

There may be a few other reasons too, but I've managed to fix a few things like disabling the netbook interface that doesn't work for anything...
Comment 3 Alexander Mentyu 2018-09-25 07:48:29 UTC

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