From owner-freebsd-current@FreeBSD.ORG  Mon Jan 15 21:50:41 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 EF69F16A47C
	for <freebsd-current@freebsd.org>; Mon, 15 Jan 2007 21:50:41 +0000 (UTC)
	(envelope-from spaceman@stonehenge.sk)
Received: from otana.stonehenge.sk (otana.stonehenge.sk [82.208.39.177])
	by mx1.freebsd.org (Postfix) with SMTP id 34D7A13C4EF
	for <freebsd-current@freebsd.org>; Mon, 15 Jan 2007 21:50:38 +0000 (UTC)
	(envelope-from spaceman@stonehenge.sk)
Received: (qmail 46389 invoked by uid 1000); 15 Jan 2007 21:24:03 -0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on otana.stonehenge.sk
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RECEIVED,NO_RELAYS 
	autolearn=disabled version=3.1.7
Date: Mon, 15 Jan 2007 22:24:03 +0100
From: Varga Michal <varga@stonehenge.sk>
To: Andre Oppermann <andre@freebsd.org>
Message-ID: <20070115212403.GB1049@stonehenge.sk>
References: <200701152055.18416.doconnor@gsoft.com.au>
	<20070115164034.GC74652@lor.one-eyed-alien.net>
	<45ABBFCC.3040204@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <45ABBFCC.3040204@freebsd.org>
User-Agent: Mutt/1.4.2.2i
Cc: 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 21:50:42 -0000

On Mon, 2007-Jan-15 at 18:54:20 +0100, 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.
> 
Just for the record, this problem doesn't seem to be KDE-specific. I'm experiencing the same behaviour under Gnome 2.16 - xscreensaver isn't able to 
correctly close itself and without manually killing the proces, you are not able to return to the desktop.

- i386 FreeBSD 7.0-CURRENT #0: Mon Jan 15 06:48:57 CET 2007
- gnome2-2.16.2  
- xscreensaver-gnome-hacks-4.24_1 

Sending a sigterm to gnome-screensaver does the trick.

m.