Package Base Details: lightdm-devel

Git Clone URL: https://aur.archlinux.org/lightdm-devel.git (read-only)
Submitter: alucryd
Maintainer: alucryd
Last Packager: alucryd
Votes: 286
Popularity: 0.226144
First Submitted: 2013-03-14 11:18
Last Updated: 2015-06-08 09:10

Latest Comments

alucryd commented on 2014-06-13 23:47

Indeed, sorry about that, I shouldn't blind update packages.

padfoot commented on 2014-06-13 22:00

Need to update the patch file lightdm-default-config.patch

Line 40:
[User Accounts]
Change to:
[User List]

and update package sums for this to build correctly.

alucryd commented on 2014-01-14 08:35

padfoot: Bumped, ths for the heads up.

padfoot commented on 2014-01-14 07:23

Lightdm fails with the xorg-server-1.15.0 unless you rebuild.

Please bump package to 1.9.5-2 to force a rebuild against the new xorg.

alucryd commented on 2013-09-13 08:29

padfoot: I just fixed those perms here and in [community], for some reason mine had the right perms. I was setting them in the install file, I must have forgotten to put them back in there while transferring the line in the PKGBUILD (which was an epic fail because I used chown lightdm:lightdm instead of chown 620:620, the latter works even if the user and group do not exist).

padfoot commented on 2013-09-13 06:32

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

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.

padfoot commented on 2013-09-12 09:09

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

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

alucryd commented on 2013-09-12 08:15

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].

padfoot commented on 2013-09-12 08:11

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.

padfoot commented on 2013-09-12 07:52

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

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

padfoot commented on 2013-09-12 06:43

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

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.

alucryd commented on 2013-07-17 07:54

pouar: Hmm, I couldn't reproduce the error, however I have improved the moc detection, can you test now?

padfoot commented on 2013-07-17 06:54

@ pouar

Looks like an update to qt is no longer compatible with this package.

If you are not using the qt greeter, you can safely disable the building of the liblightdm-qt4/5 libraries in the PKGBUILD.

Otherwise, someone would need to look at updating/patching the package to work with the updated qt.

Cheers.

pouar commented on 2013-07-17 01:44

I get this error while building
http://pastebin.com/rsnsmZJZ

alucryd commented on 2013-05-13 17:46

I know, I'm the one who did it :) I'll update lightdm-devel and lightdm-bzr later.

devrs0 commented on 2013-05-13 17:21

The lightdm binary has been moved from /usr/sbin to /usr/bin in the community package.

alucryd commented on 2013-05-08 09:02

padfoot: Thx, package adopted and updated.

alucryd commented on 2013-05-08 08:59

padfoot: I've got a working PKGBUILD here https://github.com/Alucryd/aur-alucryd/blob/master/personal/lightdm-devel/PKGBUILD
I can take over if you wish.

padfoot commented on 2013-05-08 08:50

Alucryd, thanks for that.

Disowning so you can pick up the package.

Might just want to bump your pkgrel to 2.

Cheers.

alucryd commented on 2013-05-08 08:44

padfoot: I've got a working PKGBUILD here https://github.com/Alucryd/aur-alucryd/blob/master/personal/lightdm-devel/PKGBUILD
I can take over if you wish.

padfoot commented on 2013-05-08 08:23

I picked up ownership of this package to update it to v 1.7.0.

I have disabled building liblightdm-qt5 as I am getting a make error, which I am unsure how to fix (even though qt5-base is installed, it is not being found when building liblightdm-qt5).

All the qt5 options are still in the PKGBUILD, just commented out. Just uncomment them and remove the --disable-liblightdm-qt5 option from the build line to re-enable qt5.

If anyone can advise of the appropriate fix for this, let me know.

Again, I only picked up this package to update it to v 1.7.0. If anyone else is interested in taking over maintainership, let me know and I will orphan the package.

Cheers.

padfoot commented on 2013-05-08 08:18

Overview of changes in lightdm 1.7.0

* Use logind instead of ConsoleKit if it is available
* Use Q_SLOTS and Q_SIGNALS instead of slots and signals.
* Ignore stale X server locks
* Pass through system locale or set locale from AccountsService/.dmrc
* Fix bug where seat failure before D-Bus acquired would not stop daemon

Anonymous comment on 2013-04-09 09:47

Oks, I´ll do it like that, because I use xfce, and with the lightdm from the official repo I don´t need qt or anything special to make shutdown as a user.

Thanks!.

applebloom commented on 2013-04-05 21:32

mardomo: I'm not sure if this is 100% accurate, but this package depends on qt because it builds and installs a library providing functions like shutdown (which connects to dbus interfaces using either gdk or Qt), which Qt-based greeters use. You can edit the PKGBUILD to not install this, if you want.

Thanks for fixing the patch.

Anonymous comment on 2013-04-04 21:21

If this it's the development package, and needs Qt5, it doe it means that lightdm will need qt in the future?

logos commented on 2013-04-02 12:43

OK, thanks for the answer! ;)

applebloom commented on 2013-03-27 04:33

logos: this is because this package is installing liblightdm-qt5-devel. You could install qt5, install this, then remove liblightdm-qt5-devel and qt5.

logos commented on 2013-03-25 16:41

Why is qt5-base a dependencie? I use lightdm-gtk3-greeter and I don't want to install qt libraries. I thought that lightdm was independant from gtk/qt libraries and then yo could choose the greeter that best fits to you.

logos commented on 2013-03-25 14:39

Why is qt5-base a dependencie? I use lightdm-gtk3-greeter and I don't want to install qt libraries. I thought that lightdm was independant from gtk/qt libraries and then yo could choose the greeter that best fits to you.

applebloom commented on 2013-03-23 20:12

I found a fix. The shutdown/reboot buttons don't appear because when the greeter executes lightdm_get_can_restart/lightdm_get_can_shutdown, it gets false, though it should get true (I've checked with the dbus interface).
And this happens, because the patch that adds support for org.freedesktop.login1 (lightdm-1.5.1-systemd_login1_power.patch) has a bug. The line:
g_variant_get (result, "(b)", str_result);
should look like this I think:
g_variant_get (result, "(s)", &str_result);
With this change the function returns true now, and options for shutdown and reboot appear. Also, Gdk errors associated with this line disappear from logs.

I'm not sure if this is a proper fix. According to http://www.freedesktop.org/wiki/Software/systemd/logind the functions should return a string. "s" was causing an error, and "(s)" worked.

alucryd commented on 2013-03-23 12:49

applebloom: I noticed that too, haven't had time to look into it yet though. I'll try what dgbaley27 posted and report back here asap.
Morfeo: I've moved lightdm's home to /var/lib/lightdm in the [community] package, you might want to do the same too^^ BTW, your maintainer line is wrong, it should be spelled Maintainer, with an i, please run namcap on your PKGBUILD to notice these kind of errors.

alucryd commented on 2013-03-23 12:47

applebloom: I noticed that too, haven't had time to look into it yet though. I'll try what dgbaley27 posted and report back here asap.
Morfeo: I've moved lightdm's home to /var/lib/lightdm in the [community] package, you might want to do the same too^^

applebloom commented on 2013-03-23 11:37

I had shutdown and reboot entries in the menu. Then yesterday, I made an update and got the lightdm from community. Since then, I only have hibernate and suspend. I tried installing this package, but it didn't fix the issue. I tried what dgbaley27 suggested, but it didn't help either.
What could I do to fix this, or at least, how can I debug it?

alucryd commented on 2013-03-16 08:28

Morfeo: I made a mistake when I last updated lightdm-autologin, please find a working version here: http://dl.dropbox.com/u/43076209/lightdm-autologin.pam
Also, I've made enabling the autologin feature easier, while retaining some security. I didn't want any user with an uid >= 1000 to be able to enable this, I preferred the solution mentioned on the wiki. Now, users just have to add themselves to the autologin group, and of course modify lightdm.conf. Please find an updated default config patch here: http://dl.dropbox.com/u/43076209/lightdm-default-config.patch
I've also updated the wiki accordingly, and lightdm in [community] already contains these changes.

alucryd commented on 2013-03-14 17:39

I know, but I'd have created this package when 1.7 would be released anyway, so I figured I might as well create it now.

dgbaley27 commented on 2013-03-14 17:11

Another possibility is leaving 1.5 in [community] then start the every-other cadence with 1.6, 1.8, ...

alucryd commented on 2013-03-14 16:21

dgbaley27: Yes lightdm 1.5.1 works fine, and that is the version I pushed in the first place. But a fellow TU urged me to push the stable version instead.
I realize wine is the devel release, but apparently a lot of linux distros are packaging this one, it appears to be the one exception. Besides, Lightdm is at 1.4 in every distro (except Fedora Rawhide). Still I'll take it to the other TUs and see what they think.

dgbaley27 commented on 2013-03-14 16:10

Alucryd,

It's not necessarily a bad thing to package the odd-numbered releases in [community]. Look at how we handle wine, even-numbered releases are stable, but we're all fine with the "preview" releases.

alucryd commented on 2013-03-14 11:53

Morfeo: I've pushed lightdm 1.4.0 in [community], as it is the latest stable release. To avoid conlicts, I've uploaded lightdm-devel in AUR and will merge this package into it. Please ping me if you want to reclaim ownership of the package, and I'll disown it for you to adopt.

alucryd commented on 2013-03-13 09:17

Morfeo: The package is in [community]. Just a quick question before I delete this one, is dbus-glib really needed? It builds and appears to run fine without, and namcap isn't complaining at all (also I checked packages from other distros, none has added dbus-glib in the deps).

alucryd commented on 2013-03-12 15:40

Morfeo: If that's okay with you, I will be transferring lightdm to [community], I hope to be able to do this this evening.

mrbit commented on 2013-03-11 11:19

no compila with qt5..??

power_moc5.cpp:14:2: error: #error "This file was generated using the moc from 4.8.4. It"
power_moc5.cpp:15:2: error: #error "cannot be used with the include files from this version of Qt."
power_moc5.cpp:16:2: error: #error "(The moc has changed too much.)"
In file included from greeter.cpp:256:0:
greeter_moc5.cpp:14:2: error: #error "This file was generated using the moc from 4.8.4. It"
greeter_moc5.cpp:15:2: error: #error "cannot be used with the include files from this version of Qt."
greeter_moc5.cpp:16:2: error: #error "(The moc has changed too much.)"
power_moc5.cpp:71:7: error: 'QMetaObjectExtraData' does not name a type
power_moc5.cpp:77:47: error: 'staticMetaObjectExtraData' was not declared in this scope
power_moc5.cpp: In member function 'virtual const QMetaObject* QLightDM::PowerInterface::metaObject() const':
power_moc5.cpp:86:71: error: conditional expression between distinct pointer types 'QDynamicMetaObjectData*' and 'const QMetaObject*' lacks a cast
make[3]: *** [liblightdm_qt5_2_la-power.lo] Errore 1

swiftgeek commented on 2013-03-01 04:32

In case of sticking to tmpfiles, one addition is needed for gtk3
f /run/lightdm/.pam_environment 0644 lightdm lightdm - GDK_CORE_DEVICE_EVENTS=true

This will fix gdk's wrong behavior when setting mouse cursor.

surlykke commented on 2013-02-23 19:12

I think it would be better if lightdm's home directory was /var/lib/lightdm rather than /var/run/lightdm.
lightdm-gtk-greeter writes last user to the file ~lightdm/.cache/lightdm-gtk-greeter/state so that it can default to that user at next login. When ~lightdm is /var/run/lightdm this doesn't work across reboots.
I'm currently working to add similar functionality to razor-lightdm-greeter upstream.

br. Christian Surlykke

pepedopolous commented on 2013-02-22 22:30

Hi,

On KDE I still don't have shutdown or restart options even though I added the extra lines to /etc/pam.d/lightdm-greeter


dgbaley27 commented on 2013-02-13 10:28

In case anyone doesn't have suspend, reboot, shutdown working from the greeter, if you add to /etc/pam.d/lightdm-greeter:

session required pam_loginuid.so
session required pam_systemd.so class=greeter

you should get them.

Anonymous comment on 2013-02-11 17:38

I found some errors in the patch and corrected them. Now the Shutdown and Reboot options appear in the menu! The corrected version follows (notice that I named it like Fedora):

https://www.dropbox.com/s/0sgchuk21ke1stt/lightdm-1.5.0-systemd_login1_power.patch

scar commented on 2013-02-04 16:23

