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 696278 - Unable to switch keyboard layout when message tray opened
Unable to switch keyboard layout when message tray opened
Status: RESOLVED DUPLICATE of bug 695143
Product: gnome-shell
Classification: Core
Component: message-tray
3.7.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-03-21 12:10 UTC by Anton Sudak
Modified: 2013-03-21 21:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Anton Sudak 2013-03-21 12:10:24 UTC 
Unable to switch keyboard layout when message tray opened.

Using gnome-shell from git, gnome-setings-daemon 3.7.91. Ubuntu 13.04
Comment 1 Florian Müllner 2013-03-21 14:23:25 UTC 
If you are referring to the "Switch to next input source" binding, it has been disabled on purpose as a workaround, see bug 693907. (The bug has been closed, so I'd use this bug to track progress on a "proper" fix - unfortunately it'll be an intrusive change, so it won't be included in any 3.8.x release).

If you are referring to the "Modifiers-only switch to next source" binding, see bug 689839 - I'm still hoping for a patch in the 3.8.1 timeframe :-)
Comment 2 Anton Sudak 2013-03-21 14:54:06 UTC 
Hi Florian, thanks for answer.
Yes, I'm talking about "Switch to next input source". Tested with "Modifiers-only switch to next source layout" (I didn't notice this shortcut) - no changes. Hope it will be fixed in 3.8.*.
Comment 3 Rui Matos 2013-03-21 21:26:13 UTC 
(In reply to comment #1)
> If you are referring to the "Switch to next input source" binding, it has been
> disabled on purpose as a workaround, see bug 693907. (The bug has been closed,
> so I'd use this bug to track progress on a "proper" fix - unfortunately it'll
> be an intrusive change, so it won't be included in any 3.8.x release).

I had already opened bug 695143 for that so let's dupe this one.

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