Bug 19281 – Random X crash in gEdit & staroffice on et6000 card

Bug 19281 - Random X crash in gEdit & staroffice on et6000 card

Summary:	Random X crash in gEdit & staroffice on et6000 card

Status:	CLOSED WORKSFORME

Aliases:	None

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

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Mike A. Harris
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-10-17 15:36 EDT by Need Real Name
Modified:	2007-04-18 12:29 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-07-16 03:59:50 EDT
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 Need Real Name 2000-10-17 15:36:34 EDT

X crashes every few minutes.  Always seems to crash while in gEdit of
Staroffice.  The exact same hardware platform was stable with 5.2, 6.0,
6.1, and 6.2.  Single AMD K2 on MPV3 board with et6000 display adapter.

Can recreate and send core dumps.

Any workaround until this is fixed??  Read the existing bug report and
found other instances of this kind of problem, and some mention of going
back-level on some components.

Please recommend something soon, as my productivity is being eaten up by X
crashes and restarts!

Comment 1 Mike A. Harris 2001-07-16 03:58:40 EDT

If you are still having this problem, try using:
Xconfigurator --preferxf3 --nodri

Comment 2 Mike A. Harris 2001-07-16 03:59:46 EDT

If the above does not solve it, please attach X logs and config files.

Comment 3 Mike A. Harris 2001-10-04 07:34:53 EDT

Presumeably you are not experiencing the problem anymore, so I'll close
the report.  If the problem does still occur, attach the requested info
and reopen the bug report.  Thanks.

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