Date: Sat, 11 Dec 2010 20:48:02 +0530 From: ashish@freebsd.org (Ashish SHUKLA) To: Andrea Venturoli <ml@netfence.it> Cc: Ashish SHUKLA <ashish@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: emacs and gconf troubles Message-ID: <86lj3wpcd1.fsf@chateau.d.if> In-Reply-To: <4CFC9C0D.1080702@netfence.it> (Andrea Venturoli's message of "Mon, 06 Dec 2010 09:17:17 %2B0100") References: <4CFA816B.9080505@netfence.it> <86aakkjoax.fsf@chateau.d.if> <4CFBFEB2.8000502@netfence.it> <8662v7khyd.fsf@chateau.d.if> <4CFC9C0D.1080702@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi Andrea, Sorry for the late reply. Andrea Venturoli writes: > On 12/05/10 22:50, Ashish SHUKLA wrote: >> setup, which is 'startx' based, with following contents of $HOME/.xinitr= c: >>=20 >> #v+ >> #!/bin/sh >>=20 >> xrdb ~/.Xdefaults >> xmodmap ~/.Xmodmap >> exec dbus-launch --exit-with-session ck-launch-session xmonad 2>$HOME/.x= session-errors >> #v- > I've got dbus_enable=3D"YES" in /etc/rc.conf; I don't remember why. > I probably read about it in some entry in UPDATING; that might be > 20061219: I also run hald, but not polkit... > # ps ax|grep dbus > 1620 ?? I 0:00.00 dbus-launch > --autolaunch=3Db3fbd8cb89ee22fd22fc292600001a5f --binary-syntax > --close-stderr > 1621 ?? Is 0:00.00 /usr/local/bin/dbus-daemon --fork > --print-pid 6 --print-address 8 --session > 1697 ?? Ss 0:00.00 /usr/local/bin/dbus-daemon --system > Anyway, I tried stopping dbus and I get the same warning. 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 "dbu= s" keeps running in the same TTY after you close emacs, so when you try to exit From=20the SSH session, it hangs waiting for all processes (attached to cur= rent TTY) to exit, and therefore you've to kill the SSH session forcibly. To ver= ify this, you can kill the started dbus-daemon (attached to the same TTY) and y= ou should be able to exit from SSH session as usual. I'm not sure if my explanation is correct for this behavior. HTH =2D-=20 Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 freebsd.org!ashish | http://people.freebsd.org/~ashish/ Avoid Success At All Costs !! --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iQIcBAEBCgAGBQJNA5YvAAoJEMdGz6nnT6SwUzcP/i/MbvwgXlpUkqg0e10/oV1O yQOfT6Ugp1Jbvbh2HlT9ebL8sXeTrsrFrkuq/gKaRZ0PgyyZnk7y3Tbi0uHi9jYJ ZdgIHC00dPk+9Ke3RMjtlCfxzfHyIGa8g/ZSzxSiAQeH+xAwVt11tIceTpsBIaqC nSyqn+nLWxkuS95G6aGrUDw3l/lOir0l/PE8Vs77BMGespJqumHGzOPrfG1xFJCy NgcQ5mByvQuXOudE0IwmFXAUqU8OKFKEufrmJdKZpdBc+fRhRVuOHI9+PQZJLLgG 1k1R6f/3CnuiRpCj3ZPLX5MeeUfTfwZwDP6E9GbzPKpXgoid39yGvYfBqTWIziOe oUQFQtfEhrYjA2ZF2uwPligXdALkRc9xfekO7qPOZyF0gOnR9eMCPTR5jJbc4M6O hSur0wZut//23NyTRu/bgADSH+riVFKIFN2g5xivN9YR5ldvw7LI/KsmQrJK7jRo 6mCP2L7bIav2h/NdBKKyhFNj2E16D2E6m6BgCu3cguGnKuEUnsLYf7dEqm5LP+fI Z8+RUZ0ig7aHbO/WAHqVCWTpe7X96FmNrjZ1eP7rfF3FVyXI+2MTyrgdgkpHb8Ro 3iIoBhjZRWwqk1vr/ZeKu7/xjQCUf30A/lIJC7L/TLdlIL+laGZWDWif8ZMrTmS1 3Q7FMjgU2AyieGemqIyS =T026 -----END PGP SIGNATURE----- --=-=-=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86lj3wpcd1.fsf>