Date: Tue, 28 Sep 1999 10:32:31 +0300 (EEST) From: Evren Yurtesen <yurtesen@ispro.net.tr> To: Mikhail Teterin <mi@aldan.algebra.com> Cc: Tim Liddelow <tim@aba.net.au>, stable@FreeBSD.ORG Subject: KDE 1.1.2 - problems Message-ID: <Pine.BSF.4.05.9909281027430.61516-100000@localhost> In-Reply-To: <199909280335.XAA67204@rtfm.newton>
next in thread | previous in thread | raw e-mail | index | archive | help
But KDE has many more problems for example when I donot login with root then if I use kvt as terminal application then I do not see myself on the output of the command w somehow xterm is working file Is there anybody who knows a solution for this? Also when I start kde in the ps ax output I always see 4 instances of startkde program. How can I solve this problem>?? dc:/usr/local/bin#ps ax |grep kde 6835 ?? I 0:00.01 /bin/sh /usr/X11R6/lib/X11/xdm/Xsession kde 6847 ?? I 0:00.00 /bin/sh /usr/local/bin/startkde 6848 ?? I 0:00.00 /bin/sh /usr/local/bin/startkde 6849 ?? I 0:00.00 /bin/sh /usr/local/bin/startkde 6850 ?? I 0:00.00 /bin/sh /usr/local/bin/startkde 7151 p3 D+ 0:00.00 grep kde dc:/usr/local/bin# On Mon, 27 Sep 1999, Mikhail Teterin wrote: > 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 > 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?Pine.BSF.4.05.9909281027430.61516-100000>