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 689839 - Keyboard layout switching with modifier-only shortcuts is broken in lockscreen and command window
Keyboard layout switching with modifier-only shortcuts is broken in lockscree...
Status: RESOLVED DUPLICATE of bug 697008
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
: 692290 694879 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-12-07 11:57 UTC by Alexander Bokovoy
Modified: 2013-04-02 08:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexander Bokovoy 2012-12-07 11:57:08 UTC
When keyboard layout switching set to modifier-only shortcuts (available through bug 681685 solution), there are issues in GNOME 3.6.2. They are observable with, for example, CapsLock set as a modifier.

- Lockscreen does not allow to use the modifier to switch layout. More to that, when layout is switched via the language button in the password/unlock dialog, the changed state is not propagated and keyboard applet in GNOME3 desktop does not show correct layout.

- Command window (ALT+F2) of the GNOME3 desktop does not allow to use the modifier to switch keyboard layout. Since there is no language button, it is not possible to switch layout at all.
Comment 1 Matthias Clasen 2012-12-07 22:32:01 UTC
This is part of the larger problem that  _no_ keyboard shortcuts work in any modes where gnome-shell has a grab. It is being addressed for 3.8
Comment 2 Florian Müllner 2013-01-22 13:34:00 UTC
*** Bug 692290 has been marked as a duplicate of this bug. ***
Comment 3 Florian Müllner 2013-02-28 16:33:55 UTC
*** Bug 694879 has been marked as a duplicate of this bug. ***
Comment 4 Rui Matos 2013-04-02 08:06:28 UTC
I filed a patch in bug 697008 for this.

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