Package Base Details: lightdm-devel

Git Clone URL: https://aur.archlinux.org/lightdm-devel.git (read-only)
Submitter: alucryd
Maintainer: ljmf00
Last Packager: dbirks
Votes: 281
Popularity: 0.000358
First Submitted: 2013-03-14 11:18
Last Updated: 2017-11-07 02:15

Latest Comments

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

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