Your message dated Mon, 26 Mar 2012 19:05:05 +0200
with message-id <[email protected]>
and subject line Closing, fixed in 2.3.1
has caused the Debian Bug report #659958,
regarding i3lock: fails to recognize Caps. Lock
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.)
--
659958: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659958
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: i3lock
Version: 2.2-1
Severity: important
Hi,
i3lock fails to recognize passwords typed using Caps. Lock.
My password contains uppercase letters, and when I lock my screen using
i3lock
(without any options), I can't use the Caps. Lock. key to type them. When I
do,
two error messages are printed (by i3lock, I guess) in the shell :
WARNING: unhandled event of type 19
WARNING: unhandled event of type 12
and so, the authentication is impossible :
Authentication failure
When I re-type my password using Shift for uppercase letters, it works :
successfully authenticated
It may be an X error, I don't know how to verify it.
Regards,
Damien
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages i3lock depends on:
ii libc6 2.13-26
ii libcairo2 1.10.2-6.2
ii libpam0g 1.1.3-7
ii libxcb-dpms0 1.8-2
ii libxcb-image0 0.3.8-1
ii libxcb-keysyms1 0.3.8-1
ii libxcb-shm0 1.8-2
ii libxcb1 1.8-2
i3lock recommends no packages.
i3lock suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Closing this bug since it is fixed in 2.3.1, which is in Debian.
--- End Message ---
