Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
This change depens on gsettings key in mate-desktop.
|
|
|
|
Closes #51
https://github.com/mate-desktop/mate-settings-daemon/issues/51
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
** (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
|
|
use libnotify 0.7, not libmatenotify
|
|
|
|
|
|
|
|
|
|
|
|
Since we now require GTK 2.24, we can directly use
gdk_window_get_width(), gdk_window_get_height(), and gdk_window_get_screen()
|
|
And use:
gdk_display_get_app_launch_context() on GTK3
gdk_app_launch_context_new() on GTK2
|
|
for:
gdk_x11_window_lookup_for_display()
gdk_x11_window_foreign_new_for_display()
|
|
|
|
Fixes compiler warning: 'i' may be used uninitialized in this function
Indeed, rather than initializing 'i' to zero, 'lv' (char arr of **lv) was
erroneously being assigned the value of 0 in the for loop's initialization.
g_strv_behead copied from gkbd_strv_behead from libgnomekbd/gkbd-util.c
For reference: Using shared gkbd_strv_* utility functions, reducing the code
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=f62d0846143b8a65606daa6860e6b2cd7f9cb465
|
|
|
|
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
|
|
|
|
Fix fake events generated by applications being the wrong button.
https://bugzilla.gnome.org/show_bug.cgi?id=627084
|
|
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=2674a0fa89abb08443d8f93da6fe9ae7f81c1120
|
|
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=d08b1b05997b3591c7ac1eefebd04a503c97c06e
and bump PolicyKit minimum required to 0.97
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=d1c499e9e6b2aae3b0d1e0004e38f1d280e31144
|
|
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=b9b785508085d77818c76ab4aed8ee574dbd1756
|
|
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
|
|
a11y-keyboard: gtk_dialog_set_has_separator(), deprecated in GTK+ 2.22
common|mouse: prefix GDK key constants with _KEY (GTK3)
|
|
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=1c1677dcfd55eb7e1f6a20435af466331ec2a911
|
|
1. Use g_settings_get_mapped instead of our own hack get_gsettings_int_with_default.
2. Don't force hard-coded default when value is 0, as that's used to allow
paranoid scanning on shutdown.
3. Only unref the settings object at the end of _stop routine, not before
do_cleanup is potentially called, since purge_thumbnail_cache uses the settings.
This was also causing asserts when killing msd, as described in (now closed) #23.
These are regressions introduced by the gsettings port of the plugin -- 03478b4d
|
|
gtk_dialog_set_has_separator deprecated in GTK+ 2.21.8
simple gtk_object -> gtk_widget switch for GTK3 forward compat.
|
|
Namely:
1. In caja_is_drawing..(), only get atom for WM_CLASS property if it exists.
2. Cache gsettings draw-background & show-desktop-icons key-values, and only update
when either actually changes, to avoid unnecessary queries to the dconf-service.
3. Avoid conflicts between settings_change_event_cb() & on_bg_handling_changed().
4. Keep track of screen sizes, to ensure size actually changed when signalled, to
avoid double-redraw on an extraneous signal, which can lockup the daemon, because
we draw immediately (w/out g_idle_add). Though we don't fade in re-draws triggered
by size/monitors-changed signals, making all re-draws queued causes issues with
fading, when we do fade (on bg change), and queueing is unnecessary here anyway.
5. Track a redraw in progress, to avoid any possible (and unforseeable) clashes.
|
|
|
|
|
|
instead of g_timeout_add().
daemon: Use g_timeout_add_seconds (30 seconds)
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=61c8ca9ad8add09830e72d0c10b97f59e80dd0f5
smartcard: Use g_timeout_add_seconds() (2 seconds)
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=5e85aa9cdf6624effea5a890a2516f11d25a8bf3
|
|
Was used to setup old X legacy fonts, and was disabled by default in bug:
https://bugzilla.gnome.org/show_bug.cgi?id=613604
|
|
had xklavier-related warning everytime m-s-d is started, specifically after
we stopped daemonizing the daemon, in a previous commit.
and the bug revolves around libxklavier issue
https://bugzilla.gnome.org/show_bug.cgi?id=150542
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=4239cb8a5d73af79d2cdf0f294a33d31fbbb9afe
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=241c970c1361c4d1b2663af20252ef127055d768
|
|
Updates volume code from gnome-media
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=5f4b71733713741ec6c48480e3ddc73bf72eb290
referenced bug also says fixes a memory leak
https://bugzilla.gnome.org/show_bug.cgi?id=612024
|
|
And instead, use glib macros (since 2.14)
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=0dda56c4462e070dabdab68092b6574b5e894181
|
|
for reference: xsettings: Port XSettings sync to GSettings
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=6d7498114930de358573e97f54880c586c9f9c66
|