Commit Graph

18612 Commits

Author SHA1 Message Date
a28f66f541 Update Slovenian translation 2024-02-19 10:09:32 +00:00
692f6078b5 Update Slovenian translation 2024-02-19 10:03:43 +00:00
f8229628ef Update Lithuanian translation 2024-02-18 20:34:40 +00:00
ac10cae1e3 Update Dutch translation 2024-02-18 16:42:31 +00:00
d76d773acc Update Turkish translation 2024-02-18 15:41:55 +00:00
ab19afa9f8 Update Turkish translation 2024-02-18 09:23:01 +00:00
0f287d8196 Update Norwegian Bokmål translation 2024-02-17 22:25:01 +00:00
3dd5dcd9bb authPrompt: Disregard smartcard status changes if VERIFICATION_IN_PROGRESS
commit c8bb45b41c introduced a new
verification state, VERIFICATION_IN_PROGRESS, to detect when the user
has already interacted with the authentication prompt, so the
prompt can rate limit the number of times the user can cancel
authentication attempts with the escape key (without also rate limiting
the number of times they can hit escape to go back to the clock without
interacting with the prompt).

That means there are now two states that represent the user actively
undergoing verification: VERIFYING and VERIFICATION_IN_PROGRESS.

It's inappropriate to reset the smartcard service if the user is
actively conversing with it. We try to check for that by looking at the
original verification state, VERIFYING, but we unfortunately, neglect
to account for the new VERIFICATION_IN_PROGRESS state.

The result is that if a user types their smartcard pin at the clock,
and then inserts their smartcard, the pin will get cleared instead of
used, and they have to retype it again.

This commit fixes the oversight, and allows users to again pre-type
their smartcard pin at the clock before inserting their smartcard.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2765>
2024-02-17 14:04:04 +00:00
aebef54a1d Update Czech translation 2024-02-17 13:58:20 +00:00
974f747f6b Update Persian translation 2024-02-17 12:42:53 +00:00
d6651706fe sessionMode: Use property spread to sync mode
The parameters here come from a fixed set of mode definitions rather
than a function parameter, so the additional check performed by
Params.parse() isn't relevant here.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3196>
2024-02-17 12:02:25 +01:00
fe1eab1b3c cleanup: Also replace Params.parse(..., true) with spread
This is what Params.parse() boils down to when accepting extra
parameters, so we can just as well use standard syntax here.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3196>
2024-02-17 12:02:25 +01:00
8eec7ac3f4 cleanup: Use spread properties instead of Object.assign()
It's more concise and has been around long enough to embrace it.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3196>
2024-02-17 11:53:43 +01:00
5ce991749d lg: Replace remaining Color.init_from_4ub usage
Fixes cd33baff7d

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3197>
2024-02-17 10:46:37 +00:00
3b0e1a6b5a main: Remove timestamp parameter from popModal()
It has been unused since the move to Clutter.grab() in commit
f4cae72d17.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3195>
2024-02-17 10:42:46 +00:00
96471b9d19 main: Remove unused parameters from pushModal()
Both timestamp and options parameters have been unused since
the switch to Clutter.grab(), so remove them.

Stop using Params.parse(), so that code that still passes the
parameters doesn't throw an error.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3195>
2024-02-17 10:42:46 +00:00
3f72a04a1b modalDialog: Remove timestamp parameter from open()
It is now unused.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3195>
2024-02-17 10:42:46 +00:00
0ae285cc82 modalDialog: Remove onPrimary parameter
It was added in commit 48fb16b570 for the lock screen, but that
hasn't been based on ModalDialog for a long time.

