From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98) Description of problem: When I run startx from command line the screen goes black for about 30 seconds then it exits. It was working fine yesterday. I did install openoffice yesterday and restarted my computer today. Since I have been unable to start X. Version-Release number of selected component (if applicable): 4.3.0-55 How reproducible: Always Steps to Reproduce: 1. init 3 2. startx Added openoffice after installation using rpm. Actual Results: got X log to screen Expected Results: Startx startin Additional info:
Created attachment 101221 [details] message Log
Created attachment 101222 [details] Xfree 86 Config File
Created attachment 101223 [details] Xfree86 Log
This is a misconfiguration problem on your system in the core fonts subsystem. The error message you are seeing is a very highly frequently reported error message, however it does not indicate a bug in the X server or applications, but rather it indicates a font misconfiguration on your system. Sometimes these problems are caused accidentally by installing fonts by hand, and other times problems can be caused by incorrect file or directory permissions or ownership, or a variety of other reasons. According to your X server log, it is unable to connect to the xfs font server socket. This means the xfs font server isn't running, so it is unable to access core X11 fonts that are required in order for the server to properly start (cursor, fixed). Make sure that xfs is configured properly and configured to start at bootup time. Also make sure it is running currenty, and that there is plenty of space available in partition that /tmp writes to. If /tmp is full or near full when xfs tries to start up, then the xfs server can't create it's socket. Another possibility is that openoffice incorrectly installed fonts into a fontpath and damaged the font metadata files which are required for xfs to work properly. Rebooting your computer or restarting the xfs server should fix that in most cases, as our xfs initscript tries to reconstruct the metadata files as best it can. If it doesn't automatically solve the problem however, you'll need to troubleshoot your font configuration manually in order to resolve the problem. If you still have difficulty getting things working again, you may wish to subscribe to the fedora-list or xfree86-list Red Hat mailing lists for technical support. X.Org and XFree86 mailing lists are also quite helpful for working out these types of configuration issues, as well as searching for the error message on the Google search engine. Best wishes. Setting status to "NOTABUG"