similar to: lightdm 1.8.1 released

Unstable release in 1.8 series. Overview of changes in lightdm 1.7.2 * Fix incorrectly distributed guest-session apparmor data Overview of changes in lightdm 1.7.1 * Fix .pc file for liblightdm-qt5-3 * Add a new option "autologin-in-background" which lets an autologin happen in a second display while still showing the greeter. * Stop if fail to create default

This is the first release in the stable 1.6 series. This series will be maintained on the lp:lightdm/1.6 branch and trunk (lp:lightdm) will now be used for the unstable 1.7 series. Overview of changes in lightdm 1.6.0 * Allow VNC command to be specified in lightdm.conf * Register enums with QObject meta type system. https://launchpad.net/lightdm/+download -------------- next part

Second unstable release towards 1.6. Overview of changes in lightdm 1.5.1 * QLightDM: Add Qt5 version of the library: liblightdm-qt5-2 * QLightDM: Add some missing role names in UsersModel * QLightDM: Add a backgroundPath role to UsersModel * QLightDM: Fix potential crash in QLightDM::UsersModel closedown. * Improve guest session apparmor * Run each test in its own /tmp

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

First unstable release towards 1.8. 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

Another stable release... Overview of changes in lightdm 1.0.4 * Fix --enable-gtk-greeter=yes not working * Fix X sessions with arguments in Exec not working * Use previous session for automatic login or if greeter does not request one. * Correct ownership of ~/.Xauthority if upgrading from buggy version of LightDM that had it root owned. * Set default resolution

Hi, I made the switch from KDE4->XFCE, and because gdm takes more time than xfce to start I would like to replace it with lightdm. I installed lightdm, set it as default display manager and configured the gtk greeter. However, when I start I only get a black screen (x running) and nothing else happens. When I start it as root with the --test-mode argument, I get the following message: lightdm

With the retirement of Ubuntu 10.04 LightDM 1.0 is now no longer supported. I am currently supporting each LightDM release for as long as it is supported in an Ubuntu release [1]. If anyone wants to extend support for releases beyond this please let me know and I'm happy to pass maintenance of that branch to appropriate individuals. You can see the support status of each branch here:

I came across a race condition in lightdm greeter setup phase before the login screen is displayed (at boot time or after logout). I reported this also on Launchpad with more details (https://bugs.launchpad.net/lightdm/+bug/1172752), but to work on a proper fix, ideas on how to fix this would be welcome. During greeter setup "lightdm --session-child" is spawned twice. The first call to

Hi, I'm currently testing the XDMCP functionality of LightDM which seems to work flawless, however, there is one issue which I cannot resolve: The machine I am using for my setup is a dedicated machine running some VM's, these VM's don't have any graphics card associated and run headless and the only form of command is via a web interface or SSH. LightDM seems to use the

Does LightDM support multiseat setups? For example, I have a PC with multiple graphics cards, monitors, keyboards - used by multiple users concurrently. Will LightDM let me use one PC by many users concurrently (i.e. login screen on every monitor, allowing to start different sessions for different users). -- Tomasz Chmielewski http://wpkg.org

Hi all, I'm setting up an LXC container for Ubuntu 13.10 where the X server is started in the host on vt6. The unix socket and authority file are then mounted in the LXC container. I can start X sessions and applications from the container but I can't get LightDM to use this server. I would really like to have the container's LightDM/Ubuntu greeter to automatically start on this

The VNC server just listens to the appropriate TCP/IP port and then runs Xvnc which does the actual VNC communication. Ideally I'd be able to do the same thing for RDP then the daemon doesn't get any more complicated, and a bug in the RDP layer can't crash the server. I don't know enough about how NX works but I suspect we could do the same thing as for VNC and RDP. I'm

Hi all, I've removed two legacy features from LightDM: 1. lightdm-set-defaults This tool was created so that scripts could easily modify the LightDM configuration, in particular so packages could modify it on installation / removal. This is not required since LightDM 1.8 as you can now create a snippet of configuration in /etc/lightdm/lightdm.conf.d or /usr/share/lightdm/lightdm.conf.d.

Or how to avoid the whirlwind. Greetings everyone. I observe the coding of lighdm is well under way and I'm thinking the pressure to meet the releases of 11.11 is probably going to build without bounds. Is there time now to consider the inclusion of some of the more offbeat use cases? 1: Headless(no monitor, keyboard, or monitor) 2: True headless(no video card) but Xvfb. 3: No X but only

In light (pun not intended) of the announcement here https://wiki.ubuntu.com/MirSpec what does this mean for LightDM being a viable free desktop display manager. The diagram shows the system compositor as being launched by LightDM in much the same way X is, and the plan looks very much like what we would do for Wayland. Is MIR going to be a hard dependency? Is Wayland support going to be dropped

I want to say abut what I see. The Display manager should be desktop DE and WM independent also the same goes for linux distro. as you surly agree, for instance Openbox is fully appropriated among linux users and at this moment there is growing interest in matter of tilling Windows managers. So if lightdm wants to become the replacement of GDM , it is surly agreeable to add support for such. I

https://bugs.freedesktop.org/show_bug.cgi?id=96737 Bug ID: 96737 Summary: G98: LightDM 1 : 0 Nouveau Product: xorg Version: git Hardware: All OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org

Overview of changes in lightdm 0.9.6 * Only unlock displays if switched to from greeter * Make log file not system readable * Write ~/.Xauthority inside the session process so it cannot be hijacked * Set PAM_TTY and PAM_XDISPLAY when opening PAM session * Add VNC server support * Do not write ~/.dmrc and ~/.Xauthority as root. [CVE-2011-3349]

I've been using lightdm for about a year now and with all the versions I've tried, Gentoo prints a message about lightdm and xdm failing to stop if I reboot from the lightdm menu or the xfce4 menu. If I issue 'reboot' as root from an xterm within xfce4, lightdm stops fine. I couldn't find anything in the logs, but in which one of syslog-ng's logs should I look? I'm