You are not logged in.
Pages: 1
Yesterday I left my computer at the slim screen all night because I typed reboot instead of shutdown (I don't know if this part matters).
But this morning, when I tried to login, it said "failed to execute login command". So I rebooted and tried again, still the same error. So I went to virtual console one and typed "xinit" as my user. It said it was already running in virtual console 0.
And now I'm stuck.
Last edited by cryticfarm (2009-08-08 19:07:21)
Offline
Hello Cryticfarm!
Can you show your ~/.xinitrc file ?
Offline
Sometimes slim.log eats free space at the partition.
Last edited by sirocco (2009-08-08 15:47:39)
Offline
Yeah, and a lock file of slim can cause this situation too.
Offline
My .xinitrc is:
exec nitrogen --restore &
exec pypanel &
(sleep 6 && exec devilspie) &
exec dbus-launch --exit-with-session openbox-session
And djszapi, what does the lock file thingy mean :\.
Offline
Is this when you "startx"? Or "xinit" it doesn't really matter. I think I got this and I had to "sudo startx" first, then Ctrl+Alt+F1 out, Ctrl+C and then "startx" normally.
Life in Linux: Ubuntu 8.10 > Mint 6 > Debian > Backtrack 3 > Arch Linux.
Offline
Well I just realized I was REALLY slim on space in my home partition, and I am fixing that now whether it fixes it or not.
EDIT:
Problem was fixed after I upped home partition size.
Last edited by cryticfarm (2009-08-08 19:06:58)
Offline
Pages: 1