• Post Reply Bookmark Topic Watch Topic
  • New Topic

Can't start XWindows  RSS feed

 
Marilyn de Queiroz
Sheriff
Posts: 9082
12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So I'm editing my .bashrc and /etc/profile to add environment variables. I logout to make them go into effect and suddenly XWindows won't start any more.

The error message is:

Could not init font path element unix/:7100, removing from list!

Fatal server error:
could not open default font 'fixed'
1) I don't understand how this "font" disappeared.
2) Any ideas on how I can fix it?

(update)
I did a shutdown and a hard reboot.
If I type "/etc/init.d/xfs status"
I get:
"xfs dead but pid file exists"
So I type
"/etc/init.d/xfs start"
and I see
Starting xfs: [ OK ]
When I type
"/etc/init.d/xfs status" again I still see
"xfs dead but pid file exists"
"du: "proc/1059/fd/3' No such file or directory"
[ March 07, 2004: Message edited by: Marilyn de Queiroz ]
 
Ernest Friedman-Hill
author and iconoclast
Sheriff
Posts: 24217
38
Chrome Eclipse IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Generally this kind of thing happens when xfs can't create its UNIX domain socket file in /tmp. This can happen if the permissions in /tmp or /tmp/.font-unix are wrong, or if the partition /tmp is on is full, or maybe even if /tmp doesn't exist.
So first, check "df" and make sure that the disk isn't full up. It probably won't be, but if it is, make some room.
Did you add/change the TMPDIR environment variable in /etc/profile? This may affect xfs, depending on how things are configured. If you did, does it point to a real directory? If so, substitute that directory for /tmp in the below. If not, well, then it needs to, of course.
Otherwise, have a look at /tmp. Permissions for /tmp should look like
% ls -lad /tmp
drwxrwxrwt 41 root root 36864 Mar 8 09:17 tmp
And permissions for /tmp/.font-unix, if it exists, should look like
% ls -lad /tmp/.font-unix
drwxrwxrwt 2 xfs 102 4096 Mar 8 06:58 /tmp/.font-unix/
And a running xfs ought to be able to create a socket file in the above directory:
[ejfried@asllinux .font-unix]$ ls -la /tmp/.font-unix
total 40
drwxrwxrwt 2 xfs 102 4096 Mar 8 06:58 .
drwxrwxrwt 41 root root 36864 Mar 8 09:17 ..
srwxrwxrwx 1 xfs 102 0 Mar 8 06:58 fs7100
If you find that /tmp's permissions are wrong, fix them. If you find that .font-unix's permissions are wrong, just blow the whole thing away and try to restart xfs.
[ March 08, 2004: Message edited by: Ernest Friedman-Hill ]
 
Adrian Yan
Ranch Hand
Posts: 688
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Do you boot right into x-window? What environment variables did you change? Also, on your command line, do a startx and see what it tells you. Paste any error here so we can debug it easier.
 
Marilyn de Queiroz
Sheriff
Posts: 9082
12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Adrian Yan:
Do you boot right into x-window? What environment variables did you change? Also, on your command line, do a startx and see what it tells you. Paste any error here so we can debug it easier.

I don't boot right into x-windows. I created JAVA_HOME, J2EE_HOME, ANT_HOME, and J2EE_CLASSPATH.
 
Marilyn de Queiroz
Sheriff
Posts: 9082
12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Ernest Friedman-Hill:
Generally this kind of thing happens when xfs can't create its UNIX domain socket file in /tmp. This can happen if the permissions in /tmp or /tmp/.font-unix are wrong, or if the partition /tmp is on is full, or maybe even if /tmp doesn't exist.


The disk was full. However it wasn't tmp that was the problem, it was ~/ where I had downloaded the xxx.tar.gz files. When I deleted all the *.gz and *.tar and *.zip files, I was able to start xfs and then x-windows.

I wouldn't have thought that two or three large files would make such a difference.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!