Comment 16 for bug 144641
Revision history for this message
| Motin (motin) wrote Re: displayconfig-gtk should generate an randr 1.2 configuration where possible | #16 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
@unggnu: Despite fewer mandatory configuration items in xorg.conf there are some things that are suited to remain in it. For instance, desired RandR defaults can be specified therein, making it unnecessary to run xrandr-based scripts upon login to get that extended desktop configured etc.
But whether or not displayconfig-gtk is needed or can be replaced by some other application - I'd say probably. But, of the three major apps in this area: grandr, urandr and displayconfig-gtk, it seems that displayconfig-gtk is the most active for the moment and most likely to remain the default screen configuration application - granted that it will solve this bug... Also I think displayconfig-gtk is the only one that actually modifies xorg.conf, but I am not sure on that point.
@Bryce Harrington: I am curious to know if you are adding the possibility to write the RandR-configuration into xorg.conf as well or making a wrapper around xrandr? I too would love to try a test version btw...
Cheers,
Fredrik