[Ubuntu-x-swat] [Bug 432024] Re: Keyboard layout initialization

2010-08-20 Thread Fabio Marconi
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at

[Ubuntu-x-swat] [Bug 432024] Re: Keyboard layout initialization

2010-08-20 Thread Fabio Marconi
Hello Wolfgang Can you verify if this problem is present with the latest updated Karmic or Lucid's packages? If it still exist, please run in a terminal: apport-collect 432024 Thanks Fabio -- Keyboard layout initialization https://bugs.launchpad.net/bugs/432024 You received this bug

[Ubuntu-x-swat] [Bug 432024] Re: Keyboard layout initialization

2010-08-20 Thread Bryce Harrington
** Changed in: xserver-xorg-input-keyboard (Ubuntu) Status: Incomplete = New ** Changed in: xserver-xorg-input-keyboard (Ubuntu) Status: New = Incomplete -- Keyboard layout initialization https://bugs.launchpad.net/bugs/432024 You received this bug notification because you are a

[Ubuntu-x-swat] [Bug 432024] Re: Keyboard layout initialization

2010-08-20 Thread Bryce Harrington
** Tags added: hardy -- Keyboard layout initialization https://bugs.launchpad.net/bugs/432024 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-keyboard in ubuntu. ___ Mailing list:

Re: [Ubuntu-x-swat] [Bug 432024] Re: Keyboard layout initialization

2010-08-20 Thread Wolfgang
Fabio, This was reported on 8.04.3 and persisted on all Hardy upgrades. I've moved on to 10.04 and the problem no longer exists. I never ran Karmic or Lucid and don't have an easy way to go back. Since the problem was related to maintaining state, it probably can't be checked with a live CD.

[Ubuntu-x-swat] [Bug 432024] Re: Keyboard layout initialization

2010-08-20 Thread Fabio Marconi
Thanks for the reply 10.04 = Lucid Lynx This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the