From owner-freebsd-current@FreeBSD.ORG  Mon Jan 15 12:47:52 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 71F4D16A412
	for <freebsd-current@freebsd.org>; Mon, 15 Jan 2007 12:47:52 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42])
	by mx1.freebsd.org (Postfix) with ESMTP id 4884413C45D
	for <freebsd-current@freebsd.org>; Mon, 15 Jan 2007 12:47:52 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [209.31.154.41])
	by cyrus.watson.org (Postfix) with ESMTP id C996A4A685;
	Mon, 15 Jan 2007 07:47:51 -0500 (EST)
Date: Mon, 15 Jan 2007 12:47:51 +0000 (GMT)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Daniel O'Connor <doconnor@gsoft.com.au>
In-Reply-To: <200701152055.18416.doconnor@gsoft.com.au>
Message-ID: <20070115124603.R24395@fledge.watson.org>
References: <200701152055.18416.doconnor@gsoft.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: andre@FreeBSD.org, freebsd-current@freebsd.org, kde@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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jan 2007 12:47:52 -0000


On Mon, 15 Jan 2007, Daniel O'Connor wrote:

> 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?

Yes -- Peter recently ran into this, and John did a bit of debugging. 
Andre's work to optimize socket send may have broken 0-byte writes on stream 
sockets.  My recent commit of the zerosend regression test is intended to help 
encourage fixing it.  :-)  I've not investigated exactly why KDE performs 
zero-byte writes on a stream socket, but it could be it's sending ancillary 
data but no normal data.  Whether it's legitimate or not, we should fix this, 
however.

Robert N M Watson
Computer Laboratory
University of Cambridge