Bug 1042671

Summary: X crash on GNOME start with fully updated Fedora 18 guest
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: xorg-x11-drv-qxlAssignee: Alon Levy <alevy>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 18CC: alevy, crobinso, dblechte, hdegoede, marcandre.lureau, sandmann, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:35:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Xorg.0.log from a failed start attempt
none
/var/log/messages from affected VM, contains several X start attempts none

Description Adam Williamson 2013-12-13 03:28:22 UTC
Was just trying to test F18 to F20 fedup, and found this.

Using an F20 host and the virtual machine I use for just about all my testing, which has a typical qxl/SPICE config, I did a clean install of F18 from the x86_64 desktop live image. The live and the installed system both booted to GNOME just fine. I then 'yum update'd to the latest F18 packages, and since then, it looks like X crashes on system boot, or if I boot to runlevel 3, log in as a user and run 'startx'. Will attach logs.

Comment 1 Adam Williamson 2013-12-13 03:30:09 UTC
Created attachment 836112 [details]
Xorg.0.log from a failed start attempt

Comment 2 Adam Williamson 2013-12-13 03:32:46 UTC
Created attachment 836113 [details]
/var/log/messages from affected VM, contains several X start attempts

I see this:

Dec 12 19:10:54 localhost kernel: [   26.586607] [drm:qxl_release_from_id_locked] *ERROR* failed to find id in release_idr
Dec 12 19:10:54 localhost kernel: [   26.796968] [drm:qxl_release_from_id_locked] *ERROR* failed to find id in release_idr

but those lines are only present once, and I did at least three tries (two just booting runlevel 5, one booting runlevel 3 and 'startx').

Comment 3 Cole Robinson 2013-12-17 22:42:35 UTC
I can't reproduce, but honestly at this point it's highly unlikely to be fixed in F18: no one has pushed an f18 qxl package since _before_ f18 even went GA (one update attempt was karam'd out of existence).

Comment 4 Adam Williamson 2013-12-17 23:51:01 UTC
Heh, coincidentally I just reproduced it while filing karma for F18 security updates. Happened just the same. Booting with 'nomodeset' works around it.

Comment 5 Fedora End Of Life 2013-12-21 14:49:01 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 6 Fedora End Of Life 2014-02-05 22:35:43 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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