Comment 2 for bug 1253913

I reproduced this issue in Ubuntu 14.04 development release, the GNOME Shell environment absolute sure.
Because I using only with keyboard the gnome-terminal application and screen reader support, if this working method not a bug, anybody please tell me what gconf/gsettings key I have possibility enable again the F10 key main menubar activation possibility.
The edit menu, shortcut preference pane awailable F10 related check box possible nothing doing, I not see any gsettings value changes if I changing this check box state and closed the prerefence pane.
Before I changing checkbox state, I ran gsettings list-recursively >filename1 command. After this, I changed the checkbox state and ran again gsettings list-recursively >file2 command, and doed a diff -u file1 file2 command to look the differences.
Unfortunately not have differences. :-(:-(

I tryed compiling an original upstream gnome-terminal 3.8 release from git, but because have dependency problems with ./autogen.sh command, I not succesfuly doing the upstream verification.
In gnome-terminal upstream 3.8 source tree the ./autogen.sh give following errors:
configure: error: Package requirements (vte-2.90 >= 0.34.6
   glib-2.0 >= 2.32.0
   gio-2.0 >= 2.33.2
   gtk+-3.0 >= 3.6.0
   gsettings-desktop-schemas >= 0.1.0
   dconf >= 0.12.0
   uuid
   x11) were not met:

No package 'dconf' found
No package 'uuid' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables TERM_CFLAGS
and TERM_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

Attila