Your message dated Sun, 9 Nov 2025 21:03:09 -0500
with message-id
<CAAajCMaQ4aUjtM4OA418LXsro+LK0Q2-77rVcR2Z3tyvj=4...@mail.gmail.com>
and subject line closing old gnome-settings-daemon bugs
has caused the Debian Bug report #662648,
regarding Cannot hold down modifier and hit several keyboard shortcuts after
one opens a window; must release modifier in between
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 [email protected]
immediately.)
--
662648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662648
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-settings-daemon
Version: 3.2.2-2
Severity: normal
I have several keyboard shortcuts set, all using Super as a modifier,
which I've mapped to Caps Lock using the following line in
~/.xsession:
xmodmap -e "remove lock = Caps_Lock" -e "keycode 66 = Super_L"
Among other things, I've mapped Super-N to create a new terminal, and
Super-M to maximize. I frequently chain these shortcuts without
releasing Super; for instance, Super-N-M creates a terminal and
maximizes it. This worked fine in GNOME 2. However, since upgrading to
GNOME 3, this no longer works if one of the shortcuts opens a window.
Thus, if I press Super, then N (creating a terminal window), then M,
the terminal does not maximize when I press M. If I release Super,
press it again, and then press M, it works.
This only seems to apply to a chain of keyboard shortcuts which includes
the opening of a windows. I can chain keyboard shortcuts which don't
open a window, such as Super-M-Right-Down (unmaximize, throw to right
edge, throw to bottom edge). Perhaps the opening of a window breaks
gnome-settings-daemon's focus or grab handling?
Also, this doesn't seem to apply if I use the existing Super key on the
keyboard; it only occurs when I use the Caps Lock key as Super with the
mapping above in place.
- Josh Triplett
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gnome-settings-daemon depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.10.0-3
ii dpkg 1.16.1.2
ii gsettings-desktop-schemas 3.2.0-2
ii libatk1.0-0 2.2.0-2
ii libc6 2.13-27
ii libcairo-gobject2 1.10.2-6.2
ii libcairo2 1.10.2-6.2
ii libcanberra-gtk3-0 0.28-3
ii libcanberra0 0.28-3
ii libcolord1 0.1.16-2
ii libcomerr2 1.42.1-2
ii libcups2 1.5.2-6
ii libdbus-1-3 1.4.18-1
ii libdbus-glib-1-2 0.98-1
ii libfontconfig1 2.8.0-3.1
ii libfreetype6 2.4.8-1
ii libgconf2-4 3.2.3-3
ii libgcrypt11 1.5.0-3
ii libgdk-pixbuf2.0-0 2.24.1-1
ii libglib2.0-0 2.30.2-6
ii libgnome-desktop-3-2 3.2.1-3
ii libgnome2-common 2.32.1-2
ii libgnomekbd7 3.2.0-1
ii libgnutls26 2.12.16-1
ii libgssapi-krb5-2 1.10+dfsg~beta1-2
ii libgtk-3-0 3.2.3-1
ii libgudev-1.0-0 175-3.1
ii libk5crypto3 1.10+dfsg~beta1-2
ii libkrb5-3 1.10+dfsg~beta1-2
ii liblcms2-2 2.2+git20110628-2
ii libnotify4 0.7.4-1
ii libpackagekit-glib2-14 0.7.3-1
ii libpango1.0-0 1.29.4-2
ii libpolkit-gobject-1-0 0.104-2
ii libpulse-mainloop-glib0 1.1-3
ii libpulse0 1.1-3
ii libsqlite3-0 3.7.10-1
ii libupower-glib1 0.9.15-2
ii libx11-6 2:1.4.4-4
ii libxfixes3 1:5.0-4
ii libxi6 2:1.4.5-1
ii libxklavier16 5.2.1-1
ii nautilus-data 3.2.1-2
ii zlib1g 1:1.2.6.dfsg-2
Versions of packages gnome-settings-daemon recommends:
ii hwdata <none>
ii pulseaudio 1.1-3
Versions of packages gnome-settings-daemon suggests:
ii gnome-screensaver 3.2.0-2+b1
ii metacity [x-window-manager] 1:2.34.1-2
ii x11-xserver-utils 7.6+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 13 (or
with Debian 12 or Testing or Unstable), please report a new bug.
Thank you,
Jeremy Bícha
--- End Message ---
