@Mailyfesux: Argh. What ixtab said.
What did you try, in as much details as possible, and in what order? (ie. did you have custom fonts installed, if so how many and which ones, was the fontconfig cache up to date, etc.).
Also, where (when) in the boot process did it first start to go wrong, if you can tell (ie. tree, spinning circle, progress bar?)
EDIT: For the record, and if you don't have the rescue pack installed, the most conservative (ie. blasting the least amount of stuff) way to recover from this would be to:
1/ Disable the hack: delete
USE_ALT_FONTS and
linkfonts/auto
1b/ You might want to clear the
fonts directory, too.
2/ Reset the very, very annoying restart counter as described in the bottom of the page ixtab linked to.
For point 2/, if you don't have the rescue pack installed, all is not lost. Every startup script I write start by looking for an 'emergency' script, for just such an occasion. The fonts hack will try to launch
linkfonts/bin/emergency.sh. So just put the commands shown in ixtab's howto in there as a simple shell script (unix line endings), like so:
Code:
#!/bin/sh
rm -f /var/local/upstart/lab126_gui.restarts
rm -f /var/run/upstart/lab126_gui.restarts
# Hell, might need this too...
rm -f /var/local/upstart/x.restarts
rm -f /var/run/upstart/x.restarts
# Hai, PW2!
rm -f /var/local/upstart/mesquite.restarts
rm -f /var/run/upstart/mesquite.restarts