One other thing to do:
chmod 1777 /tmp
I'm no expert, but it sounds like the error you mention is probably a socket/queue/pipe/whatever into a font server. If the font server daemon is already running, then it's not going to recreate that socket. Do the chmod above and reboot. Nothing in the /tmp directory is supposed to be permanent. That being the case, sockets are created when a process is launched to allow other process to communicate. Again, take that with a grain of salt, because I'm not an expert in the whole inter-process communication thing. It would seem pretty stupid to expect a permanent file inside a filesystem tree named "tmp".