Date: Mon, 15 Jan 2007 10:40:34 -0600 From: Brooks Davis <brooks@one-eyed-alien.net> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: freebsd-current@freebsd.org, kde@freebsd.org Subject: Re: Can't unlock desktop after updating to recent -current Message-ID: <20070115164034.GC74652@lor.one-eyed-alien.net> In-Reply-To: <200701152055.18416.doconnor@gsoft.com.au> References: <200701152055.18416.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--6zdv2QT/q3FMhpsV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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=20 > desktop - I have to manually kill the kdesktop_lock process. >=20 > I've recompiled kdebase but it had no effect. I plan to try kdelibs soon. >=20 > 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. -- Brooks --6zdv2QT/q3FMhpsV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFq66CXY6L6fI4GtQRAv+PAJ0TDqR5LENKHk2QvgIN3Ktw7oBr+QCeIEAb wN4PgEyLxQn29muk1pZcgEQ= =90Ez -----END PGP SIGNATURE----- --6zdv2QT/q3FMhpsV--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070115164034.GC74652>