GNOME Bugzilla – Bug 631388
Add gconf key to disable automatic xrandr settings without conf files
Last modified: 2010-11-05 16:03:10 UTC
In https://launchpad.net/bugs/640807 we got a lot of reports that starting with 2.31.91 (which introduced automatic xrandr settings when there are no configuration files) a lot of people get misconfigured monitors. Examples: * Monitor is at 60 Hz, while X.org correctly configures it at 75. * External monitor is changed from native 1280x1024 (as set up by X.org) to 1024x768 (and variations) Even for situations where the current behaviour does not actually change the X.org settings it is undesirable in the general case to change the xrandr settings. In a KMS world, we want exactly one mode change when the kernel starts up, and then never again. Any further mode changes do not only introduce flicker, but also introduce significant boot time delays in the order of 1 or 2 seconds. Frederico introduced this for various reasons, and some OEMs want this, but I think it should be configurable, and thus become a distro choice. This was recently discussed on IRC: "<federico1> I'll happily include a patch that makes the boot-time configuration conditional <federico1> with some use_boot_time_configuration key or something reasonably-named <federico1> use_boot_time_configuration or use_xorg_configuration (the reverse)? <federico1> I'd like it to be obvious from the key name that it's an either/or thing <federico1> tormod: I'm leaning toward a do-not-touch kind of name now, with False by default - if you need to make it True, it means that you have a special case due to your X setup anyway" I would like to work on a patch which introduces such a gconf key. By Frederico's comments it sounds like he prefers "use_boot_time_configuration"?
Seb just said that Federico meant it the other way round -- have a gconf key that, when _enabled_, disables apply_default_boot_configuration(). Thus this would be "use_xorg_monitor_settings" or perhaps "dont_configure_monitors", but I really would like to avoid the latter; we should not have gconf keys with a negation in the name, then we should rather call it "configure_monitors". With Federico's IRC statement I'll go with "use_xorg_monitor_settings" for now. (Gosh, naming -- always the hardest part)
Created attachment 171747 [details] [review] RANDR - Add gconf key for disabling boot time configuration This patch implements the proposal. It does not change the default behaviour, but when setting the gconf key to true, it does not touch the xrandr configuration any more (e. g. in gdm), but it still applies my custom monitors.xml in my own session.
This needs to use GSettings instead, and should block on the GSettings port.
Hmkay -- git master still uses gconf, though. I don't see a gsettings branch?
(In reply to comment #4) > Hmkay -- git master still uses gconf, though. I don't see a gsettings branch? Work is on-going.
Review of attachment 171747 [details] [review]: I ported this to Gsettings and pushed it to master as: commit 2ef2dfe21d6b8a6befc622a7991cf1e64e67c847 Author: Rodrigo Moya <rodrigo@gnome-db.org> Date: Fri Nov 5 10:38:40 2010 +0100 Add settings key for disabling boot time configuration In a lot of situations it is undesirable to have g-s-d change the XRandR settings, because it overrides X.org customizations, leads to unnecessary mo switches, or increases boot time. Add a key "use-xorg-monitor-settings" to disable apply_default_boot_configuration(), in which case the XRandR configuration will not be touched unless there is a global or per-user configuration file. Ported initial patch from Martin Pitt to GSettings Fixes https://bugzilla.gnome.org/show_bug.cgi?id=631388
Pushed in gnome-2-32 as well, with a change to default the configuration to TRUE, so that Xorg's behaviour isn't changed.