Bug 23470 - core keyboard loses keymap after the last client disconnects
Summary: core keyboard loses keymap after the last client disconnects
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/DDX/Xephyr (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Matthew Allum
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-23 04:00 UTC by Tomeu Vizoso
Modified: 2010-04-24 03:32 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
proposed fix (824 bytes, patch)
2009-08-23 04:00 UTC, Tomeu Vizoso 		no flags Details | Splinter Review
print XGetKeyboardMapping (1021 bytes, text/x-python-script)
2009-08-23 04:01 UTC, Tomeu Vizoso 		no flags Details
View All

Description Tomeu Vizoso 2009-08-23 04:00:36 UTC 
Created attachment 28862 [details] [review]
proposed fix

To reproduce:

- launch Xephyr
- launch attached script, see the keymap printed
- launch script again, see how the keymap is empty

Explanation:

This is because the core keyboard device doesn't reconfigure correctly the keymap, because no default xkb rules are set. The default xkb rules are unset when the devices are uninitialized, but aren't set again on reinitialization.

The patch attached "fixes" the issue, but have no idea how correct it is.

This only applies to 1.6.3, in git HEAD this code has changed completely and this issue shouldn't be present. If this means no release will be made with this fix/workaround, would liek to hear opinions about distros shipping this as a patch.
Comment 1 Tomeu Vizoso 2009-08-23 04:01:59 UTC 
Created attachment 28863 [details]
print XGetKeyboardMapping
Comment 2 Tomeu Vizoso 2009-10-14 11:58:28 UTC 
This bug is not present in 1.7.0.
Comment 3 Julien Cristau 2010-04-24 03:32:50 UTC 
Marking as fixed per comment 2.

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.