From: Gary Thomas <gary@mlbassoc.com>
To: Poky Project <poky@yoctoproject.org>
Subject: Re: TERMCMD and SSH
Date: Fri, 15 Jul 2011 06:52:14 -0600 [thread overview]
Message-ID: <4E2037FE.4010501@mlbassoc.com> (raw)
In-Reply-To: <4E2030F3.9050906@mlbassoc.com>
On 07/15/2011 06:22 AM, Gary Thomas wrote:
> I often build Poky on remote systems which I access using 'ssh -X' (SSH
> connection with X forwarding). However, I have problems when the build
> needs to open a terminal window, e.g. 'bitbake virtual/kernel -c menuconfig'
> I get this error:
>
> | Failed to summon the GConf demon; exiting. Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale
> NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Address does not contain a colon)
>
> As far as I can see, bitbake is trying to run this command:
> gnome-terminal --disable-factory -t "something" -x "make menuconfig"
>
> If I run this command manually from my SSH window, it works fine.
> How can I get it working from bitbake? I tried adding 'SSH_CONNECTION'
> and 'DISPLAY' (both set specially in this situation) to BB_ENV_EXTRAWHITE
> without success.
I found that if I set
TERMCMD="${XTERM_TERMCMD}"
TERMCMDRUN ?= "${XTERM_TERMCMDRUN}"
it works fine via SSH. I like the look of 'xterm' better than 'gnome-terminal'
so that's what I'll use, but I'd like to understand why the GNOME version does
not work.
Note: I had to edit meta/conf/bitbake.conf to change these. Putting
them in local.conf had no effect.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2011-07-15 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 12:22 TERMCMD and SSH Gary Thomas
2011-07-15 12:52 ` Gary Thomas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E2037FE.4010501@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.