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 491059 - gnome-keyboard-applet incorrectly detects the current group if "Separate layout for each window" is disabled
gnome-keyboard-applet incorrectly detects the current group if "Separate layo...
Status: RESOLVED OBSOLETE
Product: gnome-applets
Classification: Other
Component: keyboard indicator (gswitchit)
2.20.x
Other All
: Normal minor
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
: 582727 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-10-28 13:33 UTC by Yann Rouillard
Modified: 2020-11-06 19:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Yann Rouillard 2007-10-28 13:33:36 UTC
Please describe the problem:
gnome-keyboard-applet incorrectly displays the current group if "Separate layout for each window" is disabled and another group than the first one has been set as ethe default.

Steps to reproduce:
1. launch gnome-keyboard-properties
2. in the layout tab, add a second layout (there must be more than one) and set is as the default
3. disable "Separate layout for each window"
4. disconnect and reconnect



Actual results:
The gnome-keyboard-applet displays the second layout as being the current one although it is not.

Expected results:
The gnome-keyboard should display the real current layout

Does this happen every time?
yes

Other information:
The original bug report is here: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-applets/+bug/158044

It seems the gnome-keyboard-applet relies on the XKLAVIER_STATE param of the top window to get the current group, but this param doesn't give the real group when a group has been locked (which is the case when "Separate layout for each window" is disabled)
Comment 1 Sergey V. Udaltsov 2007-10-28 13:58:06 UTC
What is your configuration? I cannot reproduce it using "US English + Russian (Winkeys)" configuration. Could you please provide "xprop -root| grep XKB"
Comment 2 Yann Rouillard 2007-10-29 10:49:49 UTC
I am under Ubuntu Hardy, but at this time it's very close to Ubuntu Gutsy 7.10.

$ xprop -root| grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "fr", "oss", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "fr,gb", "oss,", "grp:alts_toggle"

you can see that the french keyboard is activated.

However for any windows I get:
$ xprop | grep XKLAVIER
XKLAVIER_STATE(INTEGER) = 1, 0

The first group is the "Great Britain" keyboard, as I set it as default before disabling "Separate layout for each window".


From what I saw the gnome-keyboard-applet (in fact gkb-indicator) relies on XKLAVIER_STATE to know which layout is the current, but from what I understood, that doesn't seem to work when a group has been locked. 

This happens after login, maybe it's bad keyboard initialisation from gnome ?

Comment 3 Yann Rouillard 2007-11-03 10:16:14 UTC
Do you have enough information or do you need me to perform more tests ?
Comment 4 Sergey V. Udaltsov 2007-12-12 00:13:22 UTC
I just checked your configuration. It works with disabled "Separate layout" as expected. Not reproducable problem :// I am using Gutsy. Yes you are right about XKLAVIER_STATE - it is used for saving the state. But it is actually ignored when "Separate layout" checkbox is clear.
Comment 5 Sergey V. Udaltsov 2009-12-07 16:04:13 UTC
*** Bug 582727 has been marked as a duplicate of this bug. ***
Comment 6 Tobias Mueller 2010-04-11 18:33:34 UTC
Sergey, is this NOTABUG then?
Comment 7 André Klapper 2020-11-06 19:56:00 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-applets/-/issues/

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