From: gc-user <gc-user@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] libxfce4ui 4.18.4 - User name still / already typed-in after resume from standby
Date: Sat, 25 Nov 2023 10:35:20 +0100 [thread overview]
Message-ID: <20231125093520.TKId191c0k29LhRxrLeWEcBofv6mHtCUsBJIxErm22I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44551@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
Closed issue by gc-user on void-packages repository
https://github.com/void-linux/void-packages/issues/44551
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.34_1 x86_64
### Package(s) Affected
libxfce4ui-4.18.4
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
No.
### Expected behaviour
If
greeter-hide-users=true
in /etc/lightdm/lightdm.conf.d/50-lightdm.conf, the user name (short form) should have to be entered into a text box (instead of a drop down menu with all available user names (long form)) and that text box should be empty after boot or resume from standby.
### Actual behaviour
After updating libxfce4ui to v4.18.4 (and reboot), the user name (short form) is still / already typed into the text box after resume from standby.
### Steps to reproduce
1. Log in.
2. Go to standby
3. Resume
4. The user name is still / already typed into the text box for the user name.
"Fix":
1. Log in.
2. Downgrade libxfce4ui to v4.18.3
3. Reboot
4. Log in
5. Go to standby
6. Resume
7. The text box for the user name is empty - as it should be.
next prev parent reply other threads:[~2023-11-25 9:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 16:19 [ISSUE] " gc-user
2023-06-26 4:12 ` CabrioletDiskette
2023-06-26 14:38 ` gc-user
2023-06-27 7:42 ` CabrioletDiskette
2023-06-27 9:25 ` gc-user
2023-06-27 9:50 ` CabrioletDiskette
2023-06-27 9:51 ` CabrioletDiskette
2023-06-27 10:08 ` CabrioletDiskette
2023-06-27 20:03 ` gc-user
2023-06-28 2:41 ` CabrioletDiskette
2023-06-28 2:47 ` CabrioletDiskette
2023-06-28 2:48 ` CabrioletDiskette
2023-06-28 2:50 ` CabrioletDiskette
2023-06-28 15:03 ` gc-user
2023-06-28 15:21 ` gc-user
2023-06-28 16:00 ` gc-user
2023-06-28 16:01 ` gc-user
2023-06-28 16:26 ` gc-user
2023-06-28 23:55 ` CabrioletDiskette
2023-11-25 9:33 ` gc-user
2023-11-25 9:35 ` gc-user [this message]
2023-11-25 19:02 ` gc-user
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231125093520.TKId191c0k29LhRxrLeWEcBofv6mHtCUsBJIxErm22I@z \
--to=gc-user@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).