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 421944 - Conflicts with screensaver lock mode
Conflicts with screensaver lock mode
Status: RESOLVED WONTFIX
Product: DrWright
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: drwright-maint
drwright-maint
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2007-03-23 16:29 UTC by Sven Arvidsson
Modified: 2018-07-01 08:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Sven Arvidsson 2007-03-23 16:29:11 UTC
This bug was reported to the Debian BTS.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321773

The original bug report was about xscreensaver, but also occurs with gnome-screensaver.

"When "Take a break" is activated (locking the keyboard and screen
after a set amount of activity), if the user (on a notebook) closes
the notebooks lid, ACPI scripts start up an instance of xscreensaver
in lock mode.
After the time of the schedulet break runs out, the gnome applet
unlocks the keyboard and screen messing up the xscreensavers setup.
xscreensaver still thinks that it is in locked mode and disables lots
of keys (including Alt-Tab and others), but the screen is not blanked
and the keyboard input goes to the first application on the screen.

Workaround is to call "xscreensaver-command -activate" and then unlock
it as usual."

Steps to reproduce:
"The bug exists in both configurations. Easy to check on a laptop:
* make screen locking to activate on lid close
* activate "take a break" feature
* work until the "take a brake" starts
* close the lid
* wait enough time for "take a brake" to finish
* open the lid
* observe all the desktop visible, but keyboard and mouse still disabled
* close the lid and open it again, observe the typical lock screen
* enter password and all works again."
Comment 1 Richard Hult 2007-03-23 17:09:08 UTC
Isn't this a bug in the screensaver rather than typing-monitor?
Comment 2 Sven Arvidsson 2007-03-23 17:31:06 UTC
I'm not sure. There is a (possibly) related issue, bug 334772, talking about notifications between typing monitor and the screensaver.

Anyway, if you do feel this is an issue more closely related to the screensaver, please reassign it.
Comment 3 Bastien Nocera 2010-11-21 00:11:21 UTC
Mass move to DrWright module. The code has been removed from the control-center, and put back in the drwright module as its interaction with the GNOME 3.x experience was not defined.

See http://git.gnome.org/browse/drwright
Comment 4 André Klapper 2018-07-01 08:56:49 UTC
DrWright is not under active development anymore, has not seen code changes for about five years, and saw its last tarball release in the year 2012.
Its codebase has been archived: https://gitlab.gnome.org/Archive/drwright/commits/master

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.