Bug 374622 - Display Setting Buggy and Unusable With High Scale + Low Resolution
Summary: Display Setting Buggy and Unusable With High Scale + Low Resolution
Status: RESOLVED DUPLICATE of bug 354227
Alias: None
Product: KScreen
Classification: Plasma
Component: kcm (show other bugs)
Version: git
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Kügler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-06 08:40 UTC by lukebenes
Modified: 2017-01-10 00:08 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lukebenes 2017-01-06 08:40:27 UTC
The last UI element you want to malfunction when you’re playing with Display Settings is the Display Settings itself. 

Steps to reproduce:
1.On 1920x1080 or 1280x1024 display, Display -> Scaling -> 2x
2.Reboot
3.Try to change scaling back

I have a 1920x1080 13” laptop. I was not happy with some widgets at 1.5 so I made the mistake of trying 2x scaling factor. After a reboot there was no way to access the scaling setting or the any of the bottom buttons for the Display dialog. Meanwhile I had the huge waste of a laptop screen that was useless. Even if you hide the laptop screen, you still can’t access the buttons below. If you try maximizing / resizing, you get all kinds of rending artifacts. 

Of all the settings dialogs, this one should be the most resilient. Instead it seems to be one of the most fragile. Tested with KDE Neon (1280x1024) and KDE Arch (1920x1080)

After much time wasted deleting .local/share/kscreen and other KDE system files, I finally got out of this mess by using xrandr and faking a 2K display.

My suggested solution to this bug, is to allow the display settings to be any size, but if the buttons are off the screen put in a scroll bar. Also the display should shrink/be hidden before the buttons disappear.
Comment 1 Christoph Feck 2017-01-10 00:08:27 UTC

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