Bug 613082 - xterm crashes when changing fonts in rawhide
Summary: xterm crashes when changing fonts in rawhide
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server   
(Show other bugs)
Version: 14
Hardware: x86_64 Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-09 16:26 UTC by lethalwp
Modified: 2010-08-11 16:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-11 16:38:46 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description lethalwp 2010-07-09 16:26:58 UTC
Description of problem:
xterm crashes when changing fonts with the error:
xterm:  fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0.0"

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

How reproducible:

Steps to Reproduce:
1. open xterm
2. left shift + left alt +  "+" from numeric keypad, 3 or 4 times will result in the crash;   same if you ctrl + leftclick and change the fonts to "Huge" (some other settings may crash too)
Actual results:

Expected results:
bigger window

Additional info:

this seems to be font related,  when doing ltrace xterm:
(snip till the problem occured):
strlen("-Misc-Fixed-bold-R-*-*-20-200-75"...)    = 41
strlen("-Misc-Fixed-bold-R-*-*-20-200-75"...)    = 41
strcat("-Misc-Fixed-bold-R-*-*-20-200-75"..., "ISO8859-1") = "-Misc-Fixed-bold-R-*-*-20-200-75"...
XLoadQueryFont(0x219f650, 0x2203d40, 0x7fff72e8bc60, 2, 0 <unfinished ...>
__errno_location()                               = 0x7f508e0cf6e8
strerror(11)                                     = "Resource temporarily unavailable"
__fprintf_chk(0x7f508c82c860, 1, 0x44b108, 0x445262, 11xterm:  fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0.0"
) = 95
removeFromUtmp(84, 95, 0x7f508c82de20, 1, 0x7f508e0cf740 <unfinished ...>
--- SIGCHLD (Child exited) ---

Comment 1 Thomas E. Dickey 2010-07-12 09:09:37 UTC
In a quick check, I'm not seeing this break.

#261 doesn't touch anything related.  Perhaps one of the ongoing
changes I've made to reduce the use of the "term" variable (in
#260 for instance) is breaking.

Comment 2 lethalwp 2010-07-12 09:21:09 UTC
it was working well in fc13,  took the xterm.src.rpm from f13, and installed on this system,  problem remains.

It's more likely to be a Xserver, fontserver(/libs), or other lib problem.

How could i help debugging this? Can you confirm the crash on another rawhide system?

Comment 3 Thomas E. Dickey 2010-07-12 09:26:42 UTC
At the moment I have a f12 (64-bits), but am running Debian/testing (32-bits).
I can install f13 (perhaps tomorrow), and compare more directly.

Do you get a core dump from the crash?  A traceback from that would be helpful.

Comment 4 Thomas E. Dickey 2010-07-12 09:30:44 UTC
hmm - I finally see the f14 remark.  Perhaps you've not installed
the miscellaneous fonts package, and there's (still) a hole in the
checks for absent bitmap fonts.

Comment 5 lethalwp 2010-07-12 10:02:48 UTC
There is no coredump, but just the error:
xterm:  fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0.0"

when ltracing, the last relevant line is:
strcat("-Misc-Fixed-bold-R-*-*-20-200-75"..., "ISO8859-1") =
(before the XLoadFont)

when listing with xlsfont it looks i have no matching font with these requirements

I did a yum install of every package with font & bitmap included,
and also did a yum groupinstall of "Fonts" and "Legacy Fonts"

And to avoid user environment dependancies, i've tried with a newly created user

How can i find the required package (if it exists?)

Comment 6 Thomas E. Dickey 2010-07-12 10:53:25 UTC
yum has an option for listing available packages.

In my f12, I have this, which iirc contains the needed fonts:


Comment 7 lethalwp 2010-07-12 12:22:54 UTC
thx for your reply,

here are the xorg fonts installed:
 ~]$ rpm -qa | grep -i xorg | grep -i fonts

but also have plenty of others (152 packages with "font" & without ^xorg)

By googling the fontname, i'm not sure a fixed-bold-20-200 font exist at all,
it looks like xterm is inventing the name? Maybe it worked in f13 because of the 'non existant font protection', which rawhide now temporarily lacks, as you've suggested.

i think it could be locally fixed by adding a specific xterm font listing to xresources or whatever.

I'm not sure this is the correct way to do it

Comment 8 Thomas E. Dickey 2010-07-12 20:32:51 UTC
xterm asks the font server for that combination, and the font server
provides something (usually ;-).  Even if the font server cannot
provide, it shouldn't produce an error.

Comment 9 Miroslav Lichvar 2010-07-14 14:44:12 UTC
Reassigning to xorg-x11-server.

Comment 10 Bug Zapper 2010-07-30 12:29:36 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:

Comment 11 lethalwp 2010-08-11 16:38:05 UTC
fixed with update libX11-1.3.4-3,
closing this issue

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