Bug 481014 - hotplugged keyboard layout doesn't respect selection made at login
Summary: hotplugged keyboard layout doesn't respect selection made at login
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-21 18:24 UTC by Michael Williamson
Modified: 2018-04-11 08:23 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-27 18:21:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg.0.log (423.95 KB, application/octet-stream)
2009-03-23 20:37 UTC, James M. Leddy
no flags Details

Description Michael Williamson 2009-01-21 18:24:30 UTC
Description of problem:

Keyboard layout selected at GDM login screen is not respected if a keyboard is unplugged and plugged back in during a session.  (I discovered a had a keyboard with an electrical problem resulting in disconnects/connects).

Version-Release number of selected component (if applicable):


How reproducible:

100%

Steps to Reproduce:
1. select dvorak layout at login screen and log into user account
2. disconnect and reconnect keyboard
3. grumble at the resulting QWERTY (or whatever system default) layout
  
Actual results:
vdtnsaoh od.dok; ks ;t;kdm hdyafpke
keyboard reverts to system default.

Expected results:
keyboard layout choosen at login should be used.

Additional info:

Comment 1 Michael Williamson 2009-01-22 04:30:29 UTC
Keyboard used was USB, by the way.

Comment 2 James M. Leddy 2009-02-06 20:03:57 UTC
This is happening to me and while not a big deal, the resulting frustration is off the charts.

My theory is evdev,  I'll look into it if I have time.  The solution being to go into system->hardware->keyboard, click on the layouts tab, and make a selection, then redo the old selection.

Comment 3 James M. Leddy 2009-03-20 20:07:55 UTC
reassigning evdev

Comment 4 Matěj Cepl 2009-03-23 20:29:46 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf (if you have one) whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 5 James M. Leddy 2009-03-23 20:37:32 UTC
Created attachment 336380 [details]
Xorg.0.log

I don't have an xorg.conf

Comment 6 Peter Hutterer 2009-03-23 23:25:59 UTC
This isn't an evdev bug - changing to gnome-settings-daemon. The device comes up with the system-default configuration (usually what's in /etc/sysconfig/keyboard). g-s-d needs to listen to device presence events (which I think it does in rawhide).

Comment 7 Bastien Nocera 2009-04-29 18:44:50 UTC
This is done in libxklavier for rawhide.

We could do it using the patch from:
http://bugzilla.gnome.org/show_bug.cgi?id=560821
but it looks pretty invasive

Comment 8 James M. Leddy 2009-04-29 18:52:04 UTC
(In reply to comment #7)
> This is done in libxklavier for rawhide.
> 
> We could do it using the patch from:
> http://bugzilla.gnome.org/show_bug.cgi?id=560821
> but it looks pretty invasive  

It looks like ~40 lines?  All additions.

So if I download libxklavier from rawhide this will work?

Comment 9 Bastien Nocera 2009-05-08 01:59:53 UTC
(In reply to comment #8)
> (In reply to comment #7)
> > This is done in libxklavier for rawhide.
> > 
> > We could do it using the patch from:
> > http://bugzilla.gnome.org/show_bug.cgi?id=560821
> > but it looks pretty invasive  
> 
> It looks like ~40 lines?  All additions.

Invasive meaning that it could break some other stuff.

> So if I download libxklavier from rawhide this will work?  

It probably won't work with the rest of the stuff from F10, but you could probably test with an F11 live CD/usb key.

Comment 10 Thomas Fitzsimmons 2009-10-27 18:10:31 UTC
This has worked fine for me throughout Fedora 11.  It can probably be closed now.

Comment 11 James M. Leddy 2009-10-27 18:21:05 UTC
yeah, fixed in F11


Note You need to log in before you can comment on or make changes to this bug.