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
View 9 Replies
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.
View 2 Replies View RelatedI'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:
[SeatDefaults]
#xserver-command=X
#xserver-layout=
#xserver-config=
xserver-allow-tcp=false
#xdmcp-manager=
#xdmcp-port=177
[Code] .......
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.
Autologin error log.URL...
Autologin log.URL...
Lightdm.conf. URL....
I'm tried lots of autologin lightdm document. Bu i cant success for auto login.
View 7 Replies View Relatedyesterday i installed slim login manager on my computer (eee pc 1018p, ubuntu 11.04), and now it cannot get passed the ubuntu loading screen (with orange dots underneath) when booting. i tried booting into recovery mode and that didn't work either. i also left the computer trying to boot overnight and that didn't work.
basically, during this loading screen that should eventually bring you to the login screen, i can alt+tab to see the progress of the load. the progress is stuck on
Is there anything I can do from grub to remove slim?or, is there any way I can access my ubuntu partition and save all my files?
I've recently switch to Arch with Lxde, and I'm looking for a login manager. I want this to support a "guest" account, a user that can be logged on passwordlessly, but not just auto-login. I don't really want to use kdm or gdm, either.
View 5 Replies View RelatedHas 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.
View 6 Replies View RelatedSystem 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....
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:
USER: 'root' CPU: '98%' Command: '/usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch'
What this meant to be and/or how this could be circumnavigated?
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.
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 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?
Code: Select all00:02.0 VGA compatible controller: Intel Corporation Device 041e (rev 06)
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?
Just been looking at an 11.04 bootable CD, where I was reminded of the continued existence of xfce. "Must try that again!" I thought, and installed it through the Software Centre on my 10.04 laptop. I washoping/expecting that xfce would then become an option in the Sessions pulldown at log-on, but no such luck. What should I be doing? It is not my intention to switch to xubuntu, just to take another look at an alternative window manager.
View 1 Replies View RelatedOk, I've tried Unity for awhile now and I can say it lacks a couple of critical things for me. First is launchers, second is a task bar. While casually browsing the web is ok, more serious work involving several windows has become a pain.
I have a dual screen with four virtual desktops. I'm tired of searching for my windows.
Now, I've read in a few places that I just need to choose "Ubuntu-classic" whenever I boot my machine. This is fine, but for the fact that I don't have any options on my login screen... Just the login and the accessibility & power buttons at the bottom right.
How can I log in using the old gnome display manager?
I recently upgraded from 9.04 to 9.10 and I have noticed an increase in loading time when logging in.What use to take less then 1 sec is now taking 3-4. It sometimes is able to start conky but most of the time it doesn't. When I manual run it after login in it has no problems starting.When I start a session with 9.04 I noticed it would go straight to fluxbox it would then take a few seconds to load conky and pidgin. When starting a session with 9.10 the loading seems to happen before the login manager passes control to fluxbox. When the login manager is finished pidgin is signed and ready, there is no more loading to be done.
Would removing the login manager and starting a session from the terminal be advisable? I only use fluxbox.
Since upgrading to 10.04 (from 9.10) 2 days ago, I have been getting an error message whenever I log in. It tells me that 'Power manager is still running' and gives me options of 'logout anyway' or 'cancel' (I'm writing this from memory, so may have got the wording slightly wrong). Clicking 'logout anyway', then continues with the login process, with no further problems (as an aside, I am running a desktop, so I'm not sure that Power Manager has much to do anyway.
View 9 Replies View RelatedSystem: Ubuntu 9.10, upgraded from previous versions
Architecture:64 bit
Filesystem:EXT4
DE:Gnome
Occurance of the problem: After using GParted to move unallocated space to a ntfs-filesystem. Yep. I did it again. No oops this time, for I have no clue why this error appeared and why I cant get to my desktop. No recent updates that couldve borked the system.Lately I have had to work quite a bit with some Windows-only programs, and I found myself out of harddisk space pretty soon, as for the last year or two, I worked almost exclusively with Ubuntu and only had a minimally sized partition set up for Windows. I needed room. No problem, I thought, I will start up GParted, move some of the unallocated space to the NTFS partition and be done with it. I have performed tasks like that before, so no problem should occur.
After rebooting I got to the grub menu. All options were there. Looks nice. Except for the fact that Windows did not want to start, some MSDK (sorry, did not write down the name) file or whatever was missing. (I heard this is a Vista problem and the file connected to the error does not even exist on any XP system). Worse than XP not starting was the error message I got from my login screen.
"The configuration defaults for gnome-power-manager have not been loaded. Please contact your administrator."
So I did. I talked to myself and had to admit to the user that I did not have a solution at hand. User upset, administrator too. (They are no longer talking to each other.) Login is accepted, but after that nothing. Just a black screen with a mouse-pointer that can be moved around. Nada mas. Before getting to the login screen, there was something else that drew my attention, but again, I did not know what it meant. The error-message:
fsck from util-linux-ng 2.16 is udevd [527]: NAME: "%k" is superfluous and breaks kernel supplied names, please move it from /etc/udev/rules.d/51-hso-udev.rules:124
* stopping the Firestarter firewall...
9.10: clean, 467963/3055616 files, 8323370/12205383 blocks
[code]...
SuperGrub. It allowed me to boot, but thats it. No further steps taken, if only because SuperGrub does not support the EXT4 filesystem (yet?).I have heard people were able to get to their desktop after receiving this error by using a root account they had previously created. I dont have one, so that would not work.So, I did the three finger salute, stopped the gdm from the terminal, moved gconfd to somewhere else, hoping a new file would be created and the problem would be solved with that, but no. Restarted gdm, it worked but the problem remained.
Ok. Perhaps a reinstall of the GDM might work, I thought. Well, it might, but the problem is I have no internet connection and the usual way I connect my laptop is through phone-tethering. Not having a desktop will not allow me to make a connection.So, sudo apt-get --reinstall install gnome-power-manager did not work as an active connection is required. Also I dont know if that is going to solve the problem.So now I am in the dark. I have booted up a live CD, mounted my HD partition in order to check my /root/.Xauthority, but I could not even find the file.
I refuse to believe there is a serious problem with my Ubuntu install. As far as I can see, there is a problem with some config-files but the system itself looks OK. Reinstalling is preferably not an option, as I love my install and have been working with it for a long time now, with lots of user data on it as well. Also, I have not seperated /HOME, which makes a reinstall a bit of a drag. I am certain there is an easy fix somewhere, someway, but I would need some advice from someone more knowledgable than I am. The only thing I could think of is to find a way to reinstall gnome-power-manager without an active connection. I can download the .deb file with some other device than my laptop but I would not know how to add that to /etc/apt/sources.list. Also, I kind of doubt that the problem lies within a faulty power-manager.
After running a backup script, but previously deleting old downloads and files from the rubbish bin, I then logged out. When logging back in later I got the Ubuntu loading screen as normal, but then instead of the Ubuntu login I got another login screen that I have not seen before; black background with the login screen in the middle.
I tried to login in, but all I got was an error message saying 'Install problem - The configuration defaults for Gnome power manager have not been installed correctly. I am running Ubuntu 10.04 and had a stable system.
I was playing around with the window managers (in XFCE) by clicking each one to see what each one looks like, then screen went black and kicked me the login screen. Now I cannot login to that user, after inputting password it just kicks me back to the login screen. I can login to another user and the terminal. How can I return to the default window manager using the terminal or is there a file I can delete that will automatically return to
View 3 Replies View RelatedI downloaded a theme from gnomeart, and in the readme it tells me to use "gdmsetup" to install it - however, when I try typing "gdmsetup" in the console, it says "command not found". How would I go about installing the theme?
View 3 Replies View RelatedopenSUSE 11.3 with KDE 4.4.4 release 2.I can change the desktop theme and the splash theme, but I can not change the KDM login manager theme.First, I changed th setting /etc/sysconfig/displaymanager DISPLAYMANAGER_KDM_THEME from suse to nothing in Yast -> /etc/sysconfig editor in order to get rid of the ugly Suse login theme.That resulted in having the traditional KDM login theme with the clock.I go to Personal Settings -> Advanced tab -> System: Login Manager (I enter the root password).In tab "General" I checked "Use themed greeter". Gui style and color scheme are set to default.In tab "Theme" I select a theme, click apply, then clikc ok.I log out and log in again. Nothing has changed. I still have the oldstyle KDM login theme.
View 3 Replies View RelatedI was trying to set up my Xfce desktop on a fresh install.
I personally dislike Xdm, which is given as the default login manager, and would prefer to use Slim instead.
It is possible to install it using the Package Search feature (it's listed under the Contrib repository), but I haven't been able to set it as the default login manager (I wasn't able to find such a setting in /etc/sysconfig).
I've been using kde environment in fedora 11 but I get the login screen gdm instead of kdm. Is there any way to change the display (login) manager from gdm to kdm.
View 3 Replies View RelatedIs it possible to bring KDM up after startup instead of tty1? Is yes, how?
View 3 Replies View RelatedAnyone recommend a good lightweight login manager? Been searching around online and I've found
Slim
Qingy
Orthos
Any others I should check out/anyone have input on any that I have listed? I'd prefer it to be graphical and have the option to select your session.
I had Slim working with the latest -Current updates, but that was with a package I built before updating.
I borked my system yesterday and had to do a fresh install. Now I can't get Slim working.
I tried running the Slim SlackBuild from Slackbuilds.org, and it failed without giving any errors. I figured out that the problem was with this section:
Code:
The strip commands were failing and caused the SlackBuild to exit, so I added '|| true' to them.
Code:
Not sure why this is needed in -Current and not 13, maybe because of Bash 4.1?
Anyway, now the package builds successfully, but Slim won't start. My system just hangs at a black screen after 'Starting up X11 session manager'...Has anybody been able to get Slim working in -Current?
