Login fails to work

BruceJohnJennerLawso · 2014-04-11 03:00:43

Ah, so it appears that things have gone crunch and bang. yikes

I just recently got my C++ SFML projects up & running on Crunchbang, and was testing one of my programs which turned out to be a little unstable. The program locked up for reasons not related to the operating system, and I couldnt shut it off by clicking on the window close button. As a result I decided to shut down the computer & restart. After I did that Crunchbang started up fine, but when trying to log in, I get the "Failed to execute login command" message. I did check multiple times, so I am sure that the issue isnt a mistyped password.

Ive checked the contents of the crunchbang partition from my Kubuntu distro, and it appears intact. (or at least its still there, which is good) Beyond that I have no idea how to proceed, although I wonder if the original process is still causing problems. Is it possible that crunchbang went into a hibernation session like windows can do instead of completely shutting down?

Any help on this will be greatly appreciated. I desperately dont want to have to reinstall crunchbang if I dont have to.

damo · 2014-04-11 03:08:15

That error message is usually caused by not enough disc space left. Check the space available, and see if there is a huge error log eg .xsession-errors.

BruceJohnJennerLawso · 2014-04-11 03:10:29

damo wrote:

That error message is usually caused by not enough disc space left. Check the space available, and see if there is a huge error log eg .xsession-errors.

So, the error log is taking up all of the extra space on its own? I was a little short on disk space, but 800 mb is a lot for an error log to consume. Where am I looking for this file?

BruceJohnJennerLawso · 2014-04-11 03:14:47

Okay, found the file you mentioned, what do I need to do with it?

damo · 2014-04-11 03:19:10

Get rid of it! It will be created again the next time errors need to be logged.

What is causing the errors? You should fix that first really.

GTK errors are common, and quickly cause the error log to grow. I use a script in autostart to trim all but the last 100 lines of it.

BruceJohnJennerLawso · 2014-04-11 03:45:19

damo wrote:

Get rid of it! It will be created again the next time errors need to be logged.
What is causing the errors? You should fix that first really.
GTK errors are common, and quickly cause the error log to grow. I use a script in autostart to trim all but the last 100 lines of it.

Just wanted to ask first. Better to have waited than leaped without looking in this case.

That fixed it! In fact Im using crunchbang again right now. Bizarrely enough, when I queried the file size in Kubuntu, it told me 4.6 GB!!! I dont even know how that could be possible.

I'll try to hunt down the issue, but I have no idea what it really is. What exactly is GTK?

damo · 2014-04-11 04:09:50

gtk

"GTK+, or the GIMP Toolkit, is a multi-platform toolkit for creating graphical user interfaces"

The window themes you use (set by lxappearance) use gtk. There are different versions, and some themes don't keep up with new releases, which causes all kinds of errors. Major errors may stop a theme from displaying, minor ones just fill up your error logs. The theme I like does this - I could find a theme which is compatible, or live with it and empty the error log every time I start up

The most common error I get is

(geany: xxxx): GdkPixbuf-CRITICAL .......

because "gdk_pixbuf_get_width" no longer works properly. So every time the geany window starts or changes, an error is thrown up.

damo · 2014-04-11 04:17:27

From a crunchbanger (sorry, I forgot who posted this...)

#!/bin/bash
# Remove all but last 100 lines from .xsession-errors, if > 100KB

if [ $(du -b ~/.xsession-errors | cut -f1) -gt 102400 ]; then
    KEEP_LINES="$(tail -n 250 ~/.xsession-errors)"
    echo "$KEEP_LINES" > ~/.xsession-errors
fi

Make this executable, put it in your path, then add it to autostart. Mine looks like this:

## Tidy up .xsession-errors log
clean-error-log &

BruceJohnJennerLawso · 2014-04-11 19:22:09

damo wrote:

From a crunchbanger (sorry, I forgot who posted this...)
#!/bin/bash
# Remove all but last 100 lines from .xsession-errors, if > 100KB

if [ $(du -b ~/.xsession-errors | cut -f1) -gt 102400 ]; then
    KEEP_LINES="$(tail -n 250 ~/.xsession-errors)"
    echo "$KEEP_LINES" > ~/.xsession-errors
fi
Make this executable, put it in your path, then add it to autostart. Mine looks like this:
## Tidy up .xsession-errors log
clean-error-log &

Thanks, I'll try to get that set up in a little bit

I checked the source code & found the problem, the command for the C key that caused the issue was set up to request console input from the user (ie via cin), which blew up since the program wasnt running from a terminal instance. I'll have to see if I can force g++ to include a terminal instance when the program runs, or maybe just remember to run the program from a script that calls xterm to call the program, and so on...

thanks damo, thought I was fried there for a minute ops

CrunchBang Linux

SEARCH

#1 2014-04-11 03:00:43

Login fails to work

#2 2014-04-11 03:08:15

Re: Login fails to work

#3 2014-04-11 03:10:29

Re: Login fails to work

#4 2014-04-11 03:14:47

Re: Login fails to work

#5 2014-04-11 03:19:10

Re: Login fails to work

#6 2014-04-11 03:45:19

Re: Login fails to work

#7 2014-04-11 04:09:50

Re: Login fails to work

#8 2014-04-11 04:17:27

Re: Login fails to work

#9 2014-04-11 19:22:09

Re: Login fails to work

Board footer