Debian Patches
Status for gnome-shell/48.0-1
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| debian/Revert-tests-Fail-on-warnings-too.patch | Revert "tests: Fail on warnings too" This reverts commit 207b9bb3c0a582b830218fd1b6e8760684adbc48. |
Jeremy Bicha <jeremy.bicha@canonical.com> | no | 2023-02-17 | ||
| shell-app-Warn-instead-of-crashing-if-disposed-before-sta.patch | shell/app: Warn instead of crashing if disposed before startup notification This is currently easy to reproduce by launching and immediately closing Chrome, then closing the shell. But automated crash reports show it can also happen while using the shell, during a garbage collection run. It's currently the top gnome-shell crasher in Ubuntu, and mostly with Chromium/Electron apps. But regardless of the offender, we shouldn't ever trust application behaviour to keep the shell alive. |
Daniel van Vugt <daniel.van.vugt@canonical.com> | yes | upstream | 2024-08-29 | |
| st-theme-node-Forget-properties-cache-on-stylesheet-chang.patch | st/theme-node: Forget properties cache on stylesheet change To avoid `node->properties` pointing to freed memory after each `st_theme_unload_stylesheet`, flush the cache that is `node->properties`. They will be reloaded as soon as they are required by `ensure_properties`. And yes `node->stylesheets_changed_id` already existed, but was unused. Why not just fix Croco? Croco does not use proper reference counting everywhere it should, and retrofitting it would be difficult due to the recursive nature of `CRDeclaration`. Includes commit: st/theme-node: Forget properties cache before unref'ing the theme Which the properties point into. |
Daniel van Vugt <daniel.van.vugt@canonical.com> | yes | upstream | 2024-03-28 | |
| tray-icons/build-Add-explicit-dependency-on-Xfixes.patch | build: Add explicit dependency on Xfixes We use the xfixes extensions in tray icons but we rely on the dependency brought to us from other libraries as mutter but let's make it explicit |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | https://gitlab.gnome.org/3v1n0/gnome-shell/-/commits/tray-offscreen-xwindows | 2024-05-01 | |
| tray-icons/shell-tray-Ensure-that-only-a-child-can-be-added.patch | shell-tray: Ensure that only a child can be added | =?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | https://gitlab.gnome.org/3v1n0/gnome-shell/-/commits/tray-offscreen-xwindows | 2024-05-01 | |
| tray-icons/shell-tray-icon-Trigger-a-relayout-when-the-underneath-xe.patch | shell-tray-icon: Trigger a relayout when the underneath xembeded size changes | =?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | https://gitlab.gnome.org/3v1n0/gnome-shell/-/commits/tray-offscreen-xwindows | 2024-05-01 | |
| tray-icons/shell-tray-icon-Use-available-space-when-that-s-defined.patch | shell-tray-icon: Use available space when that's defined | =?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | yes | upstream | https://gitlab.gnome.org/3v1n0/gnome-shell/-/commits/tray-offscreen-xwindows | 2024-05-01 |
| tray-icons/tray-na-tray-manager-Remove-outdated-comment-and-return-v.patch | tray/na-tray-manager: Remove outdated comment and return value | =?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | https://gitlab.gnome.org/3v1n0/gnome-shell/-/commits/tray-offscreen-xwindows | 2024-05-01 | |
| tray-icons/tray-na-xembed-Destroy-socket-window-when-ending-the-embe.patch | tray/na-xembed: Destroy socket window when ending the embedding Currently when embedding a tray icon is ended we are leaving the X11 socket window around as we don't really destroy it, while we're just listening for its child destruction. So, when embedding is ending we need to make sure that: - If the plug window is still alive, move it back to its old parent (normally that's the root window, but we query for it, to be sure) - If the plug window has been already destroyed or reparented (by us or by something else), we've to just destroy the socket window |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | yes | upstream | https://gitlab.gnome.org/3v1n0/gnome-shell/-/commits/tray-offscreen-xwindows | 2024-05-01 |
| tray-icons/tray-na-xembed-Use-proper-indentation-style-header.patch | tray/na-xembed: Use proper indentation style header | =?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | https://gitlab.gnome.org/3v1n0/gnome-shell/-/commits/tray-offscreen-xwindows | 2024-05-01 | |
| tray-icons/tray-na-xembed-Use-XShape-to-remove-input-on-socket-windo.patch | tray/na-xembed: Use XShape to remove input on socket window We don't want this window to take any input as, a part from blocking the events on the shell representation itself, they may potentially make the plugged window to do anything with the event is processing (such as showing tooltips). And we don't want this since we only want to send to those windows only the synthetic events that we explicitly control. This was already the case before of commit ab60902058 but a similar approach was not replicated, leading to input events being fully processed from tray icons plugs. It requires adding an explicit build dependency on Xext, but this is something that mutter already depends on so not really a new dependency |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | yes | upstream | https://gitlab.gnome.org/3v1n0/gnome-shell/-/commits/tray-offscreen-xwindows | 2024-05-01 |
| tray-icons/tray-Zero-initialize-the-event-structures-on-initializati.patch | tray: Zero-initialize the event structures on initialization | =?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | https://gitlab.gnome.org/3v1n0/gnome-shell/-/commits/tray-offscreen-xwindows | 2024-05-01 |
Showing 1 to 12 of 12 entries
All known versions for source package 'gnome-shell'
- 48.0-1 (trixie, sid)
- 43.9-0+deb12u2 (bookworm-security, bookworm)
- 3.38.6-1~deb11u2 (bullseye, bullseye-security)