From ArchWiki
Latest comment: 16 June 2023 by Emerald in topic Fish environment variables

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)Reply[reply]

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)Reply[reply]

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)Reply[reply]

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)Reply[reply]

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)Reply[reply]

Improving the greeter list

Currently the list in LightDM#Greeter is split between greeters in the official repos and those in AUR. I think it would be more useful to instead split it into actively developed greeters and dead ones.

For example, looking at LightDM#Greeter may give one the impression that using lightdm-webkit2-greeter is a good idea, but that project's git repo was last updated in 2018 and is now archived. IMO it's very easy to miss this.

-- nl6720 (talk) 15:10, 4 May 2023 (UTC)Reply[reply]

Fish environment variables

It might be useful to add an example for fish in the section on environment variables. Fish handles environment variables differently than other shells, so it took me a while to figure out how to make it work. There is probably a better way, but this is what I did:

export PATH="$PATH":$(fish -c "string join ':' \$fish_user_paths")

--Emerald (talk) 21:54, 16 June 2023 (UTC)Reply[reply]