From ArchWiki

When do lightdm greeters block autologin in which cases and why?

Dikasetyaprayogi (talk) 00:37, 26 March 2021 (UTC): this is based on personal experince though, feel free to remove the article if it is not apporiate.

When? lightdm 1:1.30.0-4 + graphical-greeter, latest test with lightdm-gtk-greeter 1:2.0.8-1. Which case? installing lightdm along with graphical greeter made infinite blank screen on lightdm autologin attempt. Why? unfortunately i dont very skilled to throughfuly investigate the problem.

Hmm, this sounds like this can be a misconfiguration or similar. Got any links to relevant bug reports? Might help to check your logs first to get a relevant error message. -- NetSysFire (talk) 00:06, 26 March 2021 (UTC)
Dikasetyaprayogi (talk) 00:37, 26 March 2021 (UTC) [update] Thanks for your concern, found the cause is you need to set logind-check-graphical=true in /etc/lightdm/lightdm.conf otherwise the autologin fails and im throwed back into login screen or blank screen happens. Not sure if another user lightdm greeter worked out of the box but im add this to wiki in case if autologin with greeter fails. Sorry for all the trouble :) .

Tap to click using touchpad not working

The solution offered seems "unclean". I assume the person changes his input options by running "xinput" at the beginning of their session. That way they have to mirror the same behaviour twice. Once for their user X session and once for LightDM (the mentioned solution in the article). Using Xorg config files would be way cleaner and only require the option to be set in 1 place.

I don't know if this should be mentioned in the LightDM article or if the hacky solution should be removed?

Justasug (talk) 12:29, 14 May 2017 (UTC)

The solution Justasug mentions Special:Diff/472431/next has since been removed by the author Special:Diff/483300/next because "it was causing lightdm to lock up" (didn't try it, can't confirm).
I did a quick search and found the following suggestion using Xorg config files on Debian Wiki - Synaptics Touchpad. Creating the following configuration file for libinput and restarting lightdm (or just rebooting) works. Is this the "cleaner" solution? Lightdm runs as its own user - may be some user-specific configuration is better than this system wide change?
Section "InputClass"
        Identifier "libinput touchpad catchall"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
        Driver "libinput"
        Option "Tapping" "on"
Restart lightdm (caution - it is going to nuke your session) for changes to take effect or reboot:
systemctl restart lightdm

Is there a better, cleaner, per user (i.e. lightdm user) way of solving this?

Romstor (talk) 23:15, 23 August 2019 (UTC)

Cursor size in lightdm-gtk-greeter

The cursor size for the gtk-greeter is set by org.gnome.desktop.interface.cursor-size in root's dconf and gtk-cursor-theme-size= in /etc/gtk-3.0/settings.ini. To be sure, set both (one or the other tends to be ignored).

Note: It is not possible to change any value in root's dconf in Archlinux since the removal of x11 support from dbus. You must install dbus-x11AUR and use gsettings or dconf-editor as root.

quequotion (talk) 20:41, 18 October 2017 (UTC)

light-locker screen black

As noted by the accuracy flag added to the section 'Black screen on lid up with light-locker', the problem is most likely cuased by an upstream bug or is considered a 'missing feature', rather than a genuine bug. This problem is odd as light-locker, by defualt, is not built with upower support. This may imply that it is a problem with how light-locker runs alongside the firmware. I am currently replicating the bug to file a upstream bug report, as I did not have my system logs saved for it. Does anybody have any other information on this?

Bytecode (talk) 18:33, 4 January 2018 (UTC)

I can't seem to replicate the error...

Bytecode (talk) 18:52, 4 January 2018 (UTC)

Removed section due to irreproducability. I will undo this if I can reproduce it succsessfully.

Bytecode (talk) 19:00, 4 January 2018 (UTC)

Add Source .bashrc on login

I think it would be useful for others if they don't have .profile

ln -s ~/.bash_profile ~/.profile

--CatchMe (talk) 06:14, 22 June 2018 (UTC)

add XDMCP chooser to LightDM greeter.

the top of the article lists

  • Supports remote login (incoming - XDMCP, VNC, outgoing - XDMCP, pluggable).

but nowhere in the article it is explaind on how to do outgoing XDMCP.. i have search but did not find an answer anywhere.. Could someone please add the steps on how to add the XDMCP chooser to the LightDM greeter. or instructions on how to login to a remote xserver from LighDM greeter on the local machine. Fruitycake (talk) 13:56, 16 September 2018 (UTC)

lightdm-slick-greeter "preferred ... by distro creators"

In the description for lightdm-slick-greeter, it says, "preferred over the lightdm-gtk-greeter by distro creators". Anybody know which creators of which distribution prefer it over lightdm-gtk-greeter? I happen to think it's a pretty greeter, but this text seems dubious. Magotchi (talk) 14:20, 20 March 2019 (UTC)

Also, if it is "preferred" -- why it is still in AUR and not in the community or extra repositories? Romstor (talk) 00:16, 24 August 2019 (UTC)

Changing Your Avatar Section Unclear

This section gets a bit bunched-in with the sections about greeters. It's unclear reading if methods discussed here relate only to a specific greeter or to lightdm as a whole. It mentions that you should "change username" to your username but doesn't specify that this needs to be done for both commands listed below. It should be noted that the file may have been autocreated and that the entry for [icon] may already exist but should be altered to reflect the location and configuration specified. Lastly, the tip about KDE should be moved to the bottom so this doesn't appear KDE specific. TheChickenMan (talk) 15:28, 18 April 2019 (UTC)

lightdm-gtk-greeter is NOT the default greeter

Can someone find a better description and change it please. For me a fresh install has default #greeter-session=example-gtk-gnome. Without changing this lightdm will not boot successfully! --Joouutur (talk) 14:40, 26 February 2021 (UTC)

If you check the PKGBUILD file of the lightdm package you can see that the default greeter-session (i.d. if you don't change the configuration) is set to lightdm-gtk-greeter with the line --with-greeter-session=lightdm-gtk-greeter. So if you install lightdm-gtk-greeter you don't have to change /etc/lightdm/lightdm.conf and lightdm will work.
This is also explained by the comment: "lightdm-gtk-greeter: this is the default greeter LightDM attempts to use when started unless configured to do otherwise."
Lastly the # indicates that the line in /etc/lightdm/lightdm.conf is commented out, so it has no effect but serves only as an example.
--Stefan0xC (talk) 23:01, 26 February 2021 (UTC)
Sorry not sure why earlier the default config did not work for me. Can confirm indeed the default should work.
--Joouutur (talk) 00:40, 27 February 2021 (UTC)

Requires users accounts to be managed by homed

If you go with clean install, lightdm depends on `accountsservice`, and which depends on `homed`. If you created your users without this service (i.e. you don't have managed `~/.identity` - it won't work). Iamkarlson (talk) 20:41, 13 December 2022 (UTC)