Bug 64203 - can't change fonts in gtk apps
Summary: can't change fonts in gtk apps
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: xchat
Version: skipjack-beta2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact:
URL: http://bcjanes2.home.attbi.com/mm/bug...
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-29 06:09 UTC by Need Real Name
Modified: 2008-05-01 15:38 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2002-04-29 06:09:39 UTC


Attachments (Terms of Use)

Description Need Real Name 2002-04-29 06:09:35 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/20020417

Description of problem:
When trying to change the font in xchat, you can view all the fonts on the
system, but if you try to change it, it says it can't load the font, no matter
what font you choose. You also get the same error as other gtk apps load, but
they will run with the default font.

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


How reproducible:
Always

Steps to Reproduce:
1.Load xchat, or gvim. Error font not found dialogs pop up, but program loads.
2.Try to change font in settings menu. Can see fonts, seem to accept changes,
click on apply
3.Error, font not found appears, font doesn't change.
	

Actual Results:  Fonts won't change in gtk apps (xchat and gvim for sure)

Expected Results:  Fonts should change to selected font

Additional info:

If I launch a gtk app from console ie: #: up2date -i I get the following lines
then the app loads:
Gdk-WARNING **: locale not supported by Xlib, Locale set to C

Gdk-WARNING **: locale not supported by Xlib, locale set to C

Gdk-WARNING **: locale not supported by Xlib, locale set to C

Yes, it prints the line 3 times in the console before it loads any GTK app.

Comment 1 Mike A. Harris 2002-05-21 02:01:08 UTC
Beta-only problem fixed in final release, please upgrade to RHL 7.3.



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