Package Base Details: lightdm-devel

Git Clone URL: https://aur.archlinux.org/lightdm-devel.git (read-only, click to copy)
Submitter: alucryd
Maintainer: None
Last Packager: dbirks
Votes: 280
Popularity: 0.000008
First Submitted: 2013-03-14 11:18
Last Updated: 2017-11-07 02:15

Latest Comments

« First ‹ Previous ... 3 4 5 6 7 8 9 10 11 12 13 ... Next › Last »

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?