From owner-freebsd-gnome@FreeBSD.ORG Tue Jun 15 22:41:56 2010 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51791106567D for ; Tue, 15 Jun 2010 22:41:56 +0000 (UTC) (envelope-from marcus@freebsd.org) Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by mx1.freebsd.org (Postfix) with ESMTP id 0AB348FC0C for ; Tue, 15 Jun 2010 22:41:55 +0000 (UTC) X-TACSUNS: Virus Scanned Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id o5FMfsrc011315; Tue, 15 Jun 2010 18:41:55 -0400 (EDT) Received: from fruit-rollup.marcuscom.com (jclarke-pc.cisco.com [172.18.254.236]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id o5FMfoHE028145; Tue, 15 Jun 2010 18:41:50 -0400 (EDT) Message-ID: <4C1801AE.2040409@freebsd.org> Date: Tue, 15 Jun 2010 18:41:50 -0400 From: Joe Marcus Clarke Organization: FreeBSD, Inc. User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: Bear References: , <4C171C41.1080405@freebsd.org>, <201006160003293357455@Gmail.com>, <4C17A631.5060407@freebsd.org> <201006160113087580919@Gmail.com> In-Reply-To: <201006160113087580919@Gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-gnome Subject: Re: GNOME can work well in VMWare but cannot work in real machine X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2010 22:41:56 -0000 On 6/15/10 1:13 PM, Bear wrote: > hi, > I have done this. I created a new account named 'test' but it still have this problem... Can you rebuild gnome-panel and gnome-session with debugging symbols, then attach gdb while gnome-panel is "hung?" Once attached, run "bt" to get a backtrace. That may help isolate the problem. Joe > > ------------------ > Bear > 2010-06-16 > > ------------------------------------------------------------- > From:Joe Marcus Clarke > Send Date:2010-06-16 00:11:32 > To:Bear > CC:freebsd-gnome > Subject:Re: GNOME can work well in VMWare but cannot work in real machine > > On 6/15/10 12:03 PM, Bear wrote: >> hi, Yes of course I am sure that my hostname is reslovable. I used to >> install GDM but it still has this problem. And also, I dont wanna >> install it because I *DO NOT* need it. > > You might try creating a virgin account on the problem machine, and see > if the problem follows the account. That is, a new account may not see > any problem. > > Joe > >> >> ------------------ Bear 2010-06-16 >> >> ------------------------------------------------------------- >> From:Joe Marcus Clarke Send Date:2010-06-15 14:23:03 To:Lingfeng >> Xiong CC:freebsd-gnome Subject:Re: GNOME can work well in VMWare but >> cannot work in real machine >> >> On 6/14/10 9:50 PM, Lingfeng Xiong wrote: >>> hi there, I found a strange thing. As I described, my GNOME cannot >>> work with these error messages: gnome-session[69785]: WARNING: >>> Unable to determine session: Unable to lookup ses sion information >>> for process '69785' ** (gnome-panel:69812): WARNING **: Could not >>> ask session manager if shut down i s available: Did not receive a >>> reply. Possible causes include: the remote applic ation did not >>> send a reply, the message bus security policy blocked the reply, t >>> he reply timeout expired, or the network connection was broken. >>> >>> >>> And gnome-panel has a very very slow responding. And also, the >>> driver cannot be mounted without any error message. The thread >>> about this problem with more information is here: >>> http://forums.freebsd.org/showthread.php?t=15013 >>> >>> I has performed a test, and found that GNOME can work well in my >>> VMWare!! But in my real machine, no matter how many times I >>> reinstalled my system, it cannot work. Could you help me? thx!! >> >> Make sure your machine's hostname is resolvable, and make sure you >> are running gdm. Gdm will provide GNOME the ability to reboot and >> shutdown. >> >> Joe >> > > -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome