You are not logged in.
Pages: 1
Now I figured this was the best place to put it. As I feel you guys are a bit more intelligent than some people. Anyway, so I recently obtained a mint Thinkpad T40. I installed Arch Linux on it, but I seem to have messed it up somewhere. I have AwesomeWM installed and SLIM login manager.
Problem is, when it starts up. It goes to the TTY1, then goes to the Slim screen. I am able to enter my name and password, but instead of logging into Awesome, it just stays at Slim. If I jump back into TTY and startx, it's running fine. Has anybody experienced any thing familiar? If so, how did you fix it?
Also if I posted this in the wrong section, I apologize. I just trust the opinions of the people here more than other forums
"You either die a hero, or you live long enough to see yourself become the villain." - Cyber Steve Jobs
Offline
Strange. I figured the Arch forums would be the best place. Anyways, let's see.....
So it basically sounds like a SLIM problem. Typical 
I'm not the best person to ask, but doesn't SLIM have a log file of some sort (slim.log probably)? Could you locate that and post its contents, for starters. Also might be worth posting your slim.conf, xinitrc and other (if any) init files you're employing. We'll need to narrow down whether SLIM is failing to launch X or just the wm.
Could be one of many issues. Maybe Xauthority related, d-bus daemon related, permission related..... but they all most probably lead to SLIM
Last edited by gutterslob (2012-10-09 03:54:37)
Point & Squirt
Offline
Have you got a ~/.xinitrc file?
This file should have;
exec awesomeSLIM needs this file 
or it could require an ~/.xsession file as per this infinite loop thread;
http://crunchbanglinux.org/forums/topic … nite-loop/
Have you read through the Arch wiki?
https://wiki.archlinux.org/index.php/SLiM
This thread might also be relevant;
http://crunchbanglinux.org/forums/topic … em-solved/
Hope this helps.
Not for me to say but as you are using Arch you should maybe try the Arch forums...
Let us know how you get on with the above suggestions.
Last edited by chameleon (2012-10-09 04:16:05)
Offline
You might also check this: https://bbs.archlinux.org/viewtopic.php?id=145146
There's a bug report about it ( https://bugs.archlinux.org/task/30864 ) and the solution, provided your ~/.xinitrc is correct and you've been checking slim logs ( $ journalctl /usr/bin/slim if you're using systemd, $ tail /var/log/slim.log otherwise ), would be to install slim-nock (Slim w/o Consolekit support) from the AUR
#Linux user 482038, eeepc 901 with 32GB Runcore SSD
Offline
Here's my .xinitrc code
#!/bin/sh
#
#~/.xinitrc
#
# Executed by startx (run your window manager from here)
DEFAULT_SESSION=awesome
case $1 in
awesome ) exec $1 ;;
*) exec $DEFAULT_SESSION ;;
esac
# exec gnome-session
# exec startkde
#exec startxfce4
# ...or the window Manager of your choice
exec awesomeAnd my slim.conf is way too much to type out, but I added awesome to sessions and it looks like
sessions awesome,xfce4,icewm-session,wmaker,blackboxI tried the xsessions and all that, yet it still hangs on the slim screen.
Last edited by Dyzphagia (2012-10-11 02:22:10)
"You either die a hero, or you live long enough to see yourself become the villain." - Cyber Steve Jobs
Offline
Got it fixed, forgot to enable the dbus daemon. Now I just feel silly
"You either die a hero, or you live long enough to see yourself become the villain." - Cyber Steve Jobs
Offline
Pages: 1
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.