Your message dated Mon, 10 May 2021 08:29:46 +0200
with message-id <[email protected]>
and subject line Re: Bug#987945: physlock: Locking does not seem to use current
configured keyboard ("dpkg-reconfigure keyboard-configuration")
has caused the Debian Bug report #987945,
regarding physlock: Locking does not seem to use current configured keyboard
("dpkg-reconfigure keyboard-configuration")
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.)
--
987945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987945
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: physlock
Version: 13-1+b1
Severity: important
Dear Maintainer,
I've a Laptop with printed DE keys layout, but is configured (dpkg-reconfigure
keyboard-configuration) to use US
international layout. Attached to the laptop is an external keyboard with
printed US keys layout. After physlocking,
the programm uses the DE keyslayout (to reproduce change to a password using
different keys on different layouts,
or to avoid having that problem change the password to use common keys on
differeny layouts).
Thanks in advance,
xiscu
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (900, 'testing'), (10, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages physlock depends on:
ii libc6 2.31-11
ii libpam0g 1.4.0-7
ii libsystemd0 247.3-5
physlock recommends no packages.
physlock suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
* xiscu [Sun May 09, 2021 at 09:47:13PM +0200]:
> I'm currently not able to reproduce the behaviour (hat some updates in
> between and dpkg-reconfigured
> again), anyway the context is: X.org, i3, /usr/bin/physlock -sdm, (just using
> the same KB as on the
> first message). Disconecting/connecting the external KB doesn't seems to
> trigger the issue either.
> Please feel free to close the issue, if somehow happens again I'll try harder
> trying to reproduce.
I see, I'll keep an eye on it and will follow up if I should be able
to reproduce this.
Thanks for your report, closing hereby.
Feel free to reopen if you (or anyone else) should be able to
reproduce it.
regards
-mika-
signature.asc
Description: Digital signature
--- End Message ---
