Debian Patches
Status for gnome-shell/49.3-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| libgvc/mixer-control-Always-sync-devices.patch | mixer-control: Always sync devices This ensures any changes ports get updated, otherwise we'll fail to match the updated port. |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-control-Reset-stream-id-s-on-UI-devices.patch | mixer-control: Reset `stream-id`s on UI devices If we find a matching UI device for a stream matching card and port and the same stream is also on another port, reset that UI devices `stream-id`. Since wireplumber 1.5.84 will merely flip the port but not the `stream-id` we need to make sure the UI device loses its stream-id. Otherwise `gvc_mixer_control_change_output` will try a `gvc_mixer_stream_change_port` which seemingly succeeds but fails silently as the port doesn't exist on that stream at the moment. By resetting the `stream-id` we ensure that we take the `gvc_mixer_control_change_profile_on_selected_device` code path in `gvc_mixer_control_change_output` instead and thus the sink/port gets properly selected. |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-control-Fix-typos-and-remove-trailing-whitespace.patch | mixer-control: Fix typos and remove trailing whitespace | Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| Revert-main-Register-session-with-GDM-on-startup.patch | Revert "main: Register session with GDM on startup" This depends on GDM changes that are not in this release. This reverts commit 6457a1454a05bac8f7e172c17fbcb2b5baeae619. |
Joan Torres Lopez <joantolo@redhat.com> | yes | debian upstream | upstream, 49.4, commit:ba60daead6a54ec02ed5aa2841e72cd5acb591cb | 2026-01-27 |
| libgvc/mixer-control-Use-automatic-cleanup-in-match_stream_with_.patch | mixer-control: Use automatic cleanup in match_stream_with_devices Simplifies the loop |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-control-Print-port-names-with-profiles.patch | mixer-control: Print port names with profiles Other debug code uses port names instead of the description so this simplifies debugging. |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-control-Print-error-when-we-fail-to-update-source-o.patch | mixer-control: Print error when we fail to update source or sink port Since we allow for port lookups to fail we should check if the update worked. |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-control-Print-error-when-we-fail-to-set-default-sou.patch | mixer-control: Print error when we fail to set default source Makes is consistent with error handling for setting default sink |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-control-Use-consistent-debug-prefix.patch | mixer-control: Use consistent debug prefix The debug statements all used different prefixes making it harder than needed to grep for them |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-control-Don-t-lie-about-found-devices.patch | mixer-control: Don't lie about found devices We should only print that a device wasn't found when it is actually the case. |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-control-Don-t-emit-output-update-on-default-sink-se.patch | mixer-control: Don't emit output-update on default-sink set Don't emit the signal when setting. It will be emitted when the sink actually changes. This makes things consistent with switching the default source. |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-stream-Allow-ports-to-not-exist.patch | mixer-stream: Allow ports to not exist With pipewire 1.5.84 the port list might change underneath us, see https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/5053 We thus can't assume anymore that we find a given port. |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-stream-Allow-to-update-port-list.patch | mixer-stream: Allow to update port list | Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-control-Always-update-port-list.patch | mixer-control: Always update port list It can change underneath us, see https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/5053 |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-control-Let-sink-update-handle-active-output-change.patch | mixer-control: Let sink update handle active output change A signal is emitted when the output changes so don't set it right away as the stream might change port. |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-control-Let-source-update-handle-active-output-chan.patch | mixer-control: Let source update handle active output change A signal is emitted when the output changes so don't set it right away as the stream might change port. This also brings set_default_source in line with set_default_sink() |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-control-Clear-stream-ids-from-UI-devices-when-BT-st.patch | mixer-control: Clear stream-ids from UI devices when BT stream loses all ports Bluetooth streams can become portless so we can't just unconditionally add a new UI device for devices without streams. Instead reset stream-ids from existing streams that reference the stream that just became portless. |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-control-Check-for-invalid-input.patch | mixer-control: Check for invalid input With pipewire 1.5.84 there can be a zombie default-source as the current profile can't have a stream, see https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/5053#note_3256202 |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-04 |
| libgvc/mixer-control-Simplify-device-lookup.patch | mixer-control: Simplify device lookup There were too branches, one for portless streams (called "network streams" here) and those with ports. The portless one checked the stream-id only while the other branch checked stream-id and port. Simplify this by checking the stream-id and only comparing ports when available. As other streams can be portless nowadays this also removes some confusion. Best reviewed with 'git show -w' |
Guido Günther <agx@sigxcpu.org> | yes | debian upstream | https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31 | 2026-01-05 |
| 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 | |
| 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 | ||
| debian/data-Add-im-config.desktop-to-System-folder.patch | data: Add im-config.desktop to System folder Debian installs this by default, but most users will only need to run it once, or perhaps not at all. |
Simon McVittie <smcv@debian.org> | not-needed | 2025-06-10 |
All known versions for source package 'gnome-shell'
- 49.3-2 (forky, sid)
- 48.7-0+deb13u1 (trixie)
- 43.9-0+deb12u2 (bookworm-security, bookworm)