Me neither, I do not have the suspend/reboot options.
Do these options need consolekit?
I've found this in /var/log/lightdm/x-0-greeter.log:

/var/log/lightdm/x-0-greeter.log

** (process:1164): WARNING **: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files

I don't know, if it is helpful, I've just started to use lightdm

electric_indigo commented on 2013-02-03 17:38

@padfoot: install consolekit-git from AUR

shosca commented on 2013-02-01 15:19

Updated to 1.5:

https://www.dropbox.com/s/iz9yq778gzq5rpt/lightdm.tar.gz

padfoot commented on 2013-01-27 22:37

I now have suspend and hibernate in my lightdm power menu, but I still do not have reboot or shutdown.

shosca commented on 2013-01-27 14:48

Updated using two patches from fedora package that drops consolekit for systemd and added polkit rules file to enable restart/shutdown/suspend.

https://www.dropbox.com/s/iz9yq778gzq5rpt/lightdm.tar.gz

Anonymous comment on 2013-01-20 12:24

@mezcal,
See this bugI submitted in launchpad. https://bugs.launchpad.net/lightdm/+bug/1069218
There is an easy fix; rename [UserAccounts] to [UserList] in users.conf.

mezcal commented on 2012-12-29 09:16

lightdm ignores settings in the file user.conf. minimum-uid is default value 500. User lightdm(uid=620) is visible in the user list. I have not AccountsService installed.

padfoot commented on 2012-12-15 21:10

I have tried the fedora patch, everything seems to build ok yet I still have no power options, and journalctl still reports consolekit errors.

dgbaley27 commented on 2012-12-11 18:59

Awesome, are they done using bzr? It has prevented me from contributing in the past

n00b commented on 2012-12-11 08:54

did someone try to use the patch from the fedora guys for logind support?
those patch http://pkgs.fedoraproject.org/cgit/lightdm.git/tree/

dgbaley27 commented on 2012-12-09 21:51

Can you post your /etc/pam.d/lightdm* files

Also, what failed? Creating the lightdm user or running lightdm after you created the user?

marmotz commented on 2012-12-09 21:49

Lightdm won't launch:

/var/log/lightdm/lightdm.log:
...
[+0.47s] DEBUG: Started session 685 with service 'lightdm-greeter', username 'lightdm'
[+0.48s] DEBUG: Session 685 authentication complete with return value 10: User not known to the underlying authentication module
[+0.48s] DEBUG: Greeter failed authentication
[+0.48s] DEBUG: Greeter failed to start
[+0.48s] DEBUG: Stopping display
...

If I replace "lightdm" by my username in /etc/lightdm/lightdm.conf, it works:

...
[LightDM]
#start-default-seat=true
greeter-user=myusername
...

But in my opinion, it's not the good solution.

I tried to create lightdm user and group, but that failed...

gdamjan commented on 2012-11-27 17:33

Does lightdm depend on ConsoleKit? Since CK has been deprecated in Arch I've removed it, but now lightdm doesn't show the list of users in the gtk-greeter.

I also have these errors in the logs:
from /var/log/lightdm/x-0-greeter.log
** (process:347): WARNING **: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files

from /var/log/lightdm/lightdm.log
[+7.36s] WARNING: Could not call FindUserByName: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.9 was not provided by any .service files

dgbaley27 commented on 2012-11-22 16:41

@Morfeo,

Can you maybe confirm here before you make changes rather than just (mis)interpreting the comments? I'm not sure why you moved away from using system-local-login, but you still need the auth sections for gnome-keyring

#%PAM-1.0
auth requisite pam_nologin.so
auth required pam_env.so
auth required pam_unix.so
-auth optional pam_gnome_keyring.so
account required pam_unix.so
session required pam_limits.so
session required pam_unix.so
password required pam_unix.so
-session optional pam_loginuid.so
-session optional pam_systemd.so
-session optional pam_gnome_keyring.so auto_start

Anonymous comment on 2012-11-20 15:00

I can confirm that adding
-session optional pam_gnome_keyring.so auto_start
as dgbaley27 suggested fixes the problem where the keyring doesn't get unlocked at login.

Thaodan commented on 2012-11-16 16:20

'lightdm-kde: Qt lightdm greeter' in $optdepends is wrong: lightdm-qt is the qt greeter.

Anonymous comment on 2012-11-14 21:39

ok sorry, just since now my keyring doesn't get unlocked at login, I thought that was the case...

dgbaley27 commented on 2012-11-14 21:30

On top of that, I'm pretty sure you need

-session optional pam_gnome_keyring.so auto_start

for the gnome_keyring module to be useful.

hermes14 commented on 2012-11-14 12:47

