gnome-screensaver indicates bad keyboard layout

[SebastienBarthelemy]

I'using Gutsy and the "keyboard indicator" to switch between french and us layouts. This is working fine.

When I lock the screen, gnome-screensaver 2.20.0 indicates the current layout together with the password prompt.

Sometimes, gnome-screensaver indicates the bad layout (ie. the one that is not currently used). In such a case, the password I type isn't the good one, and it is hard to unlock. I should also say that in such a case, the "keyboard indicator" indicates the good keyboard layout.

[Philipp Kohlbecher (xt28)]

I can confirm this bug. I am using hardy (updated from gutsy) with gnome-screensaver 2.22.2-0ubuntu1.

Please let me know what other information I can provide to help debug this.

[Mark Edgington (edgimar)]

Has this bug been resolved? I still see the bug in Hardy, but in particular after resuming from a suspend.

[Dmitriy Larchenko (neokril)]

I can confirm this bug. I am using Intrepid (clean install) with russian locale.

[Sebastien Bacher (seb128)]

could you try if that's an issue on jaunty?

[Dmitriy Larchenko (neokril)]

It seems that this bug has been resolved on jaunty.
I can't reproduce it now.

[SebastienBarthelemy (barthelemy)]

I still have the bug on Karmic.

[Stamatis Mitrofanis (stamit)]

Same here. I don't know what is wrong.

[Stamatis Mitrofanis (stamit)]

I think only the displayed layout name is wrong. The keyboard layout that is actually active is different than what is displayed next to the password entry box.

[Stamatis Mitrofanis (stamit)]

Karmic

[MilkaJinka (milkajinka)]

Still an issue under Lucid RC.

I'm using Swiss French (Che) as a default layout and French Bépo (Fre) as a second layout. When locking the screen the keyboard indicator doesn't always display the current layout in use - but when you type it is the current layout that is used. It can be confused if, like me, you switch between a "traditional" and a "dvorak-like" layout.

[Chris Coulson (chrisccoulson)]

Could somebody please provide the information requested on the upstream bug report

[Marc Deslauriers (mdeslaur)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to 'New'. Thanks again!