Bug 356818 - Provide support for configuring custom modeline for each monitor
Summary: Provide support for configuring custom modeline for each monitor
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kscreen (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-17 07:44 UTC by Mikhail Khvoinitsky
Modified: 2022-11-08 23:14 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail Khvoinitsky 2015-12-17 07:44:49 UTC
My problem:
I use a laptop with two monitors:
* 2560x1440@60Hz at home
* 1920x1200@60Hz at work
(so, only one monitor at the time)
Unfortunately, laptop's video adapter do not support 2560x1440@60Hz monitors so the maximum resolution I can set up for the home monitor is 2048x1152@60Hz. However, I can generate a custom modeline with reduced refresh rate but with full resolution. To make it permanent I can write Xorg's config file like this:

Section "Monitor"
    Identifier             "HDMI1"
    ModeLine               "2560x1440_50.00_rb" 200.25 2560 2608 2640 2720 1440 1443 1448 1474 +HSync -Vsync
    Option "PreferredMode" "2560x1440_50.00_rb"
EndSection

The problem is that Xorg have no way to apply this options only for certain monitor (neither by serial nor by something else) (that means that I will have good configuration at home but completely broken at work). The only way available to filter monitors is by port (option 'Identifier             "HDMI1"') but it do not suits my needs.
Even worse, after applying such kind of a config, kscreen sometimes stops distinguish monitors.

So, it will be very useful to have some way to do fix that. One of the options could be launching a user script after connecting a monitor before kscreen apply his configuration.

Reproducible: Always
Comment 1 postix 2022-07-14 18:47:56 UTC
*** Bug 456697 has been marked as a duplicate of this bug. ***