Bug 1134299

I can reproduce the same problem in Fedora 21 too.

% gsettings get org.gnome.desktop.input-sources xkb-options
['grp:rctrl_rshift_toggle']

　I can also reproduce this on f20.

$ gsettings get org.gnome.desktop.input-sources xkb-options
['terminate:ctrl_alt_bksp', '', 'eurosign:5', 'grp:rctrl_rshift_toggle']

I have Super+Space set as the switch to next input source
and (just as the reporter) RightCtrl+RightShift as the modifier only
input source switch.

I can now use *all* of the following key combinations to switch input sources:

RightCtrl+RightShift
LeftCtrl+RightShift
LeftAlt+RightShift
LeftShift+RightShift

Rui Matos told me in IRC that this is an X server problem, 
it has nothing to do with Gnome.

Rui Matos also told me that LeftAlt+RightShift does not switch
(only the other 3 combinations mentioned in comment#2 switch).

I tried again and Rui is right.

The reason why I thought that LeftAlt+RigthShift does switch input
sources is that switching the input source to “gucharmap”
unexpectedly remapped my keyboard layout (probably to “us”). This
changed the position of the left alt key (My own layout has the left
alt key on the left control key and the left alt key is "Meta" (for
use in Emacs)). Switching to the "gucharmap" input source mapped the
left alt key to its usual position and the left control key became
control again. So it was LeftCtrl+RightShift again doing the input
source switching, *not* LeftAlt+RightShift.

(In reply to Mike FABIAN from comment #3)
> Rui Matos told me in IRC that this is an X server problem, 
> it has nothing to do with Gnome.
What does this mean to a poor user?

(In reply to Stas Sergeev from comment #5)
> (In reply to Mike FABIAN from comment #3)
> > Rui Matos told me in IRC that this is an X server problem, 
> > it has nothing to do with Gnome.
> What does this mean to a poor user?

It means that it won't be fixed until we switch to wayland. In any case, this is a fairly low priority bug, there's much bigger fish to fry out there.

(In reply to Rui Matos from comment #6)
> It means that it won't be fixed until we switch to wayland. In any case,
> this is a fairly low priority bug
This bugzilla doesn't allow me to change priority for
some reason...
I agree the bug is rather minor, but in pidgin you do
a newline with RShift-Enter, and the new line usually
starts with the capital letter, so LShift gets pressed
as well. So the annoyance factor is non-zero.

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

I guess this problem happens in GNOME Wayland too because both X11 and Wayland use the same mutter logic.

(In reply to fujiwara from comment #12)
> I guess this problem happens in GNOME Wayland too because both X11 and
> Wayland use the same mutter logic.

I think you're right, mutter doesn't distinguish between left/right modifiers in its keybindings code:

https://git.gnome.org/browse/mutter/tree/src/core/keybindings.c#n490

 491   else if (g_str_equal (iso_next_group_option, "ctrl_shift_toggle") ||
 492            g_str_equal (iso_next_group_option, "lctrl_lshift_toggle") ||
 493            g_str_equal (iso_next_group_option, "rctrl_rshift_toggle"))
 494     {
 495       resolved_key_combo_copy (&keys->iso_next_group_combo[0],
 496                                &keys->iso_next_group_combo[1]);
 497 
 498       keys->iso_next_group_combo[0].mask = ShiftMask;
 499       keys->iso_next_group_combo[1].mask = ControlMask;
 500       keys->n_iso_next_group_combos = 2;
 501     }

[...]

 511   else if (g_str_equal (iso_next_group_option, "alt_shift_toggle") ||
 512            g_str_equal (iso_next_group_option, "lalt_lshift_toggle"))
 513     {
 514       resolved_key_combo_copy (&keys->iso_next_group_combo[0],
 515                                &keys->iso_next_group_combo[1]);
 516 
 517       keys->iso_next_group_combo[0].mask = Mod1Mask;
 518       keys->iso_next_group_combo[1].mask = ShiftMask;
 519       keys->n_iso_next_group_combos = 2;
 520     }

So basically, it just checks for the modifier mask (which is not different for left and right)

Is there an upstream bug for this?

Still happens with F27+ presumably?

(In reply to Jens Petersen from comment #14)
> Is there an upstream bug for this?

True.

(In reply to Jens Petersen from comment #15)
> Still happens with F27+ presumably?

True.

>> Is there an upstream bug for this?
> True.

Sorry, ignore this, meant to answer to comment #15.

This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Still happening in F30+?

If someone could confirm for F31 even that would be good

Created attachment 1678415 [details]
Image showing default next input source selection options in F31, F32-Beta

Steps followed:
1. Added more inputs
2. Pressed "Both Shift keys"

Behaviour Observed:  No changes in input sources.

Steps Followed:
1. Window Key + Space 

Behaviour Observed:  Next input source getting selected.

Working as expected for me.


Not reproducible in both Fedora 31 and Fedora 32 Beta as well. Let me know, if anyone else can reproduce this issue, else will close this by next week.


Additional Info: Though i observed one another bug : I cant change default next input source selection keys, but that deserve more discussion and another bug.

Closing bug as a working for me. Feel free to reopen if problem reproduced again.