similar to: Enabling auto-login

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

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

Hello, in the assumption that I understand them correctly I specified in /etc/lightdm/lightdm.conf autologin-user=xxxx autologin-user-timeout=10 so that after 10 seconds the user xxxx is logged-in automatically. What happens is that the user xxxx is logged-in immediately i.e. without any delay. Do I understand the second variable wrong or am I missing something? Thanks for any help. K.D.J.

Check out the Ruby on Rails page on my web site at: http://jasonhsu.com/ror.html I''ve included my procedure for installing Ruby on Rails in Linux Mint Debian Edition. That''s right, I''m no longer dependent on Ubuntu or Ubuntu-based Linux distros for developing Ruby on Rails applications. Linux Mint Debian Edition offers the smoothness and user-friendliness of its

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

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

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

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

Hello CentOS-Community, I have to maintain a server that should be useable with VNC and some software requires to run VirtualGL. Also a nvidia graphic card is installed. After downloading and installing the nvidia driver from nvidias homepage and modifying the xorg.conf as mentioned on the virtualgL-homepage, I am not able to restart lightdm anymore. Lightdm should be running, otherwise

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

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

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

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

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

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

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

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

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