You are not logged in.
Pages: 1
I just recently installed SLiM and it fails every time I try to login. I also can't get to console, so my question is how do I go about fixing this if I can't even seem to get a command line?
Last edited by brandon88tube (2009-11-08 18:11:59)
Offline
You can't get to console? Or you get there but your login fails?
Offline
press ctrl+alt+f1 for a non gui login.
Last edited by murfMan (2009-11-08 06:26:27)
Offline
press ctrl+alt+f1 for a non gui login.
That might be great and all for when and if I do a normal install, but right now I am running it as a virtual machine for testing purposes. By doing so, it fails to work in virtual box and kicks me out of my host linux and brings me to a command line login for it... this kicked me out of everything that was running at that time.
Offline
uh, Ctrl-Alt-F7 should bring you back to your X unharmed...
Ogion
(my-dotfiles)
"People willing to trade their freedom for temporary security deserve neither and will lose both." - Benjamin Franklin
"Enlightenment is man's leaving his self-caused immaturity." - Immanuel Kant
Offline
Well you can always boot into runlevel 1 (only root login, no services started) by appending '1' to your kernel line in grub. Alo, if you start X only in runlevel 5 (that depends on how you start slim) then you can also boot to runlevel 3 by appending '3'.
As far as slim failing, remember that slim only executes ~/.xinitrc after login, so make sure you have something sensible there (eg a command which runs your preferred window manager).
Offline
To clear things up some, as I forgot to mention, the error slim is giving me is "Failed to execute login command" and then it brings me back to the login screen. I also setup my file to read what was stated in the wiki since I'm using hal. exec dbus-launch --exit-with-session openbox-session.
Offline
Then most probably your home directory does not have a .xinitrc chmoded with 7xx (root does not have one by default) you can write one or copy it from /etc/skel in order to get the default one.
And to avoid that slim loads you can add 3 to the kernel line using grub or just pressing 3 in lilo.
Last edited by ezzetabi (2009-11-08 15:49:51)
Offline
Then most probably your home directory does not have a .xinitrc chmoded with 7xx (root does not have one by default) you can write one or copy it from /etc/skel in order to get the default one.
And to avoid that slim loads you can add 3 to the kernel line using grub or just pressing 3 in lilo.
I don't know what the chmod settings are, but I did copy over the .xinitrc file to my home directory.
Offline
Assuming it did not work, check its contents: does it start the desktop enviroment or the window manager?
Offline
And to avoid that slim loads you can add 3 to the kernel line using grub or just pressing 3 in lilo.
I though that works only if you use inittab method, not if you start it by adding it to DAEMONS in rc.conf.
"Chmod settings" are also called "permissions". .xinitrc needs to have to 'executable' permission set. You can achieve it by doing what ezzetabi suggested, namely run 'chmod 755 ~/.xinitrc'.
Offline
ezzetabi wrote:And to avoid that slim loads you can add 3 to the kernel line using grub or just pressing 3 in lilo.
I though that works only if you use inittab method, not if you start it by adding it to DAEMONS in rc.conf.
"Chmod settings" are also called "permissions". .xinitrc needs to have to 'executable' permission set. You can achieve it by doing what ezzetabi suggested, namely run 'chmod 755 ~/.xinitrc'.
Lol, I didn't mean I did not understand what chmod was, but that I did not know what I had it set at.
Offline
also in your ~/.xinitrc make sure you have one of the following uncommented
# exec gnome-session
# exec startkde
#exec startxfce4
exec openbox-session
# ...or the Window Manager of your choice
i think i had a similar problem
Offline
Take a look here http://wiki.archlinux.org/index.php/SLIM. It might be a Policy-Kit problem.
I am not stupid. I just have bad luck when thinking.
Offline
also in your ~/.xinitrc make sure you have one of the following uncommented
# exec gnome-session # exec startkde #exec startxfce4 exec openbox-session # ...or the Window Manager of your choice
i think i had a similar problem
I already stated that I was using
exec dbus-launch --exit-with-session openbox-session
I also changed the permissions to 755 and it still fails to login. I am lost as to what the issue is.
Offline
Well it seems that the wiki was wrong. I decided to try
exec openbox-session
by itself instead of what the wiki told me to run if I was using hal. This worked.
Offline
yeah i don't think you need to launch dbus if hal is already running.
Offline
Pages: 1