Your message dated Mon, 21 Apr 2025 14:30:11 -0400
with message-id
<cad+gyvywb1hs_90mxsrjyrojqay-mtd_5t0tnufyyhttpff...@mail.gmail.com>
and subject line closing old GNOME Shell bugs
has caused the Debian Bug report #925622,
regarding gnome-shell: Workspace numbering is wrong when doing "Switch to
Workspace" shortcuts
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
925622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell
Version: 3.32.0-1
Severity: important
Dear Maintainer,
I just upgraded to gnome-shell 3.32 and noticed the "Switch to Workspace X"
shortcuts
aren't working as expected. I normally have 5 static workspaces configured, and
use
shortcuts to move between them.
Previously, the workspaces were in order: 1, 2, 3, 4, 5
Now they seem to be in this order: 1, 4, 3, 2, 5
I assume something simple just got messed up in the 3.32 release since it
worked fine in 3.30
and in all previous releases.
-- Wayne Rowcliffe
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (700, 'testing'), (650, 'unstable'), (600, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gnome-shell depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2
ii evolution-data-server 3.30.5-1
ii gir1.2-accountsservice-1.0 0.6.45-2
ii gir1.2-atspi-2.0 2.30.0-7
ii gir1.2-freedesktop 1.58.3-2
ii gir1.2-gcr-3 3.28.1-1
ii gir1.2-gdesktopenums-3.0 3.32.0-1
ii gir1.2-gdm-1.0 3.30.2-3
ii gir1.2-geoclue-2.0 2.5.2-1
ii gir1.2-glib-2.0 1.58.3-2
ii gir1.2-gnomebluetooth-1.0 3.28.2-3
ii gir1.2-gnomedesktop-3.0 3.30.2.1-1
ii gir1.2-gtk-3.0 3.24.5-1
ii gir1.2-gweather-3.0 3.28.2-2
ii gir1.2-ibus-1.0 1.5.19-4
ii gir1.2-mutter-4 3.32.0-1
ii gir1.2-nm-1.0 1.14.6-2
ii gir1.2-nma-1.0 1.8.20-1
ii gir1.2-pango-1.0 1.42.4-6
ii gir1.2-polkit-1.0 0.105-25
ii gir1.2-rsvg-2.0 2.44.10-1
ii gir1.2-soup-2.4 2.64.2-2
ii gir1.2-upowerglib-1.0 0.99.10-1
ii gjs 1.54.3-1
ii gnome-backgrounds 3.30.0-1
ii gnome-settings-daemon 3.32.0-1
ii gnome-shell-common 3.32.0-1
ii gsettings-desktop-schemas 3.32.0-1
ii libatk-bridge2.0-0 2.30.0-5
ii libatk1.0-0 2.30.0-2
ii libc6 2.28-8
ii libcairo2 1.16.0-4
ii libcroco3 0.6.12-3
ii libecal-1.2-19 3.30.5-1
ii libedataserver-1.2-23 3.30.5-1
ii libgcr-base-3-1 3.28.1-1
ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii libgirepository-1.0-1 1.58.3-2
ii libgjs0g 1.54.3-1
ii libgles2 1.1.0-1
ii libglib2.0-0 2.58.3-1
ii libglib2.0-bin 2.58.3-1
ii libgstreamer1.0-0 1.14.4-1
ii libgtk-3-0 3.24.5-1
ii libical3 3.0.4-3
ii libmutter-4-0 3.32.0-1
ii libnm0 1.14.6-2
ii libpango-1.0-0 1.42.4-6
ii libpangocairo-1.0-0 1.42.4-6
ii libpolkit-agent-1-0 0.105-25
ii libpolkit-gobject-1-0 0.105-25
ii libpulse-mainloop-glib0 12.2-4
ii libpulse0 12.2-4
ii libsecret-1-0 0.18.7-1
ii libsystemd0 241-1
ii libx11-6 2:1.6.7-1
ii libxfixes3 1:5.0.3-1
ii mutter 3.32.0-1
ii python3 3.7.2-1
Versions of packages gnome-shell recommends:
pn bolt <none>
ii chrome-gnome-shell 10.1-5
ii gdm3 3.30.2-3
ii gkbd-capplet 3.26.1-1
ii gnome-control-center 1:3.30.3-1
ii gnome-user-docs 3.30.2-1
pn ibus <none>
pn iio-sensor-proxy <none>
pn switcheroo-control <none>
ii unzip 6.0-22
Versions of packages gnome-shell suggests:
ii gir1.2-telepathyglib-0.12 0.24.1-2
ii gir1.2-telepathylogger-0.2 0.8.2-3
-- no debconf information
--- End Message ---
--- Begin Message ---
There have been many changes to Debian since this bug was originally
reported. If you are still experiencing this issue with Debian 12 (or
with Testing or Unstable), please report a new bug.
Thank you,
Jeremy Bícha
--- End Message ---
