Red Hat Bugzilla – Bug 500377
gnome-screensaver kicks in when mouse and keyboard are active
Last modified: 2018-04-11 05:59:01 EDT
Description of problem:
gnome-screensaver locks my screen while I am reading email - so I am hitting the space bar at least once a minute, and using the mouse. The timeout is set for 10 minutes.
Version-Release number of selected component (if applicable):
Seems to reproduce every day.
Steps to Reproduce:
2. Do work that involves light typing
gnome-screensaver kicks in when it should not.
gnome-screensaver only kicks in after the designated timeout
I run synergy. Today the problem occurred while I was using my primary screen, and the screensaver on the primary screen went black (as if the screensaver kicked in).
I realize that this could also be an issue with X11 not updating something based on keyboard or mouse events. I don't know much about X11's current architecture, but I am running:
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
I experience roughly the same, except that the screen saver does not actually kick in, but both monitors go completely blank (I think they power down). A mouse movement or key press wakes them up again. Sometimes this happens < 1 sec after the last keyboard or mouse action.
My screen saver is set to 5 minutes, the display sleep time is set to 30 minutes.
I'm running a standard Fedora 11 gnome desktop with NVidia Quadro NVS 295 using the nouveau driver and two Samsung 24" displays connected via DVI.
I've been running Fedora 11 since the beta release, and this behaviour hasn't changed since.
I can reproduce this bug with an IBM Thinkpad T61 and a Dell Mini 9. One of my coworker as well.
I have the gnome-screensaver set to blank screen after 5 minutes and I have the power management to shutdown the screen after 6.
I have the same problem. My HP L1955 monitor connected to a NVidia 7600 GS via DVI enters in *standby mode* even if I use the mouse and keyboard.
I am using:
xorg-x11-drv-nvidia-180.51-1.fc11.x86_64.rpm (binary driver from NVidia)
I had the same issue with the Fedora 11 preview, but IIRC I was using the nouveau driver.
Sounds like the same problem here.
$ rpm -qa xorg-x11-drv-nvidia\* gnome-screensaver xorg-x11-server-Xorg DeviceKit-power gnome-power-manager
Dupe of 499061?
Seeing on my dual monitor system as well since upgrading to fedora 11, Quadro NVS 285 using nvidia driver. This bug is slowly driving me insane.. guess since someone else is seeing it with the nouveau driver that it may not be an issue with the driver.
If everyone is in agreement, I think this bug is a dupe of bug 499061.
Try "yum --enablerepo=updates-testing update xorg-x11-server-Xorg
gnome-power-manager" and reboot.
The screensaver gets idle information from the Xorg server.
Could anybody who is affected by this bug provide information about graphics card they use, version of kernel, and xorg-x11-drv, please?
NVidia Quadro NVS 295
The bug seems to be fixed, though. I've been running a more recent Xorg server for a few days and have not had any occurrence of screen blanking since.
The good version is xorg-x11-server-Xorg-1.6.3-4.fc11.x86_64.rpm (was in updates-testing a few days ago).
Cool news! Could anybody else reproduce it and provide this information, please?
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.]
We are seeing this same problem in F10 which we are fielding until RHEL6 is available and we'd really like to find a fix or workaround, any suggestions? It's troubling that there isn't a specific change that is supposed to have fixed this problem.
(In reply to comment #16)
> We are seeing this same problem in F10 which we are fielding until RHEL6 is
> available and we'd really like to find a fix or workaround, any suggestions?
> It's troubling that there isn't a specific change that is supposed to have
> fixed this problem.
Unfortunately Fedora 10 is not supported anymore (https://www.redhat.com/archives/fedora-announce-list/2009-December/msg00014.html). Are you able to reproduce the issue with the currently supported (preferably Fedora 12) Xorg in the latest updates of the distribution?
If you are able to reproduce the issue with the currently supported distro, please, attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.
Thanks in advance.
The bug seems to be fixed in F11 and not present at all in F12 here and on my coworkers laptops.
Don't know for F10.
(In reply to comment #18)
> Don't know for F10.
Fedora 10 is not supported anymore.
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. 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 '11'.
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 11'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 11 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:
I think we can close this bug for now as it is fixed in F-11, F-12 and F-13.
If someone still encounter the problem, I welcome them to reopen this bug.