Bug 7108 – X dies with segfault

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 7108 - X dies with segfault

Summary:	X dies with segfault

Status:	CLOSED WORKSFORME

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Preston Brown
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-11-18 13:05 EST by Dave Booth
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-01-14 11:54:52 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 Dave Booth 1999-11-18 13:05:18 EST

I'm seeing a lot of X crashes on two systems where I'm using rh6.1 - both
of them clean installs.

Configuration 1: Cyrix 686 box, matrox millennium II card, SVGA X server.
Configuration 2: Compaq deskpro, built-in S3 graphics, S3 x server.

In all cases the only error message is that the server caught a SIGSEGV.

no apparent correlation to a specific task, crashes appear to be sporadic
and unrelated to which apps are open, length of session etc.

most commonly used X environment on both machines is GNOME/Enlightenment,
updating to latest versions of either or both does not cure the problem.
Switching window managers does not cure the problem - I therefore conclude
problem is in X rather than an environment-specific thing.

Comment 1 Preston Brown 2000-01-14 11:54:59 EST

without more specifics, we don't have a real starting place on this bug,
unfortunately. You may for instance have flakey hardware, or there may be any
number of programs crashing the X server, or the server itself may be buggy.

If you can isolate the problem, please reopen the bug with more details.

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