Date: Mon, 15 Jan 2007 18:54:20 +0100 From: Andre Oppermann <andre@freebsd.org> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: freebsd-current@freebsd.org, kde@freebsd.org Subject: Re: Can't unlock desktop after updating to recent -current Message-ID: <45ABBFCC.3040204@freebsd.org> In-Reply-To: <20070115164034.GC74652@lor.one-eyed-alien.net> References: <200701152055.18416.doconnor@gsoft.com.au> <20070115164034.GC74652@lor.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Brooks Davis wrote: > On Mon, Jan 15, 2007 at 08:55:07PM +1030, Daniel O'Connor wrote: > >>Hi, >>I recently updated my machine to -current, however I can nolonger unlock my >>desktop - I have to manually kill the kdesktop_lock process. >> >>I've recompiled kdebase but it had no effect. I plan to try kdelibs soon. >> >>Is this a known issue? > > > The problem is apparently due to breaking of sending zerobyte messages > over certain types of sockets. I think peter has a patch that works > around it in KDE, but I'm not sure it's available anywhere. I have a fix in the works. -- Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45ABBFCC.3040204>