@9souldier
I think the ` is just a typo.
The '-' character is not a syntax error, it means errors won't be logged, and it's especially useful when the module is not present. pam_loginuid should be without the dash, I agree; I don't know if arch can still work without systemd, which would lead me to leave the dash in front of pam_systemd. If you look at /etc/pam.d/system-login, you'll notice the line
-session optional pam_systemd.so

flan_suse commented on 2012-11-14 12:39

@9souldier

That might explain my earlier comment below that reads:

"With the latest updates, after I login, NetworkManager asks me to unlock the Default keyring. If I log out and log back in, it always asks me to unlock the keyring..."

Anonymous comment on 2012-11-14 12:23

this file is broken, there are three extra characters:
first is the "`" character in line
auth optional pam_gnome_keyring.so`
next are the two "-" characters in the last two lines.
I wouldn't trust a pam file coming from a person who doesn't even know the syntax of these files, since pam *is* the authentication mechanism.

gtmanfred commented on 2012-11-12 17:55

http://ix.io/3nA

if you use this as your pamfile, it will allow for audited systemd sessions, but wont require you to use systemd

Anonymous comment on 2012-11-09 09:10

I had it working with a fresh Arch i6i6 install using cygwin X. When I changed from dhcp to static ip, it stopped working. This is the error I get:

Nov 09 11:00:39 archdev.holisticode.net lightdm[607]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Nov 09 11:00:39 archdev.holisticode.net kernel: lightdm-gtk-gre[609]: segfault at 3fee4303 ip b741ff9a sp bffb2190 error 4 in libgtk-3.so.0.600.1[b72c3000+4e0000]
Nov 09 11:00:39 archdev.holisticode.net lightdm[607]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Nov 09 11:00:39 archdev.holisticode.net lightdm[261]: (lightdm:261): GLib-GObject-WARNING **: invalid (NULL) pointer instance
Nov 09 11:00:39 archdev.holisticode.net lightdm[261]: (lightdm:261): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTA
Nov 09 11:00:39 archdev.holisticode.net lightdm[261]: (lightdm:261): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

flan_suse commented on 2012-11-08 02:58

With the latest updates, after I login, NetworkManager asks me to unlock the Default keyring. If I log out and log back in, it always asks me to unlock the keyring...

test0 commented on 2012-11-06 13:22

https://bugs.launchpad.net/lightdm/+bug/930488
Also see discussion there: https://aur.archlinux.org/packages/lightdm-gtk-greeter/

andreyv commented on 2012-11-06 07:22

This started after ConsoleKit was replaced with logind.

test0 commented on 2012-11-06 01:04

No shutdown/reboot/hibernate icons in upper-right corner button menu: the drop-down menu is just blank. How can I solve this?
Just moving to systemd, tried to recompile lightdm, but no luck.

Foucault commented on 2012-10-31 18:18

After the last update I can't seem to be able to login via lightdm. X Server dies with
Fatal server error:
no screens found
(EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

I am using a custom session in /usr/share/xsessions called Xinitrc that just calls startx. My .xinitrc contains

xrdb -merge ~/.Xdefaults
urxvtd -q -o -f &
exec dbus-launch --auto-syntax --exit-with-session startxfce4

After checking Xorg.1.log I get the following weird error
(EE) NVIDIA(GPU-0): EVO Push buffer channel allocation failed
(EE) *** Aborting ***
(EE) NVIDIA(GPU-0): Failed to allocate EVO core DMA push buffer
(EE) *** Aborting ***

Googling around a bit I found that this is connected to multiseat configurations with multiple gpus. The problem is I only have a single GPU and this only happens with lightdm not manual startx. Has anyone experienced anything similar?

Foucault commented on 2012-10-31 17:28

After the last update I can't seem to be able to login via lightdm. X Server dies with
Fatal server error:
no screens found
(EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Switching to a VT and launching startx seems to work OK. Xorg.X.log does not seem to provide any relevant information. I am using a custom session in /usr/share/xsessions called Xinitrc that just calls startx. My .xinitrc contains

xrdb -merge ~/.Xdefaults
urxvtd -q -o -f &
exec dbus-launch --auto-syntax --exit-with-session startxfce4

Jristz commented on 2012-10-31 11:56

I need rebuild this ackage now, because consolekit is deprecated, I'm right???

dgbaley27 commented on 2012-10-30 19:59

Does anyone else notice this taking a long time to stop with systemd? I needed to decrease the timeout so my system doesn't take a long time to poweroff.

Anonymous comment on 2012-10-27 20:45

Addendum: livesys-late.service can probably be removed too (along with getty@tty1.service), it seems to be something Fedora-specific.

Anonymous comment on 2012-10-27 20:42

Here are some suggestions:

1. Now that a common PAM file, /etc/pam.d/system-login, exists on Arch, lightdm.pam can be replaced with this (taken from kdm):
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/kde.pam?h=packages/kdebase-workspace

2. Remove WantedBy= from lightdm.service (graphical.target depends on display-manager.service by default so it's not needed anymore).

3. Or you could simply replace lightdm.service with Fedora's version, which already does (2.) plus some other goodies:
http://pkgs.fedoraproject.org/cgit/lightdm.git/tree/lightdm.service
It has some nice additions, like Documentation, Restart and BusName, but I don't get why they disable tty1. I suggest using the Fedora version without the tty1 parts. (My guess is that Fedora just copied that from gdm, which needs tty1 for itself, but that's not the case with lightdm.)
(Also note: Even though Fedora's After= contains plymouth-quit.service, it's not an error if you don't have plymouth installed. I think this would mean one .service file would work both with and without plymouth instead of having a separate lightdm-plymouth.service. But I'm not sure.)

The above has been tested to work on my computer, but hopefully it should work everywhere.

M0Rf30 commented on 2012-10-26 00:52

lightdm-plymouth.service moved to plymouth package

Atterratio commented on 2012-10-15 04:55

I just only with broken autologin?

Thaodan commented on 2012-10-14 18:22

Please add lightdm-qt as optimal depency.

Almin commented on 2012-10-05 14:38

1.4.0 is out. E-Mail:

This is the first release in the stable 1.4 series. This series will
be maintained on the lp:lightdm/1.4 branch and trunk (lp:lightdm) will
now be used for the unstable 1.5 series.

Overview of changes in lightdm 1.4.0

* Correctly implement and test autologin timeouts
* Add greeter-show-remote-login hint
* Correctly annotate enums in vapi file
* QLightDM: Add default constructor to Qt power interface
* QLightDM: Expose image path in UserModel
* QLightDM: Add parameter to session model to show either local or remote
sessions
* Fix race conditions in tests

DyrverE commented on 2012-10-05 13:25

btw, you should probably make sure lightdm.service is aliased (symlinked) with display-manager.service I think.
"Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details."

display-manager.service
The display manager service. Usually this should be aliased (symlinked) to gdm.service or a similar display manager service.

systemd automatically adds dependencies of type After for this target unit to all SysV init script service units with a LSB header referring to the $x-display-manager facility, for compatibility with Debian.

dgbaley27 commented on 2012-10-03 18:14

@switfgeek,

Huh? The greeters are defined by desktop files in /usr/share/xgreeters/*.desktop.

Nothing is implicitly backed up by placing it in /etc, it needs to be in the backup=() array of the PKGBUILD.

@Jristz,

The crowd-greeter is just kind of silly, but not really practical.

Jristz commented on 2012-10-03 16:29

gtk-greeter is 'teh basick'
webkit-greeter need many tweaks, by default practically all are commented or point to nonexisten archives (in ./webkit-greeter.conf)
unity-greeter, need patch ar changed deps for pointing to Archlinux in place of for example ubuntu-wallpapers
crowd-greeter, I not try it
kde/qt-greeter need a TON of KDE deps

This info is for future users wanting a greeter

swiftgeek commented on 2012-09-29 20:30

I also think that "Greeter session" should be set to a symlink provided by this package ;)
Eg. "/etc/lightdm/lightdm-greeter"

I guess that by placing it in /etc it wont be overwritten on upgrade.

dgbaley27 commented on 2012-09-29 02:50

Out of curiosity, what are most people using for the greeter? The gtk-greeter sucks.

I want something that shows up to around 6 users at a time and uses icons.

dgbaley27 commented on 2012-09-29 02:42

> accountsservice should be an optional dependency

+2

swiftgeek commented on 2012-09-29 02:38

accountsservice should be an optional dependency

logos commented on 2012-09-23 09:52

When is going to be lightdm in general packages? It's one of the most used display managers!

flan_suse commented on 2012-09-20 01:28

@dgbaley

Isn't that an option in NetworkManager (per connection) to have a wireless connection globally available (to all users)?

I forgot to mention that I actually disabled "Available to all users" in my wireless connections. At least LightDM still passes the (user login) password to gnome-keyring to unlock the default keyring (used by NetworkManager.)

flan_suse commented on 2012-09-20 01:26

@dgbaley

Isn't that an option in NetworkManager (per connection) to have a wireless connection globally available (to all users)?

dgbaley27 commented on 2012-09-20 00:27

Wouldn't you prefer your network passwords to be stored in /etc/NetworkManager so that all users can access them? NM should only store user-specific connections in the keyring.

flan_suse commented on 2012-09-19 23:52

@Morfeo

Thank you! It works great now.

I just tested this on Xfce using NetworkManager (nm-applet) with multiple wireless routers (WPA2).

For others who are interested, I have the gnome-keyring package installed and this is enabled in my Xfce startup applications:

Secret Storage Service (GNOME Keyring: Secret Service)
/usr/bin/gnome-keyring-daemon --start --components=secrets

After the first time I tried to connect to a wireless router, I was asked for the WPA2 key, then I was asked to enter a new default keyring password. I used the same exact password as my user account's. Upon connecting to the wireless again, I was greeted with a prompt for the default keyring password, with the option to "Remember". Now, whenever I login with LightDM, I do not need to enter my default keyring password anymore! It works the same, just like on a standard GNOME desktop with GDM.

flan_suse commented on 2012-09-19 03:24

Please add this to the end of /etc/pam.d/lightdm. This is needed for applicatios, such as NetworkManager (nm-applet), even in a non-GNOME environment (Xfce, LXDE, et al.)

# Allow user to automatically unlock the default gnome-keyring
auth optional pam_gnome_keyring.so
session optional pam_gnome_keyring.so auto_start

progandy commented on 2012-09-13 14:57

I use a custom pam file referencing system-login for everything.

#%PAM-1.0
auth include system-login
account include system-login
password include system-login
session include system-login
# Unlock Gnome keyring
-auth optional pam_gnome_keyring.so
-session optional pam_gnome_keyring.so auto_start

hermes14 commented on 2012-09-10 12:30

You should also add this line to /etc/pam.d/lightdm:
session required pam_limits.so
Without it:
$ ulimit -r -l
real-time priority (-r) 0
max locked memory (kbytes, -l) 64
With it (values are from /etc/security/limits.d/99-audio.conf, owned by jack2):
real-time priority (-r) 99
max locked memory (kbytes, -l) unlimited

swiftgeek commented on 2012-08-29 04:43

Please add:
-session optional pam_systemd.so
to /etc/pam.d/lightdm

padfoot commented on 2012-08-27 07:15

@android_808 may I suggest you create a forum topic and post your config and both lightdm and gtk-greeter logs. Without this minimum detail it is impossible to work out what is causing your issue, let alone fix it.

Cheers

android_808 commented on 2012-08-26 21:20

I've had nothing but grief since I updated this and gtk-greeter earlier today. Went through config files, merged appropriate changes etc etc.

Login screen displays fine. Enter password, login and let the wait begin. Eventually desktop (Xfce) appears but as soon as I do anything it stops working. Click menu for example, menu appears but keyboard and mouse proceed to stop working. Desktop also appears incorrectly, putting icons underneath the panel, conky is not transparent.

I had 1.2.2 and greeter 1.1.5 kicking about so I've downgraded to them with systemd fix for tty.

Stemp commented on 2012-08-07 08:41

Please add a lightdm-plymouth.service (similar to gdm-plymouth.service) to provide a seamless transition with plymouth.

[Unit]
Description=LightDM Display Manager
After=systemd-user-sessions.service

Conflicts=plymouth-quit.service
After=plymouth-quit.service

[Service]
ExecStart=/usr/sbin/lightdm
StandardOutput=syslog

[Install]
WantedBy=graphical.target
Alias=display-manager.service

Stemp commented on 2012-08-07 07:03

There should be a line in lightdm.service about display-manager.service like in gdm.

[Install]
WantedBy=graphical.target
Alias=display-manager.service

gdamjan commented on 2012-07-30 09:53

The patch to source .xinitrc seems wrong.
First of all, ~/.xinitrc is run by startx, similarly as xdm runs ~/.xsession

Second, running ~/.xinitrc depends on there beeing a /etc/X11/xinit/xinitrc.d/ directory

dgbaley27 commented on 2012-07-24 18:45

@thesame, oops, I misread that. I don't think sourcing .xinitrc is a good idea. I think .xinitrc is meant for startx/xinit to completely build up a session. What I had thought I had read was $HOME/.xinitrc.d/*", that would be more appropriate for sourcing from xsession.

dgbaley27 commented on 2012-07-24 13:39

@thesame +1

Also, did something change with xsession because it keeps going <defunct>?

thesame commented on 2012-07-24 10:30

damn formatting
http://pastebin.com/Pxw8te7i

thesame commented on 2012-07-24 10:29

Patch suggestion:


--- xsession 2012-04-10 16:19:44.000000000 +0300
+++ /etc/lightdm/xsession 2012-07-24 16:25:30.000000000 +0300
@@ -44,7 +44,7 @@
# Run all system xinitrc shell scripts.
xinitdir="/etc/X11/xinit/xinitrc.d"
if [ -d "$xinitdir" ]; then
- for script in $xinitdir/*; do
+ for script in $xinitdir/* "$HOME/.xinitrc"; do
echo "Loading xinit script $script"
if [ -x "$script" -a ! -d "$script" ]; then
. "$script"

Leonardo19 commented on 2012-07-14 12:58

Thanks!

cmaloney commented on 2012-07-13 21:51

it is in extra: http://www.archlinux.org/packages/extra/any/itstool/

Leonardo19 commented on 2012-07-13 11:17

I tried to install LightDM and stopped because of this:
error: itstool: package not found in AUR.

cmaloney commented on 2012-07-12 18:23

/etc/pam.d/login is actually provided by the util-linux package (probably for /sbin/agetty). /etc/pam.d/system-local-login is the base defaults for any service which is logging in locally. /etc/pma.d/login includes two extra modules, pam_securetty and pam_nologin. pam_nologin is actually included by default, pam_securetty doesn't apply to lightdm because it's not logging in at a tty.

padfoot commented on 2012-07-11 06:37

@cmaloney, should that be /etc/pam.d/login so all the required module includes are used?

cmaloney commented on 2012-07-11 02:41

Could you update the pam files to use pambase (/etc/pam.d/lightdm should use /etc/pam.d/system-local-login)?

padfoot commented on 2012-07-10 08:52

I have auto login working again. Please replace the current lightdm-autologin.pam file with the following: http://pastebin.com/ZSVtjvAG

This is simply a direct copy of the current gdm package autologin file.

Cheers.

mika.fischer commented on 2012-07-09 16:40

I get the following since a few releases with every update:

warning: directory permissions differ on run/lightdm/
filesystem: 770 package: 755

In /usr/lib/tmpfiles.d/lightdm.conf, the directory is specified with 770, while in the package it's included as 755. I don't know which one's correct but they should both be identical.

And also it would probably be good to change the path in /usr/lib/tmpfiles.d/lightdm.conf to /run instead of /var/run as well.

DyrverE commented on 2012-07-09 14:34

And to conform with changes in filesystem, use /run instead of /var/run (which is a symlink now) in the future :)

dgbaley27 commented on 2012-07-08 03:44

Did the lightdm pam file have gnome keyring support at one point? It hasn't worked for me in a few weeks.

graysky commented on 2012-06-27 00:32

@Morfeo - Can you modify /etc/pam.d/lightdm to contain this line to make it work properly with systemd:

session optional pam_systemd.so

gdamjan commented on 2012-06-26 14:44

The pam file needs to have
-session optional pam_systemd.so
like all the other login managers

darehanl commented on 2012-06-25 15:07

Anyone else see terrible flickering with gnome3 after the 1.3 update? My gnome3 session has serious repaint issues and turns into a collage of windows, but the problems go away if I switch to gdm. I didn't have any issues prior to the update, but I don't have a old 1.2.2 package handy to test.

I'm using intel 945 by the way.

M0Rf30 commented on 2012-06-24 13:46

I'm searching for a solution to this issue
authentication complete with return value 19: Conversation error lightdm

padfoot commented on 2012-06-23 23:32

Confirming - autologin no longer works

jose1711 commented on 2012-06-23 19:21

somehow autologin stopped working for me.. :-(

mfs commented on 2012-06-21 17:39

itstool should be added to the makedepends array, not a seperate array called makedeps (as it is the case now)

mika.fischer commented on 2012-06-21 16:55

itstool needs to be added to makedepends

M0Rf30 commented on 2012-06-09 18:23

where is lightdm-plymouth.service?

gog commented on 2012-06-06 13:16

I made a fix for the systemd services.

http://ompldr.org/vZTRuag/lightdm-systemd-services.patch

gog commented on 2012-06-06 13:10

I made a fix for the systemd services.

http://ompldr.org/vZTRuag/lightdm-systemd-services.patch

gog commented on 2012-06-06 13:07

I made a fix for the systemd service and plymouth.

http://ompldr.org/vZTRuZw/lightdm-plymouth+systemd.patch

Anonymous comment on 2012-06-03 17:07

I think this package doesn't need to depend on gtk3 (and namcap agrees with me);
only lightdm-gtk-greeter needs that.
All you need is the makedepend on gobject-introspection

Indeed, most of the point of lightdm is to separate the greeter from the backend,
so depending on gtk3 rather defeats its purpose!

So far as I could see, it doesn't need to makedepend on gnome-doc-utils or gnome-common either,
although I could be wrong there.

darehanl commented on 2012-06-01 16:01

As @gdamjan mentioned, lightdm.service needs the line "Requires=dev-tty7.device" removed now.

Anonymous comment on 2012-05-28 23:33

If you are using testing you have probably noticed this. Today's updates to systemd caused lightdm.service to "hang"

gdamjan commented on 2012-05-28 23:30

As of systemd 88e995fd, VC devices do not have the 'systemd' tag anymore, since they are always available.

Units that still have the dependency on dev-tty7.device will timeout when started.

https://github.com/falconindy/systemd-arch-units/pull/123

So lightdm should prepare for this soon

dgbaley27 commented on 2012-05-19 14:50

You're right, I missed those couple of lines, I was too busy staring at the rest of my patch with your name on it.

eworm commented on 2012-05-18 15:58

@dgbaley27: You should look at what I submitted to accountsservice. I iterate thought what getusershell() returns. So it actually DOES check for a valid login shell in /etc/shells.

dgbaley27 commented on 2012-05-18 15:42

Eworm, I don't appreciate you submitting my patch to accountsservices under your name. Especially since you don't even know what it does. /etc/shells is not consulted, it only checks they aren't "false" or "nologin," and that these are checked elsewhere in the daemon, just for whatever reason the shell check was skipped in one spot.

eworm commented on 2012-05-18 10:57

accountsservice 0.6.21 should fix the issues for all of you. It only lists users with a valid login shell (one of those listed in /etc/shells). So if any system service is still listed you should think about whether or not it needs /bin/bash or the like as login shell.

XeCycle commented on 2012-05-08 11:08

WebKit is not needed for this package. Why add it there?

padfoot commented on 2012-05-08 07:32

@ eworm, changing the uid to <500 will work if you remove accountsservice. At least that is what I had to do. Of course, if accountsservice is required by other packages on your system, you could always try dgbaley27's patch.

dgbaley27 commented on 2012-05-07 14:35

Ok, I've tried to fix AccountsService: http://lists.freedesktop.org/archives/freedesktop/2012-May/000282.html
Feel free to apply the patch in the meantime (to AccountsService, not LightDM).

dgbaley27 commented on 2012-05-07 13:49

AccountsService no longer uses a min UID. It now just checks for no shell at all, false, or nologin. I put some debugging statements into this function (daemon.c) and it's saying that lightdm is excluded. So there's obviously a bug elsewhere. My guess is that this function isn't working at all and only the hard-coded blacklist is working.

eworm commented on 2012-05-07 13:33

> I changed my uid for lightdm and mpd to <500 and they still displayed in the lightdm list.

@padfoot: This is a problem in mpd's package. Change the login shell to /bin/false and it will no longer be displayed.

Users with loginshell /sbin/nologin should be hidden as well... So no idea why lightdm user itself is shown.

magicfish1990 commented on 2012-05-07 04:13

/var/run is tmpfs, all configuration will be lost at shutdown, such as the use of unity-greeter.
Home directory may be moved to other places?

Anonymous comment on 2012-05-05 04:04

@padfoot

You are right,and your solution is working well for xfce.
Gnome users would use gdm instead,so they don't have the problem.
:)

padfoot commented on 2012-05-05 03:25

@dgbaley27
Yes, the intended behaviour is to use users.conf when accountsservice is not present, yet my install does not do that. Users.conf is completely ignored. I had to change the uid of users to be hidden to <500 for them to no longer display.

dgbaley27 commented on 2012-05-04 22:02

lightdm uses accountsservice if available. It falls back to users.conf if it has to. It never uses both. I have added a wishlist item to lightdm to allow users.conf to be used no matter what.

As far as accountsservice goes, I think they changed it from a min uid to just a blacklist. It's really dumb. People keep writing these stupid DBus daemons and don't provide any flat config files.

padfoot commented on 2012-05-04 21:51

@pomhg, you are right, but it is a combination of the 2. I changed my uid for lightdm and mpd to <500 and they still displayed in the lightdm list.

I use Xfce, so my only requirement for accountsservice is lightdm. I rebuilt without the accountsservice dependency, removed accountsservice and then the uid's < 500 no longer showed.

Now, without accountsservice, I changed to uid's to >500 but <1000, and they displayed again.

So there is a problem with accountsservice, but there is also a problem with lightdm as it seems to ignore the users.conf file (defaults to hide uid's <1000), where lightdm actually hides uid's <500.

So I have my solution, no accountsservice and uid's <500 for those to be hidden. Although this will not work for Gnome users, as accountsservice is required.

Anonymous comment on 2012-05-04 15:01

@padfoot

I think the problem is AccountsService.
On my machine as long as AccountsService is installed,even mpd whose uid is 45 by default is also displayed in the userlist of LightDM.

Anonymous comment on 2012-05-04 06:03

It seems it's required to have dbus up and running for lightdm to work - at least, I got a blank screen everytime I tried to start up lightdm until I started up dbus. Can this be added to the wiki page?

dgbaley27 commented on 2012-05-02 14:13

As far as accountsservice goes, the real problem is the damn thing has no configuration options. Just because it's a dbus daemon doesn't mean it can't have a flat config file in /etc. In any event, I put in a request: https://bugs.launchpad.net/lightdm/+bug/976554 so +1 it or whatever they do on launchpad.

padfoot commented on 2012-05-02 09:44

@morfeo

May I suggest you change the uid of the lightdm user to <500 so the lightdm user is not displayed in the user list at login.
Also, accountsservice is not a required dependency. It would be better suited as an optdepend.

Cheers.

jrk commented on 2012-04-22 18:43

Ok, for heaven's sake..

https://aur.archlinux.org/packages.php?ID=58707

dgbaley27 commented on 2012-04-18 16:09

That's your opinion. I don't see why upstream would be opposed to supporting alternate xsessions locations. For now it's just not high priority and would require some rework to get a separate list for each user (or generate a new list each time a new user is selected). This could get complicated when typing an unlisted user.

padfoot commented on 2012-04-18 08:33

The contents of /usr/share/xsessions and any corresponding user folder in /home should not be customised/configured by lightdm. These should only be provided by the chosen DEs/xsessions the user has opted to install as each has it's own particular requirements for launching. Lightdm only provides the user the choice of which one to launch at login.

If you are that passionate about providing an easier way for the user to create custom xsessions (although I cannot see what is difficult about adding your own .desktop file to run whatever scripts you like yourself) in /usr/share/xsessions, why not code a simple gui to do so?

It is not a task lightdm should be involved in.

dgbaley27 commented on 2012-04-17 19:02

I think it would actually be ~/.config/xessions. It's a feature I would like to see myself. Until then, you don't have a lot of options. You're correct about how the wrapper is used.

I'd guess it's pretty easy to implement. The issue is working with bazaar!

jrk commented on 2012-04-17 18:10

So how would I make my custom xinitrc script pop up as an option at the lightdm dialog?

What about multiple machines? I'd don't want to fiddle with /usr on every machine I install and configure. That's what pkg management is for.

As long as lightdm won't list session in $HOME/.local/share/xsessions there's no alternative.
As far as I understood the session wrapper script is run by lightdm with the Exec line as argument.

yuyichao commented on 2012-04-15 17:10

Your suggested desktop file has nothing to do with lightdm I think, so there is no reason to add it here~~.

dgbaley27 commented on 2012-04-15 17:05

You can add that file on your own machine if you want. It won't do the same thing as an xsession wrapper though. The program in Exec won't be called with any arguments.

jrk commented on 2012-04-15 09:35

Could you a file like this to the package?

$ cat /usr/share/xsessions/lightdm-xsession.desktop
[Desktop Entry]
Name=XSession
Comment=Run a custom ~/.xsession client script
Exec=~/.xsession

Thanks!

eworm commented on 2012-04-13 19:10

systemd unit files should go to /usr/lib/systemd/system/ now.

padfoot commented on 2012-04-12 08:12

Just change the /etc/lightdm/lightdm.conf session-wrapprr key to point at whatever file you like. As long as the file is executable and can be executed by the lightdm user it will be fine.
You are not restricted to using the packaged file.
No need to raise a feature request for something which is totally user/distro dependent, and is 100% configurable right now.

dgbaley27 commented on 2012-04-11 17:52

Yeah, my bad. Like I said below there are way too many layers called session =/

gdamjan commented on 2012-04-11 17:45

well no, /etc/lightdm/xsession is not run by root. It's run by the loged user.
Anyway, thanks - and good idea for ~/.local/share/xessions

dgbaley27 commented on 2012-04-11 16:18

http://pkgbuild.com/git/aur-mirror.git/tree/lightdm

* Firstly, it would be -x, but it's used by root so It doesn't quite matter.

* Actually, I think this should be a feature request for lightdm. Lightdm should honor other xsession dirs like ~/.local/share/xessions

* Can't argue with that last point =)

gdamjan commented on 2012-04-11 15:23

Is the `/etc/lightdm/xsession` file maintained in some revision system? Or where should we suggest improvements?

* I'd suggest changing -f tests to -r in most places, since those files actually need to be *read*

* how about allowing for a user session wrapper, something like (at the end):

userwrapper="$HOME/.xsession"
if [ -x "$userwrapper" ]; then
echo "System X session wrapper complete, running $userwrapper $@"
exec "$userwrapper" $@
else
echo "X session wrapper complete, running session $@"
exec $@
fi


* I've also noticed some inconsistencies that might be fixed, like

for i in `ls $xsessionddir`;
vs
for script in $xinitdir/*;

padfoot commented on 2012-04-10 07:55

@andreyv
http://pastebin.com/71rw4Qx9 here is the link to the previously packaged file. Just save it as /etc/lightdm/xsession and make it executable. Then set /etc/lightdm/lightdm.conf session-wrapper key to point at that file.

Look carefully at lightdm.conf, each section is listed twice, first is commented out to show you the defaults, the second is the actual config.

padfoot commented on 2012-04-10 07:52

@andreyv
http://pastebin.com/71rw4Qx9 here is the link to the previously packaged file. Just save it as /etc/lightdm/xsession and make it executable. Then set /etc/lightdm/lightdm.conf session-wrapper key to point at that file.

andreyv commented on 2012-04-10 07:35

Thanks for the explanation. Since the last update the session-wrapper line is commented out in /etc/lightdm/lightdm.conf, and I still get the same result as @graysky — after login (to Xfce) I get thrown out and .xsession-errors reads "No such file or directory". Is it correct to try session-wrapper="~/.xinitrc"?

padfoot commented on 2012-04-10 07:12

Thw session wrapper is not included in the source as it is different for each distro. A convenience script was included with previous packages of lightdm in the AUR, but is technically not required. It is used to set up your user session environment, and that is all dependent on your DE, and personal preferences.

Some use ~/.xinitrc, some use ~/.xsession, some write their own scripts. Personally, I use /etc/X11/xinit/xinitrc slightly modified to launch the DE selected from the greeter. /etc/X11/xinit/xinitrc is the closest Arch default you will get to the previously supplied script.

Alternatively, you can just set the session-wrapper key to nothing in /etc/lightdm/lightdm.conf and your DE should still launch. It is not recommended though, as your environment variables most likely will not be set correctly.

So the fact that the script is not there is not a packaging or source error, as there are many different ways you can do that config, so it is impractical to try and provide a catchall solution.

Cheers.

dgbaley27 commented on 2012-04-09 22:31

I don't think the wrapper is required. For me it's useful for /etc/X11/xinit/xinitrc.d. But there might be a config value to bypass the wrapper entirely.

andreyv commented on 2012-04-08 22:17

Wait a minute, how is this software supposed/intended to work if its source is missing a critical file?

dgbaley27 commented on 2012-04-08 12:41

Thanks, there are way too many layers here called "session"

I think accountservice should be an optional dep.

padfoot commented on 2012-04-08 00:30

@dgbaley27
It seems the Xsession script from the previous build has been omitted. Generally you can use a slightly modified version of /etc/X11/xinit/xinitrc (I use this file and just change the end to launch my DE using exec $1 after executing the /etc/profile scripts)

http://pastebin.com/71rw4Qx9 here is the link to the previously packaged file.

dgbaley27 commented on 2012-04-07 22:47

Where is the lightdm-session script supposed to come from? I see that Debian and Ubuntu have it, but it doesn't look like it's included in the source for lightdm-1.2.0

graysky commented on 2012-04-07 15:39

I can't login since the bump to 1.2.x -- love it if some folks could respond on the bbs in this thread: https://bbs.archlinux.org/viewtopic.php?id=139176

graysky commented on 2012-04-07 15:04

I built the optional lightdm-gtk-greeter package and set /etc/lightdm/lightdm.conf to use it. I am greeted by this greeter but logging in for now now does nothing but return me to the greeter screen.

Here are the uncommented lines in my /etc/lightdm/lightdm.conf

$ sed '/#/d' /etc/lightdm/lightdm.conf
[LightDM]
greeter-session=lightdm-gtk-greeter
[SeatDefaults]
[XDMCPServer]
[VNCServer]

Anonymous comment on 2012-04-07 13:51

Now it builds, thank you!

dgbaley27 commented on 2012-04-07 03:33

Could you guys take the time to read the previous few comments before you just spam everyone?

magicfish1990 commented on 2012-04-07 03:08

make[3]: Entering directory `/tmp/yaourt-tmp-root/aur-lightdm/src/lightdm-1.2.0/tests/src'
/bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DSRCDIR=\"/tmp/yaourt-tmp-root/aur-lightdm/src/lightdm-1.2.0\" -DBUILDDIR=\"/tmp/yaourt-tmp-root/aur-lightdm/src/lightdm-1.2.0\" -DCONFIG_DIR=\"/etc/lightdm\" -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -MT libsystem_la-libsystem.lo -MD -MP -MF .deps/libsystem_la-libsystem.Tpo -c -o libsystem_la-libsystem.lo `test -f 'libsystem.c' || echo './'`libsystem.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DSRCDIR=\"/tmp/yaourt-tmp-root/aur-lightdm/src/lightdm-1.2.0\" -DBUILDDIR=\"/tmp/yaourt-tmp-root/aur-lightdm/src/lightdm-1.2.0\" -DCONFIG_DIR=\"/etc/lightdm\" -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -MT libsystem_la-libsystem.lo -MD -MP -MF .deps/libsystem_la-libsystem.Tpo -c libsystem.c -fPIC -DPIC -o .libs/libsystem_la-libsystem.o
In file included from /usr/include/unistd.h:1171:0,
from libsystem.c:8:
libsystem.c: In function `pam_setcred':
/usr/include/bits/unistd.h:266:1: error: inlining failed in call to always_inline `getgroups': function not inlinable
libsystem.c:879:27: error: called from here
In file included from /usr/include/unistd.h:1171:0,
from libsystem.c:8:
/usr/include/bits/unistd.h:266:1: error: inlining failed in call to always_inline `getgroups': function not inlinable
libsystem.c:881:27: error: called from here
make[3]: *** [libsystem_la-libsystem.lo] Error 1

donniezazen commented on 2012-04-07 01:46

make all-recursive
make[1]: Entering directory `/tmp/yaourt-tmp-donnie/aur-lightdm/src/lightdm-1.2.0'
Making all in liblightdm-gobject
make[2]: Entering directory `/tmp/yaourt-tmp-donnie/aur-lightdm/src/lightdm-1.2.0/liblightdm-gobject'
CC liblightdm_gobject_1_la-greeter.lo
CC liblightdm_gobject_1_la-system.lo
CC liblightdm_gobject_1_la-language.lo
CC liblightdm_gobject_1_la-layout.lo
CC liblightdm_gobject_1_la-power.lo
CC liblightdm_gobject_1_la-session.lo
CC liblightdm_gobject_1_la-user.lo
CCLD liblightdm-gobject-1.la
GISCAN LightDM-1.gir
GICOMP LightDM-1.gir
make[2]: Leaving directory `/tmp/yaourt-tmp-donnie/aur-lightdm/src/lightdm-1.2.0/liblightdm-gobject'
Making all in liblightdm-qt
make[2]: Entering directory `/tmp/yaourt-tmp-donnie/aur-lightdm/src/lightdm-1.2.0/liblightdm-qt'
moc QLightDM/greeter.h -o greeter_moc.cpp
CXX liblightdm_qt_2_la-greeter.lo
moc QLightDM/power.h -o power_moc.cpp
CXX liblightdm_qt_2_la-power.lo
moc QLightDM/sessionsmodel.h -o sessionsmodel_moc.cpp
CXX liblightdm_qt_2_la-sessionsmodel.lo
moc QLightDM/usersmodel.h -o usersmodel_moc.cpp
CXX liblightdm_qt_2_la-usersmodel.lo
CXXLD liblightdm-qt-2.la
make[2]: Leaving directory `/tmp/yaourt-tmp-donnie/aur-lightdm/src/lightdm-1.2.0/liblightdm-qt'
Making all in tests
make[2]: Entering directory `/tmp/yaourt-tmp-donnie/aur-lightdm/src/lightdm-1.2.0/tests'
Making all in src
make[3]: Entering directory `/tmp/yaourt-tmp-donnie/aur-lightdm/src/lightdm-1.2.0/tests/src'
CC libsystem_la-libsystem.lo
In file included from /usr/include/unistd.h:1171:0,
from libsystem.c:8:
libsystem.c: In function 'pam_setcred':
/usr/include/bits/unistd.h:266:1: error: inlining failed in call to always_inline 'getgroups': function not inlinable
libsystem.c:879:27: error: called from here
In file included from /usr/include/unistd.h:1171:0,
from libsystem.c:8:
/usr/include/bits/unistd.h:266:1: error: inlining failed in call to always_inline 'getgroups': function not inlinable
libsystem.c:881:27: error: called from here
make[3]: *** [libsystem_la-libsystem.lo] Error 1
make[3]: Leaving directory `/tmp/yaourt-tmp-donnie/aur-lightdm/src/lightdm-1.2.0/tests/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/yaourt-tmp-donnie/aur-lightdm/src/lightdm-1.2.0/tests'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/yaourt-tmp-donnie/aur-lightdm/src/lightdm-1.2.0'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build lightdm.

dgbaley27 commented on 2012-04-07 00:44

You can avoid the build error by passing --disable-tests to ./configure. However, I haven't been able to log in so maybe that test was important =/

graysky commented on 2012-04-07 00:23

Need more info, donnie.

make[3]: Entering directory `/scratch/lightdm/src/lightdm-1.2.0/tests/src'
CC libsystem_la-libsystem.lo
CC dbus_env-dbus-env.o
CC X-X.o
CC test_runner-test-runner.o
CC X-x-authority.o
CC X-x-common.o
CC X-x-server.o
In file included from /usr/include/unistd.h:1171:0,
from libsystem.c:8:
libsystem.c: In function ‘pam_setcred’:
/usr/include/bits/unistd.h:266:1: error: inlining failed in call to always_inline ‘getgroups’: function not inlinable
libsystem.c:879:27: error: called from here
In file included from /usr/include/unistd.h:1171:0,
from libsystem.c:8:
/usr/include/bits/unistd.h:266:1: error: inlining failed in call to always_inline ‘getgroups’: function not inlinable
libsystem.c:881:27: error: called from here
make[3]: *** [libsystem_la-libsystem.lo] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory `/scratch/lightdm/src/lightdm-1.2.0/tests/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/scratch/lightdm/src/lightdm-1.2.0/tests'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/scratch/lightdm/src/lightdm-1.2.0'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...

donniezazen commented on 2012-04-06 23:40

==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build lightdm.
==> Restart building lightdm ? [y/N]

padfoot commented on 2012-04-06 21:02

Getting the same build error here too.

dgbaley27 commented on 2012-04-06 14:29

It actually only needs lightdm as a build-dep, and 1.2 is not required. So you can make the greeter against your current lightdm, and then install it once you've removed it (file conflicts). I'm not sure about that build error though; I get the same thing.

mamciek commented on 2012-04-06 13:16

it is impossible to install lightdm because it requires lightdm-gtk-greeter, and greeter cannot be installed because:

==> Install or build missing dependencies for lightdm-gtk-greeter:
error: target not found: lightdm=>1.2.0

I have tried to temporary remove the greeter dependency but then compilation fails:

/usr/include/bits/unistd.h:266:1: error: inlining failed in call to always_inline 'getgroups': function not inlinable
libsystem.c:879:27: error: called from here
In file included from /usr/include/unistd.h:1171:0,
from libsystem.c:8:
/usr/include/bits/unistd.h:266:1: error: inlining failed in call to always_inline 'getgroups': function not inlinable
libsystem.c:881:27: error: called from here
make[3]: *** [libsystem_la-libsystem.lo] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory `/tmp/yaourt-tmp-maciej/aur-lightdm/src/lightdm-1.2.0/tests/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/yaourt-tmp-maciej/aur-lightdm/src/lightdm-1.2.0/tests'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/yaourt-tmp-maciej/aur-lightdm/src/lightdm-1.2.0'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...

