Bug 68929 - A lot of problems seemed to go away after switching to Matrox supplied drivers
Summary: A lot of problems seemed to go away after switching to Matrox supplied drivers
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: XFree86
Version: limbo
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-16 00:47 UTC by Need Real Name
Modified: 2007-04-18 16:44 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-07-16 00:47:20 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2002-07-16 00:47:16 UTC
Description of Problem:After upgrade to limbo, seemed to have a lot of random
problems related to graphics.  Not sure what had been installed to drive the
Matrox G550 video card;, decided to go with Matrox supplied driver (i.e went to
their web site and downloaded).  Random behavior seemed to stop - now just
dealing with recurrent issues.


Version-Release number of selected component (if applicable):


How Reproducible:


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:

Comment 1 Mike A. Harris 2002-07-16 05:12:22 UTC
"A lot of random problems" is not something which anyone can fix, as it
isn't something concrete or tangible.  You need to open specific
individual bug reports for each discreet problem being encountered, and
provide a detailed description of each issue, with complete details of
how to reproduce, and include as much information as possible, including
your X server logs and config files as file attachments.  Describe
in detail what you see, and what if anything you've done to try to
troubleshoot what the problem might be.  Describe in detail how things
worked in each scenario in the previous release, and how it differs from
current release.

We can't troubleshoot or debug vaguely reported problems.


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