Bug 3061 - Server crash rendering Taiwanese fonts
Summary: Server crash rendering Taiwanese fonts
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 6.8.2
Hardware: x86 (IA32) Linux (All)
: high critical
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords: want-backtrace
Depends on:
Blocks:
 
Reported: 2005-04-18 14:02 UTC by Jerry James
Modified: 2006-04-23 01:33 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jerry James 2005-04-18 14:02:45 UTC
Using the Fedora Core 3 packaging of xorg, I can repeatably crash the X server
on 3 different machines with the recipe below.  At the request of the Fedora
team, I am reporting the crash here (see Fedora bug 125973).  Note that I am
logging into the default locale; in particular, none of the locale environment
variables are set at all for the X server.

1) Start xfontsel
2) Choose foundry "arphic technology co.".  Note that after this step, the part
of the window containing the sample text has not been redrawn correctly.
3) Choose family "ar pl kaitim big5"
4) Choose registry "iso10646"

At this point, the X server segfaults.  Note that ftlint finds no problems with
the font file, which is /usr/share/fonts/zh_TW/TrueType/bkai00mp.ttf on my
Fedora machines.
Comment 1 Adam Jackson 2005-07-03 14:46:35 UTC
starting with the 6.8.99.14 snapshot, on linux systems, the X server can print
its own backtrace when it crashes.  please confirm that these bugs are still
valid with 6.8.99.14 or later, and if they are please attach a the server log
from the crash.
Comment 2 Adam Jackson 2006-04-04 23:49:01 UTC
reporter: does this still occur with 6.9/7.0 ?
Comment 3 Erik Andren 2006-04-23 18:33:11 UTC
Closing due to the lack of activity. Please reopen if you still have this issue
using a current version of xorg.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.