M0Rf30 commented on 2012-04-06 12:26

I have to fix the lightdm stop problem

padfoot commented on 2012-04-05 22:29

@morfeo
I have package up lightdm-gtk-greeter-1.1.5 in readiness for an upgrade to lightdm-1.2.0

vjraitila commented on 2012-04-05 19:43

Builds fine for me. But there's another problem with this package: "/etc/rc.d/lightdm stop" does not actually terminate the app on my system. The same issue causes a SIGTERM failure when shutting down.

eworm commented on 2012-04-05 07:22

Versions 1.0.11 and 1.2.0 have been released.

Additionally I can not build atm:
==> ERROR: lightdm was not found in the build directory and is not a URL.

graysky commented on 2012-03-28 16:53

I defined a logo in /etc/lightdm/lightdm-gtk-greeter.conf (64x64 png file) but lightdm doesn't use it. This file is available to all users (including lightdm). I started a thread about this issue. Please reply there.

https://bbs.archlinux.org/viewtopic.php?pid=1079020

Anonymous comment on 2012-03-10 20:23

Thanks for the info :) They have the x-bits as well, so I don't know. But I worked around it anyway by placing the image directly under / ;)

eworm commented on 2012-03-10 20:03

The pacman message should not be related.

For directories you need the x permission to access the content.

