Bug 566931 - xorg-x11-drv-nouveau-0.0.15-20 causes X to segfault
Summary: xorg-x11-drv-nouveau-0.0.15-20 causes X to segfault
Keywords:
Status: CLOSED DUPLICATE of bug 566619
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 12
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-20 14:25 UTC by Charles Dennett
Modified: 2010-02-22 03:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-22 03:59:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg.0.log file showing seg fault and backtrace (20.00 KB, application/octet-stream)
2010-02-20 14:25 UTC, Charles Dennett
no flags Details

Description Charles Dennett 2010-02-20 14:25:21 UTC
Created attachment 395262 [details]
Xorg.0.log file showing seg fault and backtrace

Description of problem:  
After upgrading to xorg-x11-drv-nouveau-0.0.15-20, X seg faults when trying to start.


Version-Release number of selected component (if applicable):
xorg-x11-drv-nouveau.x86_64


How reproducible:
Happens every time with latest version.  Never with previous version

Steps to Reproduce:
1. Update to latest version
2. Start X
3. X never starts.  Screen stays blank
4. Downgrade to xorg-x11-drv-nouveau-0.0.15-17 (previous version)
5. Start X
6. Works.
7. Repeat from step 1.
  
Actual results:
X fails to start.  Screen is blank.  ssh in from another system to reboot.


Expected results:
X windowing system should start

Additional info:  Found bug 562713 but don't know if it's the same one. Video card is NVidea GEForce FX5200 (NV34).  Xorg log file that includes a backtrace is attached.

Comment 1 Ben Skeggs 2010-02-22 03:59:44 UTC
Appears likely to be a duplicate of 566619, it's possible nomodeset may be broken.  As I asked the other reporter, any particular reason you're using nomodeset in the first place?

*** This bug has been marked as a duplicate of bug 566619 ***


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