unity-gtk-module blocks several applications the F10 key press

Bug #1253913 reported by Attila Hammer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-gtk-module (Ubuntu)
New
Undecided
Unassigned

Bug Description

Dear Developers,

My Ubuntu Saucy and later my Ubuntu trusty installation the Gnome Terminal F10 key not activating main menu bar, independent if checked the F10 key related check box in Shortcuts preference pane or not.
My previous Saucy installation after I upgraded with GNOME 3.10 version I experienced similar results.
When I previous upgraded, I added ppa:gnome3-team/gnome3, gnome3-team/staging, and gnome3-team/gnome3-next ppa's and doed an apt-get dist-upgrade command.
I using Saucy with GNOME Shell classic session mode the Orca Screen Reader.
Have chance this bug existing in Ubuntu 14.04 development release too.

Attila

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gnome-terminal 3.6.1-0ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
Date: Fri Nov 22 08:39:00 2013
InstallationDate: Installed on 2013-11-21 (0 days ago)
InstallationMedia: BeLin 3.02 i386
MarkForUpload: True
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Attila Hammer (hammera) wrote :
Revision history for this message
Attila Hammer (hammera) wrote :

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

Revision history for this message
Attila Hammer (hammera) wrote :

I think I possible founding what the real problem, very crazy if this is real true, please confirm my test result in GNOME Shell:
If unity-gtk3-module and unity-gtk2-module installed a system (this is the case with basic installation), and the actual session is not Unity, the F10 key press blocking the proper module for example with following apps:
gnome-terminal, Pidgin, Totem.
I don't no what other applications are affected, I found this applications already this issue.
I removed this two packages with sudo apt-get purge unity-gtk3-module unity-gtk2-module command.
After the packages removed and I logout and log in again, the F10 key press again presenting main menu with gnome-terminal, Totem, Pidgin applications.
How can possible fixing this issue without lost functionality in Unity environment, but other sessions works right the F10 key with all applications without need defining blacklist scheme and adding all affected applications?
I no, Ubuntu default session is Unity, but I think need fixing this issue to all other sessions works right the F10 key press with other sessions.
This bug affecting bigger for example visually impaired users with have possibility only to use keyboard and screen reader.

Attila

Attila Hammer (hammera)
description: updated
summary: - In Gnome Terminal F10 key not activating menu bar
+ unity-gtk-module blocks several applications the F10 key press
affects: gnome-terminal (Ubuntu) → unity-gtk-module (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.