Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Andrea Adami <andrea.adami@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: devshell spawning twice
Date: Wed, 31 Oct 2012 15:11:51 +0000	[thread overview]
Message-ID: <14856362.dnuymTkSFD@helios> (raw)
In-Reply-To: <CAAQYJAu+7f+HLBp5xTw8fQk7H5b91=pc5pbkvMB4wEXXhcCpEQ@mail.gmail.com>

On Tuesday 30 October 2012 00:23:52 Andrea Adami wrote:
> On Sun, Oct 28, 2012 at 1:59 AM, Andrea Adami <andrea.adami@gmail.com> 
wrote:
> > On Sun, Oct 28, 2012 at 1:55 AM, Andrea Adami <andrea.adami@gmail.com> 
wrote:
> >> Since commit c76da87511d2668479745c2f18b8a9b8116c7489 (terminal: Add
> >> support for running custom terminals.) screen opens also in the master
> >> terminal, waiting for input.
> >> 
> >> Reverting the patch fixes the funny behavior.
> >> 
> >> This on Gentoo, using xterm.
> > 
> > Sorry, is gnome-terminal on this host.
> > 
> >> Regards
> >> 
> >> Andrea
> 
> Same happens using Ubuntu as build host: bitbake -c devshell foo
> launched in uXterm does spawn two gnome-terminals.
> This has also other bad effects on do_menuconfig task for linux-yocto.
> 
> I can confirm that reverting c76da87 fixes the things.

Confirmed here. I have filed a bug:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=3371

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-10-31 15:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-27 23:55 devshell spawning twice Andrea Adami
2012-10-27 23:59 ` Andrea Adami
2012-10-29 23:23   ` Andrea Adami
2012-10-31 15:11     ` Paul Eggleton [this message]
2012-10-30  8:07 ` Robert Yang
2012-10-31  8:18   ` Richard Purdie
2012-11-02  2:28     ` Robert Yang
2012-11-02 11:28       ` Richard Purdie
2012-11-04  7:58         ` Robert Yang

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=14856362.dnuymTkSFD@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=andrea.adami@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox