From: CabrioletDiskette <CabrioletDiskette@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libxfce4ui 4.18.4 - User name still / already typed-in after resume from standby
Date: Tue, 27 Jun 2023 09:42:32 +0200 [thread overview]
Message-ID: <20230627074232.o2IgVxWTPS-oXUgW-c0rPupeo-MS_prLmfgex5B1FG4@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: 591 bytes --]
New comment by CabrioletDiskette on void-packages repository
https://github.com/void-linux/void-packages/issues/44551#issuecomment-1608966505
Comment:
I was unable to replicate the issue. However, my best bet is that you have a conflicting line in /etc/lightdm/lightdm.conf. I would delete that file and all the lightdm config files in /etc/lightdm and then reinstall lightdm and all the lightdm greeters. After that add the greeter-hide-users=true line to /etc/lightdm/lightdm.conf again. If you have a complex lightdm configuration just temporarily back it up. Let me know what happens.
next prev parent reply other threads:[~2023-06-27 7:42 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 [this message]
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 ` [ISSUE] [CLOSED] " gc-user
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=20230627074232.o2IgVxWTPS-oXUgW-c0rPupeo-MS_prLmfgex5B1FG4@z \
--to=cabrioletdiskette@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).