CrunchBang Linux

JohnRulz

New Member

Registered: 2013-12-14

Posts: 4

"Failed to execute login command" (SOLVED)

Hello,
I have been using CrunchBang now for about 4 days, and I've done (what I consider) a remarkable job as a beginner linux user, solving the great number of problems I caused, thanks to the wonderful resources provided in this forum. That is, all but one problem,  which began at about 3 am this morning. When I attempt to login, I get the message you see in the title above.

Previously, using ctrl+alt+F1, purging slim, reinstalling it, then running startx will get me to the desktop. Now I think I managed to partially solve the problem (or maybe break it more), as all I need to do now is ctrl+alt+F1 and run startx. Don't ask me what I changed to fix it—I have messed with many things at this point, and I don't even know when that actually started working. I did reconfigure the xorg server, or at least I think I did. I am absolutely not out of disk space on any partition.

Before all this happened, I was fucking around with xkeybinds and xdotools, which were severely misbehaving with stuck keys. It turns out, xdotools and dvorak don't get along unless you explicitly setxkbmap dvorak. I added setxkbmap dvorak and xbindkeys to the autostart. I initially forgot an &, but that is fixed now. I had also been attempting to install redshift 1.8, before giving up and settling with 1.7.

Thanks in advance,
John

Last edited by JohnRulz (2014-01-06 03:22:57)

damo

#! gimpbanger

From: N51.5 W002.8 (mostly)

Registered: 2011-11-24

Posts: 4,442

Re: "Failed to execute login command" (SOLVED)

Have you searched the forums for "Failed to execute login command"? There are many posts that may help you (Search tool top right of page )

One common reason is that there is no space left on the drive due to enormous error logs

---

Artwork at deviantArt;  Iceweasel Personas;  SLiM #! Themes;  Openbox themes

JohnRulz

New Member

Registered: 2013-12-14

Posts: 4

Re: "Failed to execute login command" (SOLVED)

I did search the forums, and tried many of the posted solutions, to no avail. I ended up running a clean install.