Bug 16562

Summary: When autologin is enabled, GNOME keyboard settings are not activated
Product: xorg Reporter: Simos Xenitellis <simos.bugzilla>
Component: Server/Input/XKBAssignee: Daniel Stone <daniel>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: simos.bugzilla
Version: unspecified   
Hardware: All   
OS: All   
Whiteboard:
i915 platform: i915 features:
Bug Depends on: 16364    
Bug Blocks:    

Description Simos Xenitellis 2008-06-29 11:27:46 UTC 
When autologin is enabled in GNOME, it appears that libxklavier fails to set the layout settings. The system falls back to the /etc/X11/xorg.conf layout settings.

This has been reported in Ubuntu 8.04, running
  X.Org X Server 1.4.0.90
  Release Date: 5 September 2007
  X Protocol Version 11, Revision 0
  Build Operating System: Linux Ubuntu (xorg-server  2:1.4.1~git20080131-1ubuntu9.2)
  Current Operating System: Linux computer 2.6.24-19-generic #1 SMP Wed Jun 18 14:15:37 UTC 2008 x86_64 (or x86)
  Build Date: 13 June 2008  01:10:57AM

When setting XKL_DEBUG=100, .xsession-errors shows the following:

[1214761388,100,xklavier_config_xkb.c:xkl_xkb_multiple_layouts_supported/] !!! Checking multiple layouts support
[1214761388,100,xklavier_config.c:xkl_engine_get_ruleset_name/] Rules set: [xorg]
[1214761388,100,xklavier_config_xkb.c:xkl_xkb_multiple_layouts_supported/] !!! Multiple layouts ARE supported
[1214761388,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application[1214761389,100,xklavier_config.c:xkl_engine_get_ruleset_name/] Rules set: [xorg]
[1214761389,100,xklavier_config.c:xkl_engine_get_ruleset_name/] Rules set: [xorg]
[1214761390,100,xklavier.c:xkl_engine_reset_all_info/] NOT Resetting the cache: same configuration
[1214761390,100,xklavier.c:xkl_engine_reset_all_info/] NOT Resetting the cache: same configuration
[1214761390,100,xklavier.c:xkl_engine_reset_all_info/] NOT Resetting the cache: same configuration
[1214761390,100,xklavier.c:xkl_engine_reset_all_info/] NOT Resetting the cache: same configuration
Comment 1 Sergey V. Udaltsov 2008-06-29 11:35:30 UTC 
Has nothing to do with libxklavier
Comment 2 Sergey V. Udaltsov 2008-06-29 11:36:39 UTC 
It is well-known issue with autologin and startx - X reports XKB configuration as being set, but actually it is not.
Comment 3 Simos Xenitellis 2008-07-24 02:36:37 UTC 
I updated the title; a discussion on the underlying cause of this issue is at 
http://lists.freedesktop.org/archives/xorg/2008-July/036947.html
Comment 5 Peter Hutterer 2008-07-28 23:15:17 UTC 
> --- Comment #2 from Sergey V. Udaltsov <svu@gnome.org>  2008-06-29 11:36:39 PST ---
> It is well-known issue with autologin and startx - X reports XKB configuration
> as being set, but actually it is not.

Sergey:
I'm trying to track this down, can you give me any hints on what to look for
here?
Where (and how) does gnome actually set the xkb configuration at startup?
Comment 6 Peter Hutterer 2008-08-08 00:17:28 UTC 
This should be fixed with the commits leading up to
c06e27b2f6fd9f7b9f827623a48876a225264132.

See also http://lists.freedesktop.org/archives/xorg/2008-August/037710.html
Comment 7 Sergey V. Udaltsov 2008-09-14 16:22:59 UTC 
Is this bug related to #16364 ?
Comment 8 Peter Hutterer 2008-09-14 19:00:56 UTC 
(In reply to comment #7)
> Is this bug related to #16364 ?

sort-of. 16364 describes an xmodmap issue, and xmodmap had the right behaviour already (i.e. apply to all devices instead of just the VCP/VCK).
xkb didn't have this behaviour until c06e27b2f6fd9f7b9f827623a48876a225264132.

16364 was caused by the VCK having a different keymap before the first key is pressed, which would also be an issue for this bug I guess. So this bug depends on 16364, but not the other way round.
Comment 9 Peter Hutterer 2008-12-17 18:01:50 UTC 
This should be fixed in master now. We have the same keymap for both MDs and
SDs now, so anything GNOME does on the MD propagates down.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.