Your message dated Thu, 21 Aug 2025 00:26:44 -0400
with message-id
<caaajcmyb2fxwpwtognu-mhez2zeuc16lsxmf_eor-fkqypg...@mail.gmail.com>
and subject line Re: libgnomekbd7: after upgrade to gnome 3.4.2, all keyboard
shortcuts were lost
has caused the Debian Bug report #678031,
regarding libgnomekbd7: after upgrade to gnome 3.4.2, all keyboard shortcuts
were lost
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.)
--
678031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678031
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libgnomekbd7
Version: 3.4.0.2-1
Severity: important
Dear Maintainer,
(not sure this should be under gnome-shell instead)
after updating the system in two machines (using testing), all the keyboard
shortcuts were lost (including custom defined).
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.5.0-rc2+ (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libgnomekbd7 depends on:
ii iso-codes 3.36-1
ii libatk1.0-0 2.4.0-2
ii libc6 2.13-33
ii libcairo-gobject2 1.12.2-1
ii libcairo2 1.12.2-1
ii libfontconfig1 2.9.0-6
ii libfreetype6 2.4.9-1
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.32.3-1
ii libgnomekbd-common 3.4.0.2-1
ii libgtk-3-0 3.4.2-1
ii libpango1.0-0 1.30.0-1
ii libx11-6 2:1.4.99.901-2
ii libxklavier16 5.2.1-1
libgnomekbd7 recommends no packages.
libgnomekbd7 suggests no packages.
-- 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 ---
