[K12OSN] GDM login manager problem

[Peter Scheie]

To use KDM for the display manager but Gnome for the desktop, put this 
in /etc/sysconfig/desktop:

DISPLAYMANAGER="KDE"
DESKTOP="GNOME"

Then, at the console, make sure you are not logged in via the GUI--press 
Ctrl-Alt-F1 to get to a command prompt, login as root, and run 
/usr/sbin/gdm-stop.  This will stop gdm, but init will restart the 
display manager but it will be KDM this time.  Anyone who is logged in 
at a terminal or the console GUI when you do this will get kicked off, 
so you may want to do it after hours.

Petre

Meelis Mihhailov wrote:
> Hi all
>  
> My server has a strange problem. At the moment client login takes a long 
> time and same when they log out but when they are finlly logged in 
> everything works fine. Programs open an run as usual.
>  
> Looking at the messages log I get this :
> **********************************************************************************************************
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Failed to connect to 
> socket, not sleeping
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Trying failed command 
> again.  Try 2 of 5.
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Failed to connect to 
> socket, not sleeping
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Trying failed command 
> again.  Try 3 of 5.
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Failed to connect to 
> socket, not sleeping
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Trying failed command 
> again.  Try 4 of 5.
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Failed to connect to 
> socket, not sleeping
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Trying failed command 
> again.  Try 5 of 5.
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Failed to connect to 
> socket, not sleeping
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Command failed 5 
> times, aborting.
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]: Could not access 
> configuration key <daemon/DefaultSession=gnome.desktop>
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]: Using compiled in value 
> <gnome.desktop> for <daemon/DefaultSession=gnome.desktop>
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Failed to connect to 
> socket, not sleeping
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Trying failed command 
> again.  Try 2 of 5.
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Failed to connect to 
> socket, not sleeping
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Trying failed command 
> again.  Try 3 of 5.
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Failed to connect to 
> socket, not sleeping
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Trying failed command 
> again.  Try 4 of 5.
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Failed to connect to 
> socket, not sleeping
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Trying failed command 
> again.  Try 5 of 5.
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Failed to connect to 
> socket, not sleeping
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]:   Command failed 5 
> times, aborting.
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]: Could not access 
> configuration key 
> <greeter/Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,gdm,postgres,pvm,rpm,nfsnobody,pcap>
> Jan  4 08:52:37 terminalbackup gdmlogin[30067]: Using compiled in value 
> <bin,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,gdm,postgres,pvm,rpm,nfsnobody,pcap> 
> for 
> <greeter/Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,gdm,postgres,pvm,rpm,nfsnobody,pcap>
> **********************************************************************************************************
> and there is a lot more of that.
> I suspect that it has something to do with gdm bug and so I updated the 
> gdm to the latest releace that is out for FC5.
> This did not solve my problem. Login window has it's default login 
> stuff. Not k12 logo but GNOME logo.
>  
> So I googled a lot and cryed and finally found some info that I can 
> change my login manager to something else but still manage to use GNOME 
> as my desktop.
> I would like to try this with my clients but where can I find the config 
> where it's written what is my default login manager and where can I 
> change the values so that clients use the following method :
>  
> DESKTOP = GNOME
> LOGIN MANAGER = KDE (for example)
>  
> Any ideas ? :)
>  
> 
> Meelis
> ---
> meelis at nlib.ee <mailto:meelis at nlib.ee>
>  
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>