*** This bug is a duplicate of bug 878492 ***
https://bugs.launchpad.net/bugs/878492
** This bug is no longer a duplicate of bug 726639
F10 is captured even if gnome-terminal setting is explictly set to not
capture
** This bug has been marked a duplicate of bug 878492
Keyboard shortcut
*** This bug is a duplicate of bug 726639 ***
https://bugs.launchpad.net/bugs/726639
** This bug has been marked a duplicate of bug 726639
F10 is captured even if gnome-terminal setting is explictly set to not
capture
* You can subscribe to bug 726639 by following this link:
https://bugs
This should get passed to application inside of terminal, you're right.
Setting to confirmed sorry; I misunderstood the report for a moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/722680
Title:
Ok so this was actually added to Unity itself and I was unaware of it.
This is expected behavior and not a bug in Unity. It is a bit confusing
though, but I think that this bug should be re-targeted against GNOME
terminal.
** Changed in: unity
Status: New => Won't Fix
** Changed in: unity
Alex, I've just tested gnome-terminal on a freshly updated Natty classic
desktop with indicator-appmenu. Here's what I get:
When checkbox "Enable the menu shortcut key (F10 by default)" is
checked, F10 key doesn't work at all. But when the checkbox is
*unchecked*, F10 key does work and it can be v
Interestingly it doesn't work at all for me in default gnome session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/722680
Title:
Unexpected F10 key behaviour in GNOME terminal
--
ubuntu-bugs mail
Unity doesn't handle F10 as a menu command by default. Could you verify
that this is behaving correctly in a classic gnome session and that it's
not a bug in gnome-terminal?
** Changed in: unity
Status: New => Incomplete
** Changed in: unity (Ubuntu)
Status: New => Incomplete
--
Y