Anonymous comment on 2012-03-10 19:50

All dir's from / up to to /usr/share/backgrounds have the r bit on "others", so I really don't know.. If it's readable by myself with no special privelieges, I presume it should be for lightdm as well...

Do you know if the pacman message has something to do with this?

eworm commented on 2012-03-10 18:57

Does lightdm have the right for the directories? If /usr/share/background/ is 0700 (rwx------) it does not help if the file itself has the correct bits set.

Anonymous comment on 2012-03-10 18:53

Hm... I made a copy of the image to /usr/share/backgrounds and did 'chmod a+r file.jpg'... Shouldn't that make it readable by anybody, including the user 'lightdm'? The output of 'ls -l' is:


-rw-r--r-- 1 root root 638376 mars 10 19:26 /usr/share/backgrounds/file.jpg

Sorry for the obvious noob question, but perhaps I don't understand file permissions O_o

eworm commented on 2012-03-10 17:55

@mariusmeyer: The lightdm greeter is running with user permissions for user 'lightdm'. So if it can't access the image (is it placed into your home directory?) it will show a blue background.

Anonymous comment on 2012-03-10 16:47

Hello! Today I upgraded from 1.0.6-4 to 1.0.9-1. I can log in just fine with correct permission and all that, but the greeter now shows a blue color instead of the background image specified in /etc/lightdm/light-gtk-greeter.conf. However, if I change the background variable to #FFFFFF, the color turns white as expected. Anybody experience the same thing? If relevant, I got this warning at install time:


warning: directory permissions differ on var/run/lightdm/
filesystem: 711 package: 755

eworm commented on 2012-03-05 09:08

Flagged out-of-date, this time for real. ;)

Version 1.0.9 has been released with security fixes.

eworm commented on 2012-03-01 20:39

@ maloy and anybody having problems with lightdm and systemd:

You may use lightdm-bzr and lightdm-*-greeter.bzr until version 1.2.0 (next stable) is released.
Just tested and it works with revision 1442.

gdamjan commented on 2012-03-01 19:17

@maloy
look at the previous comment

also, according to https://bugs.launchpad.net/lightdm/+bug/881466 it's fixed in 1.1.4

Anonymous comment on 2012-02-26 15:15

When I use lightdm with systemd my session of LXDE doesn't start (black screen), I have to and restart lightdm with '/etc/rc.d/lightdm restart' to make it work.

Anyone knows what happen?

gdamjan commented on 2012-02-23 23:27

This version of lightdm when used with systemd, has a bug in how it uses pam and executes the user session.

It seems, it opens the pam session before forking, which is wrong, since systemd-logind will think the greeter itself is the session's controlling process, so it will kill the session when the greeter exits.

eworm commented on 2012-02-13 20:05

Ok, here are my changes... Please apply.
http://www.eworm.de/download/linux/lightdm.patch

Running the greeter with root privileges is really a bad idea... :-p

eworm commented on 2012-02-12 13:16

This starts the greeter with root privileges by default? Can we create a user 'lightdm' and start the greeter with this unprivileged user?
Let me know if you need help, I could prepare patches.

Anonymous comment on 2012-02-09 00:42

@padfoot: Please, read the mailing list. This was the same with version 1.1.0, which also had a newer release date and was not marked as a developer version in the download box. But in the mailing list it is written, that versions 1.1.x are development version on the road to the next stable release 1.2.0. That's why I said, they are not marked as such, but they are.

From the mailing list:
"This first unstable 1.1.0 release has been made, which will work towards a 1.2.0 stable release in six months."

padfoot commented on 2012-02-09 00:15

Just saying it may warrant further investigation.

padfoot commented on 2012-02-09 00:15

@cyberpatrol, latest version in the downloads box on the right of the home page is now 1.1.2 released 6 Feb 2012. Seems things may have changed since the Oct 11 update. Prior to the 6 Feb change, the download version was 1.0.6. This indicates to me that 1.1.2 is now considered the latest stable.

Cheers.

Anonymous comment on 2012-02-08 22:50

@padfoot: Versions 1.1.x are development versions. They are not marked as such, but they are. Read the thread on upstream's mailing list I already linked to. The next stable release will be 1.2.0.

padfoot commented on 2012-02-08 22:43

Updated trunk version is now available v 1.1.2. It does not include greeters anymore. They will need to be separate packages.

