Bug 119831

Summary:	Changing local date / time through yast and click apply, gnome-screensaver starts
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	A Nagappan <anagappan>
Component:	GNOME	Assignee:	Rodrigo Moya <rodrigo>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	evan_ochs
Version:	RC 4
Target Milestone:	---
Hardware:	i386
OS:	SUSE Other
Whiteboard:
Found By:	Component Test	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description A Nagappan 2005-10-03 03:36:38 UTC

Steps to reproduce:
1. In clock applet right click and select 'Adjust Date & Time'
2. Type root password when prompted (I tried these steps as a normal user)
3. In Time and Date field, click 'Change' button
4. In 'Change System Date and Time' dialog, change either date or time and click
apply. (I changed both)

Actual result:
Screen become blank. Thought of pressing control + alt + backspace, when
pressing control key, gnome-screensaver poped me for password.

Expected result:
There is no relation between changing time and screen saver (according to the
end user), so screen saver should not prompt.

How often:
Always

Comment 1 JP Rosevear 2005-10-03 12:06:19 UTC

There is definitely a relation - the screensaver waits for the user to be idle
an amount of time.

Comment 2 A Nagappan 2005-10-03 14:07:19 UTC

JPR: I have set screen saver timeout as 30 minutes. Immediately after clicking
'Apply' in the Yast window, screen goes blank and when you move the mouse or
press any key, gnome-screen saver will popup for password.

Comment 3 JP Rosevear 2005-10-18 13:01:59 UTC

Yes - because it looks at the last time it new about, say "1pm" and then the new time, say "3pm", and when the code checks it sees 2 hours of idle and blanks the screen.

Setting the clock back might make the user wait longer than expect however.

Please check this out rodrigo out.

Comment 4 Gabriel Moreno 2005-10-31 16:37:44 UTC

(In reply to comment #3)
> Yes - because it looks at the last time it new about, say "1pm" and then the
> new time, say "3pm", and when the code checks it sees 2 hours of idle and
> blanks the screen.
> 
> Setting the clock back might make the user wait longer than expect however.
> 
I think AN is right because AN said that from the point of view of the user, there is no relation between changing the system time and triggering the screen saver. What you're explaining is the relation that exists in the screen saver triggering algorithm.

Comment 5 Rodrigo Moya 2005-10-31 16:53:48 UTC

Unfortunately, the timeout code in glib, which is what is used in gnome-screensaver, uses the system time to trigger the timeouts, so I don't see an easy fix for this.

Comment 6 JP Rosevear 2006-01-24 22:01:59 UTC

*** Bug 144499 has been marked as a duplicate of this bug. ***

Comment 7 Marc Ruehrschneck 2006-01-30 14:24:34 UTC

As far as I understand, the YaST module actually changes the CMOS clock of the system and re-reads it then.
Thus the "offset" of the whole system changes instantly.
I'm closing this in agreement with Dell, as it's a behaviour by design.