From owner-freebsd-ports@FreeBSD.ORG Tue Apr 19 22:52:06 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95B5816A4CE; Tue, 19 Apr 2005 22:52:06 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60F5943D55; Tue, 19 Apr 2005 22:52:06 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Tue, 19 Apr 2005 15:52:05 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 22C0D5D07; Tue, 19 Apr 2005 15:52:05 -0700 (PDT) To: Jung-uk Kim In-reply-to: Your message of "Tue, 19 Apr 2005 18:30:12 EDT." <200504191830.12579.jkim@niksun.com> Date: Tue, 19 Apr 2005 15:52:05 -0700 From: "Kevin Oberman" Message-Id: <20050419225205.22C0D5D07@ptavv.es.net> cc: freebsd-current@freebsd.org cc: David Xu cc: freebsd-ports@freebsd.org Subject: Re: gnome can not shutdown X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2005 22:52:06 -0000 > From: Jung-uk Kim > Date: Tue, 19 Apr 2005 18:30:12 -0400 > Sender: owner-freebsd-current@freebsd.org > > On Saturday 16 April 2005 08:03 pm, David Xu wrote: > > David Xu wrote: > > > With newest -CURRENT kernel, I can not shutdown gnome from > > > panel, did anyone encounter the problem ? > > > > > > David Xu > > > > Here is some gdb outputs, it seems thread 2 stuck in connect(), > > is UNIX socket broken ? > > I am experiencing the same problem. I rebuilt whole system from world > and ports, tried different threading libraries, kernel options, > removed gnome configurations from home directory, etc. but nothing > helped. :-( I am using Xfce4 for now... Just a "me too" (TM-AOL). In my case I see one application, gkrellm, locking up things. It is stuck in a run state (literally Rs), but is consuming almost no CPU and can't be killed. kill-9 is simply ignored. I can only get out of gnome with CRTL-ALT-BS and, when I shout down the system, I am notified that one or more processes can't be killed. I'm sure that it is referring to gkrellm. The problem started sometime after March 31. I have backed up to April 5 and I am still seeing the problem. I will continue to try to track down exactly when it started as time permits. Is this the same problem? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634