https://bugzilla.novell.com/show_bug.cgi?id=559110 https://bugzilla.novell.com/show_bug.cgi?id=559110#c8 --- Comment #8 from Gábor Varga <vargusz@fazekas.hu> 2012-02-06 10:11:51 UTC --- I tried to reproduce the same thing on another machine. The only difference was that this one was set to require a password when returning from the screensaver. The fade-out effect occured as before, but instead of resuming the desktop, the password entry dialog was shown, as if the SimulateUserActivity would indeed simulate some user activity after the screensaver has kicked in, but not before. Looking at the output of `gnome-screensaver --no-daemon --debug`, when xdg-screensaver signals gnome-screensaver via the D-BUS method before the activation of the screensaver, the following output is logged: [gs_manager_request_unlock] gs-manager.c:1346 (<time>): Request unlock but manager is not active My guess is that gnome-screensaver does not reset its idle counter correctly upon receiving the SimulateUserActivity call. Apparently the gs_manager_request_unlock function is called from gs_monitor_simulate_user_activity in gs-monitor.c. This function has the following comment: "FIXME: reset the xsync timer?" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.