Your message dated Thu, 20 Feb 2025 15:33:17 +0100 (CET)
with message-id <20250220143317.7b199be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1043558,
regarding keyboard doesn't respond after waking up
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.)
--
1043558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-6.1.0-11-amd64
Version: 6.1.38-4
Control: affects -1 src:linux linux gnome
After a stationary PC suspended itself due to inactivity and then woke
up from suspend (on mouse or key press – I can't recollect), the
keyboard was not responsive. It had power: the LED 🄵 was lit.
Pressing the keys (I tried several keys, including 🄵Umsch and NumLock)
had no visible effect whatsoever. After physically unplugging and
plugging in the keyboard cable again to the same place, the keyboard
starting working.
The keyboard has “Microsoft® Natural® Ergonomic Keyboard 4000 v1.0” and
“Model: 1048” written on its bottom, has a German layout, and is
connected to the PC via a cable ending with a USB-A plug.
As opposed to the keyboard, the mouse, which was plugged into the
neighbor USB-A port, was working normally.
The error happens only seldom (every couple of weeks or even months)
after suspend due to inactivity followed by getting awake; much more
often, the keyboard works normally. A simple test consisting of putting
the PC to sleep manually followed by awakening it did not cause the
error to reoccur.
Gratefully,
Alma
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a very old kernel or the bug is old itself
without resolution.
If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from backports
please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Regards,
Salvatore
--- End Message ---
