Sign up ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

After some update and reboot, X fails to start.

I don't get any errors or warnings from the console, after the last service has started, nothing happens. I can then switch to any terminal I'd like, log in and start X with startx. This works perfectly fine. Prior to this there doesn't seem to be any attempt to start X (I removed the logs in /var/log/X* and rebooted, no logs were then generated after I logged in).

I'm now running 3.5.0-17-generic on Linux Mint 14 Nadia (XFCE). I'm using the proprietary Nvidia drivers (although bear in mind X starts perfectly fine with startx).

How can I make X start automatically again? What is the reason I experience this behaviour from the system?

Edit: I can add that I've tried to reinstall the proprietary Nvidia drivers (and they installed successfully), I get hardware acceleration and everything seems to work fine after I've started X with startx.

Second edit: I have S30mdm in /etc/rc2.d/ which points to /etc/init.d/mdm

share|improve this question
What is the output of cat /proc/cmdline? – Salem Mar 1 '13 at 0:23

4 Answers 4

sudo mv /etc/profile.d/ /etc/
sudo chmod a+rx /etc/

To .bashrc, add:

. /etc/
share|improve this answer
Can you please explain what the code does? – slhck Sep 24 '13 at 10:26
To make infinality started after mdm. I use this way to workaround this problem when I was using mint15 MATE – Rangi Lin Dec 1 '13 at 10:29

In some occasions Infinality font rendering can cause problems when loading the Display Manager.

If you have infinality installed and reconfiguring mdm doesn't works, try to:

sudo apt-get remove fontconfig-infinality

you can also reconfigure mdm as follows:

sudo dpkg-reconfigure mdm

this way it won't be necessary to install mdm again, task that may become hard

share|improve this answer

Fixed this issue with:

apt-get remove mdm
apt-get install mdm
share|improve this answer

I had this exact same problem, and none of the solutions here worked me. After many hours of struggling, and logs showing no errors, I found that my problem was (surprisingly) the result of an unrelated syntax error in /etc/profile.d/ Fixing my script fixed the issue for me.

share|improve this answer

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.