From owner-freebsd-stable@FreeBSD.ORG Wed Aug 11 01:34:46 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E539516A4CE for ; Wed, 11 Aug 2004 01:34:46 +0000 (GMT) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3E0A43D2F for ; Wed, 11 Aug 2004 01:34:45 +0000 (GMT) (envelope-from jesper@hackunite.net) Received: from mail.hackunite.net ([213.112.193.12] [213.112.193.12]) by mxfep02.bredband.com with SMTP <20040811013444.PUTI23867.mxfep02.bredband.com@mail.hackunite.net> for ; Wed, 11 Aug 2004 03:34:44 +0200 Received: from 213.112.193.117 (SquirrelMail authenticated user z3l3zt@hackunite.net) by mail.hackunite.net with HTTP; Wed, 11 Aug 2004 03:35:53 +0200 (CEST) Message-ID: <3011.213.112.193.117.1092188153.squirrel@mail.hackunite.net> Date: Wed, 11 Aug 2004 03:35:53 +0200 (CEST) From: "Jesper Wallin" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: SquirrelMail 1.4.2 X-Priority: 3 Importance: Normal Subject: "Unable to read from thread kernel pipe" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2004 01:34:47 -0000 Hello.. I've finally installed and configured my freebsd system to work as I want as a workstation.. I've been running it for like 2-3 days and rebooted a couple of times for different reasons.. Today, when I started XFree86 4.3.0 with Xfce4, it starts normally, but as soon as I tried to start any programs from the menu/panel, it's crashing and I get a "Unable to read from thread kernel pipe" error.. I've tried deinstalling and recompiling any xfce4 programs/components, yet, I have the same error.. I've also seen some people on google having the same problem, but yet no solution to the error.. What is causing this and how can I solve/prevent it from happening again? Regards, Jesper Wallin