[Bug 287769] New: Screen doesn't lock after resume (from suspend to disk)
https://bugzilla.novell.com/show_bug.cgi?id=287769 Summary: Screen doesn't lock after resume (from suspend to disk) Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: Ulrich.Windl@rz.uni-regensburg.de QAContact: qa@suse.de Found By: --- Usually when I resume from suspend to disk, the GNOME desktop is restored and the screen locks (I have an automatic screen saver enabled after a few minutes of being idle). However occasionally the screen does not lock, and any user who turns on the computer could resume work. Maybe it's related to moving the mouse during restore, but I really don't know. As a security feature, a password should be verified after resume (like in Windows/XP). -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769 Stefan Behlert <behlert@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |329281 AssignedTo|bnc-team-gnome@forge.provo.novell.com |rodrigo@novell.com Priority|P5 - None |P3 - Medium -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c2 Gary Ekker <gekker@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|rodrigo@novell.com |cgaisford@novell.com --- Comment #2 from Gary Ekker <gekker@novell.com> 2007-10-22 10:38:21 MST --- Calvin, can you take a poke at this after working the screensaver issues for Lenovo? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c3 Calvin Gaisford <cgaisford@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #3 from Calvin Gaisford <cgaisford@novell.com> 2007-10-23 08:28:28 MST --- This may very well be related to the other screensaver/locking issues for which I just submitted a fix. I'll verify if this issue is fixed and report back. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c4 Calvin Gaisford <cgaisford@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #4 from Calvin Gaisford <cgaisford@novell.com> 2007-10-23 12:48:33 MST --- I've tried this several times on my thinkpad and I believe this issue is also fixed by the screensaver fix. When you sleep or Hibernate the machine, the first step is to activate the screensaver which wouldn't happen due to keyboard issues. Now the screensaver can activate. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c5 Noritoshi Yoshiyama <nority@jp.lenovo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nority@jp.lenovo.com Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #5 from Noritoshi Yoshiyama <nority@jp.lenovo.com> 2007-10-24 23:01:14 MST --- I can repro with gnome-screensaver-2.14.0-19.42.i586.rpm. This issue occurs only when system enters STR/STD before gnome-screensaver process is started 1. Boot SLED 10 SP1 2. Enter Suspend to RAM just after login 3. Wake up 4. Screen is not locked. Could you please try STR just after login ? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c6 Rodrigo Moya <rodrigo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rodrigo@novell.com --- Comment #6 from Rodrigo Moya <rodrigo@novell.com> 2007-10-25 03:32:23 MST --- Right, gnome-screensaver is started 30 seconds after login, to improve performance, so if you suspend before those 30 seconds, gnome-power-manager has no way of locking the screen. Not sure if we should fix this, or just make g-p-m wait for a given time before doing the suspend. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c7 Christian Zoz <zoz@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hmacht@novell.com, seife@novell.com, | |zoz@novell.com --- Comment #7 from Christian Zoz <zoz@novell.com> 2007-10-25 10:54:57 MST --- Even if it will probably rarely happen that someone suspends a system quite after he logged in, we should make sure that the screen is locked when suspending. This is a security problem. So either please enable screensaver earlier or disable or delay suspend until screen can be locked. Is that possible? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c8 Christian Zoz <zoz@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gekker@novell.com, jpallen@novell.com Priority|P3 - Medium |P2 - High --- Comment #8 from Christian Zoz <zoz@novell.com> 2007-10-31 11:53:44 MST --- Calvin, Rodrigo can you please comment on this issue? This needs to be fixed for the Lenovo Preload issue. Does starting screensaver later really save so much? If yes, why can't the screensaver not be started when the user requests it? If i try to start scrennsaver manually (via main menu) immediately after login, it does simply do nothing (== 'it does not work' for the average user). I suggest that we start screensaver either immediately after login or at least by request if it still does not run. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769 Gary Ekker <gekker@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |lenovo -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c9 --- Comment #9 from Calvin Gaisford <cgaisford@novell.com> 2007-11-06 14:46:40 MST --- I'm not sold on starting the screensaver immediately. I don't have any numbers but I'm guessing the number of people that are going to login and sleep their machines within 30 seconds of login is VERY small. So small that I don't think it makes sense to make a change that will effect everyone using the preload. The original issue of the screen not ever locking has been fixed and submitted. The 30 second issue is something different that I think should be left alone. In other words, I think it's an acceptable issue to leave in. If people feel strongly about it, we should address the issue upstream in the gnome desktop for the future. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c10 --- Comment #10 from Rodrigo Moya <rodrigo@novell.com> 2007-11-07 06:31:11 MST --- Yes, starting the screensaver, and other processes, with some delay helped us improving the login time by a few seconds, so it is really something we don't want to remove, unless until the login time is greater than 5 seconds or so. I don't see how we can solve this, because making the power manager wait for 30 seconds (if the user sleeps just right after loging in) doesn't seem a good solution. I'll look at other possible solutions. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c11 Calvin Gaisford <cgaisford@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|cgaisford@novell.com |rodrigo@novell.com Status|REOPENED |NEW --- Comment #11 from Calvin Gaisford <cgaisford@novell.com> 2007-11-12 20:02:18 MST --- I'm going to assign this over to Rodrigo to look into other possible solutions for the immediate lock. I've submitted the patch (and it's been accepted) so the keyboard lock issue is fixed in screensaver. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c12 --- Comment #12 from Christian Zoz <zoz@novell.com> 2007-11-15 02:52:16 MST ---
Yes, starting the screensaver, and other processes, with some delay helped us improving the login time by a few seconds, so it is really something we don't want to remove, unless until the login time is greater than 5 seconds or so.
It is great to reduce login time. But you write that delaying screensaver and other processes improved by a few seconds. I would like to know how big the effect of just the screensaver alone would be. I currently cannot imagine that starting a screensaver application needs that much ressources. But maybe i'm wrong here.
I don't see how we can solve this, because making the power manager wait for 30 seconds (if the user sleeps just right after loging in) doesn't seem a good solution.
If you let your user sleep right after login, then i let my user activate the screensaver or suspend right after login. ;)
I'll look at other possible solutions.
Can't the screensaver be started on demand when someone tries to activate it explicitely (the user or power manager)? Or can we just delay the permission to suspend (not whole power manager)? But beeing able to suspend without locking the screen is a security problem which should be fixed in any case. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c13 --- Comment #13 from Rodrigo Moya <rodrigo@novell.com> 2007-11-15 06:28:35 MST --- This delay is, BTW, gone in 10.3 (gnome-control-center 2.20), where services like the screensaver are started in idle callbacks. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c14 Rodrigo Moya <rodrigo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|rodrigo@novell.com |cgaisford@novell.com --- Comment #14 from Rodrigo Moya <rodrigo@novell.com> 2007-11-15 06:40:56 MST --- Calvin, you'd need just to remove the delay there is in gnome-settings-screensaver.c (http://svn.gnome.org/viewvc/gnome-control-center/branches/gnome-2-14/gnome-settings-daemon/gnome-settings-screensaver.c?revision=6612&view=markup). Just make sure you call really_start_screensaver directly instead via the g_timeout_add function -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c15 --- Comment #15 from Christian Zoz <zoz@novell.com> 2007-11-15 11:13:37 MST --- Does that mean we will change that behavior? If yes and when there is a package for testing, please let Gary put it to ftp://beta.suse.com/private/Lenovo-Preload/ The sooner the better. Thanks Rodrigo and Calvin. :) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c16 --- Comment #16 from Gary Ekker <gekker@novell.com> 2007-11-15 14:41:30 MST --- Calvin any chance of getting this done before you leave China to fly home? Perhaps you are already leaving in a few hours though, I'm not sure of your schedule. We are preparing the maintenance updates now. If you can get it done, submit the changes at /work/src/done/SLES10/lenovo/ and to the SP2 branch. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769#c17 Calvin Gaisford <cgaisford@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #17 from Calvin Gaisford <cgaisford@novell.com> 2007-11-15 21:08:22 MST --- I have made the change and submitted to sle10-sp2. I don't have the rights to copy anything to /work/src/done/SLES10/lenovo so someone else can do that. I have placed built packages in: http://w3.suse.de/~cgaisford/control-center2-* to test this fix. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=287769 User ast@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=287769#c18 --- Comment #18 from Anja Stock <ast@novell.com> 2008-01-09 02:49:01 MST --- released -- 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.
participants (1)
-
bugzilla_noreply＠novell.com