From owner-freebsd-gnome@FreeBSD.ORG Sat Jun 5 04:53:10 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 9207F1065672 for ; Sat, 5 Jun 2010 04:53:10 +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 473D38FC0C for ; Sat, 5 Jun 2010 04:53:10 +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 o554r9aI013223; Sat, 5 Jun 2010 00:53:09 -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 o554r9NG005042; Sat, 5 Jun 2010 00:53:09 -0400 (EDT) Message-ID: <4C09D834.9080801@freebsd.org> Date: Sat, 05 Jun 2010 00:53:08 -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: Lingfeng Xiong References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-gnome@freebsd.org Subject: Re: gnome-session lost its folder in /proc 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: Sat, 05 Jun 2010 04:53:10 -0000 On 6/2/10 12:44 AM, Lingfeng Xiong wrote: > hi all, > I have run into a confusing problem of GNOME. The gnome-panel have a very > very slow speed to appear after I entered "startx". And there are so many > error messages in the tty1: > [quote] > record: RECORD extension enabled at configure time. > record: This extension is known to be broken, disabling extension now.. > record: http://bugs.freedesktop.org/show_bug.cgi?id=20500 > gnome-session[5689]: WARNING: Unable to determine session: Unable to lookup > sess > ion information for process '5689' > GNOME_KEYRING_CONTROL=/var/tmp/keyring-hXBL8l > GNOME_KEYRING_PID=5707 > May 24 16:41:37 bear gnome-keyring-daemon[5707]: couldn't allocate secure > memory > to keep passwords and or keys from being written to the disk > GNOME_KEYRING_CONTROL=/var/tmp/keyring-hXBL8l > SSH_AUTH_SOCK=/var/tmp/keyring-hXBL8l/ssh > GNOME_KEYRING_CONTROL=/var/tmp/keyring-hXBL8l > SSH_AUTH_SOCK=/var/tmp/keyring-hXBL8l/ssh > 窗口管理器警告：无法读取保存的会话文件 /home/bear/.config/met > acity/sessions/102b991067f3508b1112746904977822500000056890013.ms：打开文件 > “/home/bear/.config/metacity/sessions/102b991067f3508b111274690497782250000005 > 6890013.ms”失败：No such file or directory > May 24 16:41:39 bear pulseaudio[5734]: pid.c: Daemon already running. > > ** (gnome-panel:5719): WARNING **: Could not ask session manager if shut > down is > available: Did not receive a reply. Possible causes include: the remote > applica > tion did not send a reply, the message bus security policy blocked the > reply, th > e reply timeout expired, or the network connection was broken. > > ** (gnome-panel:5719): WARNING **: Error deleting > '/home/bear/.gnome2/panel2.d/d > efault/launchers/evolution.desktop': 移除文件出错：No such file or direct > ory > > [/quote] > Some characters in it are Chinese but they are not important. > I think the problem is that the gnome-session cannot read its information so > gnome-panel cannot ask it for response. > I am pretty sure that I have mounted /proc and added dbus_enable="YES" and > hald_enable="YES" into /etc/rc.conf. > But the strange thing is that every process has a folder in /proc named by > its pid except gnome-session. > I have tried both port and packages, and the problem still there. > The thread which talking about this problem is at > http://forums.freebsd.org/showthread.php?t=14456 , you can got some more > information there. If you need more detail, plz contact me. I only wanna > this problem solved ;) Try rebuilding and reinstalling sysutils/polkit, sysutils/policykit, and sysutils/consolekit. That should fix this. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome