Bug 1056180

Summary: Screen 0 deleted because of no matching config section
Product: [Fedora] Fedora Reporter: Peter H. Jones <jones.peter.busi>
Component: xorg-x11Assignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 10:54:15 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:
Embargoed:
Attachments:
Description Flags
Xorg.0.log file
none
Xorg.0.log
none
Xorg.0.log none

Description Peter H. Jones 2014-01-21 16:15:00 UTC
Description of problem:
Dark screen after bootup

Version-Release number of selected component (if applicable):
Build ID: xorg-x11-server 1.15.0-2.fc21

How reproducible:
Every time

Steps to Reproduce:
1. See bug 1056170

Additional info:
Xorg.0.log (attached)

Comment 1 Peter H. Jones 2014-01-21 16:16:19 UTC
Created attachment 853357 [details]
Xorg.0.log file

Comment 2 Peter H. Jones 2014-01-21 20:40:34 UTC
*** Bug 1056179 has been marked as a duplicate of this bug. ***

Comment 3 Peter H. Jones 2014-01-30 09:43:25 UTC
Created attachment 857411 [details]
Xorg.0.log

Got dark screen booting Fedora-Live-Jam-KDE-x86_64-rawhide-20140129.iso in basic graphics mode with threadirqs, quiet and rhgb removed. Note the following:
"$ grep EE Xorg.0.log
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   117.607] Initializing built-in extension MIT-SCREEN-SAVER
[   121.447] (EE) open /dev/dri/card0: No such file or directory
[   121.447] (EE) open /dev/dri/card0: No such file or directory
[   121.715] (EE) open /dev/fb0: No such file or directory
[   121.737] (EE) open /dev/fb0: No such file or directory
[   121.742] (EE) Screen 0 deleted because of no matching config section.
[   121.742] (EE) Screen 0 deleted because of no matching config section.
[   121.746] (EE) Screen 0 deleted because of no matching config section.
[   125.157] (EE) AIGLX: reverting to software rendering
"

Comment 4 Peter H. Jones 2014-03-01 23:16:28 UTC
Created attachment 869521 [details]
Xorg.0.log

Still have this bug when booting Fedora-Live-Jam-KDE-x86_64-rawhide-20140301.iso in basic graphics mode. I have the following EE lines in Xorg.0.log:

"# grep -n EE X*log
15:	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
55:[   436.081] Initializing built-in extension MIT-SCREEN-SAVER
369:[   437.241] (EE) open /dev/dri/card0: No such file or directory
371:[   437.243] (EE) open /dev/dri/card0: No such file or directory
378:[   437.265] (EE) open /dev/fb0: No such file or directory
386:[   437.270] (EE) open /dev/fb0: No such file or directory
387:[   437.272] (EE) Screen 0 deleted because of no matching config section.
389:[   437.274] (EE) Screen 0 deleted because of no matching config section.
391:[   437.274] (EE) Screen 0 deleted because of no matching config section.
2764:[   438.521] (EE) AIGLX: reverting to software rendering"

Comment 5 Peter H. Jones 2014-03-01 23:19:18 UTC
Current version is xorg-X11-server-1.15.0-5.fc21.

Comment 6 Jaroslav Reznik 2015-03-03 15:24:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 7 Fedora End Of Life 2016-07-19 10:54:15 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.