A couple of build errors I cam across:
tests/Makefile.am:107: whitespace following trailing backslash
lightdm-1.1.2/tests/src/test-runner.c:786: undefined reference to `g_key_file_unref'

Removing the whitespace in tests/Makefile.am solved that error.
Looking at gkeyfile.h, there is no function g_key_file_unref. Should this be g_key_file_free?

Changing the function to g_key_file_free and using your current PKGBUILD build instructions:
./autogen.sh
./configure --prefix=/usr \
--sysconfdir=/etc --disable-static --libexecdir=/usr/lib/lightdm \
--localstatedir=/var --with-greeter-user=root \
--with-greeter-session=lightdm-gtk-greeter

The build now succeeds. Of course I do not know enough to package this correctly for Arch.

Hope this helps in updating the package, then I can look at changing my osk package to just build the gtk-greeter.

Cheers.

skull-y commented on 2012-01-26 15:51

1.1.1 is released on 2012-01-17

eworm commented on 2012-01-22 19:43

Ok, back to 1.0.6... But why do we have pkgrel=1 now? Currently I have install 1.0.6-10.

M0Rf30 commented on 2012-01-21 16:43

restored 1.0.x branch.sorry for the mistake

Anonymous comment on 2012-01-21 14:05

@cucullus: Right, and I can't find any in upstream's download section.

cucullus commented on 2012-01-21 13:43

So ATM there are no gtk greeter on aur?

cucullus commented on 2012-01-21 13:37

So ATM there are no gtk greeter on aur?

Anonymous comment on 2012-01-21 06:00

@Morfeo: Are you sure, that this update to 1.1.1 is meant as a stable release?
From the mailing list (http://lists.freedesktop.org/archives/lightdm/2011-October/000148.html):
This first unstable 1.1.0 release has been made, which will work
towards a 1.2.0 stable release in six months. This release contains
the fixes from the stable branch and some deprecations. It is
recommended to stick with the 1.0.x series for now, this is mostly
being released before the NEWS file gets too large to read.

Anonymous comment on 2012-01-21 05:54

@jon2: It's not a bug, it's a feature. From upstream's changelog (http://lists.freedesktop.org/archives/lightdm/2012-January/000212.html):
* Move the GTK+ and Qt greeters into their own projects

Anonymous comment on 2012-01-21 04:06

The new version of lightdm does not include the standard gtk-greeter in /usr/share/xgreeters, so lightdm fails to start. Error message on TTY7: "id x respawning too fast disabled for 5 minutes".

strider2 commented on 2012-01-17 20:05

Please adapt PKGBUILD to reflect the new download location :
http://launchpad.net/lightdm/trunk/$pkgver/+download/
Thanks

Blender commented on 2012-01-16 00:01

Sorry for the confusion, I just flagged it out of date because the package wasn't compiling.

Anonymous comment on 2012-01-15 15:43

The release dates don't say anything. This is what the version numbers are for. That the release date of an older version is newer than the release date of a newer version can happen due to backporting a feature or security fix or the like for whatever reasons.

But in this case version 1.1.0 is indeed an unstable release as I now read in upstream's mailing list archives. So in this case 1.0.6 is indeed the latest stable release. Maybe upstream should mark 1.1.0 as unstable in their downloads section.

graysky commented on 2012-01-15 15:23

@cyber - that's a mistake talked about previous in these comments... look at the dates:

Light Display Manager 1.1.0 None 2011-10-08
Light Display Manager 1.0.6 None 2011-11-04
Light Display Manager 1.0.5 None 2011-10-27
Light Display Manager 1.0.4 None 2011-10-26

Anonymous comment on 2012-01-15 15:16

Probably because there's a version 1.1.0 at least in the downloads section.

graysky commented on 2012-01-15 15:09

1.0.6 was released on 2011-11-04... why is the PKG out-of-date? Morfeo just needs to update the source array.

<<<START PATCH>>>

--- PKGBUILD 2012-01-15 10:08:28.793278167 -0500
+++ PKGBUILD 2012-01-15 10:07:33.492489999 -0500
@@ -5,7 +5,7 @@
arch=('i686' 'x86_64')
url="https://launchpad.net/lightdm"
license=('GPL3' 'LGPL3')
-source=("http://people.ubuntu.com/~robert-ancell/lightdm/releases/$pkgname-$pkgver.tar.gz"
+source=("http://launchpad.net/lightdm/trunk/1.0.6/+download/$pkgname-$pkgver.tar.gz"
lightdm
lightdm.service
lightdm-gtk-greeter.conf

<<<END PATCH>>>

graysky commented on 2012-01-15 15:03

1.0.6 was released on 2011-11-04... why is the PKG out-of-date?

Blender commented on 2012-01-13 07:37

Files moved to launchpad: http://launchpad.net/lightdm/trunk/1.0.6/+download/lightdm-1.0.6.tar.gz

donniezazen commented on 2012-01-07 20:59

Thanks working fine.

M0Rf30 commented on 2012-01-07 15:47

please install base-devel group

Anonymous comment on 2012-01-07 11:09

@mschaeuble: https://wiki.archlinux.org/index.php/AUR_User_Guidelines#Prerequisites

mschaeuble commented on 2012-01-07 10:27

Dependency "autoconf" is missing.

M0Rf30 commented on 2011-12-27 15:02

waiting for a better solution

M0Rf30 commented on 2011-12-27 15:02

now it builds. I've temporary commented out the third row in utils/Makefila.am

gdamjan commented on 2011-12-26 21:03

it's the automake upgrade from round 24th december that breaks the lightdm build

Anonymous comment on 2011-12-26 18:14

Same error here Prettyflower. I already have it installed, but when I ran an aur update today I got that error.

PrettyFlower commented on 2011-12-24 18:08

Hey I can't seem to install it. I get the error

utils/Makefile.am:3: `pkglibexecdir' is not a legitimate directory for `SCRIPTS'

when it runs automake-1.11

eworm commented on 2011-12-23 10:42

"auth optional pam_gnome_keyring.so" is in the pam configuration file twice.

broken.pipe commented on 2011-12-23 07:54

thanks yuyichao, fix works :)

yuyichao commented on 2011-12-22 23:16

try adding

find -iname '*moc*' -exec rm {} \;

before

./autogen in build()

yuyichao commented on 2011-12-22 22:24

try adding a find -iname '*moc*' -exec rm {} \; before ./autogen

yuyichao commented on 2011-12-22 22:12

Tried to compile just now, same here, seems because Arch is using qt 4.8.0 now.
(not sure how to workarround now~~~)

Anonymous comment on 2011-12-22 22:11

greeter_moc.cpp:14:2: error: #error "This file was generated using the moc from 4.7.4. It"
greeter_moc.cpp:15:2: error: #error "cannot be used with the include files from this version of Qt."
greeter_moc.cpp:16:2: error: #error "(The moc has changed too much.)"

Looks like an upstream issue caused by the update to Qt 4.8.0.

broken.pipe commented on 2011-12-22 21:29

can't get it compiled :( ... base-devel is installed

http://pastebin.com/4JuFRC7q

Anonymous comment on 2011-12-19 02:46

@MorningWood: You should read the AUR User Guidelines before using or installing from the AUR and install the group base-devel.

yuyichao commented on 2011-12-19 01:06

@MorningWood

You won't believe I once missed "gcc" (or "make", cannot remember clearly~~)~~~

MorningWood commented on 2011-12-19 00:58

....wow! Thanks yuyichao. I can't believe I missed that one hahah

MorningWood commented on 2011-12-19 00:56

nah, I have the patch right there in the lightdm folder.

lightdm-x11.patch

Unless there's something else that I'm missing.

yuyichao commented on 2011-12-19 00:20

@MorningWood LOL the problem seems to be you don't have patch (command)

@Morfeo Maybe you need to add patch ad makedeps~~

MorningWood commented on 2011-12-18 23:05

I keep getting the following error:
==> Removing existing pkg/ directory...
==> Starting build()...
/home/mxw/Downloads/lightdm/PKGBUILD: line 34: patch: command not found
==> ERROR: A failure occurred in build().
Aborting...

All of the base dependencies are installed (including gnome-common & gtk-doc). Don't know what I'm overlooking.
Running x64.

MorningWood commented on 2011-12-18 23:04

I keep getting the following error:
==> Removing existing pkg/ directory...
==> Starting build()...
/home/mxw/Downloads/lightdm/PKGBUILD: line 34: patch: command not found
==> ERROR: A failure occurred in build().
Aborting...

All of the base dependencies are installed (including gnome-common & gtk-doc). Don't know what I'm overlooking.

MorningWood commented on 2011-12-18 22:53

I keep getting the following error:
==> Removing existing pkg/ directory...
==> Starting build()...
/home/mxw/Downloads/lightdm/PKGBUILD: line 34: patch: command not found
==> ERROR: A failure occurred in build().
Aborting...

All of the base dependencies are installed (including gnome-common & gtk-doc). Don't know what I'm overlooking.

MorningWood commented on 2011-12-18 22:50

I keep getting the following error:
==> Removing existing pkg/ directory...
==> Starting build()...
/home/mxw/Downloads/lightdm/PKGBUILD: line 34: patch: command not found
==> ERROR: A failure occurred in build().
Aborting...

All of the base dependencies are installed. Don't know what I'm overlooking.

M0Rf30 commented on 2011-12-17 01:06

These latest releases of lightdm are not so gentle with us. There are a lot of little bugs that still waiting to be fixed.
I think I will not remove the apparmor related folder cause you can install apparmor from aur(also this package is not officially supported :))

Anonymous comment on 2011-12-16 22:33

Somehow I can't login with lightdm. Lightdm compiles and starts (by the inittab method), but if I select the Xsession (Xfce), and enter the username and password I just get a black, blank screen for about a second and then lightdm comes up again.

Does anybody know if this is a bug or if I'm doing anything wrong?

And, btw., it would be nice if /etc/apparmor.d/lightdm-guest-session could be removed from $pkgdir, because apparmor is not officially supported by Arch Linux. So this file and subdirectory are not needed.

Anonymous comment on 2011-12-11 11:37

As already noted by graysky: The package 'gnome-common' should be added as dependency, since 'gone-autogen.sh' is needed by autogen.sh.

yuyichao commented on 2011-12-10 22:57

and they are only makedeps I guess

yuyichao commented on 2011-12-10 22:55

~~~Ah, yes, you need some additional dev packages if you use ./autogen I believe at least gnome-common and gtk-doc (probably)

I remember now this is the reason I didn't ask for a new release to include the patch here~~~

speps commented on 2011-12-10 22:54

@Morfeo lightdm-crowd-greeter optional dependency is mistyped in PKGBUILD (i read light-crowd-greeter). Cheers

graysky commented on 2011-12-10 22:37

Missing a dep?

==> Starting build()...
patching file configure.ac
which: no gnome-autogen.sh in (/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/vendor_perl:/usr/bin/core_perl)
You need to install gnome-common from the GNOME CVS
==> ERROR: A failure occurred in build().
Aborting...

yuyichao commented on 2011-12-09 22:25

I think this is already fixed in trunk (at least lightdm-bzr) doesn't have the problem (probably without the patch altough I didn't check)

Well, probably ok to include it for now~~~

graysky commented on 2011-12-09 22:14

Nice, maybe Morfeo can add this patch and line to ./autogen to the PKGBUILD and update?

yuyichao commented on 2011-12-09 21:10

@graysky

well the patch in the bug report in @loafer's comment works (for me), but you have to also add ./autogen to PKGBUILD or ./confugure will not read ./configure.ac again~~~

https://bugs.launchpad.net/lightdm/+bug/898134/+attachment/2613513/+files/lightdm-x11.patch

graysky commented on 2011-12-09 20:30

patch?

yuyichao commented on 2011-12-09 20:00

@graysky no it is just a upstream bug in configure.in

graysky commented on 2011-12-09 19:58

Ack... missing a dep I think:


Making all in gtk
make[3]: Entering directory `/tmp/WORK/lightdm/src/lightdm-1.0.6/greeters/gtk'
CCLD lightdm-gtk-greeter
/usr/bin/ld: lightdm_gtk_greeter-lightdm-gtk-greeter.o: undefined reference to symbol 'XClearWindow'
/usr/bin/ld: note: 'XClearWindow' is defined in DSO /usr/lib/libX11.so.6 so try adding it to the linker command line
/usr/lib/libX11.so.6: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make[3]: *** [lightdm-gtk-greeter] Error 1
make[3]: Leaving directory `/tmp/WORK/lightdm/src/lightdm-1.0.6/greeters/gtk'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/WORK/lightdm/src/lightdm-1.0.6/greeters'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/WORK/lightdm/src/lightdm-1.0.6'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...

Anonymous comment on 2011-12-08 00:00

no problems here, just installed fine @ x86_64

