[solved] Can't login when using slim and awesome

iso · 2010-07-14 01:07:38

I have followed the setup instructions http://wiki.archlinux.org/index.php/Awesome3 and http://wiki.archlinux.org/index.php/Display_Manager and have added slim to the startup daemons.

I get the login screen, but get a "Failed to execute login command" message after attemping to login.

I have checked out the following links regarding the issue, but none of them solve the problem for me.
http://bbs.archlinux.org/viewtopic.php?id=53685
http://www.linux-solved.com/post/Solved … 38446.html
http://www.linuxquestions.org/questions … nd-736159/

Here are my files:

// .xinitrc
#!/bin/sh

exec awesome

// /etc/rc.conf
...
DAEMONS=(... slim)

// /etc/slim.conf
...
sessions      awesome, xfce4, icewm, wmaker, blackbox

Thanks for the help.

Last edited by iso (2010-07-14 04:13:01)

George.Harmony · 2010-07-14 01:18:58

I think because you have multiple options for DM;s in your slim.conf you will have to define them in you .xinitrc.

Mine looks like this

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
# The following variable defines the session which is started if the user doesn't explicitly select a session
# Source: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample

# Avoid relying on autolaunch to improvise D-Bus sessions for each process
if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
    eval `dbus-launch --sh-syntax --exit-with-session`
fi


case $1 in

Terminal)
    exec terminal
    ;;
Compiz)
    stalonetray &    
#    xscreensaver -no-splash &
    batti &
    syndaemon -t -i 2 &
    alltray gnome-alsamixer &
    compiz --replace ccp &
    conky &    
    osmo &
    nm-applet --sm-disable &    
        exec ck-launch-session /home/arch_owner/.config/adesk-menu/adesk-menu 
    ;;
Browser)
    stalonetray &    
    batti &
    volwheel &
    compiz --replace ccp &
    conky &    
    osmo &
    nm-applet --sm-disable &    
        exec ck-launch-session /home/arch_owner/.config/adesk-menu/adesk-menu
    ;;
*)
    stalonetray &    
#    xscreensaver -no-splash &
    batti &
    syndaemon -t -i 2 &
    alltray gnome-alsamixer &
    compiz --replace ccp &
    conky &    
    osmo &
    nm-applet --sm-disable &    
        exec ck-launch-session /home/arch_owner/.config/adesk-menu/adesk-menu      
    ;;
esac

# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
# exec xterm

As you can see I have an option to laucnh a Terminal only session, my Compiz session, A browser session (which I use mostly as a testing entry and my default setting which is the same as my compiz entry.

The *) one is my default one. The one chosen if I don't press a key combination. (can't recall it right now) so I think you will at least need one that looks like this.

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
# The following variable defines the session which is started if the user doesn't explicitly select a session
# Source: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample

case $1 in

awesome)
    exec awesome
    ;;
*)
 exec awesome
    ;;
esac

# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
# exec xterm

Last edited by George.Harmony (2010-07-14 01:21:50)

iso · 2010-07-14 01:29:19

I removed all the sessions WM's except awesome, but still get the same thing result when logging in after a restart.

# /etc/slim.conf
sessions awesome

George.Harmony · 2010-07-14 01:43:51

The slim.conf sessions are what is called by alt+f1 (i logged out to find the key combination for you) you have to have the corresponding entry in your .xinitrc for it to run. I think if you are not going to have multiple sessions you would just comment out the sessions part of the slim.conf all together but I am not sure.

You can try the Slim Wiki for more info. Thats how I managed to get mine set up correctly.

Last edited by George.Harmony (2010-07-14 01:44:57)

jasonwryan · 2010-07-14 02:30:51

Are you getting any errors in your Xorg log? What happens if you switch to TTY1 and login there? Are you dual-booting?

iso · 2010-07-14 04:12:24

I installed it on a different computer and it works fine. The previous computer was a VMWare virtual machine.

Thanks for the help.

Arch Linux

#1 2010-07-14 01:07:38

[solved] Can't login when using slim and awesome

#2 2010-07-14 01:18:58

Re: [solved] Can't login when using slim and awesome

#3 2010-07-14 01:29:19

Re: [solved] Can't login when using slim and awesome

#4 2010-07-14 01:43:51

Re: [solved] Can't login when using slim and awesome

#5 2010-07-14 02:30:51

Re: [solved] Can't login when using slim and awesome

#6 2010-07-14 04:12:24

Re: [solved] Can't login when using slim and awesome

Board footer