After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 680507 - Keyboard shortcuts not working anymore after upgrade to GNOME 3.4
Keyboard shortcuts not working anymore after upgrade to GNOME 3.4
Status: RESOLVED DUPLICATE of bug 662580
Product: gnome-settings-daemon
Classification: Core
Component: keybindings (obsolete)
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2012-07-24 07:58 UTC by Stephan Haller
Modified: 2012-08-30 01:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stephan Haller 2012-07-24 07:58:21 UTC
Hi,

since I upgraded GNOME 3.2 to GNOME 3.4 my keyboard shortcuts don't work anymore. First I thought the shortcut "Start a terminal" in group "Desktop" was removed but even after I created a custom shortcut using the same key-press sequence it doesn't work. I set "<Mod4> + T" to start a terminal whereby Mod4 modifier is the "Windows" key in my german keyboard layout.

It looks like the modifier "<Mod4>" is eaten by any component and the "key press" to left to a single "T". My workaround is to use "<Ctrl><Alt> + T" in the moment.

Steps to Reproduce:

1.) Open "Keyboard" in Gnome Control Center and select tab "Shortcuts".
2.) Create a custom shortcut in group "Custom Shortcuts" with name "Start terminal" with the command "gnome-terminal"
3.) Assign "<Mod4> + T" to it

Actual Results:

Press "<Mod4> + T" to start a terminal but you will get a filter box of GTK+ for the list (GtkListView?) of shortcuts instead of a terminal window.


Expected Results:

A terminal should be started.

Additional Platform Information:
Gnome 3.4.2 on Gentoo amd64

Regards,
Stephan
Comment 1 Florian Müllner 2012-08-30 01:55:04 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 662580 ***