From: gc-user <gc-user@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 11:25:11 +0200 [thread overview]
Message-ID: <20230627092511.LwfocNcXzvIA8Ie5TkrhUX_nCeYV0Ob44w3hwbfin2o@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: 1463 bytes --]
New comment by gc-user on void-packages repository
https://github.com/void-linux/void-packages/issues/44551#issuecomment-1609124042
Comment:
I can replicate it every time, even if the conf file only contains that line and no other. Of course, the changes only get applied after reboot. And, of course, if this line is also removed, the bug can't be noticed as the user name list to choose from is displayed.
Also, I'm talking about
/etc/lightdm/lightdm.conf.d/50-lightdm.conf,
not
/etc/lightdm/lightdm.conf
The latter is the official / default file, the former is the one one can / should use for modifications.
But you wrote about lxdm. I couldn't determine if you tried to replicate the issue with lxdm being activated or not.
The bug seems to be happening between xfce4ui and one of the light* packages. Having lxdm installed might interfere with that and mask the bug.
Also, if that bug only appears after updating libxfce4ui to v4.18.4 and disappears after downgrading libxfce4ui to v4.18.3, why would uninstalling and reinstalling (the same versions of) lightdm / lightdm-gtk3-greeter have any effect?
Anyway, maybe one day, if there are no updates to the light* packages in the near future, or another future update to xfce4ui doesn't revert that bug, I might have to go and check the difference between the current and the previous version of xfce4ui to see if I maybe can detect something that could affect the login screen.
next prev parent reply other threads:[~2023-06-27 9:25 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 [this message]
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=20230627092511.LwfocNcXzvIA8Ie5TkrhUX_nCeYV0Ob44w3hwbfin2o@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).