LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices



Reply
 
Search this Thread
Old 03-11-2004, 12:55 PM   #1
jeffreybluml
Member
 
Registered: Mar 2004
Location: Minnesota
Distribution: Fedora Core 1, Mandrake 10
Posts: 405

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


Hey linux gurus...

I have been unable to boot my fedora core, and as you can read in the post titled "fedora wont boot, displays nvidia splash screen over and over" I had origianlly thought it was an nvidia driver or card issue. However, when I recently typed "startx" from the command line (in runlevel 3) I found the following error message after it went to the nvidia splash screen and then returned to the command line:


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

Fatal server error:
could not open default font 'fixed'


So I commented out the line

#FontPath "unix/:7100"

in XF86Config and typed startx. Now, the splash screen comes on for only a moment (as it used to) and then it goes the the black X cursor that you see when booting right before you see the boot progress. I almost jumped out of my seat, as I though it was fixed. But after about two seconds it went back to command line, and shows the following error:

Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list!

/root/.Xclients: line 8: /root/.Xclients-default: No such file or directory
/root/.Xclients: line 8: exec: /root/.Xclients-default: cannot execute: No such file or directory


So, anybody have any ideas? I still a bit of a newbie, and I'm totally stuck here. PLEASE HELP!!!!
 
Old 03-11-2004, 01:39 PM   #2
jeffreybluml
Member
 
Registered: Mar 2004
Location: Minnesota
Distribution: Fedora Core 1, Mandrake 10
Posts: 405

Original Poster
Rep: Reputation: 30
fixed!

Thanks for helping everyone.

It turns out it was related either to the font path element or the "/root/.Xclients: line 8: /root/.Xclients-default: No such file or directory" error, because I commented out the 'FontPath "unix/:7100" ' from the XF86Config file, and copied my existing .Xclients-localhost..... file to .Xclients-default and EVERYTHING is fine again!!

Still dont understand what happened to cause all this, or what "all this" even was about, but for now I'm glad it's fixed.

This forum is such a great resource! What a lifesaver it has been for a guy trying to dump windows, but who has NO programming experience. Thanks to all!
 
Old 03-11-2004, 01:40 PM   #3
jharris
Senior Member
 
Registered: May 2001
Location: Bristol, UK
Distribution: Slackware, Fedora, RHES
Posts: 2,243

