Bug 9205

Summary:	Doom & Kde (possible all Xwindows System)
Product:	[Retired] Red Hat Linux	Reporter:	Francesco Andreozzi <francesco.andreozzi>
Component:	svgalib	Assignee:	Bill Nottingham <notting>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	CC:	bero, rvokal
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-03-27 22:13:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Francesco Andreozzi 2000-02-08 08:27:59 UTC

If you start doom in tty1 and then switch into tty2; In tty2 you start kde.
When you kill sdoom from kde, the system goin krash.
I don't know what sort of problem it's bug produce!

Comment 1 Bernhard Rosenkraenzer 2000-02-08 16:00:59 UTC

Are you sure it's causing a complete crash, and not just a display lockup?
SVGALib and XFree86 have never played too well together (and they can't).

Comment 2 Francesco Andreozzi 2000-02-09 07:40:59 UTC

I don't know if its a screen lookup, but when it occur i resolve with reboot,
if you have some key combination to verify it, please send me.
Hi

Comment 3 Bill Nottingham 2000-02-14 23:28:59 UTC

Hitting ctrl-alt-f1/f2/f3 etc. might help.

How did you kill sdoom? In general, doing kill -9
of something that has direct control of the graphics
card & keyboard is a *bad* idea.

Comment 4 Bill Nottingham 2000-03-27 22:13:59 UTC

closed, lack of input.