summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2024-08-15build: escape newlineorbea1-1/+1
2024-07-15ci: fix Debian buildslukefromdc1-1/+2
The policykit-1 transitional package seems to no longer exist in Debian testing
2024-02-16release 1.28.0v1.28.0raveit652-3/+7
2024-02-16tx: sync with transifexraveit653-16/+15
2024-01-25release 1.27.1v1.27.1raveit652-1/+17
2024-01-25tx: sync with transifexraveit65109-8148/+8239
2024-01-23ci: use ubuntu jammy as dockerraveit651-1/+1
2023-10-22Open default application using async functionXiaotian Wu1-17/+22
2023-10-20replace deprecated gtk_image_menu_item*raveit654-6/+8
2023-10-08ci: remove dbus-glibXiaotian Wu1-4/+0
2023-10-08remove dbus-glib from build systemXiaotian Wu1-4/+1
2023-10-07rfkill: change bus name to org.mate.SettingsDaemonXiaotian Wu2-2/+2
2023-10-07rfkill: allow another message bus connection to claim the bus name.Xiaotian Wu1-3/+2
2023-10-07xrandr: migrate from dbus-glib to GDBusWu Xiaotian4-66/+138
2023-10-07media-keys: migrate from dbus-glib to GDBusWu Xiaotian4-96/+232
2023-10-07msd: migrate from dbus-glib to GDBusWu Xiaotian6-348/+283
2023-09-28smartcard: migrate from dbus-glib to GDBusWu Xiaotian1-45/+70
2023-09-22datetime: migrate from dbus-glib to gdbusWu Xiaotian6-527/+608
2023-06-29a11y-keyboard-atspi: Fix memory leakColomban Wendling1-6/+6
Fix fairly large memory leak when beeping on keys while caps lock is enabled. The libatspi2 docs and API were quite misleading, so I overlooked the fact the event parameter should be freed in the callback. This changes the constness of the callback argument, which is new in libatspi2 2.40 -- yet the actual behavior didn't change, only the qualifier was removed, see [1]. This might however bring up a compiler warning when building against libatspi2 < 2.40; but on the other hand it fixed build with clang >= 16, see #399. As it is unlikely to build with clang >= 16 and libatspi2 < 2.40, I think it's a good compromise. [1] https://gitlab.gnome.org/GNOME/at-spi2-core/-/commit/7dfb0b7fc2d1710ef7fad54f910fa4c6a5e3af17
2022-11-11release 1.27.0v1.27.0mbkma2-1/+26
2022-11-03configure.ac: The macro 'AC_HELP_STRING' is obsoleterbuj1-9/+9
2022-11-03a11y-keyboard: migrate from dbus-glib to GDBusWu Xiaotian1-28/+28
2022-11-03Relax High DPI limitsFabio Pugliese Ornellas1-2/+4
2022-10-29tx: update resourcembkma1-69/+69
2022-10-28tx: migrate config filembkma2-6/+16
2022-08-17msd-keyboard-xkb: use G_N_ELEMENTS macrorbuj1-8/+4
2022-08-08Add setting for adjustment of audio volume above 100 per cent: Part 3Gordon Norman Squash1-1/+14
There is often a need for the user to increase the audio playback volume above the volume level known as "100% volume". While increasing the audio volume above 100% can result in degraded audio quality, sometimes the audio was, for example, originally recorded at an extremely low volume, and the user has no other option to clearly hear the audio. Unfortunately, most MATE applications with volume controls do not allow the user to set the volume level above 100%. For example, the main MATE Sound Preferences dialog lets you set the audio volume beyond 100% (when possible), whereas the Volume Control Applet, Volume Control status icon, and special "multimedia" volume control keys do not. In fact, if the user even tries to change the volume using any of the latter methods, and the current volume level is above 100%, these latter methods will all reduce the volume to 100%, even if the user tried to increase the volume! This is part 3 of a patch to change this situation. This patch adds this capability to the handlers for the "multimedia" volume control keys -- if the appropriate setting is enabled in the MATE Volume Control Dialog (see patch 2), then the user can increase the audio volume beyond 100% by pressing the "Volume Up" key on their keyboard (if they have such a key). While this patch is smaller than patch 2, it is equally important since the original feature request was for the multimedia keys and not for anything else in particular.
2022-06-22build warning: AC_OUTPUT should be used without argumentsrbuj1-1/+2
2022-03-27mate-settings-manager: fix memory leakrbuj1-1/+4
2022-03-14Fix implicit conversion changes signedness: 'gboolean' to 'guint'rbuj2-2/+2
2022-03-10datetime: declaration shadows a variable in the global scoperbuj1-5/+1
2022-03-10Fix build warnings about missing field initializerrbuj2-2/+3
2022-03-10Cppcheck: function parameter can be declared with constrbuj5-10/+10
2022-03-10Use GLib's new g_clear_signal_handler() function to simplify coderbuj1-0/+6
2022-03-10housekeeping: disconnect manager's changed settings signal on finalizerbuj1-13/+24
2022-02-12ci: drop -Wunused-parameter compiler cflag from debian buildraveit651-1/+1
2022-01-23xrdb: wrong type field in printf format stringrbuj1-3/+3
2021-11-28datetime: fix memory leakrbuj1-2/+4
2021-11-24build: show configure summary using a pretty formatrbuj1-31/+33
2021-11-24Use a blank line at mostrbuj33-55/+0
2021-09-18tx: update resourceraveit651-3/+3
2021-09-18xrandr: fix typo reported by translatorsraveit651-1/+1
2021-08-05release 1.26.0v1.26.0raveit652-2/+7
2021-08-05tx: sync with transifexraveit65109-13884/+13889
2021-08-05travis-Ci: use libera.chat as notification serverraveit651-1/+1
2021-06-23tx: update resourceraveit651-127/+127
2021-06-23update copyright to 2021raveit65142-0/+142
2021-05-30release 1.25.1v1.25.1raveit652-1/+36
2021-05-30tx: pull from transifexraveit65109-6697/+7246
2021-05-30travis-ci: use ubuntu focal as host systemraveit651-1/+1
fixes build issues with fedora:latest (f34) tag.