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 582727 - session starts with wrong layout when layout the same for all applications
session starts with wrong layout when layout the same for all applications
Status: RESOLVED DUPLICATE of bug 491059
Product: gnome-applets
Classification: Other
Component: keyboard indicator (gswitchit)
2.26.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
: 582728 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-05-15 08:18 UTC by Lionel Dricot
Modified: 2009-12-07 16:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Lionel Dricot 2009-05-15 08:18:23 UTC 
using GNOME 2.26 on Ubuntu 9.04.

I'm using two layouts : Belgian Azerty (Bel) and French Bépo (Fra). I've unchecked the "different layout for different window". I want to use Fra nearly all the time. I applied it to the sysem.

1) As soon as this "different window" option is unchecked, there's no way anymore to set a default keyboard. It's logical.

2) When I start the computer, GDM is in Fra. Nice.

3) When my session starts, the keyboard indicator applet says "Fra". But the actual keys are in Bel. *bug*

4) Clicking on the applet doesn't work at all. The text stays "Fra" and the layout stays Bel. *bug*

5) Right clic on the applet > group > French Bépo. Now the layout is Fra. And the applet is working again, I can change layout by clicking on it.

This means that I have to do step 5) at each logon!

6) Might be related : when checking the "different layout for different window" box, it appears that Bel is the default layout.
Comment 1 Lionel Dricot 2009-05-15 08:21:44 UTC 
*** Bug 582728 has been marked as a duplicate of this bug. ***
Comment 2 Philippe Gauthier 2009-12-07 15:56:09 UTC 
Perhaps this is the same problem as in bug #491059 ?
Comment 3 Sergey V. Udaltsov 2009-12-07 16:04:13 UTC 
yes, it looks like dupe of #491059

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