Bug 443292 - Screen goes blank in random intervals
Summary: Screen goes blank in random intervals
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nv   
(Show other bugs)
Version: 9
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-04-20 09:37 UTC by Mauri Korkeala
Modified: 2018-04-11 14:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 17:36:57 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Xorg log file (485.53 KB, text/plain)
2008-04-20 09:37 UTC, Mauri Korkeala
no flags Details

Description Mauri Korkeala 2008-04-20 09:37:38 UTC
Description of problem:
While testing Fedora 9 preview-release live CD, the screen goes blank
occasionally for few seconds. Each time everything resumes normally. 

No errors/warnings/messages is printed to logs. At least I didn't see any.

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

How reproducible:
It happens randomly (or at least it seems so). The interval is anything from
5mins to 30mins.

Steps to Reproduce:
1. Boot Fedora 9 preview release live CD
2. Use desktop normally (browse bugzilla, look system logs)
Actual results:
The monitor goes blank for few seconds every now and then, no messages/warnings
is printed to logs.

Expected results:
The monitor is on while the user is active.

Additional info:
When installing fedora 8, the graphics card was not supported with NV or Noveau
drivers. when using the NVidia binary driver, there is no problems with screen

Comment 1 Mauri Korkeala 2008-04-20 09:37:38 UTC
Created attachment 303048 [details]
Xorg log file

Comment 2 Matěj Cepl 2008-05-03 12:47:57 UTC
Are you sure the blank is more than a second?

Comment 3 Mauri Korkeala 2008-05-04 14:51:10 UTC
No, not sure. I would estimate that it's closer to 1 sec. 

Comment 4 Bug Zapper 2008-05-14 09:46:27 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:

Comment 5 Bug Zapper 2009-06-10 00:18:18 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: 

Comment 6 Bug Zapper 2009-07-14 17:36:57 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.