LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 12-30-2004, 08:03 AM   #1
jtp51
Member
 
Registered: Dec 2002
Location: Omaha, Nebraska
Distribution: Ubuntu 8.10
Posts: 79

Rep: Reputation: 15
Dropline 2.8.2 causes font path element error in X Windows


Details:

Linux slackware 2.6.7
Dropline GNOME 2.8.2 update from applet
cdparanoia-IIIalpha9.8
perl-5.8.4
pilot-link-0.11.8
wget-1.9.1

Issue:

After using the applet to update Dropline to v2.8.2, I restarted my workstation, afterwards when I type 'startx'; I receive the following error message:

Quote:
(WW) ATI(0): Failed to set up write-combining range (0x40000000, 0x80000000)
Could not init font path element /usr/X1186/lib/X11/fonts/local/, removing from list!

Again, I only get this error when I try to start X. In the directory noted in the error (/usr/X1186/lib/X11/fonts/local/), I do have the following file:
Quote:
-rw-r--r-- 1 root root 2 2004-12-03 01:24 fonts.dir
Any suggestions or help would be greatly appreciated!

Thank you!
 
Old 12-30-2004, 02:05 PM   #2
shilo
Senior Member
 
Registered: Nov 2002
Location: Stockton, CA
Distribution: Slackware 11 - kernel 2.6.19.1 - Dropline Gnome 2.16.2
Posts: 1,132

Rep: Reputation: 49
THe font error is not what is causing X not to start. THat is simply a message telling you that there are no fonts in that directory. You can safely ignore it. The problem lies somewhere else in your /etc/X11/xorg.conf

What's the output of the following command?

Code:
cat /var/log/Xorg.0.log |grep "WW\|EE"
 
  


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! jeffreybluml Fedora 18 10-12-2011 08:06 AM
"Could not init font path element""Unix /: 7100 removing from list/ zameer_india Linux - Networking 7 07-03-2006 06:11 AM
Could not init font path element?? nu_us3r Linux - Newbie 4 08-25-2004 07:01 PM
could not init font path element - Xvfb harry349 Linux - General 16 08-15-2004 08:52 AM
Could not init font path element. Could not find default font "fixed" SidA Red Hat 0 06-19-2004 08:42 PM


All times are GMT -5. The time now is 08:57 PM.

Main Menu
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