Date: Mon, 8 Jan 2007 20:38:30 +0100 From: Tijl Coosemans <tijl@ulyssis.org> To: freebsd-current@freebsd.org Cc: kde@freebsd.org, Michael Nottebrock <lofi@freebsd.org>, Abdullah Al-Marrie <almarrie@gmail.com> Subject: Re: [kde-freebsd] Re: KDE 3.5.5 lock issue was (Xorg with lock session issue) Message-ID: <200701082038.33761.tijl@ulyssis.org> In-Reply-To: <200701081159.51056.lofi@freebsd.org> References: <499c70c0701071038k34d10214ya7a0cd00e6c1f800@mail.gmail.com> <200701081159.51056.lofi@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 08 January 2007 11:59, Michael Nottebrock wrote: > On Sunday, 7. January 2007 19:38, Abdullah Al-Marrie wrote: > > On 1/7/07, Giorgos Keramidas <keramida@ceid.upatras.gr> wrote: > > > On 2007-01-07 18:38, Abdullah Al-Marrie <almarrie@gmail.com> wrote: > > > > I use lock session which comes with KDE 3.5.5 which in the start menu, > > > > I don't know if this is xlockmore or not. > > > > > > Unfortunately, I don't use KDE, so I don't really know. Can you connect > > > remotely through SSH to the system and try "ps xau" to find out what > > > programs are running? This could provide some hint about the locking > > > program KDE uses. > > > > Actually it's KDE issue > > Make sure /usr/local/bin/kcheckpass is suid root. I have the same issue. kcheckpass is suid root and works: tijl@kalimero ~% kcheckpass; echo $? Password: 0 tijl@kalimero ~% The error message given when I try to unlock is: Cannot unlock session because the authentication system failed to work; you must kill kdesktop_lock (pid xxxx) manually.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200701082038.33761.tijl>