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

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

Required by (47)

Sources (9)

Latest Comments

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

flan_suse commented on 2012-11-14 12:39 (UTC)

@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..."

<deleted-account> commented on 2012-11-14 12:23 (UTC)

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 (UTC)

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

<deleted-account> commented on 2012-11-09 09:10 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

This started after ConsoleKit was replaced with logind.

test0 commented on 2012-11-06 01:04 (UTC)

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 (UTC)

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?

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