Bug 364871 - resolution drop down list width is too narrow
Summary: resolution drop down list width is too narrow
Status: RESOLVED DUPLICATE of bug 403153
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kscreen (show other bugs)
Version: 5.14.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
: 361204 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-06-28 20:15 UTC by Pascal d'Hermilly
Modified: 2020-06-15 14:06 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot (19.53 KB, image/png)
2016-06-28 20:16 UTC, Pascal d'Hermilly
Details
screenshot, other widget style works (29.88 KB, image/png)
2016-06-29 13:19 UTC, Pascal d'Hermilly
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal d'Hermilly 2016-06-28 20:15:21 UTC
When I click the screen resolution drop down to select another resolution I confronted with resolutions such as 192...080 instead of 1920x1080.
I'l attach screenshot.

Reproducible: Always
Comment 1 Pascal d'Hermilly 2016-06-28 20:16:08 UTC
Created attachment 99753 [details]
screenshot
Comment 2 Christoph Feck 2016-06-29 12:56:49 UTC
Is this issue also visible, if you are using a different widget style?
Try running "kcmshell5 -style Fusion kscreen" in Konsole.
Comment 3 Pascal d'Hermilly 2016-06-29 13:18:37 UTC
It's not an issue when I run your command as the drop down list then seems to be dependent of the width of the dialog. I'll add a screen shot.
Just now I realize that the resolution widget is different for my laptop screen and for my external screen. On the laptop it's a drop down, on the external screen it's a slider. My guess is that it's because the laptop has more options.
Comment 4 Pascal d'Hermilly 2016-06-29 13:19:33 UTC
Created attachment 99762 [details]
screenshot, other widget style works
Comment 5 Martin Flöser 2016-07-20 14:06:37 UTC
*** Bug 361204 has been marked as a duplicate of this bug. ***
Comment 6 Nate Graham 2020-06-15 14:06:51 UTC

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