From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005-hi6Y0CQ0nG0@public.gmane.org>
To: Elliott Martin
<johnelliottmartin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-TtF/mJH4Jtrk1uMJSBkQmQ@public.gmane.org
Subject: Re: after resume usb mouse will allow input before unlocking screensaver
Date: Mon, 04 Jul 2005 14:53:37 +0200 [thread overview]
Message-ID: <42C93151.5040107@gmx.net> (raw)
In-Reply-To: <200507020244.46843.johnelliottmartin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Elliott Martin schrieb:
> When I restore my pc from suspend to disk and I'm using a USB mouse, I am able
> to type and interact with my programs before being prompted for a password. I
> normally have a root shell sitting open and I was able to run a couple of
> commands before the screensaver popped up for a password asking me to unlock
> my KDE session. If I resume with just my laptops touchpad going I get asked
> for a password before I can doing anything else, so I think this might be a
> problem with acpi, but I'm using suse linux so it could be a problem with
> suseplugger.
The problem is that suspend does not wait for the screensaver to be active,
so there is a race condition between the screensaver and suspend. I have no
idea how to fix it, but as a temporary workaround making this *less* likely
change POWERSAVE_SCREENSAVER_SIMPLE in /etc/sysconfig/powersave/common to
POWERSAVE_SCREENSAVER_SIMPLE="yes"
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-07-04 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 9:44 after resume usb mouse will allow input before unlocking screensaver Elliott Martin
[not found] ` <200507020244.46843.johnelliottmartin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2005-07-04 12:53 ` Carl-Daniel Hailfinger [this message]
2005-07-05 14:04 ` Thomas Renninger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42C93151.5040107@gmx.net \
--to=c-d.hailfinger.devel.2005-hi6y0cq0ng0@public.gmane.org \
--cc=acpi-devel-TtF/mJH4Jtrk1uMJSBkQmQ@public.gmane.org \
--cc=johnelliottmartin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.