Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
taken from:
https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=544526d
|
|
|
|
This fixes the invisible text for GTK+ 3 themes which don't support mate-panel explicitly. Themes could still overwrite the background if they want in the usual way.
|
|
xrandr tray applet (gtk3) support custom panel themes,
with robust support for transparency in cases where gtk3
does not correctly detect a compositing window manager
|
|
Closes https://github.com/mate-desktop/mate-settings-daemon/pull/93
|
|
Taken from GSD commit: 6cd5f46fcb6d0580e541f8d462a1a61e5f0150a3
From: Bastien Nocera <[email protected]>
|
|
Based on gnome-settings-dameon commit: 107f7cdea4bcc508622e040d22e43a9e65574401
From: Emilio Pozuelo Monfort <[email protected]>
|
|
Now the methods are called is_active and is_connected
Based on gnome-settings-daemon commit: 68ff8cf63cea899b45d0ffb6950fdcc28d71fffd (patch)
From: Giovanni Campagna <[email protected]>
|
|
Taken from gnome-settings-deaemon commit:9b1fd55f4e65cad07a3f39de441aca53e34e7473
From: Rodrigo Moya <[email protected]>
|
|
Based on gnome-settings-daemon commit: 3d4bb7d247ac1d70840cd7ea7247263d3f590d9f
From: Giovanni Campagna <[email protected]>
- mate_rr_screen_new has lost the callback parameter, replaced by "screen-changed" signal
- mate_rr_screen_destroy is gone
|
|
Based on gnome-settings-daemon commit 8fb7dd9c4dc6da34b4b2961c6212b91d6342152a
From: Giovanni Campagna <[email protected]>
MateRRScreen, MateRRConfig and MateRROutputInfo have been turned
into GObjects. Adapt to that.
|
|
|
|
|
|
|
|
|
|
|
|
** (mate-settings-daemon:27918): WARNING **: /usr/lib64/mate-settings-daemon/liba11y-keyboard.so: undefined symbol: notify_notification_attach_to_status_icon
** (mate-settings-daemon:27225): WARNING **: /usr/lib64/mate-settings-daemon/libxrandr.so: undefined symbol: notify_notification_new_with_status_icon
liba11-keyboard change done similarily to GNOME, just removing it:
https://github.com/GNOME/gnome-settings-daemon/commit/e1ab570b0dce479ba235e5542ea07d1b5bafc4c9
|
|
|
|
for:
gdk_x11_window_lookup_for_display()
gdk_x11_window_foreign_new_for_display()
|
|
In plugins/housekeeping/gsd-ldsm-dialog.c
- Initialize GSList ignore_paths before use
- Use g_slist_prepend instead of _append in loop (more efficient), reverse after
In plugins/media-keys/msd-media-keys-manager.c
- Default to mate-terminal if terminal "exec" key is empty
In plugins/xrandr/msd-xrandr-manager.c
- Only start_or_stop_icon when the show icon key actually changes
Also, adapt this for media-keys plugin:
Don't use org.gnome.settings-daemon for volume_step setting
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=1a9eea8224d41643a8a7a05d799198058e36e1a8
|
|
|
|
|
|
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.
|
|
|