Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 62918

Summary: 'gdk-pixbuf' incompatible with locale 'en_US.iso885915'
Product: [Retired] Red Hat Public Beta Reporter: Joachim Frieben <jfrieben>
Component: gdk-pixbufAssignee: Havoc Pennington <hp>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: skipjack-beta2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-04-07 17:32:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joachim Frieben 2002-04-07 17:32:18 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020401

Description of problem:
After a straightforward install of 'Skipjack 2', where the suggested default
language setting ('American English') has been retained, window title bars of
e.g. 'sawfish' or 'twm' remain empty.

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

How reproducible:
Always

Steps to Reproduce:
1. Log in to GNOME session
2. Choose 'sawfish' or 'twm' as default window manager
	

Actual Results:  Window title bars remain empty whereas they used to display the
name of the respective X client or some other useful information for previous
versions of Red Hat Linux including 'Skipjack 1'.

Expected Results:  Window title bars should display the names of the respective
X clients.

Additional info:

The '.xsession-errors' file exhibits the following error message: 'Gdk-WARNING
**: locale not supported by Xlib, locale set to C'.
Logging in to a GNOME session after explicitly chosing 'POSIX/C' as current
language (instead of the default 'en_US.iso885915'), the title bars behave
correctly.

Comment 1 Jeremy Katz 2002-04-07 19:56:03 UTC

*** This bug has been marked as a duplicate of 62844 ***