Commit Graph

18591 Commits

Author SHA1 Message Date
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
8e7d235513 tools/toolbox: Explicitly use /bin/bash
The script uses bash-specific language extensions which cause syntax
errors when run with /bin/sh -> /bin/dash.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3186>
2024-02-11 14:41:31 -08:00
fbe3c4120f Bump version to 46.beta
Update NEWS.
2024-02-11 17:54:00 +01:00
c9d163cc0d screencastService: Remove unused variable assignment
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2976>
2024-02-11 12:36:23 +01:00
5c0c1b15f8 screenshot: Also do pipeline fallback on screencast crashes during startup
Since the last commit, we have infrastructure in place in the ScreencastService
to blocklist pipelines which crashed the recorder.

If such a crash happens a few minutes into a screencast, we can't do any better
than telling the user about the problem and encouraging them to try again (with
the faulty pipeline now blocklisted).

If the crash happens while starting the recording though, we can actually do
better: We can try to auto-restart the ScreencastService ourselves, and the
recording might still succeed without the user noticing anything. So retry
that start of the recorder for two more times, and then finally give up.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2976>
2024-02-11 12:36:23 +01:00
b6bfe07137 screenshot: Blocklist the current screencast pipeline if recorder failed
When gstreamer crashes during recording, it pulls the whole screencastService
down with it.

These crashes are typically caused by the gstreamer pipeline that's in use,
so to avoid running into them again and again, we can blocklist the last
used pipeline in case the recorder didn't shut down (aka crashed) last time.

To store this state, create a file (gnome-shell-screencast-pipeline-blocklist)
in the XDG runtime dir and store the ID of the current pipeline in that file
before we try to start.

Now when we crash while running the pipeline, the entry in that file will stay
around and we'll pick it up on the next start of the screencastService as a
blocklist.

When the recording was successful on the other hand, we'll call
`this._updateServiceCrashBlocklist([...this._blocklistFromPreviousCrashes])`
and remove the new entry from the file again before shutting down the recorder.

In addition to that, we can now encourage the user to try recording again
after a crash happened. Adjust the failure notification a bit to say
"please try again".

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6747

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2976>
2024-02-11 12:34:54 +01:00
ce613f5d15 screenshot: Show a special error when screencast ran out of disk space
Since we now propagate error types back to gnome-shell now, let's start
with showing a special error message in case the disk ran out of space,
which is probably the most typical error.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2976>
2024-02-11 11:32:19 +01:00
7133fac91f screenshot: Handle screencast startup failures using special notification
When the screencast fails to start, we currently don't really inform the
user, other than the red screencasting indicator in the panel going away.

Re-use the failure handling paths to also show a notification when the
screencast fails to start. The notification in this case obviously should
not have an action to open a file (there is no file), so make that depend
on whether this._screencastPath is set and unset the path.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2976>
2024-02-11 11:32:19 +01:00
75f86a6f60 screencastService: Propagate machine-parseable error types to gnome-shell
We'll be using hardware encoding for screencasts soon, so we'll likely see
more things go wrong in the future, including crashes of the whole
screencastService. To deal with this, we'll introduce logic to blocklist
certain recording pipelines in case of failure and also add some logic
to retry the recording automatically.

To allow for better messaging to the user in those failure cases, we want
to be aware in gnome-shell, what exactly the error in the recorder was.

So propagate the most common types of errors that can happen in the
ScreencastService to gnome-shell using the new DBusError module.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2976>
2024-02-11 11:32:19 +01:00
a7e93f3af2 ci: Bump mutter image
The new image no longer includes the development version of glib,
which provides a newer API version of GIRepository that breaks
gjs' package module.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3181>
2024-02-11 02:15:34 +01:00
251a82f4ea Update Turkish translation 2024-02-10 10:58:40 +00:00
5cca9009f1 messageList: Fix spacing between messages in calendar
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3177>
2024-02-09 23:23:14 +00:00
9c7e1f1180 layout: Stop using deprecated display property
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3178>
2024-02-09 19:04:53 +01:00
b09eced160 layout: Don't use supports_extended_barriers()
The method was deprecated in favor of backend capabilities,
so query those instead.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3176>
2024-02-09 17:32:57 +01:00
02c85fbb64 layout: Don't use get_feedback_group_for_display()
The global method was deprecated in favor of a corresponding
method on Meta.Compositor, use that instead.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3176>
2024-02-09 17:32:57 +01:00
40376d90fd style: Adjust search content width to realign items
- default max-width doesn't align with new padding, fixed by tweaking

Closes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7389
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3175>
2024-02-09 10:12:35 -03:30
bb918fff3c messageTray: Remove _createPolicy() hook
It is now unused (at least in gnome-shell itself).

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3170>
2024-02-09 11:12:51 +00:00
3fc7ed4088 notification: Pass policy in the Source contructor
Commit 932ccac1 changed Source to use a regular constructor
instead of `_init()`.

Unfortunately that results in ordering issues for subclasses
that override `_createPolicy()`, if that method needs to access
any properties that are set in the constructor (as `this` is
only available after chaining up to the parent).

We can fix that by simply setting the policy from the constructor,
instead of relying on some overriden method being called.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3170>
2024-02-09 11:12:51 +00:00
810391f41e messageTray: Add NotificationPolicy.newFromApp()
We have several places where we create an application policy
from an app if possible, and fall back to a generic policy
otherwise.

Make that more convenient by adding a small helper method.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3170>
2024-02-09 11:12:51 +00:00
ebec609207 messageTray: Don't call _createPolicy() unconditionally
Since commit 932ccac1c2, the Source constructor takes a
properties object instead of individual arguments.

That means that the policy may now be set through a construct
property, and we shouldn't override it if that was the case.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3170>
2024-02-09 11:12:51 +00:00
60fb2de15f theme: Increase padding of switches
This is to make it generally more in line with the stylesheet as well
as to resolve the blue and white bleeding together in dark mode.

It's also consistent with switches in recent mockups.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3077>
2024-02-08 20:32:50 +00:00
2dc0f48a22 window tracker: Adapt to renamed function
Ideally, the use case we have for MetaGroup would be removed but that
requires investigation that could be done as a future step

The function also expects a MetaWindowX11, so add a check to ensure
we don't crash at runtime if the function gets called on a wayland
client

Also removes an unused header import

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3157>
2024-02-08 16:45:06 +01:00