Date: Tue, 16 Jan 2007 00:09:58 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Andre Oppermann <andre@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: Can't unlock desktop after updating to recent -current Message-ID: <45AC8856.1090707@FreeBSD.org> In-Reply-To: <45ABBFCC.3040204@freebsd.org> References: <200701152055.18416.doconnor@gsoft.com.au> <20070115164034.GC74652@lor.one-eyed-alien.net> <45ABBFCC.3040204@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Andre Oppermann wrote:
> 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.
I've also been bitten by this with -current + windowmaker +
xscreensaver, so if you need another guinea pig, let me know.
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45AC8856.1090707>