Package Details: lightdm-git 1.30.0.r9.g03f21898-1

Git Clone URL: https://aur.archlinux.org/lightdm-git.git (read-only, click to copy)
Package Base: lightdm-git
Description: A lightweight display manager
Upstream URL: https://launchpad.net/lightdm
Licenses: GPL3, LGPL3
Conflicts: lightdm
Provides: lightdm
Submitter: SolarAquarion
Maintainer: SolarAquarion
Last Packager: SolarAquarion
Votes: 280
Popularity: 0.000000
First Submitted: 2017-12-18 19:45 (UTC)
Last Updated: 2019-12-15 20:56 (UTC)

Required by (47)

Sources (9)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 40 Next › Last »

<deleted-account> commented on 2013-09-13 06:32 (UTC)

alucryd: it must have been cruft left over from previous installs in /var/cache/lightdm /var/lib/lightdm and /run/lightdm. After uninstalling both lightdm and the greeter, ensuring the user and group were gone and deleting the above directories, upon re-installing, my ttys work as expected. I have X on tty1 and consoles on ttys 2-7. This is with 1.7.15 The only issue that needs attention is the permissions on /var/lib/lightdm lightdm has it owned by root:root. It should be lightdm:lightdm as the gtk-greeter tries to write an .Xauthority file there as user lightdm. With root permissions on that directory, the greeter fails to start. Cheers.

alucryd commented on 2013-09-12 09:52 (UTC)

padfoot: Hmm, can you try reinstalling lightdm-devel from scratch? Boot into a tty (so the lightdm user is not used), uninstall lightdm, make sure that the lightdm user is gone and that /var/lib/lightdm is gone too, then reinstall lightdm-devel? The changes in 1.7.14 were regarding Xauthority perms. I see that 1.7.15 is out btw, I'll update the package.

<deleted-account> commented on 2013-09-12 09:09 (UTC)

Sorry for the delay. With the installing and uninstalling of various lightdm packages, the permissions on /var/lib/lightdm/.Xauthority got screwed preventing the greeter launching. Anyway, tried lightdm from community with both lightdm-gtk2-greeter and lightdm-gtk2-greeter-devel, tty1 was X and tty2-7 were consoles. Back to lightdm-devel and 1.7.14 displays the same issue. tty1-7 are all X. With 1.7.12, I had minimum-vt=7 set so did not have any issues. I no longer have that package to confirm if the issue appeared with 1.7.12 or the latest 1.7.14 Cheers.

alucryd commented on 2013-09-12 08:30 (UTC)

I built 1.7.14, all my ttys are working as expected.

alucryd commented on 2013-09-12 08:15 (UTC)

padfoot: Does it also happen with lightdm from [community]? What about 1.7.12? I thought I had updated mine to 1.7.14 but didn't, and 1.7.12 works fine here, as does 1.6.1 from [community].

<deleted-account> commented on 2013-09-12 08:11 (UTC)

Just been playing around a little more. When I set minimum-vt=4, i have consoles on tty1-3 and X on tty 4-7. So it would seem lightdm takes over all ttys from the configured minimum and above. Cheers.

<deleted-account> commented on 2013-09-12 07:52 (UTC)

alucryd, I have a laptop, desktop and netbook. All experience the same issue. With minimum-vt=1, CTRL ALT F1-F7 all display my X session only. With minimum-vt=7, CTRL ALT F1-F6 give me my consoles while CTRL ALT F7 gives my X session. So all my ttys are taken over by the X session with minimum-vt=1. Cheers.

alucryd commented on 2013-09-12 07:26 (UTC)

padfoot: What do you mean? Our GDM uses tty1, and Fedora has their LightDM set to tty1 too. I have no problem using it.

<deleted-account> commented on 2013-09-12 06:43 (UTC)

In /etc/lightdm/lightdm.conf, please change line 23 from: minimum-vt=1 to minimum-vt=7 otherwise we no longer have our consoles. Cheers.

alucryd commented on 2013-07-17 08:01 (UTC)

pouar: I have enforced the use of moc-qt4 and moc-qt5 instead of letting the detection code do the work. This should fix your issue.