After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 709720 - Monitor is woken and cursor is visible sometimes
Monitor is woken and cursor is visible sometimes
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: lock-screen
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-10-09 10:41 UTC by Petr Schindler
Modified: 2014-11-12 09:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Petr Schindler 2013-10-09 10:41:52 UTC 
After I lock the screen the monitor is woken and the cursor is visible sometimes. Main problem is that monitor won't turn off again.

This could be reproduced: lock the screen (win+l) and then press Esc.

Version: gnome-shell-3.10.0.1-1.fc20.x86_64  Fedora 20.
Comment 1 Kamil Páral 2013-10-10 08:11:39 UTC 
The reproducer works only sometimes, but I can see it too quite often. Sometimes you hit a single key and only cursor appears (on black screen). Sometimes you don't hit any key, but after a while the display wakes up with no reason and again only a cursor on a black screen is shown. In this state the display never suspends again (and consumes power all the time).
Comment 2 Bastien Nocera 2014-11-09 17:52:52 UTC 
Quite a few cases of the DPMS status of the screen, the idle tracking code in Xorg, gnome-shell and gnome-settings-daemon getting out of sync. I haven't seen that in a long while, probably since we fixed a number of related bugs in GNOME 3.12.

Can you still reproduce the problem with GNOME 3.12 or, better, with 3.14?
Comment 3 Kamil Páral 2014-11-10 12:42:54 UTC 
I'm still on Fedora 20 with gnome 3.10, but I don't remember seeing this recently. What about you, Peter? You're on F21.
Comment 4 Petr Schindler 2014-11-12 09:50:22 UTC 
I haven't seen this for some time. It seems to be fixed in 3.14.