Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 433600 - [zh_CN] display is bad in KDE desktop
Summary: [zh_CN] display is bad in KDE desktop
Keywords:
Status: CLOSED DUPLICATE of bug 384631
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-20 09:19 UTC by A S Alam
Modified: 2018-04-11 18:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-21 18:21:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
screenshot of sys-config-display with date (deleted)
2008-02-20 09:19 UTC, A S Alam
no flags Details
xorg and xog.log (deleted)
2008-02-21 06:34 UTC, A S Alam
no flags Details
xorg.conf from the attachment 295485 (deleted)
2008-02-21 14:27 UTC, Matěj Cepl
no flags Details
Xorg.0.log from the attachment 295485 (deleted)
2008-02-21 14:27 UTC, Matěj Cepl
no flags Details

Description A S Alam 2008-02-20 09:19:05 UTC
Description of problem:
while running application in KDE desktop, it shows only Black strings instead of
character. It work for other application 'system-config-date'.
it works in gnome.

Version-Release number of selected component (if applicable):
system-config-display-1.0.51-5.fc9.noarch

How reproducible:
100% in KDE desktop

Steps to Reproduce:
1. export LANG=zh_CN.UTF-8
2. system-config-display
3.
  
Actual results:
showing Black string (screenshot)

Expected results:
should be clear character

Additional info:
Screenshot attened

Comment 1 A S Alam 2008-02-20 09:19:05 UTC
Created attachment 295409 [details]
screenshot of sys-config-display with date

Comment 2 Matěj Cepl 2008-02-21 00:23:00 UTC
Thanks for the bug report.  We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.

Also, are you sure, that system-config-display is really the only application
which presents itself with this problem? Does for example this URL
http://docs.python.org/lib/string-methods.html works without a problems for you
in Firefox?

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 4 A S Alam 2008-02-21 06:34:09 UTC
Created attachment 295485 [details]
xorg and xog.log

Comment 5 A S Alam 2008-02-21 06:35:43 UTC
> Also, are you sure, that system-config-display is really the only application
> which presents itself with this problem? Does for example this URL
> http://docs.python.org/lib/string-methods.html works without a problems for you
> in Firefox?
yes, screenshot showing 2 applications already!
and firefox was finew ith link


Comment 6 A S Alam 2008-02-21 06:50:03 UTC
surely different from another Intel machine, where it works fine.
this test report on AMD64 Machine

Comment 7 Matěj Cepl 2008-02-21 14:27:17 UTC
Created attachment 295509 [details]
xorg.conf from the attachment 295485 [details]

Comment 8 Matěj Cepl 2008-02-21 14:27:27 UTC
Created attachment 295510 [details]
Xorg.0.log from the attachment 295485 [details]

Comment 9 Adam Jackson 2008-02-21 18:21:51 UTC

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


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