loafer commented on 2011-12-06 05:53

The current version is failing to build:

Making all in gtk
make[3]: Entering directory `/home/dcm74100/lightdm/src/lightdm-1.0.6/greeters/gtk'
CC lightdm_gtk_greeter-lightdm-gtk-greeter.o
CCLD lightdm-gtk-greeter
/usr/bin/ld: lightdm_gtk_greeter-lightdm-gtk-greeter.o: undefined reference to symbol 'XClearWindow'
/usr/bin/ld: note: 'XClearWindow' is defined in DSO /usr/lib/libX11.so.6 so try adding it to the linker command line
/usr/lib/libX11.so.6: could not read symbols: Invalid operation
collect2: ld returned 1 exit status

I also found this:

https://bugs.launchpad.net/lightdm/+bug/898134

eworm commented on 2011-12-04 16:25

Or add "session optional pam_systemd.so" to make it work even if systemd is not installed. This way pam does not complain if pacm_systemd.so is not installed and accessible.

gdamjan commented on 2011-12-02 22:03

BTW, a note for anyone using systemd… you need to add "session required pam_systemd.so" in /etc/pam.d/lightdm so that ACLs are set correctly on /dev/ nodes (like /dev/dri/card0).

test0 commented on 2011-11-20 19:23

I had problems using lightdm and afterwards being able to poweroff/reboot and similar. Installing polkit-gnome did help. Maybe this comment helps someone. :)

eworm commented on 2011-11-17 17:32

Please add etc/pam.d/lightdm to backup=() array. Thanks!

Anonymous comment on 2011-11-13 07:40

@acrox999 .
no , i leave the xinitrc as it is , i just touch /etc/lightdm/Xsession, chomd +x /etc/lightdm/Xsession,
in the lightdm.conf , uncomment the "session-wrapper" and set it to the /etc/lightdm/Xsession,
i have no problem here.

acrox999 commented on 2011-11-12 16:21

Ok, got it. But the PATH problem still persist. Maybe I did it wrong. Did you overwrite the file to the xinitrc file?

acrox999 commented on 2011-11-12 15:44

@pomhg so how do I use that session-wrapper?

Anonymous comment on 2011-11-11 17:16

here's the ubuntu lightdm session-wrapper.
so far so good , no locale & PATH & xfce session-menu shutdown/reboot problems.

http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/lightdm/oneiric/revision/10/debian/Xsession#debian/Xsession
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/lightdm/files/Xsession?content-type=text%2Fplain&revision=1.1

Anonymous comment on 2011-11-06 18:33

the locale problem, i checked the archwiki about SLIM, i've got a way, hope this is helpful.
1.check out the 'locale' output
2.add them to the /etc/environment file.
3.then login with lightdm without locale issues.

maybe the PATH problem can be done like this too , i didn't try that.

Anonymous comment on 2011-11-06 01:38

A note on MilanKnizek's comment about the fix for the PATH var: if you don't need to use "ck-launch-session", lightdm already handles that for you, so it's just necessary, on the wrapper:

#!/bin/sh
[[ -f /etc/profile ]] && . /etc/profile
exec $1

Source: https://bbs.archlinux.org/viewtopic.php?pid=1006368

padfoot commented on 2011-11-05 01:39

Hi,

Re my earlier post, I have created a patch to add an onscreen keyboard to the gtk-greeter. It adds a menu item to the a11y menu in lightdm-gtk-greeter which launches the user's selected on screen keyboard based on the commands they put in /etc/lightdm/lightdm-gtk-greeter.conf

Of course, my C skills are limited, so someone may want to clean up the patch a little, but it does work without any issues on my system.

Patch can be downloaded here: http://home.exetel.com.au/padfoot/downloads/patches/lightdm-gtk-greeter.patch.tar.gz

Cheers.

Anonymous comment on 2011-11-04 10:00

I've added comment to https://bugs.launchpad.net/lightdm/+bug/783827 and until it's fixed, lightdm is pretty much useless for non-US localization.

Anonymous comment on 2011-11-04 09:58

I still have problems with locale. Anyone knows about it?

Here is what I have in my locale.conf:

LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=hr_HR.UTF-8
LC_TIME=hr_HR.UTF-8
LC_COLLATE=hr_HR.UTF-8
LC_MONETARY=hr_HR.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=hr_HR.UTF-8
LC_NAME=hr_HR.UTF-8
LC_ADDRESS=hr_HR.UTF-8
LC_TELEPHONE=hr_HR.UTF-8
LC_MEASUREMENT=hr_HR.UTF-8
LC_IDENTIFICATION=hr_HR.UTF-8
LC_ALL=

and it works with e.g. lxdm, but here is the locale output with lxdm:

LANG=
LC_CTYPE=
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=

graysky commented on 2011-11-01 19:27

Crazy :) Thanks for the explanation.

M0Rf30 commented on 2011-11-01 15:14

because 1.0.5 is a version released after 1.1.0. Honestly I misunderstood the developer's behaviour

graysky commented on 2011-10-31 10:25

Morfeo - why the downgrade?

padfoot commented on 2011-10-29 05:16

For those interested, I have managed to patch lightdm to use an onscreen keyboard. I have an Acer Iconia Tab W501 with a native Arch install, Xfce and LightDM.

I have had a terrible time trying to get an onscreen keyboard working with most DM's (wanting to avoid GDM and it's myriad of dependencies as much as possible). Light DM is so much better (and configurable) for my liking.

I literally only added about 10 lines to the gtk greeter (modifying 2 files - the greeter by adding a callback and the ui adding the menu item) by adding a new callback to launch the keyboard from the a11y menu. Not being a c programmer, I'm sure my method of launching the keyboard will need to be tidied up, but the callback function itself is sound.

Currently it only launches Florence (I hardcoded for my own testing and simplicity purposes) but I am sure an extra key can be added to the lightdm-gtk-greeter.conf to customise the choice of keyboard.

The good thing about this method, is you only need to run the keyboard as root to configure it, and LightDM will use that config (in GDM I could not for the life of me get the keyboard out of the top left corner).

Anyway, if anyone is interested (a c programmer would be ideal) in developing a proper patch for the package, respond and I will gladly share the modified code.

Cheers.

M0Rf30 commented on 2011-10-22 15:23

I'll wait for a new minor upgrade to fix locales problems

M0Rf30 commented on 2011-10-22 15:22

Thanks to all of us

chenxiaolong commented on 2011-10-21 19:58

Forgot to mention that my PKGBUILD is based off of Morfeo's PKGBUILD. Thanks to Morfeo!

chenxiaolong commented on 2011-10-21 19:58

Ubuntu already has a session wrapper script that sources /etc/profile and /etc/X11/xinit/xinitrc.d/*

It's included in my lightdm-ubuntu-bzr package (https://aur.archlinux.org/packages.php?ID=53330).

The space in Exec line bug is also fixed in the BZR version.

MilanKnizek commented on 2011-10-17 18:57

Re. the missing /etc/profile environment: A possible workaround is to create a wrapper script:
$ cat /etc/lightdm/session-wrapper.sh
#!/bin/sh
[[ -f /etc/profile ]] && . /etc/profile
exec ck-launch-session $1

Make it executable and modify the /etc/lightdm/lightdm.conf:
session-wrapper=/etc/lightdm/session-wrapper.sh

It is probably not the best way, but works. (Not my invention, I have googled a bit.)

angelblade commented on 2011-10-15 18:33

Check Path and locales, don't support Spanish and my PATH was changed

Foucault commented on 2011-10-15 17:12

@allench it is the same issue with the path. The java executables reside in /opt/java/bin. Scripts /etc/profile.d/{jdk,jre}.sh are used to inject the path of these executables into $PATH. For some unknown reason lightdm does not source these scripts (or /etc/profile at all).

allencch commented on 2011-10-15 17:05

Once I am using lightdm, the java command will not be found. The java version I am currently using is jre 7-3. This does not happened in gdm.

eldermarco commented on 2011-10-14 14:58

Someone could create a customized theme for lightdm with Arch logo, etc. Unfortunately, I'm not an artist.. but, it's a good ideia, don't you? :)

yuyichao commented on 2011-10-13 11:55

@Foucault
You can find that in my previous comment (although there might be better way, not sure)

I simply use a session wrapper that set the locale and load the session.
(use the "session-wrapper" key in [SeatDefaults] section (or your Seat's section) in lightdm.conf)

Foucault commented on 2011-10-13 11:05

I have two different problems with it
1) locale is always set to POSIX and LANG is always empty.
2) PATH is wrong, I'm missing a whole lot of directories. Does it not load /etc/profile at all?

Has anyone found any workaround for these problems. As far as I understand they are pretty common, but I haven't found any decent/working solution for it :/

Anonymous comment on 2011-10-12 23:53

I'd change the 'background=/usr/share/backgrounds/gnome/Aqua.jpg' in 'lightdm-gtk-greeter.conf' to 'background=#000000' so that you don't depend on 'gnome-backgrounds' any more.
I also assume you can change the 'theme-name', 'icon-name' and 'cursor-name' options so that you don't require 'gnome-icon-theme' or 'gnome-themes-standard' either.

M0Rf30 commented on 2011-10-12 13:36

please give me some ideas for the default visual settings in lightdm.

padfoot commented on 2011-10-12 05:58

@ yuyichao

Last update wiped my lightdm.conf, this update created a .pacnew. Using yaourt on both occassions.

Go figure! :)

Cheers.

yuyichao commented on 2011-10-11 13:31

sorry my fault,
please delete etc/dbus-1/system.d/ from PKGBUILD ~~~~~~ sorry (not really matter, just a warning~~~)

graysky commented on 2011-10-11 12:46

I think you need to add an additional file which will allow lightdm premission to unlock gnome-keyring. For more, see my post here: https://bbs.archlinux.org/viewtopic.php?id=124457

$ cat /etc/pam.d/lightdm
#%PAM-1.0
auth requisite pam_nologin.so
auth required pam_env.so
auth required pam_unix.so
auth optional pam_gnome_keyring.so
account required pam_unix.so
session required pam_limits.so
session required pam_unix.so
password required pam_unix.so
auth optional pam_gnome_keyring.so
session optional pam_gnome_keyring.so auto_start

graysky commented on 2011-10-11 12:38

I think you need to add an additional file which will allow lightdm premission to unlock gnome-keyring. For more, see my post here: https://bbs.archlinux.org/viewtopic.php?id=124457

Here is the file you need to add:
$ cat /etc/pam.d/lightdm
#%PAM-1.0
auth requisite pam_nologin.so
auth required pam_env.so
auth required pam_unix.so
account required pam_unix.so
password required pam_unix.so
session required pam_limits.so
session required pam_unix.so
session optional pam_loginuid.so
session optional pam_ck_connector.so
auth optional pam_gnome_keyring.so
session optional pam_gnome_keyring.so auto_start

yuyichao commented on 2011-10-11 12:07

@padfoot

I am not 100% sure but I think this will be done by pacman automatically

@Morfeo

THX

padfoot commented on 2011-10-11 09:03

@yuyichao

+1

This update wiped my lightdm.conf

Perhaps it should install updated versions as lightdm.conf.pacnew if lightdm.conf has been modified???

Cheers.

yuyichao commented on 2011-10-11 00:52

could you please add
backup=(
etc/apparmor.d/lightdm-guest-session
etc/dbus-1/system.d/
etc/dbus-1/system.d/org.freedesktop.DisplayManager.conf
etc/lightdm/keys.conf
etc/lightdm/lightdm-gtk-greeter.conf
etc/lightdm/lightdm.conf
etc/lightdm/users.conf
)
to PKGBUILD?

Anonymous comment on 2011-10-10 19:58

It requires --with-greeter-session=lightdm-gtk-greeter in build() section (among ./configure options), otherwise won't find a valid .desktop file for startup (if not specified in main configuration file).

gdamjan commented on 2011-10-09 18:17

In order to compile it, I had to add
sed -i 's/lightdm-session//' tests/src/Makefile
just before make in the build() function of PKGBUILD

Then also, I had to configure
greeter-session=lightdm-gtk-greeter in /etc/lightdm/lightdm.conf, since by default it was searching for default.

FiX commented on 2011-10-08 23:32

make[3]: *** No rule to make target `lightdm-session', needed by `all-am'. Stop.
make[3]: *** Waiting for unfinished jobs....
CC status.o
make[3]: Leaving directory `/tmp/yaourt-tmp-fix/aur-lightdm/src/lightdm-1.1.0/tests/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/yaourt-tmp-fix/aur-lightdm/src/lightdm-1.1.0/tests'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/yaourt-tmp-fix/aur-lightdm/src/lightdm-1.1.0'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build lightdm.
==> Restart building lightdm ? [y/N]
==> --------------------------------
==>

yuyichao commented on 2011-10-08 20:51

1.1.0 doesn't compile?

yuyichao commented on 2011-10-07 13:39

and please add
#show-language-selector=false (or true)
in lightdm-gtk-greeter.conf

yuyichao commented on 2011-10-07 13:38

@solstice I have the same problem and I temporarily use a session wrapper to set my LANG

solstice commented on 2011-10-07 13:31

version 1.0.2 does not set LANG or LC_* and then I have no lcoale set when I login instead of the system wide fr_FR.utf8

gdamjan commented on 2011-10-07 03:23

/etc/lightdm/users.conf has an option:

hidden-shells=/bin/false /usr/sbin/nologin

but in Arch it should be /sbin/nologin

yuyichao commented on 2011-10-07 01:57

+ seems the cursor problem is also fixed at least in trunk for me. =D

yuyichao commented on 2011-10-07 01:57

it seems to be fixed in trunk and 1.0.2, please update.

dhave commented on 2011-10-03 02:52

I finally reverted to lightdm-0.9.7-1, which is working fine. I tried the fix mentioned in the bug discussion (copying /etc/pam.d/gdm-autologin to /etc/pam.d/lightdm-autologin and /etc/pam.d/gdm to /etc/pam.d/lightdm), but that didn't work for me on Archlinux.

graysky commented on 2011-10-02 13:54

@Morfeo - From the errors I get when I try to run this, it seems like you should add steps to create a "lightdm" user.
https://bbs.archlinux.org/viewtopic.php?id=127486

Something like: http://pastebin.com/JzHETsLm

graysky commented on 2011-10-02 13:50

@Morfeo - From the errors I get when I try to run this, it seems like you should add steps to create a "lightdm" user.
https://bbs.archlinux.org/viewtopic.php?id=127486

yuyichao commented on 2011-10-01 18:23

mee too

dhave commented on 2011-10-01 03:03

With v. 1.0.0-1, I'm getting this bug:

https://bugs.launchpad.net/lightdm/+bug/863630

Anybody else?

Weegee commented on 2011-09-30 12:58

I just don't get it.

>cross-desktop display manager
>depends on several GNOME packages and gtk3

Is there any chance that this will be changed? Dependencies on GNOME software are not really suitable for a "cross-desktop display manager", imo.

Blender commented on 2011-09-30 03:13

LightDM 1.0.0 got released a few days ago. Could you update the PKGBUILD?

Anonymous comment on 2011-09-17 22:56

Lighdtdm 0.9.7 version it's already in launchpad. Can you please update the package?

https://launchpad.net/lightdm

Anonymous comment on 2011-09-15 07:42

lightdm changes my language settings after login from german to english. Is there a fix ?

gdamjan commented on 2011-09-08 23:29

What's the pam config file that lightdm uses? /etc/pam.d/lightdm ?

ying commented on 2011-08-27 00:36

Please change minimum-uid=500 to minimum-uid=1000 in '/etc/lightdm/users.conf'!

Anonymous comment on 2011-08-16 04:13

Starting Lightdm with inittab?????

not
x:5:respawn:/usr/sbin/lightdm
nor

x:5:respawn:/usr/sbin/lightdm >/dev/null 2>&1

start the lightdm.

Anonymous comment on 2011-08-16 04:12

where should i put this
if [ -x /usr/bin/numlockx ]; then
/usr/bin/numlockx on
fi

to active numlock it the lightdm .
which of the etc/lightdm/{key.conf, lightdm-gtk-greeter.conf, lightdm.conf, users.conf}.

Anonymous comment on 2011-08-16 04:09

after installing LightDm from AUR. and Adding it to the daemon array in rc.conf. and after reboot the mouse pointer or X cursor, doesn't show.

Anonymous comment on 2011-08-14 06:55

You should add 'accountsservice' to depends or optdepends (required for the user list)

piotrek91666 commented on 2011-07-31 13:51

lightdm starts X with -novtswitch option.
/var/log/lightdm/:0.log says: "Unrecognized option: -novtswitch"
This probably is the problem.

piotrek91666 commented on 2011-07-31 13:50

lightdm starts X witch -novtswitch option.
/var/log/lightdm/:0.log says: "Unrecognized option: -novtswitch"
This probably is the problem.

Anonymous comment on 2011-07-29 19:31

Lightdm launched from systemd does not work. First of all the exec path is /usr/sbin/lightdm , not /usr/bin/lightdm. Second some unrecognized options in ./configure. Even after changing all of this lightdm fails to start. No idea whats wrong.

b9anders commented on 2011-07-17 18:35

In my case, it won't work when launched from /etc/profile (my preferred option) and when launched as a daemon, it eventually starts hogging my cpu something fierce, even though it is fine for the first while.

b9anders commented on 2011-07-17 00:49

Need to add some installation tips in the post installation notes, such as what to add in /etc/inittab to make it work and/or what daemon to add to rc.conf.

nbvcxz commented on 2011-07-16 18:57

thx for PKGBUILD update, but I found a regression. Lightdm 0.4.4 seems to ignore language settings. For example - starting XFCE from Lightdm in is English (should be in Polish according to my settings, and it was working ok till this upgrade). Could anybody confirm it or it just my case? (what is not usual I use systemd, but I don't think it conflicts with anything, because without lightdm X session starts with proper language)

nbvcxz commented on 2011-07-03 13:30

lightdm.service should have 0644 mode so can you change for the following line:
install -m644 ../lightdm.service $pkgdir/lib/systemd/system/

xiaq commented on 2011-06-19 12:22

Hi, here is the PKGBUILD for lightdm 0.4.0: http://pastebin.com/PEKbHPMA

Anonymous comment on 2011-06-09 02:29

I have the same question regarding themes

Anonymous comment on 2011-06-05 16:52

Where do I get themes for it? Will the "webkit" theme work without /usr/lib/ldm-webkit-greeter?

Anonymous comment on 2011-06-01 16:54

@logos: Flagging a package as out-of-date is usually sufficient.

logos commented on 2011-06-01 15:26

0.3.6 is out

Jristz commented on 2011-05-30 00:36

Package relationships
Depends on:
adduser
debconf (>= 0.5)
libc6 (>= 2.4)
libdbus-1-3 (>= 1.0.2)
libdbus-glib-1-2 (>= 0.88)
libglib2.0-0 (>= 2.22.0)
libpam-modules
libpam-runtime (>= 0.76-14)
libpam0g (>= 0.99.7.1)
libxcb1
libxdmcp6
upstart-job
Provides:
x-display-manager
Recommends:
lightdm-theme-gnome
xserver-xorg

logos commented on 2011-05-25 09:12

0.3.5 is out.

Anonymous comment on 2011-05-17 05:50

lightdm installs a file /etc/init/lightdm.conf. On Arch Linux and every other distro I know there's usually no directory /etc/init and the content of this file doesn't seem to be relevant. So I guess this file and directory should be removed from the package. If this file is really necessary then it should be moved to a different directory.

frigaut commented on 2011-05-16 03:00

the dep is not "xorg-xserver-xephr" but "xorg-server-xephyr"

kozec commented on 2011-05-01 17:45

dependency gnome-themes doesn't exists

cuihao commented on 2011-04-23 01:03

0.3.2 is out.

haawda commented on 2011-01-24 15:07

pkgconfig is in base-devel group, which should be installed by all AUR and abs users. So normally we do _not_ add it to the makedependencies.

aky commented on 2011-01-24 09:06

v 0.2.3 is out
https://launchpad.net/lightdm/trunk/0.2.3

aky commented on 2011-01-24 09:01

v 0.2.3 is out
https://launchpad.net/lightdm/trunk/0.2.3

inp3dance commented on 2010-12-19 10:41

Please add pkg-config to the makedepends line because it is needed to build lightdm. Also I recommend to add xorg-xserver-xephr as optional dependency because it is needed to run lightdm in test mode:

optdepends=('xorg-xserver-xephr: run lightdm in test mode' )

or something like this.

hussam commented on 2010-12-12 02:21

pkgname=lightdm
pkgver=0.2.2
pkgrel=1
pkgdesc="A lightweight display manager"
arch=('i686' 'x86_64')
url="https://launchpad.net/lightdm"
license=('GPL3' 'LGPL3')
source=("http://people.ubuntu.com/~robert-ancell/lightdm/releases/$pkgname-$pkgver.tar.gz"
lightdm
patch)
depends=('gnome-themes' 'gnome-icon-theme' 'libwebkit' 'dbus-glib' 'gtk2' 'libxklavier')
options=(!libtool)
makedepends=('gnome-doc-utils' 'gobject-introspection')
md5sums=('143cd786a28e93ed2728b0b4afe7068d'
'990fdeb198f2ef928274bde0b9d2df99'
'cbe35f43dc52048bf9980a9d648b808e')
build() {
cd $srcdir/$pkgname-$pkgver
./configure --prefix=/usr \
--with-dbus-sys=/etc/dbus-1/system.d \
--with-log-dir=/var/log/lightdm \
--with-config-file=/etc/lightdm.conf \
--with-xauth-dir=/var/run/lightdm/authority \
--enable-introspection=yes \
--sysconfdir=/etc --disable-static --libexecdir=/usr/lib/lightdm
make || return 1
}
package() {
cd $srcdir/$pkgname-$pkgver
make DESTDIR=$pkgdir install
mkdir -p $pkgdir/etc/rc.d
install -m755 ../lightdm $pkgdir/etc/rc.d
cd $pkgdir
patch -Np0 -i $srcdir/patch
}

wonder commented on 2010-12-11 00:04

http://people.ubuntu.com/~robert-ancell/lightdm/releases/

tydell commented on 2010-12-05 14:53

I can confirm. I have all this problems in my system, when using lightdm.
The system variable $PATH returned to default in my opinion. It doesn't have all paths when using lightdm. There is no /sbin and /usr/sbin, so some commands are not available. Its problem with /etc/profile indeed.
It would be nice to use good working lightdm.

nbvcxz commented on 2010-12-05 13:05

Although I just tested lightdm and it seems that I can not have it at daily use. It could be hard to explain the bug (because I still can't figure what part of system it concerns). Symptoms are as the following (at ArchLinux):
1. no account have
2. although I am in wheel group I can not sudo any programs (everything go back ok with other dm), similar situation with other groups eg. audio (I have no rights for using gstreamer mixer)
3. some commands (from /sbin /usr/sbin) are unavailable - seems that commands from /etc/profle are not executed
Can anybody give me a clue what could be the reason of that strange behavior of lightdm (other dms: slim, lxdm works perfectly)

Anonymous comment on 2010-12-04 21:10

Lightdm doesn't fork by itself and so /etc/rc.d/lightdm gets stuck on [BUSY] forever. Bugfix: just add "&".
- [ -z "$PID" ] && /usr/bin/lightdm &>/dev/null
+ [ -z "$PID" ] && /usr/bin/lightdm &>/dev/null &

nbvcxz commented on 2010-12-01 14:15

is it possible to compile without gnome-doc-utils ?

wonder commented on 2010-11-30 15:25

mv $pkgdir/usr/etc/* $pkgdir/etc/
rm -r $pkgdir/usr/etc

kinda stupid. just pass the correct option to configure.

./configure --sysconfdir=/etc

M0Rf30 commented on 2010-11-30 13:28

solved and updated source with official repo
the problem was caused by gobject-introspection

M0Rf30 commented on 2010-11-30 12:41

I'm trying to resolve any compilation problem.

tydell commented on 2010-11-30 11:53

How to install it ? There comes some error about lightdmgreeter during make. And there is new version 0.2.2, but it can be change in PKBUILD. Anyway new version has the same problem during installation.
https://bugs.edge.launchpad.net/lightdm/+bug/683073

tydell commented on 2010-11-30 11:49

How to install it ? There comes some error about libdmgreeter during make. And there is new version 0.2.2, but it can be change in PKBUILD. Anyway new version has the same problem during installation.

piotrek91666 commented on 2010-10-21 12:25

I have error during compilation:

http://aur.pastebin.org/385009

miffe commented on 2010-10-21 05:24

During configure:
No package 'libxklavier' found

Please at it to depends.