Do

GNOME Do prevents the screen to be locked

Bug #504912 reported by BobMauchin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Do
New
Undecided
Unassigned

Bug Description

Steps:
1. Open the main GNOME Do window
2. Do no type anything nor move your mouse
3. No matter how long you wait, the screen is not locked or the screensaver is not launched
4. Move your mouse/type with keyboard : the screen goes in locked mode.

Info:
Fedora Constantine (12) with GNOME 2.28.2
GNOME Do 0.8.2

Maybe a potential security issue as the user wants his screen to be locked while he's away.

Revision history for this message
BobMauchin (zebob.m) wrote :

I'm no expert at all but after some digging, I suspect some kind of conflict in the mouse/keyboard grabbing between GNOME Do and GNOME Screensaver. As far as I understand from this http://developer.gnome.org/doc/GGAD/sec-gdkcursor.html :

"To grab the pointer, call gdk_pointer_grab(), shown in Figure 8. The first argument [blah blah]

The final argument, time, specifies when the grab should take effect, in server time. This is intended to resolve conflicts if two clients try to grab the pointer simultaneously; the time must be after the last grab time, and it must not be in the future. Usually, you will want to use the time field from the event you're processing, or the GDK_CURRENT_TIME macro. GDK_CURRENT_TIME is a magic constant that tells the X server to substitute the current time. "

It seems that GNOME Do grabs mouse/keyboard (in Do.Interface/Windowing.cs ?) and then GNOME Screensaver is trying to do the same (probably here http://git.gnome.org/browse/gnome-screensaver/tree/src/gs-monitor.c ). Therefore I'm not entirely sure it is a GNOME Do problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers