Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Sep 1999 23:35:50 -0400 (EDT)
From:      Mikhail Teterin <mi@aldan.algebra.com>
To:        Tim Liddelow <tim@aba.net.au>
Cc:        stable@freebsd.org
Subject:   Re: KDE 1.1.2 - screensaver password problem
Message-ID:  <199909280335.XAA67204@rtfm.newton>
In-Reply-To: <37F00AD3.FD00F4BA@aba.net.au> from Tim Liddelow at "Sep 28, 1999 00:24:51 am"

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909280335.XAA67204>