Bug 449104 - X11 with glint driver aborts with signal 11 on startup
Summary: X11 with glint driver aborts with signal 11 on startup
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-glint
Version: 9
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-30 13:17 UTC by David Gesswein
Modified: 2009-07-14 17:42 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-07-14 17:42:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
X server log file (14.98 KB, text/plain)
2008-05-30 13:18 UTC, David Gesswein
no flags Details
X server configuration file (701 bytes, text/plain)
2008-05-30 13:18 UTC, David Gesswein
no flags Details
F11 x server log file (15.11 KB, text/plain)
2009-06-17 00:05 UTC, David Gesswein
no flags Details
Xorg.0.log (7.38 KB, text/plain)
2009-06-19 19:58 UTC, Jeffrey Stein
no flags Details

Description David Gesswein 2008-05-30 13:17:04 UTC
Description of problem:

When X starts with a Appian Graphics Jeronimo Pro graphics card it fails with 
Fatal server error:
Caught signal 11.  Server aborting

This card uses the glint driver and has a Texas Instruments TVP4020 [Permedia 2]
chip. Works fine under Fedora 8.

The Xorg.0.log and xorg.conf are attached.

All packages updated to latest at time of bug submission

Version-Release number of selected component (if applicable):
xorg-x11-drv-glint-1.2.0-1.fc9.i386
xorg-x11-server-Xorg-1.4.99.901-29.20080415.fc9.i386

How reproducible:

Normal run level 5 startup
After X fails to start see /var/log/Xorg.0.log

Actual results:

No X

Expected results:

Pretty display

Additional info:
Config file same as working under Fedora 8

Comment 1 David Gesswein 2008-05-30 13:18:02 UTC
Created attachment 307196 [details]
X server log file

Comment 2 David Gesswein 2008-05-30 13:18:44 UTC
Created attachment 307198 [details]
X server configuration file

Comment 3 Bug Zapper 2009-06-10 01:17:38 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 David Gesswein 2009-06-17 00:05:27 UTC
Created attachment 348197 [details]
F11 x server log file

Still fails for Fedora 11, new x server log file provided.

Comment 5 Jeffrey Stein 2009-06-19 19:55:39 UTC
Fails for me too, after upgrade to Fedora 11 via "preupgrade". X was working ok in F10 before the upgrade to F11.

Comment 6 Jeffrey Stein 2009-06-19 19:58:22 UTC
Created attachment 348701 [details]
Xorg.0.log

Xorg log file

Comment 7 Bug Zapper 2009-07-14 17:42:39 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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