Alternate keyboard layout doesn't works after a suspend

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please attach your X server configuration file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.0.log) to the bug report as individual uncompressed file attachments using the "Attachment:" box below. Could you please also try to run without any /etc/X11/xorg.conf and let Xorg autodetect your settings? Please also attach the /var/log/Xorg.0.log from this attempt.

Because the problem appears with suspend/resume, I'm going to ask for some kernel information as well. Please include the information requested at https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

I'm filing this bug under xorg for now, we'll check and see if the kernel has any complaints as well. Thanks in advance.

Thanks!

Thank you for responding with that material. Can you please tell us more about your setup? Is your French keyboard a USB kb that is attached to a laptop? Can you please also attach
   lsusb -v > lsusb.txt
   lsb_release -a > lsb_release.txt

You mentioned that errors are being displayed, can you attach a screenshot for us as well? Thanks in advance.

The problem is with my USB keyboard attached to my laptop!. I can change it with the laptop keyboard. If I connect the usb keyboard, I get "???" as language by the keyboard indicator(using the laptop keyboard), but the language is correctly set .

I can't take a screenshot because the errors are showing very fast and before the login screen.

OK, thanks for explaining. A few more questions to follow up your previous response:
1) Does the problem _only_ exist after suspend? Is that USB keyboard plugged in as you wake the computer or are you plugging it in at some point after the resume process?
2) If you unplug the keyboard and plug it back it, is it detected correctly or do you get the same behavior as above?
3) Has this keyboard ever worked correctly with Ubuntu, either in the current version or in previous versions (if so, please tell which)?
4) Please clarify if you are putting the machine into standby rather than hibernating it (suspend to RAM as opposed to suspend to disk).
5) Have you tried another USB French keyboard of the same model?

The reason I ask the above questions is because it seems like you may just have a bad piece of hardware since the keyboard seems recognized otherwise.

Please also attach
   lsb_release -a > lsb_release.txt
as I requested before as well as
   cat /proc/version_signature > proc_version_signature.log

Sorry to drag this out, thanks for following up, we're almost there!

1. The problem exists only after a suspend. I plug the USB keyboard before the resume process.
2. I got the same behavior after un/plug test
3. This keyboard is working fine before suspend
4. Suspend to RAM.
5. An other keyboard do the same behavior

Thank you, right now I am just trying to figure out if this is a kernel problem or a problem with X. Can you please put your computer into the problem situation where the keyboard layout isn't detected correctly, save and close all documents, and kill/restart X with CTRL+ALT+BACKSPACE. Log back into Ubuntu - does the keyboard work correctly or does the problem still exist?

After discussing this with some other triagers, we decided that it is most likely a kernel bug since it is a USB device failing after suspend/resume, so we will file it under the package "linux".

You should also check that your BIOS is up to date, as this problem could be related to the BIOS not correctly resuming USB after suspend/resume. If that is the case, hopefully the latest version of your BIOS will have fixed this. Please let us know if you make any progress there.

There should be enough information here for a developer to begin work, so I will mark the bug as Triaged and let a developer handle it from here. Thanks again for taking the time to report this.

After the X restart using CTRL+ALT+BACKSPACE the keyboard work correctly.

Thanks for your support and happy new year to all the ubuntu team!

This is rather unusual, but I am opening this bug against xorg alongside linux since the problem appears to originate in two places. The suspend/resume cycle relates to the kernel, but since restarting X fixes the problem, there may be an issue with the hardware autodetection after suspend which is a xorg problem.

Have the same problem here. Suspend. Turn on. Choose my alternative layout: Rus. Then plugin my USB keyboard and by that moment Rus changes to ???.
Actually it's not necessary to restart X to solve the problem.
You can open System->Preferences->Keyboard choose Layouts tab. You'll see 2 layouts there USA and Rus in my case. Remove Rus and add it again, that's all - you can work again.

Chaostya, can you also attach the information I requested above.

devantor and Chaostya, can you both also please attach
   dmesg > dmesg.txt
The kernel team will likely want that. Thanks in advance.

I have a similar problem. I have configured under Sytem->Preferences->Keyboard several keyboard layouts (Swedish, Swiss-French and US). I want the L-shift + R-shift combination to switch layout.

