Ubuntu
update-manager package

dapper to edgy need xorg font path remapping

Bug #73171 reported by gratefulfrog
12
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Medium
Unassigned
xorg (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Hi Ubuntu team!

I just upgraded to Edgy on AMD64 and discovered that my emacs and terminal fonts have changed. The terminal fonts seem to have become "bold" or at least thick, and the emacs fonts have become thin and tiny, very hard to see.

In general, this upgrade hasn't been easy, compared to the upgrade to dapper - I regret having moved so quickly - sorry to say that, I love Ubuntu and fully support !

thanks for any suggestions,
GF

Tags: edgy-upgrade
Revision history for this message
gratefulfrog (gratefulfrog) wrote :

following up on this issue, i discovered that the /etc/X11/xorg.conf file contains a long list of wrong font paths since the upgrade to edgy.

After inspecting all the paths, I changed the font paths to all point to:
/usr/share/fonts/X11/<font name>

instead of the old paths which were:
/usr/lib/X11/fonts/...
and
/usr/share/X11/fonts/...

Maybe this fix could be automated in the upgrade procedure?

I found the answer at this site:
http://www.ubuntuforums.org/showthread.php?t=268024

Revision history for this message
David F. Skoll (n9l4igznqrv0dhao) wrote :

I installed Ubuntu 6.10 and noticed that Tcl/Tk fonts looked *AWFUL*. The problem is that the xorg.conf file contained things like:

 FontPath "/usr/share/X11/fonts/75dpi/:unscaled

But it should be:

 FontPath "/usr/share/fonts/X11/75dpi/:unscaled

(Swap "fonts" and "X11")

You really should fix this, or all Tcl/Tk apps will look disgusting.

(Thanks for a terrific distro, by the way... I don't want to sound too negative.)

towsonu2003 (towsonu2003)
Changed in update-manager:
importance: Undecided → Medium
Changed in xorg:
importance: Undecided → Low
Revision history for this message
amichair (amichai2) wrote :

I'd just like to add that *AWFUL* is an understatement - this is not just cosmetics. At 1280x1024 with default settings, it's quite uninteligable. Luckily I found this bug report and the fix works. Will this at least be fixed in upgrading from dapper/edgy to feisty?

Revision history for this message
Bryce Harrington (bryce) wrote :

Does upgrading to Feisty resolve this problem or does it still have it?

Changed in xorg:
status: Unconfirmed → Needs Info
Revision history for this message
gratefulfrog (gratefulfrog) wrote :

No Upgrading to Feisty did not solve this problem. The fonts had to again be re-written by hand. This may be due to my previous intervention on the xorg.conf file - perhaps the installation process doesn't touch files that were updated by hand?

If that were the case, is there a procedure to return to an automated updating of the xorg.conf?

In any case, with Feisty, as with the previous release, I had to manually fix my xorg.conf file to get the fonts straight.

Bryce Harrington (bryce)
Changed in xorg:
status: Needs Info → Confirmed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

I'm closing this bug, since in gutsy you don't need any fontpath-settings in the xorg.conf, that's the default (the xserver has correct paths built-in). If you upgrade from a clean dapper the old entries should be removed.

Changed in xorg:
status: Confirmed → Invalid
Revision history for this message
Robert Pollak (robert-pollak) wrote :

Has anyone seen this bug recently? Timo's comment suggests that this bug should be fixed since Gutsy.

gratefulfrog, maybe you need http://vlogcanic.com/how-to-automatically-update-your-xorgconf-file-in-ubuntu-804-hardy-heron-97.htm

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

I'm closing the update-manager task because it has nothing to do with font management.

Changed in update-manager:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.