74025 – Xorg crashes and locks up the system when selecting certain fonts

Bug 74025 - Xorg crashes and locks up the system when selecting certain fonts

Summary: Xorg crashes and locks up the system when selecting certain fonts

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Gentoo X packagers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-12-10 10:29 UTC by Chris Nicola
Modified:	2004-12-10 16:29 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
emerge --info (temp,2.07 KB, text/plain) 2004-12-10 10:29 UTC, Chris Nicola	Details
View All Add an attachment (proposed patch, testcase, etc.)

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

Description Chris Nicola 2004-12-10 10:29:14 UTC

When I select certan fonts using xfontsel my screen goes 'wonky' (sorry about the description, kinda like when you used to reset atari's colored lines, etc) and the system locks.

In particular it happens when I select certain bitstream fonts.  I have seen similar reports to this but the solutions did not help.  I have tried removing 'Load FreeFont' and 'Load Type1' but I get the same result.  I have remerged xorg and the bitstream fonts but same result.  I have composite disabled so it isn't that either.

Reproducible: Always
Steps to Reproduce:
1.Run xfontsel
2.Set 'fmly' to 'bitstream vera sans mono' and 'wght' to 'medium' 
3.Then as soon as I set 'slant' to 'r' the Xorg locks up and the screen goes.

Actual Results:  
Xorg locks up.  Screen goes 'wonky'

Expected Results:  
Display the font I am requesting

emerge --info attached

Comment 1 Chris Nicola 2004-12-10 10:29:43 UTC

Created attachment 45690 [details]
emerge --info

Comment 2 Chris Nicola 2004-12-10 16:29:54 UTC

I have fixed the problem by not using XFS.  I have put all the paths into xorg.conf instead of the "unix:/-1" path I was using before.  This seems to have fixed this problem.