From: Charles Shannon Hendrix <shannon@widomaker.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: xscreensaver and kernel 2.6.x
Date: Sun, 18 Jan 2004 18:57:28 -0500 [thread overview]
Message-ID: <20040118235728.GF9456@widomaker.com> (raw)
I'm trying to find the details on why xscreensaver has some troubles
with the 2.6 kernels.
On my system, something in pam is failing, causing a several seconds
delay when unlocking my screen.
In /var/log/messages, I get this:
Jan 18 17:59:07 daydream xscreensaver(pam_unix)[869]: authentication
failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=shannon
Jan 18 17:59:09 daydream xscreensaver(pam_unix)[869]: authentication
failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=root
This happens with all 2.6 kernels, and all earlier kernels work fine.
I found a lot of references to problems with pam and the 2.5 and 2.6
kernels, but can't seem to find the details I want.
Any help appreciated.
I don't get lockups, but the delay is annoying, and I hate broken
things.
--
UNIX/Perl/C/Pizza____________________s h a n n o n@wido !SPAM maker.com
next reply other threads:[~2004-01-19 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 23:57 Charles Shannon Hendrix [this message]
2004-01-19 2:39 ` xscreensaver and kernel 2.6.x Randy.Dunlap
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=20040118235728.GF9456@widomaker.com \
--to=shannon@widomaker.com \
--cc=linux-kernel@vger.kernel.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.