Debian Multimedia :: Lightdm Login Screen Does Not Bring Up Lightdm-gtk-greeter Dialog Box
May 4, 2015
In Jessie the lightdm login screen does not bring up a lightdm-gtk-greeter dialog box but what seems to be some other one. I can increase the font size by modifying the /etc/lightdm/lightdm-gtk-greeter.conf file, but the login dialog box will not grow to accommodate the larger font (old eyes). The lightdm-gtk-greeter dialog box in Wheezy was a rectangle with a glyph of a console centered in its upper portion, and all the files I have examined indicate that this should be the same in Jessie, but instead the login screen in Jessie displays a narrower rectangle with a head-and-shoulder stylization off to the left.
Since I've made the switch to Systemd, I've been having various problems with LightDM.
The most interesting and frustrating problem is when I choose Shutdown or Restart from the XFCE4 shutdown menu, the XFCE4 session closes but then the lightDM greeter pops back up. The system doesn't even try to shut down.
Its as if restart and shutdown both act the same as the Logout button.
Im running XFCE4 4.12 (but same behaviour on 4.10). I have the latest LightDM and the latest Systemd.
System is Wheezy 7.9 with lightdm and MATE desktop.
I have 128GB SSD with various partitions for operating systems and a separate HDD for the /home folders for each OS. Wheezy is my primary system, the others, apart from the original XP are experimental.
/etc/lightdm/lightdm-gtk-greeter.conf is Code: Select all# # background = Background file to use, either an image path or a color (e.g. #772953) # show-language-selector (true or false) # theme-name = GTK+ theme to use
The problem is that each time I use the Ubuntu system and I change back to Debian, the greeter background contains snippets of whatever was displayed while I was in Ubuntu. What I don't understand is how this can happen, given that the operating systems are installed in separate partitions with separate /home partitions as well. After I have used Debian and restart, the greeter screen is clear, as it should be.URL....
I'm trying to login as guest, but this option does not seem to be available even after changing the LightDM configuration file. I'm on Debian Wheezy + XFCE 4.8. My /etc/lightdm/lightdm.conf looks like this:
I have Debian 8.4.0 with lightdm. I'm trying to load some command lines at session startup, putting these in ~/.profile but the file is not loaded. The same procedure works well if I switch lightdm to gdm3.
Anyway, there is some idea to load some script lines at the session startup? The file .bash_profile neither works. I don't want to use ~/.bashrc because it would load every time I open a terminal. Neither to use init.d because it would load for all users.
I'm working on embedded debian. I do configuration to lightdm for autologin. My device start with autologin but sometimes I see login screen. ı will try it more than 20 times. 17 times its do autologin 3 times not do autologin and show login screen.
I have an odd issue -- fairly fresh Debian Testing install, using Lightdm.
After booting up, Lightdm starts, and then a moment or two later restarts. As a result, any keystrokes captured by the first run (e.g. the first few characters of my username) are lost. My lightdm log is:
Code: Select all[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.16.7, UID=0 PID=827 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.00s] DEBUG: [SeatDefaults] is now called [Seat:*], please update this configuration
This log shows me seeing the login screen, waiting for it to restart, and then logging in correctly on the first attempt.
I installed debian 7 with lightdm and MATE 1.8 (from backports) on a new PC.
Since the first day the mose keeps disappearing. For example when I click on something, the mouse disappears and only comes back when I move it. Sometimes it already disappears when hovering over a button (especially annoying when it happens while you try to resize a window).
That problem did not happen for example in LXDE, which I installed just to test that.
I did install MATE 1.8 on several laptops/PCs so far, never hat that problem. Maybe it's because of quite recent hardware?
I'm using MATE with Lightdm as display manager in Jessie and I've been using a very simple script run from /usr/share/lightdm/lightdm.conf.d/01_debian.conf to slow down the mouse cursor, something like
Code: Select all#!/bin/bash
xinput --set-prop 10 269 -1
xinput --set-prop 10 267 1.100000 the script was placed in my ~ and called from 01_debian.conf , and so far it used to work.
Lately this script wasn't executed properly, most likely because I had unplugged the mouse from its usb port and then plugged again in a different port, and as a result Lightdm wouldn't start at all.
After much trying, because this by coincidence happened after the update to 8.4, I realized that it wasn't a serious failure of the X server as I suspected (the update included a new version of the flgrx driver), but a simple matter of Lightdm failing because of this script: in fact, I could still manually start the session with startx as regular user, although this only gave me access to a LXDE session instead of MATE (I have also the LXDE environment because when I installed Jessie I did use the LXDE version and then added MATE).
What happened was that the mouse properties were scrambled up, so xinput --set-prop 10 269 -1 had now to be something like xinput --set-prop 10 268 -1 and so on - therefore the script failed and in turns Lightdm failed as well.
-is this supposed to happen when you unplug the mouse and then plug it back in a different usb port? It reminds me of some windows-like behavior, where usb peripherals had to be always in the same port to work properly.
-is Ligthdm supposed to fail because of this, or is it kind of a bug? It looks weird to me that instead of simply not executing the script, the whole display manager fails.
In testing, with an identical setup, as a matter of fact the script failed as well (it's on another partition on the same hardware) but Lightdm started as usual.
-when trying to modify the mouse properties in that script, I couldn't get them right again: what looked correct in the booted system, was once again off at the next reboot (i.e. property 269 was 270 again and so on), therefore I ditched the above setup and placed everything in the .xsessionrc file, and it worked again.
-why startx defaulted to the LXDE environment? where is this setting stored? How could I have specified to start a MATE session instead from command line?
I just installed Lightdm from "bob"'s ppa, and it looks great when I run it from a virtual console (like Ctrl+Alt+F5), but how can I replace the gdm login manager with it? And when I do that how can I make ldm not register the Samba Guest User as an actual user? I am using ubuntu 10.10
I'm running Debian 8.4 on a Lenovo W500 laptop and I recently upgraded from kernel version 3.2.0-4 to 3.16.0-4. Since then I encounter issues with lightdm (I suppose) which manifest themselves in two different scenarios:
1) scenario 1: lightdm fails to start.Instead of showing the graphical login screen, the system boots into terminal. Lightdm seems to be running, but I can't enter the X-Session (Alt+Ctrl+F7 doesn't work), nor can I restart the lightdm via
Code: Select all# service lightdm stop # service lightdm start
dmesg shows the following (I've only pasted the end of dmesg): Code: Select all[ 240.100071] INFO: task kworker/0:2:39 blocked for more than 120 seconds. [ 240.106512] Not tainted 3.16.0-4-amd64 #1 [ 240.112956] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 240.119494] kworker/0:2 D ffff880155155a48 0 39 2 0x00000000
and /var/log/lightdm/lightdm.log shows errors of type Code: Select allGtk-CRITICAL: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed
when I then try to shutdown via Code: Select all# shutdown -h now
the OS gets stuck on a message of the form Code: Select allirq 17: nobody cared
and eventually I have to force a shutdown by holding the poweroff button.scenario 2: lightdm starts, but can't be stopped/In this case I can login and use the system as usual, but when I try to shutdown either via # shutdown -h now, or via the GUI or the power button, the system gets stuck and I have to force a shutdown by holding the poweroff button.It seems that people had similar issues on other distros (see e.g.: URL... but there doesn't seem to be a good fix so far. I can for now solve the issue by downgrading the kernel to 3.2.0-4, but I was wondering if there is a permanent fix.
Has anyone sucessfully got LightDM to work? If so how did you do it? I am running Ubuntu 11.04 with the Classic Gnome Desktop and would like to use LightDM instead of GDM... I have installed LightDM but nothing is different at all.
I have a laptop connected via HDMI port to different external displays throughout the day. I have configured the displays (Settings > Displays) to turn off the laptop display and set the external display as primary. However, this setting only takes effect after login. Thus, I am unable to see the login screen greeter on my external display because I close the laptop lid, so I am logging in blindly to a gray login screen background.
he issue I am facing is that when I start the laptop with an external display connected, the greeter only appears on the laptop display. The gray login screen background image spans both laptop and external displays and my mouse pointer appears on both displays, so I know both displays are detected and configured as dual displays. But, I am guessing, the laptop display is set as primary while the external as secondary.
I would like to know if there is a way to dynamically switch the greeter between the two displays, regardless of which one is set as primary and secondary. Or, is there a way to configure the system such that if there is an external display connected via HDMI, then it is set as primary, and if no external display is connected, then the laptop display is set as primary?
I have searched all over the net and this forum to no avail. I read a post which required copying the user's ~/.config/monitors.xml file over to /var/lib/gdm/.config/ but this caused my laptop monitor to be turned off at login even when there was no external display connected.
Hardware: Acer Aspire 8730G, Core 2 Duo T9900, 8GB RAM, Nvidia Geforce 9600M GT. Software: Debian 8.4 Jessie, Gnome 3.14.1, Gallium 0.4 on NV96 (I am assuming this is the Nouveau driver)
Contents of the /etc/X11/xorg.conf file which I generated with the command "Xorg -configure" as root in console mode:
Some days ago (2015-09-28) I installed Debian testing amd64. Log in as a user failed and instead of the Gnome UI there was a sad face with the text: „Oh no! Something has gone wrong. A problem occurred and the system can't recover.
All extensions have been disabled as a precaution. Log out“.
The relevant output of journalctl (run as root) said:
etc/gdm3/Xsession: cannot connect to brltty at :0 - /etc/gdm3/Xsession: Service 'org.kde.kaccessibleapp' does not exist. - gnome-session: x-session-manager: WARNING: Application 'gnome-shell.desktop' killed by signal 5 - gnome-session: x-session-manager: WARNING: App 'gnome-shell.desktop' respawning too quickly - x-session-manager: Unrecoverable failure in required component gnome-shell.desktop
After some investigating, I found three work-arounds.
(1) Use gdm3-autologin: In /etc/gdm3/daemon.conf, remove the double crosses and insert own user name AutomaticLoginEnable = true AutomaticLogin = <own user name> Disadvantage: Only one user can have access to the Gnome ui. If you log out, you enter the gdm3 greeter and … see above.
(2) Turn off gdm3 by running 'systemctl stop gdm3' as root, log in into a terminal as a user and run startx.
(3) Install package lightdm and make it to the standard display manager with 'dpkg-reconfigure lightdm'. Disadvantage: Energy manager and screensaver settings of the Gnome control center are ignored.
The easiest way, however, especially if there are several users, is logging in via the gdm3 greeter.
I want to set the login to the old default of having to enter a username,password. I've tried to use the configuration editor to achieve this and have ticked the "disable-user-list" option under /apps/gdm/simple-greeter but it makes no difference, the greeter still starts with a user list. It appears that the default valuef TRUE for this function is overriding my choice, but I'm notre why. My next step appears to be to edit /etc/gdm3/greeter.gconf-defaults to change the default value. I haven't actually tried that yet so not sure if it would work but, even if it does, it doesn't seem a very elegant way of setting this up. Is there some simple way of changing the behaviour back to asking for username first?
I seem to remember the whole login process as being more configurable than it is now, with options to choose backgrounds, allow root accest finystem->administration->login_screen only gives a choice between selecting a user or automatic login of a particular user, with no further options available.On a general note, would the old method not be a more secure default than presenting an unauthorised user with a list of login id's to be tried?
I'm running Ubuntu Lucid Lynx (kernel 2.6.31-24). After booting, when the "pink screen" comes up, the login dialog doesn't appear for about a minute, and the KB and mouse are frozen. It takes another 30 seconds before the KB and mouse unfreeze and I can type in my password.
I installed the pam_face_recognition package to try out but decided couldn't get it working properly so removed it via YAST. Now when I boot up I get a pop up dialogue saying the login greeter widget is missing and to check my configuration. Clicking OK on the pop up drops me to the console login.
1 Debian Gnome3 does not create ~/.config/monitors.xml 2 according to dconf editor
the location is
and I tweaked, but no success.
[URL] .... method can be applied to GDM3 directory.
Since I have configured my x rortation only be xrandr command by shell init script, and never had configured by GUI setting, the monitors.xml was not created. When I done with GUI, the file is created as usual.
I searched on the internet and notice that the setup gui for changing gnome login screen is no longer available (e.g. gdmsetup does not come up with a theme that can change login screen theme.)What is the right way or where there may contain such information? I google but most of returned are prior 2.30.2, which is the version currently I am using.
How do you enable a login screen? When I turn on my computer I only get command line. When I log into root I can start my KDE desktop using startx. But if I log into any other user I get the following errorX: usser not authorized to run the X server, aborting.giving up.xinit: No such file or directory (errno 2): unable to connect to X serverxinit: No such process (errno 3): Server error.
I recently installed Debian 8 with the Xfce Desktop Environment, which uses the Lightdm gtk greeter as its login manager. My login screen at the moment looks something like this: [URL] ..... In particular, I still have the "grey person" as the default user avatar.
I have been unsuccessfully attempting to change my personal login avatar, following the advice on the Arch Linux wiki: [URL] .... I began by naming my desired avatar .face and saving it in my home directory. That didn't work, but I was not discouraged because the wiki mentioned that there were issues with the ".icon method". So I then installed accountservice, created a directory for my user, and saved my desired avatar as a 96x96 PNG named username.png in the appropriate directory (making sure that it had the necessary permissions, of course). That didn't work either...
After applying upgrades to debian 8.2 on a lenovo yoga3 notebook and a reboot I am not able to login into my GNOME desktop. The login screen stays black. If I press the power button to suspend I can see the login screen with default background for ~1 second before it turns black again. What can I do to fix this issue? Is there a way to login via terminal and do a rollback? Can I use my home folder an personal settings if i reinstall debian and keep the /home partition?
I'm running Squeeze with Gnome & GDM3. After 1 h my laptop automatically suspends while in the login screen (GDM3; so no user login). I want to prevent that, since this machine also has a server role. how this can be prevented?