Bug#989548: light-locker: Username field has focus when unlocking
> Did you maybe change something in the default lightdm configuration (like > having the userlist displayed?). No, the lightdm config is out of the box unmodifed. > Is accountsservice installed on your box? No. Should it be? -- Great music, chat and even some wit. Join me every Friday evening at 8pm for Keith's Music Box: https://www.mixcloud.com/live/KeithsMusicBox/ pgpjWvocY4TFG.pgp Description: OpenPGP digital signature
Bug#989548: light-locker: Username field has focus when unlocking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 [please keep the bug number on CC so exchanges are public, this is a bug report and not a support channel :)] On Tue, 2021-06-08 at 08:43 +0100, Keith Edmunds wrote: > I've just locked the screen and the dialog box appears with no username > populated. > > Even if your hypothesis were correct, why is the focus on the username > field? If the username is populated, the focus should be on the password > field. Here the behavior is as you say: the username is populated (and actually selected), but the focus in on the password field (and as I understand it, it's the behavior you had as well before the Bullseye upgrade). > > I can record a video of the behaviour I see if you want. I don't think that's really necessary, I trust you on this, I just don't know what happens on your box (which doesn't on mine). You might want to take a look at logs in /var/log/lightdm (and maybe .xsession-errors as well). Did you maybe change something in the default lightdm configuration (like having the userlist displayed?). Is accountsservice installed on your box? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmC/K2YACgkQ3rYcyPpX RFu2DAf/euW6Kyyn/noYc8KV5xZ+IVQ18xoqTuxvJF2/XY2T4N0N8r4DRccXmamP VSxHkyufIvHtD98OIvV5jz06MaTvRvIjp1HQ29EmfBu6HLHbgFG0sb8Dntdw6W5c g+OnN3ky2ILcyUVOxJtF1gJOL610lkwJwY5diYVJVe2OYWaIuv1ANsLoe3whYEaY xi/tBXJaDBffG+WiTFK3NOQhs6gvWJYJriHUbcN6f0ovY+W6OrCdrJ0CFrveu0hg 1BoI9k0p73KNIz+BqqPXP5KA3l4nXaBT50cmOslCpJUmBvqpG9NdzvKxRqdrfdEg l6P4KjvCE3E6Q/Gl6nfCzK5+6lBMYQ== =ysAi -END PGP SIGNATURE-
Bug#989548: light-locker: Username field has focus when unlocking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: tag -1 unreproducible moreinfo On Mon, 2021-06-07 at 09:55 +0100, Keith Edmunds wrote: New installation of Bullseye with XFCE and light-locker. When the screen is locked, the username is not populated and it also has focus. Previous versions of light-locker would fill in the username and put the focus on the password field. If one is used to the previous behaviour and starts typing the password, it appears in clear text in the username field. The username field should be populated with the logged-in user as that is by far the most likely user to be unlocking the system. Hi Keith, this is exactly the behavior I have here. I'm running a sid box, but it has the same light-locker version (and I'm assuming you also use lightdm-gtk- greeter, which also has the same version in both). Are you sure you're not entering a key or something which would erase the field content (since it's focused)? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmC/G18ACgkQ3rYcyPpX RFtEKgf/Wa7T62T0yhmpAv7d0AVNi+N8UuYOb9yPHc/yAW+CausLRjtu4THOJ3JZ Z/PEAe4t7AqnqHwWLp7313iq00BQv2sBwLCI5fEdlGWjqIgmblPY/MBxeCy9eFDY p0mK3TIp53z89E1G3Z5qmGqcmL9RAytG9GXGe3ArChumHVMB+W38PQ03Ni3Lp1L+ 3mDLDtoMxzZmxn2Ef+qRi4FqHmI5h7H46E9jz9+dFazuOl5TNd3sonz7FHORIXz8 aomJt+C3N3yPFpQD+fnS7BC8VDltPhAXPjg4mQ/2la0aoKNNRJIi0AUr0MW49OeR 700vq1WzbLzTaTqymfv1i6EJWP4zhg== =LbL7 -END PGP SIGNATURE-
Bug#989548: light-locker: Username field has focus when unlocking
Package: light-locker Version: 1.8.0-3 Severity: normal Dear Maintainer, New installation of Bullseye with XFCE and light-locker. When the screen is locked, the username is not populated and it also has focus. Previous versions of light-locker would fill in the username and put the focus on the password field. If one is used to the previous behaviour and starts typing the password, it appears in clear text in the username field. The username field should be populated with the logged-in user as that is by far the most likely user to be unlocking the system. -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages light-locker depends on: ii dconf-gsettings-backend [gsettings-backend] 0.38.0-2 ii libc62.31-12 ii libcairo21.16.0-5 ii libdbus-1-3 1.12.20-2 ii libdbus-glib-1-2 0.110-6 ii libglib2.0-0 2.66.8-1 ii libgtk-3-0 3.24.24-4 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libsystemd0 247.3-5 ii libx11-6 2:1.7.1-1 ii libxext6 2:1.3.3-1.1 ii libxss1 1:1.2.3-1 ii lightdm 1.26.0-7 light-locker recommends no packages. light-locker suggests no packages. -- no debconf information
