All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-mm@kvack.org
Subject: 2.6.0-test1-mm1 Couldn't "lock screen" after 2 days uptime.
Date: 18 Jul 2003 15:02:22 -0600	[thread overview]
Message-ID: <1058562142.17692.13.camel@spc9.esa.lanl.gov> (raw)

Here's an odd one.

After running 2.6.0-test1-mm1 for two days, I tried to password protect
my KDE session with the "Lock Screen" command from the K button.  This
is something I do every time I walk away from my desk, security and all
that.  It always works, until now.  Selecting "Lock Screen", nothing
happened.  With several attempts, and waiting for several minutes, still
no locked screen.  The system was still very responsive otherwise.  

I logged off, logged back in again, and now "Lock Screen" works as
expected.  I've never seen this before.  I've run many different kernels
on this workstation and locked and unlocked the session many times per
day for the several months I've had Mandrake 9.1 installed here.  My
other workstation is Red Hat 9, but it's been busy doing other things
than testing kernels recently.

This may of course have nothing to do with 2.6.0-test1-mm1, but I
thought I'd mention it.  One more thing for folks to look out for.


Steven

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

                 reply	other threads:[~2003-07-18 21:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1058562142.17692.13.camel@spc9.esa.lanl.gov \
    --to=elenstev@mesatop.com \
    --cc=akpm@osdl.org \
    --cc=linux-mm@kvack.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.