It doesn't appear that anything else ever used the parameter,
so just remove it.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3195>
2024-02-17 10:42:46 +00:00
a17f4a6cb8 modalDialog: Don't pass timestamp to popModal()
Just like in the pushModal() case, the parameter doesn't do
anything anymore.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3195>
2024-02-17 10:42:46 +00:00
3574c5246a modalDialog: Stop passing timestamp to Main.pushModal()
Since the move to Clutter.grab() in commit f4cae72d17, the
parameter doesn't do anything anymore.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3195>
2024-02-17 10:42:46 +00:00
0432623fc8 unlockDialog: Stop passing timestamp to Main.pushModal()
Since the move to Clutter.grab() in commit f4cae72d17, the
parameter doesn't do anything anymore.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3195>
2024-02-17 10:42:46 +00:00
fbc7290bcf appDisplay: Remove shellWorkspaceLaunch()
It was deprecated in commit 942758bb30 back in 2019.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3195>
2024-02-17 10:42:46 +00:00
dc0690b761 Update Hebrew translation 2024-02-16 22:16:17 +00:00
66ab222923 Update Ukrainian translation 2024-02-16 18:33:51 +00:00
7a27fd310e Update Basque translation 2024-02-16 15:16:34 +00:00
cd33baff7d cleanup: Prefer CoglColor.init_form_4f
As we are slowly moving colors to be represented by a [0, 1] floats.
The unsigned integer variant will likely be removed in the near future, so be
ready for that already

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3147>
2024-02-16 12:34:30 +01:00
43d4a12576 cleanup: Adapt to removal of CoglPipeline.set_color_*
Associated Mutter PR: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3553

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3147>
2024-02-16 12:34:30 +01:00
ca410bb516 Update Georgian translation 2024-02-16 11:23:31 +00:00
e5e427a315 calendar: Add a11y label to the "Clear" button
The button that clear notifications is labeled as
"Clear". When using a screen reader, this label
doesn't provide enough context about the action
that will happen.

Fix that by adding an a11y label to this button.

Closes https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7398

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3192>
2024-02-16 11:13:36 +00:00
18cfa77706 Update Persian translation 2024-02-15 21:02:27 +00:00
232d8505c4 Update Belarusian translation 2024-02-15 07:12:34 +00:00
000ed83b85 Update Georgian translation 2024-02-15 06:48:47 +00:00
9efc151b57 Update Galician translation 2024-02-15 00:04:35 +00:00
d15f6c75b1 build: Bump gsettings-desktop-schemas requirement
Needed for the `xkb-model` and `show-status-shapes` settings.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3191>
2024-02-14 21:14:32 +01:00
5d4054135e keyboardManager: Adapt to moved functions
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3189>
2024-02-14 19:24:12 +00:00
40a78ecaa6 Update Ukrainian translation 2024-02-14 18:42:27 +00:00
c170d6c956 extensionSystem: Support locking down extension installation
Currently extensions can only be locked down completely by
restricting the `enabled-extensions` key via dconf.

This is too restrictive for environments that want to allow users
to customize their system with extensions, while still limiting
the set of possible extensions.

To fill that gap, add a new `allow-extension-installation` setting,
which restricts extensions to system extensions when disabled.

As the setting is mainly intended for locking down by system
administrators, there is no attempt to load/unload extensions
on settings changes.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3180>
2024-02-14 16:20:59 +00:00
8f2ab674fc st/drawing-actor: Queue redraw when repainting
Commit e7734e30bd removed the clutter_content_invalidate() call
that took care of queuing a redraw for us. Now that we no
longer delegate to a content we have to do that ourselves.

Fixes: e7734e30bd ("st/drawing-area: Merge ClutterCanvas to StDrawingArea")
Closes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7397
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3190>
2024-02-14 00:04:20 +01:00
87966e673a Update Ukrainian translation 2024-02-13 17:40:37 +00:00
af31f37aff Update Russian translation 2024-02-13 16:35:00 +00:00
810a137f07 status/network: Fix small mistake
After introducing the system source this mistake was introduced.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3188>
2024-02-13 16:02:56 +01:00
502a592362 status/thunderbolt: Small style cleanup
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3188>
2024-02-13 16:02:56 +01:00
2bbe03c473 status/thunderbolt: Fix small mistake
After introducing the system source this mistake was introduced.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3188>
2024-02-13 16:02:56 +01:00
1db3ff301d Update Turkish translation 2024-02-13 13:09:25 +00:00
412081a689 magnifier: Keep accounting of own cursor unfocus inhibition
Do not rely on global state since there may be more users of it.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3028>
2024-02-13 11:49:28 +00:00
14db121ce5 st: Adapt to ClutterGrab becoming a GObject
Change the unref function, since it's no longer a boxed type.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3028>
2024-02-13 11:49:28 +00:00
b8db538b44 Update Czech translation 2024-02-13 10:11:39 +00:00
69ec2156bf Update Persian translation 2024-02-12 16:45:18 +00:00
a27ba309dd tools/toolbox: Expose --reconfigure meson flag
It turns out that nowadays meson updates don't always require
a full wipe of an existing build dir, but `--reconfigure` is
often enough. So let's expose that flag as well.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3187>
2024-02-12 13:48:00 +00:00
c461f2d128 Update Georgian translation 2024-02-12 13:00:59 +00:00