It's a medium priority since one can just exit from the menuconfig session first. Robert please see if we can correct the behaviour to have bitbake kill the terminal session on the second control-c.

Was the milestone value changed by mistake?

> Was the milestone value changed by mistake?
Yes. Fixed.

This issue only happens with gnome-terminal which introduced by commit: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=c706bfbabbf9f7caf2cf509eb91381fb49aa44cb

For more details, please see:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7254

As workaround, you could set OE_TERMINAL = "xterm" or OE_TERMINAL = "rxvt" in conf/local.conf.

For more details, please see bug 7254 Comment 11 . The root cause is when the gnome-terminal gets spawned, it becomes a child process for gnome-terminal-sever. Once bitbake process gets the SIGTERM, it can not kill the gnome-terminal as it is not the child process for bitbake.

It seems the Ubuntu (16.04) keeps the --disable-factory option for gnome-terminal. If you are using gnome-terminal on Ubuntu, you could apply the following patch as a workaround:

diff --git a/meta/lib/oe/terminal.py b/meta/lib/oe/terminal.py
index 94afe39..908a95d 100644
--- a/meta/lib/oe/terminal.py
+++ b/meta/lib/oe/terminal.py
@@ -52,7 +52,7 @@ class XTerminal(Terminal):
             raise UnsupportedTerminal(self.name)
 
 class Gnome(XTerminal):
-    command = 'gnome-terminal -t "{title}" -x {command}'
+    command = 'gnome-terminal --disable-factory -t "{title}" -x {command}'
     priority = 2
 
     def __init__(self, sh_cmd, title=None, env=None, d=None):

As comment in bug 7254 Comment 11 . The root cause is when the gnome-terminal gets spawned, it becomes a child process for gnome-terminal-sever. Once bitbake process gets the SIGTERM, it can not kill the gnome-terminal as it is not the child process for bitbake.

As workaround, you could set OE_TERMINAL = "xterm" or OE_TERMINAL = "rxvt" in conf/local.conf.