summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* power: Resolve race condition in test_dim testbenzea/test_dim_race_fixBenjamin Berg2018-04-301-1/+1
| | | | | Without this change we wait exactly as long as gsd-power does before dimming. Resolve this race condition by waiting a second longer.
* datetime: Add debug to timezone monitorBastien Nocera2018-03-221-1/+18
| | | | | | To make debugging issues with the automatic timezone feature easier. https://bugzilla.gnome.org/show_bug.cgi?id=794288
* media-keys: Add mapping for Ctrl + Super + TouchpadToggleHans de Goede2018-03-161-0/+1
| | | | | | | | | | Some budget laptops send Ctrl + Super + custom-scancode when their touchpad-toggle hotkey (Fn + something) gets pressed. hwdb will map the custom-scancode to TouchpadToggle, but we need to deal with the Ctrl + Super in the media-keys plugin, add a mapping for this. https://bugzilla.gnome.org/show_bug.cgi?id=793610
* media-keys: Move microphone mute button to gsettingsBenjamin Berg2018-03-162-1/+6
| | | | | | | | Allow users to configure the microphone mute key. Many laptops do not have a microphone mute key, so it can make sense for users to map it to another key (e.g. Shift+Mute). https://bugzilla.gnome.org/show_bug.cgi?id=793596
* media-keys: Remove legacy mapping from F20 to microphone muteBenjamin Berg2018-03-161-1/+0
| | | | | | | | | | | The current situation is that udev maps the microphone key to F20, which is then mapped to XF86AudioMicMute by the X keyboard config. The requirement to explicitly handle F20 is therefore gone since the xkeyboard-config change has been merged mid 2013. See also https://bugs.freedesktop.org/show_bug.cgi?id=54171 https://bugzilla.gnome.org/show_bug.cgi?id=793596
* media-keys: Improve volume keybinding descriptionsBenjamin Berg2018-03-161-4/+4
| | | | | | | | This changes the volume related strings clarifying that the mute key toggles the state and changing "system volume" to "volume" as the "system" part is not very meaningful. https://bugzilla.gnome.org/show_bug.cgi?id=793596
* Update Croatian translationgogo2018-03-131-7/+7
|
* Update Croatian translationgogo2018-03-131-16/+16
|
* Update Greek translationEfstathios Iosifidis2018-03-131-509/+489
|
* Update Estonian translationMart Raudsepp2018-03-121-1275/+1964
|
* 3.28.0GNOME_SETTINGS_DAEMON_3_28_0Bastien Nocera2018-03-122-1/+6
|
* Updated Spanish translationDaniel Mustieles2018-03-121-510/+488
|
* Update Indonesian translationKukuh Syafaat2018-03-111-558/+528
|
* Update Turkish translationEmin Tufan Çetin2018-03-111-511/+493
|
* Update Friulian translationFabio Tomat2018-03-091-507/+488
|
* Update Serbian Latin translationМилош Поповић2018-03-081-531/+498
|
* Update Serbian translationМарко Костић2018-03-081-531/+498
|
* Updated Danish translationAsk Hjorth Larsen2018-03-071-525/+532
|
* Update Italian translationMilo Casagrande2018-03-071-510/+491
|
* Update Dutch translationJustin van Steijn2018-03-061-570/+551
|
* 3.27.92GNOME_SETTINGS_DAEMON_3_27_92Bastien Nocera2018-03-052-1/+18
|
* xsettings: Fix garbage inside test logsBastien Nocera2018-03-051-13/+12
| | | | | The test suite will print those 'comments', so use '#' to comment them instead.
* power: Fix keyboard brightness testBastien Nocera2018-03-051-4/+8
| | | | | | | The error we'd have gotten from the keyboard brightness test when gsd-power crash obviously wouldn't match that returned by gsd-power. Check the error in details to make sure that the error matches our expectations.
* power: Add more details to property fetch errorBastien Nocera2018-03-051-1/+2
| | | | Like the interface name, to make sure that the error matches our call.
* power: Start mock upowerd earlier in the testsBastien Nocera2018-03-051-10/+11
| | | | | Otherwise gnome-session might try to use an unmocked upowerd on the system, causing crashes with our mock logind.
* tests: Fix reading the Xorg logBastien Nocera2018-03-051-1/+1
| | | | | The xorg log fd position will be after the written error, so re-open the log to read, and check for the expected error.
* Update Swedish translationAnders Jonsson2018-03-041-508/+489
|
* Update Croatian translationgogo2018-03-041-508/+488
|
* Update Hungarian translationBalázs Úr2018-03-041-512/+424
|
* Update Latvian translationRūdolfs Mazurs2018-03-041-867/+458
|
* Update Korean translationChangwoo Ryu2018-03-031-515/+518
|
* Update Galician translationFran Dieguez2018-03-031-524/+492
|
* Updated Lithuanian translationAurimas Černius2018-03-031-526/+493
|
* Update German translationMario Blättermann2018-03-031-11/+11
|
* Update German translationMario Blättermann2018-03-031-516/+428
|
* Update British English translationBruce Cowan2018-03-021-1017/+1186
|
* build: Fix checksIñigo Martínez2018-03-021-4/+6
| | | | | | | | | | | | Following meson guidelines[0], `G_DISABLE_CHECKS` has been removed from non debug builds. However, `G_DISABLE_CAST_CHECKS` has been added to release builds. Please see: !3 https://bugzilla.gnome.org/show_bug.cgi?id=793512 [0] https://wiki.gnome.org/Initiatives/GnomeGoals/MesonPorting
* power: Add test for previous commitBastien Nocera2018-03-021-0/+12
| | | | | | | This just tries to access the keyboard brightness, which should crash gsd-power without the fix. https://bugzilla.gnome.org/show_bug.cgi?id=793512
* power: Fix divide by zero on keyboard Brightness property requestYanko Kaneti2018-03-021-1/+2
| | | | | | | | Fail the get Brightness property request instead of crashing in gsd_power_backlight_abs_to_percentage when there is no UPower managed keyboard https://bugzilla.gnome.org/show_bug.cgi?id=793512
* power: When the the sleep timeout is too short, don't throw errorsBastien Nocera2018-03-021-6/+8
| | | | | | | | | | | | | | | When running the test suite, we set a short sleep callback that shorter than the minimum amount of time we want to able to dim the screen, so that the warning shows up before dimming. But this short sleep timeout leads to a '0' sleep warning timeout, which is an invalid value. Use 1 msec instead of 0 msec as the timeout to avoid the warning. power-plugin-DEBUG: setting up sleep callback 5s power-plugin-DEBUG: setting up sleep warning callback 0s GnomeDesktop-CRITICAL **: gnome_idle_monitor_add_idle_watch: assertion 'interval_msec > 0' failed https://bugzilla.gnome.org/show_bug.cgi?id=794000
* power: Add useful (disabled) envvar for testsBastien Nocera2018-03-021-0/+1
|
* tests: Simplify launching XvfbBastien Nocera2018-03-021-9/+7
| | | | | Instead of having 2 loops looking for a free display number, we now have a single one, making the code more comprehensible.
* tests: Fix mutter logs always being emptyBastien Nocera2018-03-021-1/+1
| | | | Copy/paste error in the logs meant we wrote to the wrong location.
* Update Brazilian Portuguese translationRafael Fontenelle2018-03-021-525/+491
|
* Updated Czech translationMarek Cernocky2018-03-021-510/+490
|
* Update Finnish translationJiri Grönroos2018-03-021-66/+78
|
* Update French translationCharles Monzat2018-03-011-511/+493
|
* Update Polish translationPiotr Drąg2018-03-011-55/+68
|
* printing: Notify user about need for authenticationMarek Kasik2018-03-012-0/+172
| | | | | | | | | | | Notify user about a need for authentication when a job changes state to "pending-held" and set "job-state-reasons" attribute to "cups-held-for-authentication" or "job-hold-until" attribute to "auth-info-required". Clicking the notification (default action) opens gnome-control-center's Printers panel with Jobs dialog which allows user to authenticate the jobs. https://bugzilla.gnome.org/show_bug.cgi?id=766563
* Update Chinese (Taiwan) translationCheng-Chia Tseng2018-02-281-537/+503
|
View Lorry Controller Status