summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* color: Always use old blackbody calculationbenzea/blackbody-color-stableBenjamin Berg2019-06-031-2/+4
| | | | | | | | | | We tried to switch to a better way of calculating the blackbody color, but unfortunately the switch was only partial and not used in most cases. Revert this to the old calculation for stable so that we can update the default values and configuration panel when moving to the better blackbody color calculation. Fixes #403
* color: Remove compatibility ifdef's for old colord versionsBenjamin Berg2019-06-032-36/+1
| | | | | We already have a dependency on 1.3.5 which removes the need for the switches.
* smartcard: Cancel cancellable when stoppingMarek Kasik2019-05-221-1/+4
| | | | | | | | | | | | | | | | self->cancellable in GsdSmartcardManager is not cancelled at gsd_smartcard_manager_stop() and hence some callbacks are still called after unload_nss() which clears SECMODListLock which is used by SECMOD_GetReadLock() / SECMOD_ReleaseReadLock(). This leads to crashes in NSSRWLock_LockRead_Util() and NSSRWLock_UnlockRead_Util() probably. Also check for return value of g_cancellable_connect(). See https://bugzilla.redhat.com/show_bug.cgi?id=1646359, https://bugzilla.redhat.com/show_bug.cgi?id=1688791 and their duplicates for additional info.
* power: Only disable Suspend/Hibernate actions inside VMBenjamin Berg2019-05-071-7/+8
| | | | | | | | | | | | | While we theoretically only want a different default value inside a VM, we currently hack this by never doing a suspend action inside VMs. However, that also breaks automatic logout, which is an unintended side effect. Move the check to not install the corresponding timeout (preventing sleep warnings from being displayed) and also only enforce the VM specific hack for the Suspend and Hibernate actions. (cherry picked from commit c07ea84b54964ef95461047c53d358f4570e8808)
* color: Add test for always on and shortened smearing timeBenjamin Berg2019-04-161-0/+55
|
* color: Allow night light to be always onBenjamin Berg2019-04-163-22/+42
| | | | | | | | | | | | | | | | | Currently if the user configures the "from" and "to" times for the night light schedule to be close together or equal, g-s-d gets confused as it still tries to smear the transition over a full hour period. To fix this, first make sure that the smearing period is short enough to fit between sunrise and sunset. Also redefine equal start/end times when calculating whether a time falls into a range as the full 24h period. This effectively means that we will smear over the full day or night time when the sunrise and sunset are closer than an hour to each other. It also means that we always enable night light when the times are equal. Based on a patch by Matthew Leeds <matthew.leeds@endlessm.com>.
* Fix MPRIS issues with disconnecting clientsBenjamin Berg2019-04-151-25/+61
| | | | | | | | | | | | | | | | When clients disconnected and they were not the active client they would not be removed from the list. This caused the controller to create a proxy for non-existing clients, causing a bad state. The "connecting" boolean was also not reset, meaning that a new MPRIS client would never be used. Also, there seems to have been a race caused by the fact that we destroyed the DBus proxy from the vanished signal. Change the DBus proxy to be removed when its g-name-owner property becomes NULL. Fixes #45 (cherry picked from commit 162379ed515a7af7601207b664b7003c4ca6fe02)
* power,media-keys: Signal connector rather than output ID for OSDBenjamin Berg2019-04-156-45/+41
| | | | | | | | | | | | | | We don't have the concept of an output ID anymore in the DBus API. The current code was entirely broken for a long time now (i.e. never signalled any output) and the fixup for 3.32 that I did was actually doing guesses that were incorrect. Fix this properly by passing around the connector name rather than an output ID. This requires changes in gnome-shell to work properly (but doesn't regress without those changes). Fixes: #401 (cherry picked from commit ded2c4c35c28422a360e681a455a26895ab99d23)
* Updated Danish translationAsk Hjorth Larsen2019-04-081-1/+1
|
* Updated Danish translationAsk Hjorth Larsen2019-04-071-488/+472
|
* Update Esperanto translationCarmen Bianca BAKKER2019-04-061-224/+236
|
* Update Croatian translationGoran Vidović2019-03-251-3/+1
|
* Update Croatian translationGoran Vidović2019-03-251-173/+175
|
* Updated Danish translationAlan Mortensen2019-03-181-19/+20
|
* Release 3.32.0GNOME_SETTINGS_DAEMON_3_32_0Carlos Garnacho2019-03-112-1/+6
|
* Release 3.31.92GNOME_SETTINGS_DAEMON_3_31_92Carlos Garnacho2019-03-062-1/+9
|
* Update Latvian translationRūdolfs Mazurs2019-03-031-177/+169
|
* Update Serbian translationМарко Костић2019-02-281-162/+162
|
* Update Korean translationChangwoo Ryu2019-02-261-162/+162
|
* Update Italian translationMilo Casagrande2019-02-251-170/+170
|
* Update Dutch translationNathan Follens2019-02-241-236/+240
|
* Update Finnish translationJiri Grönroos2019-02-231-227/+245
|
* power: Build and test sysfs backlight support only on LinuxBenjamin Berg2019-02-233-20/+48
| | | | | | | | Configuring the backlight using sysfs is only supported on linux. We depend on GUdev on linux, so that we can just check for the platform. This avoids enabling the sysfs backlight helper on platforms that have GUdev but do not support backlight control using sysfs.
* meson: Fix GUdev assert on LinuxBenjamin Berg2019-02-231-1/+3
| | | | | GUdev is required to compile g-s-d on linux. Unfortunately the assertion would never be hit as is.
* Update Polish translationPiotr Drąg2019-02-211-159/+159
|
* Update Icelandic translationSveinn í Felli2019-02-211-916/+1021
| | | | (cherry picked from commit 7f8362d4eaa50c4b098656278f6b175631d995b9)
* Release 3.31.91GNOME_SETTINGS_DAEMON_3_31_91Carlos Garnacho2019-02-202-1/+13
|
* media-keys: Ignore some key repeated eventsAndrea Azzarone2019-02-201-45/+45
| | | | | | | | Use META_KEY_BINDING_IGNORE_AUTOREPEAT flag for all the toggle shortcuts and for all the shortcuts where a repeated key-press could cause weird or useless behaviour. Fixes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/68
* media-keys: support grabFlags parameterAndrea Azzarone2019-02-204-5/+28
| | | | | | Support the grabFlags parameter of the GrabAccelerator and GrabAccelerators methods of the DBUS org.gnome.Shell API. For the moment always use META_KEY_BINDING_NONE.
* Update Brazilian Portuguese translationRafael Fontenelle2019-02-201-182/+175
|
* Update German translationTim Sabsch2019-02-171-168/+168
|
* Update Chinese (Taiwan) translationYi-Jyun Pan2019-02-171-172/+172
|
* Update Kazakh translationBaurzhan Muftakhidinov2019-02-171-181/+183
|
* Fix overflow in thumbnail cache housekeepingJing Wang2019-02-141-2/+2
| | | | | | g_settings_get_int gives a signed 32 bit integer, so setting the thumbnail cache size to 5120 MB (for example) resulted in an overflow to 1 GB. Tested on my computer by changing the cache size to a value that would previously overflow and observing the size of ~/.cache/thumbnails.
* Updated Danish translationAlan Mortensen2019-02-131-354/+324
|
* Update French translationCharles Monzat2019-02-131-173/+174
|
* Updated Lithuanian translationAurimas Černius2019-02-091-178/+170
|
* Updated Czech translationMarek Cernocky2019-02-081-162/+162
|
* Release 3.31.90GNOME_SETTINGS_DAEMON_3_31_90Carlos Garnacho2019-02-052-1/+18
|
* CI: Allow failures of delivery task for nowBenjamin Berg2019-02-051-0/+2
| | | | | | Currently the coverage report is not generating, causing the delivery to also fail. As we are already allowing a coverage failure, do the same for delivery.
* power: Add memory sanitization workaround to power enums helperBenjamin Berg2019-02-051-2/+7
| | | | | | | | | | | | | | | | | | For some reason we get an error when calling g_print. This works around the following build error: Uninitialized bytes in __interceptor_fopen64 at offset 3 inside [0x702000000160, 18) ==30133==WARNING: MemorySanitizer: use-of-uninitialized-value #0 0x7f9e3205ab75 in _g_locale_get_charset_aliases.part.0 /home/benjamin/.cache/jhbuild/build/glib/../../../../Projects/jhbuild/checkout/glib/glib/libcharset/localcharset.c:141:38 #1 0x7f9e3205afc4 in _g_locale_get_charset_aliases /home/benjamin/.cache/jhbuild/build/glib/../../../../Projects/jhbuild/checkout/glib/glib/libcharset/localcharset.c:448:3 #2 0x7f9e3205afc4 in _g_locale_charset_unalias /home/benjamin/.cache/jhbuild/build/glib/../../../../Projects/jhbuild/checkout/glib/glib/libcharset/localcharset.c:448:18 #3 0x7f9e31feb569 in g_utf8_get_charset_internal /home/benjamin/.cache/jhbuild/build/glib/../../../../Projects/jhbuild/checkout/glib/glib/gcharset.c:119:13 #4 0x7f9e31feb569 in g_get_charset /home/benjamin/.cache/jhbuild/build/glib/../../../../Projects/jhbuild/checkout/glib/glib/gcharset.c:204:24 #5 0x7f9e3201a007 in g_print /home/benjamin/.cache/jhbuild/build/glib/../../../../Projects/jhbuild/checkout/glib/glib/gmessages.c:3189:11 #6 0x494488 in output_flags_values /home/benjamin/Projects/jhbuild/checkout/gnome-settings-daemon/_build/../plugins/power/gsd-power-enums-update.c:26:3 #7 0x49432a in main /home/benjamin/Projects/jhbuild/checkout/gnome-settings-daemon/_build/../plugins/power/gsd-power-enums-update.c:41:2 #8 0x7f9e31bb4412 in __libc_start_main (/lib64/libc.so.6+0x24412) #9 0x41b33d in _start (/home/benjamin/Projects/jhbuild/checkout/gnome-settings-daemon/_build/plugins/power/gsd-power-enums-update+0x41b33d)
* tests: Disable AT bridge to silence A11Y bus warningsBenjamin Berg2019-02-051-0/+1
| | | | | Otherwise we always get warnings like: (gsd-power:2708): dbind-WARNING **: 18:29:07.343: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
* CI: Build with -Db_lundef for msanBenjamin Berg2019-02-051-1/+1
| | | | This is needed to build libgsd.
* power: Let stderr output of gsd-power test process go outsideBenjamin Berg2019-02-051-2/+3
| | | | | | | We used to redirect it into stdout which goes into a separate log. However, stderr is generally useful to see, and we actually need to see it for ASAN checking. So always let stderr go through for the gsd-power test process.
* CI: Enable verbose output during testingBenjamin Berg2019-02-051-1/+1
|
* tests: LD_PRELOAD ASan library when address sanitize is enabledBenjamin Berg2019-02-052-6/+15
| | | | This is required because umockdev is also preloaded
* CI: Add LLVM and GCC sanitizers into docker imageBenjamin Berg2019-02-053-3/+3
|
* CI: Allow coverage to failBenjamin Berg2019-02-051-0/+2
| | | | | It appears to be broken currently on rawhide. Assume that this is just an intermitten failure and hope it will just start working eventually.
* xsettings: Make assertion in test a bit nicerBenjamin Berg2019-02-051-3/+2
| | | | This just allows seeing the full list of options that is being matched.
* CI: Also store build directory when the job failedBenjamin Berg2019-02-051-0/+1
|
View Lorry Controller Status