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 628941 - gnome-screensaver ignores input events when fading to black
gnome-screensaver ignores input events when fading to black
Status: RESOLVED DUPLICATE of bug 625374
Product: gnome-screensaver
Classification: Deprecated
Component: general
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2010-09-07 09:09 UTC by tatsuno
Modified: 2010-09-07 14:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30


Attachments
Xorg.0.log (50.19 KB, text/plain)
2010-09-07 09:09 UTC, tatsuno
Details

Description tatsuno 2010-09-07 09:09:25 UTC
Created attachment 169655 [details]
Xorg.0.log

gnome-screensaver ignores events from keyboard or mouse when fading to black, so you cannot prevent the screensaver from launching.

Additional info:

$ uname -a
Linux hyrule 2.6.35-ARCH #1 SMP PREEMPT Fri Aug 27 17:14:28 CEST 2010 x86_64 Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz GenuineIntel GNU/Linux

$ pacman -Q xorg-server
xorg-server 1.8.1.902-1

$ pacman -Q gnome-screensaver
gnome-screensaver 2.30.0-2

$ pacman -Q gnome-desktop
gnome-desktop 2.30.2-1

Steps to reproduce:

Wait for the screensaver to start. When fading to black, move the mouse or hit any key. Nothing happens -the screen keeps fading to black and the screensaver appears.

Related reports:

https://bugzilla.gnome.org/show_bug.cgi?id=594082

https://bugzilla.redhat.com/show_bug.cgi?id=629419

https://bugzilla.redhat.com/show_bug.cgi?id=626472

http://bugs.archlinux.org/task/20732
Comment 1 William Jon McCann 2010-09-07 14:26:56 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 625374 ***