| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Most of the plugins do not need gnome-desktop's functionality, so there is
no point in the main process linking against it.
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=ed54ceee46b6a56613c8aeb3d594f6a485400ef9
|
|
And instead, use glib macros (since 2.14)
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=0dda56c4462e070dabdab68092b6574b5e894181
|
|
|
|
|
|
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 mode
switches, or increases boot time.
Add a mateconf 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.
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=631388
Bug-Ubuntu: https://launchpad.net/bugs/640807
|
|
fallback configurations
Previously, if a stored configuration existed but it could not be applied due
to nonmatching monitors, we would do nothing else - potentially leaving the user
in whatever startup state was used by the X server. Now, in that condition
we simply fall back to trying the system-global configuration or the boot-time
configuration.
Signed-off-by: Federico Mena Quintero <[email protected]>
|
|
In 2.32, we still want to use mate-display-properties.
This reverts commit 03112091d18ad0f9cc66b5f8835aadb1c47bc9ee.
|
|
|
|
|
|
|
|
|
