Bug 134716

Summary:	ibm font crash xterm and others
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	a b <wharms>
Component:	X11 Applications	Assignee:	Stefan Dirsch <sndirsch>
Status:	RESOLVED FIXED	QA Contact:	Stefan Dirsch <sndirsch>
Severity:	Minor
Priority:	P2 - High
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description a b 2005-11-21 17:56:57 UTC

the ibm font works fine when displayed with xfd:
xfd -fn -ibm-courier-bold-*-normal--250-1808-100-100-m-1500-iso8859-1 

but crashes with xterm eating all available mem.
xterm -fn -ibm-courier-bold-i-normal--250-1808-100-100-m-1500-iso8859-1
_XF86BigfontQueryFont: could not attach shm segment
Speicherzugriffsfehler (segfault)

 xterm -fn "-ibm-courier-bold-r-normal--10-0-0-0-m-0-iso8859-1"
 crashes also

I experimented with other sizes/codestets all the same but access to the font via fontstools is not a problem


It is not a simple font to big problem. i found that i can use this font without
any problems:
xterm -fn "-adobe-utopia-bold-i-normal--150-*-100-100-*-*-iso8859-1"

this bug could be related to 117562. what sound to me a locale problem. 

my current versions:

xterm-203-5
xorg-x11-libs-6.8.2-100.2

Comment 1 Stefan Dirsch 2005-11-29 15:02:33 UTC

I cannot reproduce this on 10.1 Alpha3. Feel free to reopen, if it surfaces for you with 10.1.

Comment 2 Mike Fabian 2005-12-12 14:28:03 UTC

I cannot reproduce it either.

Comment 3 a b 2005-12-12 14:57:35 UTC

Did you try a vanilla SUSE10.0 32bit ?
if not is there an X11 update available ? 

:~> 
xterm -fn -ibm-courier-bold-i-normal--250-1808-100-100-m-1500-iso8859-1
_XF86BigfontQueryFont: could not attach shm segment
Speicherzugriffsfehler

Comment 4 Stefan Dirsch 2005-12-12 15:00:33 UTC

Currently there is no X11 update available. This is work-in-progress.

Comment 5 Mike Fabian 2005-12-12 17:41:47 UTC

Yes, I can reproduce it on SuSE 10.0 32bit.

The problem disappears when updating to xterm 207 though.
Updated xterm packages for 10.0 are here:

ftp://ftp.suse.com/pub/projects/m17n/10.0/RPMS/i586/xterm-207-1.1.i586.rpm
ftp://ftp.suse.com/pub/projects/m17n/10.0/RPMS/ppc/xterm-207-1.1.ppc.rpm
ftp://ftp.suse.com/pub/projects/m17n/10.0/RPMS/ppc64/xterm-207-1.1.ppc64.rpm
ftp://ftp.suse.com/pub/projects/m17n/10.0/RPMS/src/xterm-207-1.1.src.rpm
ftp://ftp.suse.com/pub/projects/m17n/10.0/RPMS/x86_64/xterm-207-1.1.x86_64.rpm

That means it is most likely an xterm bug and it is
most likely already fixed in the latest version of xterm.

Please try these updated xterm packages.