Commits on Source (22)
-
Jordi Mas authored6937e0b3
-
Kukuh Syafaat authoredd4650ea4
-
Cheng-Chia Tseng authoreda13ef100
-
Charles Monzat authored49086711
-
Changwoo Ryu authored362ab5d0
-
AsciiWolf authored5581bda3
-
Christian Kirbach authored63f19252
-
Luming Zh authored59834638
-
Florian Müllner authored
We update the visibility on state or stream changes, but those changes may never happen if pipewire-pulse/pulseaudio isn't available (for example when running as root). Hiding the sliders is preferable in that case to showing non-working controls. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2295> (cherry picked from commit 9400759f)
24a587cf -
Florian Müllner authored
PolkitAgent recently added autocleanup functions itself, so check for their existence at configure time and only define our own when they don't exist upstream. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5490 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2296> (cherry picked from commit 1d0a08b5)
9aa71ba9 -
Maksym Hazevych authored
The problem is that " 9:59 AM" (notice the space at the beginning) and "12:59 AM" strings, when centred, look misaligned — strings padded with a space look off to the right by nearly half a character. This happens because the font feature "tnum", used to make numbers monospace, doesn't work on spaces. The commit overcomes this by aligning time labels to the end. However, this won't work for locales with AM/PM strings of different lengths, so they are aligned to the start instead to minimise offset. It's too complex to know whether the used locale has different AM/PM string lengths. Instead, every time the time changes, it determines whether all the time labels have the same amount of characters. Fixes #5438 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2294> (cherry picked from commit 3290ef4e)
47cd5b65 -
Florian Müllner authored
Main.pushModal() used to ensure a compositor grab, but didn't take an input grab. That changed when porting to ClutterGrab, so by limiting the grab to the shield/dialog, it is no longer possible to access top bar menus when the screen is locked. To fix that, take the grab on the whole uiGroup so that the top bar is included. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5470 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2298> (cherry picked from commit 3e7ce18d)
3bc04ab1 -
Jonas Dreßler authored
If we don't set the height property to -1 before requesting the preferred height, get_preferred_height() will just return us the fixed height that has been set before. We don't want this behavior here, so set the height to -1 before calling get_preferred_height(). This fixes a resizing issue where the keyboard is sized incorrectly after switching the monitor into portrait mode and back. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2306> (cherry picked from commit a3bfe0ab)
978e98ed -
Carlos Garnacho authored
We need this to catch events before they reach to the emoji keys, and the gesture can begin/end properly. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2304> (cherry picked from commit da3d4e82)
1cf5f4b0 -
Carlos Garnacho authored
For all instances of this gesture, we want this gesture to activate after some distance, not to eat button presses/releases right away. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2304> (cherry picked from commit 1fa5c633)
7491d830 -
Carlos Garnacho authored
This makes the gesture able to get the events that would otherwise be meant for the background actor or client window. Fixes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5335 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2304> (cherry picked from commit 9a093530)
8dc0ca5e -
Sebastian Keller authored
Absolute screen coordinates are impossible for Wayland clients to provide, because the clients don't know where the window is positioned. Some clients, such as the ones using GTK 3 were providing window relative coordinates even when screen coordinates were requested, while others, such as GTK 4 clients, were just returning an error for caret events or also window-relative coordinates for focus events. So for this to work on Wayland we have to request window-relative coordinates and translate them to the current focus window. To ensure the correct coordinates, we have to only consider events coming from the current focus window. All other events are filtered out now. As a side effect this also fixes the magnifier always jumping to a terminal cursor whenever there was some output, even if the window was not focused. This also needs some special handling for events coming from the shell itself, which should not be translated to the focus window either. As another side effect this fixes another bug that was caused by these events already including scaling and getting scaled again. Fixes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5509 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2301> (cherry picked from commit 8b5d0277)
cb0c4bd1 -
Florian Müllner authored
Update NEWS.
c6a0f4ae -
Jeremy Bicha authored575385e5
-
Jeremy Bicha authored
Upstream version 42.2
b80e6d07 -
Jeremy Bicha authored6555831d
-
Jeremy Bicha authored2c360cdd
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.