Bug 9205 – Doom & Kde (possible all Xwindows System)

Bug 9205 - Doom & Kde (possible all Xwindows System)

Summary:	Doom & Kde (possible all Xwindows System)

Status:	CLOSED DEFERRED

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	svgalib (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:	Security

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-02-08 03:27 EST by Francesco Andreozzi
Modified:	2014-03-16 22:12 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-03-27 17:13:07 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Francesco Andreozzi 2000-02-08 03:27:59 EST

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 11:00:59 EST

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 02:40:59 EST

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 18:28:59 EST

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 17:13:59 EST

closed, lack of input.

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