Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I recently had a problem with my Fedora Core 15 linux machine where something in my dotfiles got corrupted and caused a freeze on login from gdm such that the box would never get to the desktop. I've narrowed this down by creating a new user and logging in successfully.

I have nearly a hundred dot files with numerous lines of code in them. I wonder if there is a place to look or some debugging method which would help me pinpoint where exactly the gdm login process is dying when it hands off to the desktop?

share|improve this question
up vote 1 down vote accepted

The answer is pstree.

I had added a line to .bashrc to start tmux at the beginning of each bash session depending on a -z $TMUX. This was causing X to hang in between GDM and Gnome. pstree revealed the fault.

I'm answering my own question in case anybody else ever makes the same mistake I did.

share|improve this answer
I had this problem, I can confirm if for F16 and F17 as well. I removed my 'tmux list-sessions' from my .bash_profile and the problem went resolved. What are your thoughts on this? Do you think the problem is in tmux, or in gnome? THANKS – JeffG Jun 13 '12 at 1:31

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.