similar to: Logout restart shutdown Script

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

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

I noticed a few days ago that my secondary login screen, usually accessible through the screen saver pop-up, was not coming up. All that showed was the cursor in the upper left corner of the screen. Yesterday, in an effort to see if a logout-login would clear this up, I discovered that the main screen (console 7) logged out with the usual text trails on the screen, but the login window never

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.

Greetings, I've been trying to get LightDM working on FreeBSD, as there is no package for it yet. I've managed to get it compiled from source, but it fails to start. It displays the message, "Failed to get D-Bus connection". D-Bus is running, and LightDM starts the X server fine. Is there anything I need to do to get it to talk to dbus? Right now I have LightDM installed in my

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:

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

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

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

light-locker 1.1.0 is now available for download from https://github.com/the-cavalry/light-locker/releases/download/v1.1.0/light-locker-1.1.0.tar.bz2 SHA1: df4c542449f457710628d19f14148afd43034a94 MD5: 0e643658fdde4dc0aefdc3c9c10898ca What is light locker? ===================== light-locker is a simple locker (forked from gnome-screensaver) that aims to have simple, sane, secure defaults

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

I'm the founder and lead developer of the lightweight Linux distro Swift Linux. I'm currently in the process of switching from the old antiX Linux base to the new Linux Mint Debian Edition base. The new Swift Linux will be using LightDM instead of SLiM. I've found that replacing LMDE's default GDM display manager with SLiM disables many functions (like audio). Restoring these

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

Hello, I need the possibility to login to other machines on my network. With kdm it works by choosing "Remote Login" from a menu in the greeter. I would prefer not to use kdm. ;-) I saw that the option "greeter-show-remote-login" should do that for lightdm. I work with a debian "wheezy/testing" system and installed the following packages from the

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

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

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

I've just recently switched from old ssh to OpenSSH 2. So far no major problems, until now. I'm logging in from Linux to Solaris 8. Both are running 2.9.9p2. Under ssh-1.2.28 I would fire off several xterms, exit, and properly get the "waiting for forwarded X11 connection" message, and then be able to type ~& (as documented) to get back to the shell. The channel was kept

How do you enable auto-login? I went into /etc/lightdm/lightdm.conf, uncommented autologin-user (and set it to = my login name), and uncommented autologin-user-timeout (and set it to = 0). Is there something else I missed? -- Jason Hsu <jhsu802701 at jasonhsu.com>