From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
To: Nuno Monteiro <nuno.monteiro@ptnix.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: woes with 2.6.0-test1 and xscreensaver/xlock
Date: Wed, 16 Jul 2003 14:58:43 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0307161454180.32541@montezuma.mastecende.com> (raw)
In-Reply-To: <20030716172758.GA1792@hobbes.itsari.int>
On Wed, 16 Jul 2003, Nuno Monteiro wrote:
> Is anyone else having trouble with xscreensaver/xlock under 2.6.0-test1?
> Whenever I lock my session using either "lock screen" from the menu (it
> launches 'xscreensaver lock', afaik) or "xlock", I cant seem to ever get
> my session back -- I type in the correct password, but they both just
> hang there. The exact same setup works flawlessly in 2.4.21, and just for
> the sake of curiosity I also tested 2.5.75, 2.5.74, 2.5.73, 2.5.72,
> 2.5.71 and 2.5.70, they all exhibit the same behaviour as 2.6.0-test1. I
> dont really have time to go on testing kernels to find out exactly where
> it broke, so I'm hoping anyone else is experiencing these woes.
Someone reported this on bugzilla too, but i failed to reproduce it so it
appears that perhaps something else died like the keyboard. I tried it
last night on 2.6.0-test1 and i managed to login fine. It does appear that
something else is dying. It'd be good if you could collect the last few messages
from /var/log/XFree86.0.log and /var/log/messages and also perhaps
/var/log/dmesg.
Thanks,
Zwane
--
function.linuxpower.ca
next prev parent reply other threads:[~2003-07-16 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 17:27 woes with 2.6.0-test1 and xscreensaver/xlock Nuno Monteiro
2003-07-16 18:02 ` Edward Tandi
2003-07-16 18:58 ` Zwane Mwaikambo [this message]
2003-07-16 19:16 ` Randy.Dunlap
2003-07-16 19:13 ` Zwane Mwaikambo
2003-07-16 19:33 ` jjs
2003-07-16 19:32 ` Valdis.Kletnieks
2003-07-16 19:56 ` Nuno Monteiro
2003-07-16 21:00 ` Nuno Monteiro
2003-07-16 20:17 ` jhigdon
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=Pine.LNX.4.53.0307161454180.32541@montezuma.mastecende.com \
--to=zwane@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.monteiro@ptnix.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).