| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
HAVE_WAYLAND is always defined. We should check whether it is set to a
non-zero value instead of checking whether it is defined.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
A smooth transition between two color temperatures might still be active
when the next color temperature is set. Cancel any pending transitions
in this case.
This possibly fixes issues where the colour temperature is stuck in
night mode even though it is daytime.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
ERROR: test_inhibitor_idletime (__main__.PowerPluginTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/hadess/Projects/jhbuild/gnome-settings-daemon/plugins/power/test.py", line 966, in test_inhibitor_idletime
self.check_no_suspend(2)
File "/home/hadess/Projects/jhbuild/gnome-settings-daemon/plugins/power/test.py", line 335, in check_no_suspend
log = self.logind.stdout.read()
IOError: [Errno 11] Resource temporarily unavailable
https://bugzilla.gnome.org/show_bug.cgi?id=794563
|
| |
|
|
|
|
| |
See https://bugzilla.gnome.org/show_bug.cgi?id=705942
https://bugzilla.gnome.org/show_bug.cgi?id=794563
|
| |
|
|
|
|
|
|
|
| |
Rather than poke through using XTest, use Mutter's new D-Bus API to do
as if the user pressed a key on a keyboard.
See https://bugzilla.gnome.org/show_bug.cgi?id=705942
https://bugzilla.gnome.org/show_bug.cgi?id=794563
|
| |
|
|
|
|
|
|
| |
It's now implemented in mutter itself.
See https://bugzilla.gnome.org/show_bug.cgi?id=705942
https://bugzilla.gnome.org/show_bug.cgi?id=794563
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Just silently dropping the error is not really useful and makes
debugging harder.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Systemd recently merged supported for suspending then hibernate
which is a new sleep type that will suspend the system followed by
hibernate after a period of time.
If the system supports it (new enough systemd and hibernation supported)
choose this when the system is configured to suspend.
|
| |
|
|
|
| |
This adds the required glue code to support it for old dbusmock versions
and allows SuspendAndHibernate to be picked by default.
|
| |
|
|
|
|
|
|
| |
This resolves an obscure race condition which causes mutter to fire
active watch/idle watch events in the wrong order.
Failure: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/jobs/23097
Mutter issue: https://gitlab.gnome.org/GNOME/mutter/issues/113
|
| | |
|
| |
|
|
|
| |
Seems like this broke in the move to meson. Rather than trying to set it
inside the binary, set the environment variable in meson.
|
| |
|
|
| |
Without this we need to install the GSchema files for testing purposes.
|
| |
|
|
|
|
|
|
|
|
| |
The test currently needs ~260 seconds, which does not give much buffer
with a set maximum of 300 seconds. When the test is aborted, then the
python unittest will not properly show the results, as the backtrace is
only displayed with the failure.
So, err on the side of giving the test a lot more time than it needs, to
ensure that the output will be useful even with a lot of slow failures.
|
| |
|
|
|
|
|
| |
If the output (or input) is buffered, then the tests might not be able
to read the log entries right away, causing the test to fail.
Explicitly add buffering=0 to open calles where this might be relevant.
|
| |
|
|
|
| |
This simplifies the code quite a bit and makes startup much more robust
as -displayfd is now used rather than badly guessing free X displays.
|
| | |
|
| |
|
|
|
| |
Moving this is important, as gnome-session (or to be exact the
acceleration check) requires the environment variable to be set already.
|
| |
|
|
|
|
| |
The gsd-color self test does not require GTK+ to be initialized to run.
So don't call gtk_init as a display server may not be available during
test execution.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On slower machines (esp. with tracker and/or dropbox starting on login)
this may take more than the usual timeout of ~25 seconds.
We cannot use the existing retry loop here – in this bug, the first call
actually *succeeds* from gnome-shell's side, even if gsd-mediakeys gives
up on waiting for the reply.
So if we called GrabAccelerators again, we would receive no accel IDs
(because all keys are duplicates), and gnome-shell would keep sending
AcceleratorActivated signals with accel IDs that the 1st call has
established – resulting in exactly the same "Could not find accelerator
for accel id" as we're trying to fix.
https://bugzilla.gnome.org/show_bug.cgi?id=792353
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
To make debugging issues with the automatic timezone feature easier.
https://bugzilla.gnome.org/show_bug.cgi?id=794288
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
