From owner-freebsd-ports@FreeBSD.ORG Sun Dec 12 13:53:28 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61284106566B; Sun, 12 Dec 2010 13:53:28 +0000 (UTC) (envelope-from ml@netfence.it) Received: from cp-out7.libero.it (cp-out7.libero.it [212.52.84.107]) by mx1.freebsd.org (Postfix) with ESMTP id CF1C48FC14; Sun, 12 Dec 2010 13:53:27 +0000 (UTC) X-CTCH-Spam: Unknown X-CTCH-RefID: str=0001.0A0B0209.4D04D3D6.006F,ss=1,re=0.000,fgs=0 X-libjamoibt: 1555 Received: from soth.ventu (151.51.49.144) by cp-out7.libero.it (8.5.133) id 4D0257DF002F7AA9; Sun, 12 Dec 2010 14:53:26 +0100 Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.4/8.14.4) with ESMTP id oBCDrK7a030560; Sun, 12 Dec 2010 14:53:21 +0100 (CET) (envelope-from ml@netfence.it) Message-ID: <4D04D3D0.6080008@netfence.it> Date: Sun, 12 Dec 2010 14:53:20 +0100 From: Andrea Venturoli User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; it-IT; rv:1.9.2.13) Gecko/20101211 Thunderbird/3.1.7 MIME-Version: 1.0 To: Ashish SHUKLA References: <4CFA816B.9080505@netfence.it> <86aakkjoax.fsf@chateau.d.if> <4CFBFEB2.8000502@netfence.it> <8662v7khyd.fsf@chateau.d.if> <4CFC9C0D.1080702@netfence.it> <86lj3wpcd1.fsf@chateau.d.if> In-Reply-To: <86lj3wpcd1.fsf@chateau.d.if> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.1.2.13 Cc: freebsd-ports@freebsd.org Subject: Re: emacs and gconf troubles X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Dec 2010 13:53:28 -0000 On 12/11/10 16:18, Ashish SHUKLA wrote: > Hi Andrea, > > Sorry for the late reply. No problem! Really, thanks for your help. > Okay, I'm able to reproduce warnings. As emacs tries to lookup DBUS session > bus in the environment, and if it doesn't find one, it starts one. And "dbus" > keeps running in the same TTY after you close emacs, so when you try to exit > From the SSH session, it hangs waiting for all processes (attached to current > TTY) to exit, and therefore you've to kill the SSH session forcibly. To verify > this, you can kill the started dbus-daemon (attached to the same TTY) and you > should be able to exit from SSH session as usual. > > I'm not sure if my explanation is correct for this behavior. I think it only explains part of it. Scenario A: _ dbus is running on localhost; _ I run Konsole and start Emacs from there; _ I get the warning (but DBUS is running!!!); _ after I exit Emacs, Konsole usually closes, but not always (!!!). Scenario B: _ dbus is running on localhost; _ I run Konsole and SSH into another box; _ on the remote box dbus is not running; _ I run Emacs, get the warning and DBUS is started; _ after I exit Emacs I cannot close Konsole unless I also close DBUS. So your explanation fits the second scenario perfectly, but does not explain the first. Also, I read I shouldn't run DBUS on the remote machine, but let Emacs connect to the one on localhost? Is this true? How do I do it? Should I run DBUS from rc on every box? bye & Thanks av.