Bug 354690 - cannot enable my secondary monitor with full resolution in systemsettings
Summary: cannot enable my secondary monitor with full resolution in systemsettings
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: common (other bugs)
Version First Reported In: 5.4.2
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Vrátil
URL: http://imgur.com/eck3vud
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-01 14:11 UTC by Robert Derochette
Modified: 2022-11-08 21:56 UTC (History)
1 user (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 Robert Derochette 2015-11-01 14:11:15 UTC
When I start Plasma when my secondary screen is turned off, I can't enable it with a resolution which is greater than 1024x768@60Hz.

Reproducible: Always

Steps to Reproduce:
If my secondary monitor is not switched on when I start Plasma, and I run xrandr in a konsole, xrandr detects its maximum resolution to 1024x768@60Hz.
Then if I switch on my secondary screen, xrandr detects all its capabilities, which is up to 2048x1536@60Hz.
However in systemsettings this secondary monitor does not have its correct information (see screenshot in the URL).



Expected Results:  
I think Plasma reads monitor information upon startup once for all, and in my case this changes whether the screen is turned on or not. So shouldn't systemsettings asks xrandr about monitor information every time you go into display settings section ?

I didn't have this problem in KDE 4.14   (but many versions 4.x before too)
Comment 1 Robert Derochette 2015-11-01 16:13:00 UTC
Sorry if I wasn't clear, I meant that I did not have this problem with KDE 4.x (not only with 4.14)
Comment 2 Justin Zobel 2021-03-10 00:32:26 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 3 Nate Graham 2022-11-08 21:56:16 UTC
No response, closing.