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
[code]....
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....
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.
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'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
[code].....
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.
Just made a strange discovery, visiting the website: [URL] .... with iceweasel within university's network makes my computer almost unusable. htop's output indicates:
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
[Code] ....
This log shows me seeing the login screen, waiting for it to restart, and then logging in correctly on the first attempt.
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 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:
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?
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[5379]: cannot connect to brltty at :0 - /etc/gdm3/Xsession[5379]: Service 'org.kde.kaccessibleapp' does not exist. - gnome-session[5379]: x-session-manager[5379]: WARNING: Application 'gnome-shell.desktop' killed by signal 5 - gnome-session[5379]: x-session-manager[5379]: WARNING: App 'gnome-shell.desktop' respawning too quickly - x-session-manager[5379]: Unrecoverable failure in required component gnome-shell.desktop
[Code] ...
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?
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'm looking for a script that copies a random .jpg from a random folder in my ~/Pictures folder to my ~/temp folder with a standard filename. This file will then be displayed in Conky. I can fix the last part, but I cannot find a way to do the first part.
I am running Linux from a DVD, not installed. I am not good with installing software, but since the DVD cannot be corrupted, I am content to operate this way. Lately, I have been having problems that previously did not occur. When I try to click on the checkbox to get rid of emails, it doesn't register in most cases, or when it does, I am clicking multiple times so it registers twice, meaning it is unchecked again. Even more frustrating is some issues that are affecting my ability to update my business. I am trying to modify spreadsheets (text not calculations).
Whenever I try to click & drag to select something to change, it keeps jumping around to select only some of what I want, something else or some combination of the 2. When I try to copy and paste several fields from 1 column to another, everything from the several fields in the source column ends up together in the last field in the target column. I am also trying to download some images from a website. There is a single column of links to the images. I have to click on the link to get to the image in order to copy it, then back out to continue looking for more links to do the same.
My computer keeps jumping back 2 steps, then forward 2 steps, and sometimes I lose my place in that list. I could deal with it if it were a small number of links, but this is a list of probably close to 20,000 links. Again, i am operating off of a live DVD so this should not be corruptible, but this has just started happening, and has been an issue the last several sessions.
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
using the update maneger to update on ubuntu new linux images available 2.6.31-17 generic and after the download is complete both images exist in the grub menu should i remove them ? or just remove them from the boot menu ? and if so how could i do each.
I have a dual monitor setup using TwinView running an up-to-date Ubuntu 11.04 amd64. The GDM (login) greeter is displayed in the center of the screen, and thus, one half of the greeter is on the left monitor and the other half is on the right monitor. I've been trying to find away to move the greeter to only one monitor. I've searched Google and the forums for an answer.
Here's what I've tried: 1) gmdsetup => does not have an option to position the greeter 2) gconf-editor => does not have an option to position the greeter 3) ubuntu-tweak => does not have an option to position the greeter 4) Tried these settings in /etc/gdm/custom.conf, /etc/gdm/gdm.conf, /etc/gdm/gdm.conf-custom, /etc/X11/gdm/gdm.conf: Code: [greeter] SetPosition=true PositionX=200 PositionY=300 5) Mucked around with /usr/share/gconf/schemas/gdm-simple-greeter.schemas , /usr/share/gdm/gdm-greeter-login-window.ui, /var/lib/dpkg/info/gdm.conffiles
My web server has Centos 5.3 installed and uses webmin for the administration.Recently the login hangs on a black background with the mouse animation.After a long time I get the message "The greeter application appears to be crashing. Attempting to use a different one."I click OK and the message just repeats.
The web server is running fine and all the applications are still active.I can access the server via SSH.Also, I can login via my vncserver from another computer and access the gnome and kde interfaces.
I know that ImageMagick's convert program can be used as follows to convert a collection of images -- say, in PNG format -- to a PDF file:
convert *png output.pdf
The problem with this is that each image is then stretched to fit on one page, whereas I would like to keep the original dimensions of the images and put as many as possible on one page in the PDF file before moving on to another page.
I have tested this on Ubuntu 10.10 64 bit many times . Use at your own risk.
1. Enter command in terminal.
Code:
sudo cp /usr/share/applications/gnome-appearance-properties.desktop /usr/share/gdm/autostart/LoginWindow 2. Close terminal and reboot .
3. Make changes to greeter box using appearance preferences by selecting a theme that supports color change . Use Customize > Controls > Colors to change colors of the box and text.
4. Close Appearance Preferences and log in .
5. Enter command in terminal.
Code: sudo unlink /usr/share/gdm/autostart/LoginWindow/gnome-appearance-properties.desktop 6. Close terminal and reboot .
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.
After today's update in Maverick, GDM showed no users in the greeter and so it was impossible to input any login info through the GUI, though Alt-F1 console worked. I re-installed GDM and a variety of other packages to no avail.
I found this same problem in an old OpenSUSE message: [URL]
Indeed, console-kit-daemon isn't running, and if I start it by hand and restart gdm, all is fine.
I also see the error message Error org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /lib/dbus-1/dbus-daemon-launch-helper: Success#012
in the logs. I also get a similar popup after logging in. It says "You might not be able to connect to the Bluetooth network via this machine."
I am just spent half an hour hunting for a thing that should be totally available already:USB install images of Ubuntu, knoppix and all the others.And, the only good way are so far complicated tutorials where you extract the stuff from an CD image. Why??Hasn't everybody notices that CDs/DVDs are vanishing big time? That more and more systems don't have the readers anymore? Instead of following a 10 point instruction list, it would be nice to just be able to download a Ubuntu 8.10 or whatever USB image and be able to beam that DIRECTLY to a USB stick with a dd command.
Or am a missing something here? Does this exist?It should by no means be mariginal, considering how important USB stick in specific and flash memory in general have become.
