From owner-freebsd-current@FreeBSD.ORG Tue Jan 16 08:10:06 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 09EC616A412 for ; Tue, 16 Jan 2007 08:10:05 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with SMTP id 8A6A413C45A for ; Tue, 16 Jan 2007 08:10:05 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 13055 invoked by uid 399); 16 Jan 2007 08:10:01 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 16 Jan 2007 08:10:01 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45AC8856.1090707@FreeBSD.org> Date: Tue, 16 Jan 2007 00:09:58 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Andre Oppermann References: <200701152055.18416.doconnor@gsoft.com.au> <20070115164034.GC74652@lor.one-eyed-alien.net> <45ABBFCC.3040204@freebsd.org> In-Reply-To: <45ABBFCC.3040204@freebsd.org> X-Enigmail-Version: 0.94.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Can't unlock desktop after updating to recent -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2007 08:10:06 -0000 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