From owner-freebsd-stable  Mon Sep 27 20:35:59 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190])
	by hub.freebsd.org (Postfix) with ESMTP id 6397B1508F
	for <stable@freebsd.org>; Mon, 27 Sep 1999 20:35:56 -0700 (PDT)
	(envelope-from mi@aldan.algebra.com)
Received: from rtfm.newton (rtfm.newton [10.10.0.1])
	by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id XAA20479;
	Mon, 27 Sep 1999 23:35:50 -0400 (EDT)
From: Mikhail Teterin <mi@aldan.algebra.com>
X-Relay-IP: 10.10.0.1
Received: (from mi@localhost)
	by rtfm.newton (8.9.3/8.9.1) id XAA67204;
	Mon, 27 Sep 1999 23:35:50 -0400 (EDT)
Message-Id: <199909280335.XAA67204@rtfm.newton>
Subject: Re: KDE 1.1.2 - screensaver password problem
In-Reply-To: <37F00AD3.FD00F4BA@aba.net.au> from Tim Liddelow at "Sep 28, 1999
 00:24:51 am"
To: Tim Liddelow <tim@aba.net.au>
Date: Mon, 27 Sep 1999 23:35:50 -0400 (EDT)
Cc: stable@freebsd.org
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
	 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
	 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Tim Liddelow once stated:

=I  just installed  KDE-1.1.2  (after  using 1.1.1)  and  am now  having
=problems with the screensaver password. Basically, it doesn't recognise
=the password  - is this a  libcrypt problem? With 1.1.1  there wasn't a
=problem.

Before "bad memory" is suggested as a  possible reason, let me say I saw
the  same  thing  with  one  of the  KDE  installations  some  time  ago
(definetly  before 1.1.2).  Back then,  I just  decided not  to use  the
klock.

Last week, I was setting up a  machine for a friend and the same problem
reappeared with a freshly built 1.1.2. I was under a deadline to deliver
the system,  so I just  copied /usr/local/bin/klock from  another system
(also  1.1.2), which  worked  fine.  Sorry, I  did  not investigate  any
further, but  the ldd  output looked  the same on  both klock-s  and the
crypt libraries were pointing to the same places.

I  understand, this  does not  help to  solve the  problem much,  but it
confirms it exists. For the record. Yours,

	-mi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message