Bug 478323 - problem with fonts after upgrading
Summary: problem with fonts after upgrading
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-28 04:09 UTC by Garrett Mitchener
Modified: 2018-04-11 13:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-10 14:45:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Garrett Mitchener 2008-12-28 04:09:10 UTC
Description of problem:

After upgrading from Fedora 8 to 10, xemacs and xfig and various other old X programs fail with error messages like these:

Unable to load any usable ISO8859 font
Unable to convert string to FontStruct

Version-Release number of selected component (if applicable):


How reproducible:
I think it happens when you install Fedora 6, then upgrade to 8, then to 10, something like that.

Additional info:

Several versions of Fedora relied heavily on xfs, and apparently f10 no longer does.  (Correct me if I'm wrong.)  I'm posting this here so maybe it will help someone else.

I was able to fix this particular problem by removing "unix/:7100" from the font path.  You can do this temporarily by running the command:

xset fp catalogue:/etc/X11/fontpath.d

To remove it permanently, I added a # to comment out this line from /etc/X11/xorg.conf:

#       FontPath     "unix/:7100"

I turned off xfs permanently by running

chkconfig xfs reset

I spent some hours looking through news groups and google results and such and never actually found a solution to this problem.  I hope this is the right way to fix it.

Comment 1 Matěj Cepl 2009-01-07 14:17:06 UTC
Yes, it is. I wonder why this wasn't picked up during the upgrade.

Could you also check that when running without any xorg.conf, you won't reproduce this bug as well?

Adam, did we do anything about upgrades from xfs-based configuration to non-xfs-ones?

Comment 2 Jonathan Kamens 2009-01-07 14:34:53 UTC
This problem happens to me with no xorg.conf.
When I try to run "xset fp catalogue:/etc/X11/fontpath.d", I get:

xset:  bad font path element (#23), possible causes are:
    Directory does not exist or has wrong permissions
    Dierctory missing fonts.dir
    Incorrect font server address or syntax.

I have no idea what this means or how to fix it.

This system was upgraded.

Comment 3 Garrett Mitchener 2009-01-07 15:34:17 UTC
(In reply to comment #1)

> Could you also check that when running without any xorg.conf, you won't
> reproduce this bug as well?

I moved my /etc/X11/xorg.conf to another directory and started X.  xemacs and xfig work fine, so it seems that the problem goes away on my particular machine without xorg.conf.

Incidentally, several different things seem to have gone wrong when I upgraded my three machines from f8 to f10.  My laptop exhibited this font problem but not my home desktop -- go figure.  I just upgraded my workstation last night and I'll have to get back to you about that once I've fixed some of its other issues.  The script to switch from xfs to the catalogue: font system might be working fine and this problem might really originate from a bug in yum or anaconda or rpm that causes something else not to run, etc. and I have no way to figure that part out.

But I'm puzzled: Why don't the fonts work through xfs?  They certainly used to...

Comment 4 Bug Zapper 2009-11-18 10:35:26 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Garrett Mitchener 2009-12-10 14:45:53 UTC
I haven't seen this in a while.  I'm going to assume it's either fixed or irrelevant as of F12.  I'll mark it Closed / Current release (is that the right tag?)


Note You need to log in before you can comment on or make changes to this bug.