commit dabce9bbb843a1427f7cf4ca8223d8ceab46a308
Author: Daniel van Vugt <daniel.van.vugt@canonical.com>
Date: Tue Jul 7 19:46:16 2026 +0800
Revert "Drop debian/Revert-tests-Fail-on-warnings-too.patch"
This reverts commit 49e6f82f7125d4fc686b0c2b20765cb7dc20dfd7.
Turns out the patch is more about solving CI-specific warnings/failures
than making tests pass perfectly locally.
commit 49e6f82f7125d4fc686b0c2b20765cb7dc20dfd7
Author: Daniel van Vugt <daniel.van.vugt@canonical.com>
Date: Tue Jul 7 18:41:11 2026 +0800
Drop debian/Revert-tests-Fail-on-warnings-too.patch
Somewhat counterintuitively it actually led to more test failures allowing
warnings to be non-fatal.
commit c017cbc97837348d8edd65552dc19fce8ff30f15
Author: Daniel van Vugt <daniel.van.vugt@canonical.com>
Date: Tue Jul 7 14:39:47 2026 +0800
Drop deprecated binary package 'gnome-shell-extension-prefs'
commit fdd77b2f12424bc7a072d2fa09eadadca2db495e
Author: Daniel van Vugt <daniel.van.vugt@canonical.com>
Date: Tue Jul 7 14:29:52 2026 +0800
debian/control: Bump build dependencies for 51.alpha
commit a605da372d5eeb689ecc0ee37b28c0de2cc4c5db
Author: Daniel van Vugt <daniel.van.vugt@canonical.com>
Date: Tue Jul 7 14:27:17 2026 +0800
Refresh patches
commit 8a6ed56a6a9f4f7938e8eabfab0ed7eed4996f1c
Author: Daniel van Vugt <daniel.van.vugt@canonical.com>
Date: Tue Jul 7 14:25:58 2026 +0800
debian/changelog: Add an entry for 51.alpha
commit 05e528bc33ef8fe4ab39cf7f34fcbce1cb2fe869
Merge: 759a8c7e 4c5bd1ec
Author: Daniel van Vugt <daniel.van.vugt@canonical.com>
Date: Tue Jul 7 14:24:52 2026 +0800
Merge tag 'upstream/51_alpha' into debian/latest
commit 4c5bd1ec74d3e317a1e898a70ac1c72f587fbb20
Author: Daniel van Vugt <daniel.van.vugt@canonical.com>
Date: Tue Jul 7 14:21:32 2026 +0800
data/theme: Add latest CSS from the release tarball
commit d1451ce187ab817f7190a4c5a82d4911cb56f0f0
Merge: 8d8a24f9 6652f255
Author: Daniel van Vugt <daniel.van.vugt@canonical.com>
Date: Tue Jul 7 14:18:39 2026 +0800
Merge tag '51.alpha' into upstream/latest
commit 6652f2550cd17d50385d33291c8d18cc30c33d05
Author: Florian Müllner <fmuellner@gnome.org>
Date: Mon Jun 29 17:38:52 2026 +0200
Bump version to 51.alpha
Update NEWS.
commit 8f4205e7f2930a99de6cd8bbec4457d86b197d3d
Author: Florian Müllner <fmuellner@gnome.org>
Date: Sun Jun 28 11:53:41 2026 +0200
build: Remove extensions-app subproject
When turning the gnome-shell-extension-prefs helper into a proper
app, we decided to keep the code in-tree as a subproject.
In hindsight, the downside of a non-standard build workflow — in
particular no "fire up gnome-builder, hit run" — was greater than
the benefit of making coordinated changes between extension system,
D-Bus service and app more convenient (not least because those kind
of changes turned out to be very rare).
The code was therefore moved into its own repository now; the only
thing left to complete the split is to remove the original code
from the subproject.
This also removes the corresponding meson option. We could keep it
and pull in the app from a meson-wrap when requested, but as the
app now always builds as a stand-alone project (no shared translations
anymore), there isn't any point beyond keeping the option working.
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4267>
commit 609a597a67d1a6298bcc172baaa0f24108d68205
Author: Florian Müllner <fmuellner@gnome.org>
Date: Sun Jun 28 11:53:49 2026 +0200
ci: Stop building Extensions flatpak
The app moved to its own repository with its own CI that takes
care of building and publishing the flatpak.
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4267>
commit e1d4e42125c6735270e57fc4861a61cb3e30364d
Author: Florian Müllner <fmuellner@gnome.org>
Date: Sat May 30 02:24:21 2026 +0200
popupMenu: Pass params object to open()/close()
While changing the parameter type is fairly intrusive, switching to
a `params` parameter has benefits that make it worthwhile:
1. all menus can support a common subset of parameters
The `PopupAnimation` type is tied to `BoxPointer`, and makes
little sense for menus that use a different actor. The main
knob to control animations is now a boolean `animate` property
that makes sense for all menu types.
2. menus can support additional class-specific parameters
This allows the main `PopupMenu` class to support a `fadeOnly`
parameter for the cases where the slide bit should be avoided.
Other classes simply ignore parameters they don't support, so
callers don't have to be extra careful about the menu type
they are dealing with.
3. future additions are easy and non-intrusive
Both common or specific parameters can be added without affecting
existing code. As unknown values are ignored, extensions can make
use of new parameters without special-casing older versions.
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4240>
commit b328784abb303c65a9ff385d0d9eef38f184c460
Author: Florian Müllner <fmuellner@gnome.org>
Date: Sat May 30 14:30:59 2026 +0200
popupMenu: Animate `open()`/`close()` by default
We generally want menu state changes to be animated, however menus
other than quick settings currently default to no animations (as
`undefined` is implicitly converted to `0` or `false`).
Follow quick settings and default to animating state changes.
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4240>
commit ebee8bb4d9182b3821e26efb50650bde5429a378
Author: Florian Müllner <fmuellner@gnome.org>
Date: Sat May 30 00:45:50 2026 +0200
popupMenu: Factor out base `open()`/`close()` methods
Menus are assumed to have `open()` and `close()` methods, but it
is up to the subclasses to provide them. This doesn't only result
in some duplication, but also in inconsistencies in the parameters
(specifically whether animations are controlled by a PopupAnimation
value or a bool).
Start addressing this by factoring out base methods that
implementations can chain up to.
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4240>
commit 129ef1eb1762cc29e6a9e51e3a7d1395d662da13
Author: Florian Müllner <fmuellner@gnome.org>
Date: Wed Apr 29 21:36:18 2026 +0200
style: Use start/end text-align where appropriate
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4204>
commit ea9b322d672583b6d886a6183b70596643850422
Author: Florian Müllner <fmuellner@gnome.org>
Date: Wed Apr 29 21:20:07 2026 +0200
st/private: Align justified text to the start
When using justified text, the alignment still applies to partial
lines. Aligning to the start (like for LTR locales) is the better
behavior here, so do that.
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4204>
commit 3c1f53423586e15761e9292fc82040649d1aa754
Author: Florian Müllner <fmuellner@gnome.org>
Date: Wed Apr 29 21:14:02 2026 +0200
st/theme-node: Default to START text-align
We have already defaulted to right-aligned text in RTL locales since
commit 35120dd69c, but now we have a simpler way to express it.
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4204>
commit 822261385e469c488a997a0909bfb3e32d081cae
Author: Florian Müllner <fmuellner@gnome.org>
Date: Wed Apr 29 21:24:13 2026 +0200
st/theme-node: Don't tie StTextAlign to PangoAlign values
We are now explicitly converting from StTextAlign to PangoAlign,
so no need to keep some values of the two enums aligned.
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4204>
commit c712d247acd4263021283c3017ca4c8d92234ca1
Author: Florian Müllner <fmuellner@gnome.org>
Date: Wed Apr 29 21:02:05 2026 +0200
st/theme-node: Add support for START/END text align
They are part of the CSS standard[0] and resolve to left/right depending
on the text direction.
That is usually what is wanted instead of fixed left/right alignment,
so it makes sense for us to support them.
[0] https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/text-align
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4204>
commit 26d1056a9afbfcbe50e18f62cd3fcb7b7f87da74
Author: Florian Müllner <fmuellner@gnome.org>
Date: Wed Apr 29 20:51:42 2026 +0200
st/theme-node: Correct StTextAlign docs
LEFT/RIGHT always align to the left/right. Those only correspond
to the beginning/end for LTR locales, in RTL they are swapped.
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4204>
commit 6b52520d9d0c3e8d918dd87bb2a04dc3122755a5
Author: Florian Müllner <fmuellner@gnome.org>
Date: Mon May 11 15:16:16 2026 +0200
style: Give notifications on lock screen the same width as in session
There is no strong reason to use the same width as user list and prompt
for notifications, in particular as the smaller width can make the
notification's content appear more cramped.
Instead, give notifications the same width as the message list in
the session. Especially where we reuse the same component — namely
media messages — this ensures consistent presentation.
Closes: https://gitlab.gnome.org/GNOME/gnome-shell/-/work_items/9218
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4217>
commit 44a2dbc1d9e8b1c59a3cea9ef22cabdd4657d67b
Author: Florian Müllner <fmuellner@gnome.org>
Date: Fri Jun 26 16:01:51 2026 +0200
docs: Add section on JS variable naming conventions
In particular the convention that a `_` prefix indicates
private/protected scope is as old as the project itself,
but we never explicitly documented it.
Do that now, based on the corresponding section in gjs' own
style guide.
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4266>
commit c306e2b5f2bb48776aadbb1ab939f2b34dbb1842
Author: Florian Müllner <fmuellner@gnome.org>
Date: Mon Mar 16 15:15:28 2026 +0100
tools/toolbox: Fix --multi-monitor option
Specifying dummy monitors via the environment was a feature of the
removed nested backend. Devkit recently added support for creating
monitors from the command line, so switch to that to fix the option.
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4133>
commit 2b9d36abd62bd8ef8793c47bdebce0e1e244515f
Author: Florian Müllner <fmuellner@gnome.org>
Date: Mon Mar 16 14:50:35 2026 +0100
tools/toolbox: Drop support for --nested
With the release of GNOME 50, GNOME 48 is no longer a supported
version. That means all supported versions now support devkit,
so rely on that exclusively for running nested.
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4133>
commit 8e7c0290ef7b0846bf4953217b0e2241d1259811
Author: Alessandro Bono <alessandro.bono369@gmail.com>
Date: Fri Jun 19 12:43:31 2026 +0200
shell/app: Plug GTask leak
The shell_app_activate_action() function gives ownership of the task
to activate_action_get_bus_cb(), which then transfers it to
on_activate_action_cb().
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4258>
commit 26eb4f723554f8f4e498b5c4bd53762d2bf6c221
Author: Alessandro Bono <alessandro.bono369@gmail.com>
Date: Fri Jun 19 12:52:32 2026 +0200
shell/app: Format fix
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4258>
commit 89b599cb48b1e765fa7bc811bdf0b6bf549ccf7a
Author: Bilal Elmoussaoui <belmouss@redhat.com>
Date: Mon Jun 22 12:30:07 2026 +0200
ui: Use Cogl.Snippet.new instead of gjs constructor
As those are not properties
Fixes 0c86a7b35595bb33b58f9ba4c28e0b837eda6894
Closes https://gitlab.gnome.org/GNOME/gnome-shell/-/work_items/9273
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4260>
commit 30f545eb00468e3df317bc725da01fc76ac5b582
Author: Bilal Elmoussaoui <belmouss@redhat.com>
Date: Sun May 31 09:59:18 2026 +0200
Remove GLSLEffect
Now that everything uses ClutterShaderEffect
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4241>
commit 0c86a7b35595bb33b58f9ba4c28e0b837eda6894
Author: Bilal Elmoussaoui <belmouss@redhat.com>
Date: Sun May 31 09:57:31 2026 +0200
ui: Port effects to ClutterShaderEffect
As it covers all our needs nowadays
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4241>
commit 709d0634edd8f82245ff27c7184f9a612842cc6e
Author: Bilal Elmoussaoui <belmouss@redhat.com>
Date: Sun May 31 09:36:08 2026 +0200
st: Adapt ScrollViewFade to ShaderEffect changes
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4241>
commit 9d39e8d62864379b4400942fff693f0055aeb918
Author: Vasil Pupkin <3abac@3a.by>
Date: Sun Jun 21 16:36:59 2026 +0000
Update Belarusian translation
commit 3a8e65e00a1682ea4ed663f3a6fb6d53fb688771
Author: Luiggi R. Cardoso <luiggicardoso@outlook.com>
Date: Sat Jun 20 20:27:29 2026 +0000
Update Brazilian Portuguese translation
commit d0740ca05b171b6899921156cb3def2cc066e72f
Author: Victoria Niedzielska <victorian@gnome.org>
Date: Thu Jun 18 10:38:21 2026 +0000
Update Polish translation
commit 1a9df2b07371116c25bf0751767377df75cbaf6c
Author: Alessandro Bono <alessandro.bono369@gmail.com>
Date: Tue Jun 16 10:47:10 2026 +0200
background: Handle promise rejection from _loadFile()
This suppresses the following:
```
(gnome-shell:11243): Gjs-WARNING **: 19:15:39.498: Unhandled promise rejection. To suppress
this warning, add an error handler to your promise chain with .catch() or a try-catch block
around your await expression. Stack trace of the failed promise:
_loadFile@resource:///org/gnome/shell/ui/background.js:501:20
_load@resource:///org/gnome/shell/ui/background.js:531:14
_init@resource:///org/gnome/shell/ui/background.js:288:14
Background@resource:///org/gnome/shell/ui/background.js:244:4
getBackground@resource:///org/gnome/shell/ui/background.js:635:30
_createBackgroundActor@resource:///org/gnome/shell/ui/background.js:807:49
_updateBackgroundActor@resource:///org/gnome/shell/ui/background.js:779:39
_createBackgroundActor/changeSignalId<@resource:///org/gnome/shell/ui/background.js:835:18
_emitChangedSignal/this._changedIdleId<@resource:///org/gnome/shell/ui/background.js:321:18
@resource:///org/gnome/shell/ui/init.js:21:20
```
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/4253>
commit d87748ac5ec1d8ea1cc34ac41bc767c0fe550adb
Author: Flynn Peck <cirilla@tuta.io>
Date: Mon Jun 15 10:02:46 2026 +0000
Update Cornish translation
commit e116c73c22cef0f4e64c6a869289fbb33f19e8c6
Author: Cas Pascal <casboi86@gmail.com>
Date: Sun Jun 14 07:33:51 2026 +0000
Update Vietnamese translation
commit 519c447caf4142b06d464c521be685e9b64707c0
Author: Flynn Peck <cirilla@tuta.io>
Date: Wed Jun 10 12:33:47 2026 +0000
Update Cornish translation
There is 1 open security issue in bookworm.
You can find information about how to handle this issue in the security team's documentation.
Among the 3 debian patches available in version 50.2-3 of the package, we noticed the following issues:
Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.
Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/g/gnome-shell.png){kind=link}