Rep: Reputation: 46
That kind of error message means that X can't talk to the font server it is expecting to find listening on port 7100. This either means you've not got an X font server (so shouldn't be trying to use it), or it's died.

cheers

Jamie...
 
Old 03-11-2004, 02:44 PM   #4
forrestt
Senior Member
 
Registered: Mar 2004
Location: Cary, NC, USA
Distribution: Fedora, Kubuntu, RedHat, CentOS, SuSe
Posts: 1,288

Rep: Reputation: 99
To restart if it is dead:

% /etc/init.d/xfs start

Hope this helps.
 
Old 03-11-2004, 03:43 PM   #5
flyfishin
Member
 
Registered: Aug 2003
Location: KC, MO
Distribution: CentOS, RHEL, SuSE, Fedora
Posts: 243

Rep: Reputation: 30
Quote:
Originally posted by forrestt
To restart if it is dead:

% /etc/init.d/xfs start

Hope this helps.
You can also use the service command to work with the scripts in /etc/init.d . So for xfs it would be:

service xfs [start|stop|restart]
 
Old 03-11-2004, 03:48 PM   #6
forrestt
Senior Member
 
Registered: Mar 2004
Location: Cary, NC, USA
Distribution: Fedora, Kubuntu, RedHat, CentOS, SuSe
Posts: 1,288

Rep: Reputation: 99
I guess I'm showing my age .
 
Old 03-11-2004, 04:11 PM   #7
flyfishin
Member
 
Registered: Aug 2003
Location: KC, MO
Distribution: CentOS, RHEL, SuSE, Fedora
Posts: 243

Rep: Reputation: 30
Quote:
Originally posted by forrestt
I guess I'm showing my age .
Refer to is as experience . I actually have you by about 2 months in the age department.
 
Old 03-23-2004, 04:58 AM   #8
EmilR
LQ Newbie
 
Registered: Mar 2004
Posts: 1

Rep: Reputation: 0
Lightbulb

Most likelly your harddrive is full

Emil
 
Old 04-09-2004, 01:00 AM   #9
fideli
Member
 
Registered: Nov 2003
Location: Mississauga
Distribution: arch linux
Posts: 51

Rep: Reputation: 15
hi.

i'm getting that "could not init font path element" on a number of my font directories, and i don't use xfs. the x server still starts, and actually i never realized the issue until one day when i logged in through the console and had to do a "startx" for a few minutes. when i came out i saw what it had output before starting the x server and there were around 7 or 8 directories that it could not init. any ideas?

fideli
 
Old 04-09-2004, 06:43 AM   #10
jeffreybluml
Member
 
Registered: Mar 2004
Location: Minnesota
Distribution: Fedora Core 1, Mandrake 10
Posts: 405

Original Poster
Rep: Reputation: 30
HI,

I was indeed out of disk space like one of the replies suggested, although it sounds like perhaps this is not your problem. Aside from confirming that the paths causing the trouble actually exist, and have write permissions, I'm not sure what to tell you.

Anyone else?
 
Old 04-10-2004, 01:44 AM   #11
jon-do
Member
 
Registered: Feb 2004
Distribution: Red 9, FC 2 Test 3
Posts: 98

Rep: Reputation: 16
I am not sure if it is the same but I had some problems with my font paths, actually I checked my /var/log/messages and I found this "xfs: ignoring font path elements .....'
after doing a search, I found a fix.
I just removed the path to the fonts and problem solved.
This is what I did for each path listed as not found, I typed as root
$ chkfontpath -l
whatever was not found I just removed the path
$ chkfontpath -r <name of font path not found>
 
Old 04-18-2004, 04:31 PM   #12
kwingate
LQ Newbie
 
Registered: Apr 2004
Location: Loa Alamos
Distribution: fedora core2
Posts: 15

Rep: Reputation: 0
try using port 7110 instead of port 7100. i did an update a while back and this fixed it.
 
Old 04-26-2004, 11:03 PM   #13
cutecute
LQ Newbie
 
Registered: Apr 2004
Posts: 4

Rep: Reputation: 0
Thanks very much!! I think i can fix it now, it's the usage of disk is 100% !
ok, now i'm using lynx to browser. it's blessing that this site can be browserd by lynx. now i rm all the file in /tmp/ any will try to startx after posting this reply...
 
Old 05-15-2004, 03:45 AM   #14
electronick
LQ Newbie
 
Registered: May 2004
Posts: 1

Rep: Reputation: 0
I have such trouble, xfs running, but X can't connect to fontserver. It occured then / (root partition) hasn't free disk space.
Sweep your / or bay new harddisk , .
#rm ~/.fonts.cache-1. (with old .font.cache-1 doesn't work)
#service xfs restart
#startx
 
Old 08-18-2004, 01:56 AM   #15
awassero
LQ Newbie
 
Registered: Aug 2004
Posts: 1

Rep: Reputation: 0
i have 30GB free on /

hello

i am having the same issue, when i type startx i receive the error message mentioned.

I dont believe the cause of my issue is disk space. i have a 60GB hdd. I checked with du and im only using 28GB. i checked fdisk and it shows the / slice is mounted to a partition with 58GB.

this issue didnt appear until I transplanted the hdd into a totally different box. everything uninstalled/reinstalled ok as far as i can tell and I have not noticed any issues other than with xserver.

thanks!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
"Could not init font path element""Unix /: 7100 removing from list/ zameer_india Linux - Networking 7 07-03-2006 07:11 AM
Dropline 2.8.2 causes font path element error in X Windows jtp51 Slackware 1 12-30-2004 03:05 PM
Could not init font path element?? nu_us3r Linux - Newbie 4 08-25-2004 08:01 PM
could not init font path element - Xvfb harry349 Linux - General 16 08-15-2004 09:52 AM
Could not init font path element. Could not find default font "fixed" SidA Red Hat 0 06-19-2004 09:42 PM


All times are GMT -5. The time now is 10:44 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration