Red Hat Bugzilla – Bug 506419
When I close laptop screen and open it again, the screens stays off
Last modified: 2009-11-20 11:39:35 EST
Description of problem:
When I close down the screen of my laptop and open it again, the screen stays black and never switch on again.
Pressing Alt CTRL Backspace to reset X server switch on the screen again (but of course kills current work :) ).
Version-Release number of selected component (if applicable):
I don't know haw to get the xorg version. My last yum update is 16-june-2009.
Every time I close the screen on fedora.
Steps to Reproduce:
1. Start Fedora 11
2. Close your laptop screen
3. Open your laptop screen
When I open the screen again, I expect fedora to turn it on again.
Or : when I close the screen, I expect fedora to do nothing (My laptop swith of the screen anyway without any software trick).
Laptop : Dell latitude D520
VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
Kernel: Linux ****** 188.8.131.52-167.fc11.x86_64 #1 SMP Wed May 27 17:27:08 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
Workaround : you can turn on the screen again by pressing:
ALT + CTRL + F5
ALT + CTRL + F1
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 349914 [details]
Created attachment 349915 [details]
Created attachment 349916 [details]
Thank for your bug review,
I've attached the requested files.
I do not have a /etc/X11/xorg.conf
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command
yum upgrade --enablerepo='*-updates-testing'
Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .
Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
probably a duplicate of BUG528022
Reporter, do you have SELinux enforcing (/usr/sbin/getenforce would tell you)? Do you see any SELinux complaints (the yellow star in the status bar)?
Reporter, do you have SELinux enforcing (/usr/sbin/getenforce would tell you)?
Do you see any SELinux complaints (the yellow star in the status bar)?
I cannot say if I see anything in the status bar, because an other bug switch off my screen when I close the lid and I do not know how to switch it on again is there any log file I can read?
The bug is fixed.
So that's a Selinux problem.
I'll switch off selinux as a workaround until fixed. Thank you very much.
This bug seems to be related to
I've done a lot of updates yesterday an now the bug is fixed
even with setenforce 1
Thank you for letting us know.