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: Wed, 28 Jun 2023 04:48:37 +0200 [thread overview]
Message-ID: <20230628024837.FP9sN1StOW-lEIX1-s0aHDgYXBFrGF8MwZOTcS2JZHM@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: 1048 bytes --]
New comment by CabrioletDiskette on void-packages repository
https://github.com/void-linux/void-packages/issues/44551#issuecomment-1610576121
Comment:
I have some news, maybe even good news. I was able to replicate your problem. Specifically if I put the greeter-hide-users tag above the [Seat*] header in the config file(any config file to be specific) the setting does not apply. Double check that you put greeter-hide-users under that specific tag in the .conf file. I would do it in the default one just for testings sake(it should not theoretically matter but just bear with me).
So your config should look like the one attached(see line 103)
[lightdm.conf.txt](https://github.com/void-linux/void-packages/files/11889151/lightdm.conf.txt)
d
If this does not work then I really got no more leads. If it does then perhaps some update has effected the way the tags in config files work(it makes little sense but I am running in fumes here). Also, as I can't replicate it I would remove the bug tag as it seems this is likely not a bug.
next prev parent reply other threads:[~2023-06-28 2:48 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 [this message]
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=20230628024837.FP9sN1StOW-lEIX1-s0aHDgYXBFrGF8MwZOTcS2JZHM@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).