Bug 322541 - Fatal IO error 11 on exit of system-config-display
Summary: Fatal IO error 11 on exit of system-config-display
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-display
Version: 8
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-10-07 22:55 UTC by ericm24x7
Modified: 2018-04-11 13:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-01-09 07:18:29 UTC

Attachments (Terms of Use)
xorg.conf (876 bytes, text/plain)
2007-10-07 22:55 UTC, ericm24x7
no flags Details
dmesg output log (21.70 KB, text/plain)
2007-10-07 22:56 UTC, ericm24x7
no flags Details
Xorg.0.log file (44.90 KB, text/plain)
2007-10-23 19:48 UTC, ericm24x7
no flags Details

Description ericm24x7 2007-10-07 22:55:33 UTC
Description of problem:
After running system-config-display from command line at init level 3, there is
an output error after exiting the program.

Version-Release number of selected component (if applicable):
system-config-display.noarch 1.0.51-2.fc8

How reproducible:

Steps to Reproduce:
1. init 3
2. system-config-display
3. select generic monitor 1280x1024 and default to 1280x1024
4. apply the change and exit the program  

Actual results after exiting the program:
Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on
display ':17.0'.

Expected results:
no warning/error display

Comment 1 ericm24x7 2007-10-07 22:55:33 UTC
Created attachment 218931 [details]

Comment 2 ericm24x7 2007-10-07 22:56:13 UTC
Created attachment 218941 [details]
dmesg output log

Comment 3 ericm24x7 2007-10-07 23:10:21 UTC
There should at least be an option to change the refresh rate. For my system it
is default to 75Hz instead of 60Hz, which distort the screen and squeeze it to
the right side. 

Comment 4 Matěj Cepl 2007-10-08 16:53:06 UTC
Could we get /var/log/Xorg.0.log as well?

Comment 5 ericm24x7 2007-10-23 19:48:57 UTC
Created attachment 235431 [details]
Xorg.0.log file

Comment 6 John Reiser 2008-10-01 04:49:02 UTC
This bug may be related to bug 431872 "xorg-x11-drv-ati will not work on primary display on my powerbook".  Graphical install of Fedora 10 Beta fails during early anaconda on my box with symptoms "Fatal IO error 11 (Resource temporarily unavailable) on display :1.0"

Comment 7 Bug Zapper 2008-11-26 07:55:37 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 '8'.

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 8'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 8 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 8 Bug Zapper 2009-01-09 07:18:29 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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.