I also configured the keyboard to switch the position of the left ctrl key and the caps-lock key.

I always suspend the laptop when leaving the office, and when I resume it the layout will not switch anymore and it has forgotten the ctrl-key exchange.

I have found that if I then enter the System->Preferences->Keyboard menu, select the Layout tab, click Other Options, expand the Layout Switching tree, and *just click and un-click the first checkbox*, and then close everything, the layout switching works again.

Not a critical bug by any means, but a rather annoying one especially for us international users.

I use the USA Dvorak and United Kingdom Dvorak alternate layouts as well, and have found the same problem with coming out of suspend. In my case, perhaps because my System->Administration->Language Support has the Default language set to "English (Ireland)", the Keyboard Indicator v2.24.1 shows "Irl".

To get out of it I go to System->Preferences->Keyboard, click the Layouts tab, and click the Keyboard model button. I select another keyboard format, then the one I have again (Microsoft Wireless Multimedia Keyboard 1.0A), and click OK. Even though I've not actually saved a change to any setting, this seems to kick it and make the actual layout choices appear correctly of the Keyboard Indicator again, and lets me go back to a dvorak layout.

Hope this helps!

Found some interesting facts:
1. When I go home I'm doing suspend and then unplug my USB keyboard and USB mouse.
2. When I'm at home I plug in just my USB mouse and wake up my laptop in kern.log I have:

Mar 5 22:34:41 ch-laptop kernel: [29246.177643] pm_op(): usb_dev_resume+0x0/0x10 [usbcore] returns -19
Mar 5 22:34:41 ch-laptop kernel: [29246.177675] PM: Device 3-1 failed to resume: error -19
Mar 5 22:34:41 ch-laptop kernel: [29246.177690] pm_op(): usb_dev_resume+0x0/0x10 [usbcore] returns -19
Mar 5 22:34:41 ch-laptop kernel: [29246.177712] PM: Device 3-2 failed to resume: error -19
Mar 5 22:34:41 ch-laptop kernel: [29246.192178] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Mar 5 22:34:41 ch-laptop kernel: [29246.192182] pci 0000:00:02.0: setting latency timer to 64
Mar 5 22:34:41 ch-laptop kernel: [29246.193658] PM: resume devices took 2.108 seconds
Mar 5 22:34:41 ch-laptop kernel: [29246.193984] PM: Finishing wakeup.
Mar 5 22:34:41 ch-laptop kernel: [29246.193986] Restarting tasks ... <6>usb 3-1: USB disconnect, address 3
Mar 5 22:34:41 ch-laptop kernel: [29246.524800] usb 3-2: USB disconnect, address 4
Mar 5 22:34:41 ch-laptop kernel: [29246.574194] done.

3. My layouts are still working perfectly, then I suspend my laptop and get back to work.
4. If I wake it up WITHOUT plugging in my USB keybord my layout will work perfectly.
But, just plug in my USB keyboard either way before waking up or hotplug and Rus will change to ???

Thank you for bringing this bug to our attention. Unfortunately a paper cut should be a small usability issue that affects many people and is quick and easy to fix. I'm afraid this bug can't be addressed as part of this project.

This is not the setup of the majority of average users, Hence not a papercut.

A paper cut is a minor usability annoyance that an average user would encounter on his/her first day of using a new installation of Ubuntu 9.10.

For further info about papercuts criteria , pls read > https://wiki.ubuntu.com/PaperCut

Don't worry though, This bug has been marked as "invalid" ONLY in the papercuts project.

With latest Karmic Koala this bug doesn't affects me anymore.

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

I haven't noticed this behavior for a while now, looks like it's fixed.

I see exactly this bug on updated Karmic. No USB keyboards, nothing. Simple Dell Latitude D420 laptop with two keyboard layouts, hibernate, then resume and it starts to act as if there're three layouts: my two Eng and Rus plus "???". Changing anything in gnome-keyboard-properties fixes the problem up until the next hibernate.

Too bad I cannot yet upgrade to Lucid on the laptop. My big desktop didn't have this problem with Karmic and doesn't with Lucid.

[This is an automatic notification.]

Hi devantor,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 308978

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 308978 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/308978

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.