After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 676293 - Cannot log in with password with special characters as Lock dialog uses default layout
Cannot log in with password with special characters as Lock dialog uses defau...
Status: RESOLVED DUPLICATE of bug 675167
Product: gnome-screensaver
Classification: Deprecated
Component: dialog
3.4.x
Other Linux
: Normal major
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2012-05-18 06:50 UTC by Petr Schindler
Modified: 2012-05-18 19:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Petr Schindler 2012-05-18 06:50:53 UTC 
There isn't any possibility to change the layout. The name of layout is displayed, but it doesn't depend on what it shows, the dialog still uses the system default layout. This is big problem for those who have password with characters which aren't on default keyboard.

Example: I have password with Czech characters like š which isn't on US keyboard. Because the default layout after installation is US there isn't any chance to log in back to the desktop after I lock the screen - I can't change layout and write my password correctly. I have to choose 'swich users' and log in from gdm. But this brings lot of problems with sessions.

Bug in fedora with more information: https://bugzilla.redhat.com/show_bug.cgi?id=741446
Comment 1 André Klapper 2012-05-18 08:28:59 UTC 
Which exact version is this about? (Please set the Version field.)
Comment 2 Petr Schindler 2012-05-18 08:58:32 UTC 
I have gnome-screensaver-3.4.1-1.fc17.x86_64 installed. But it doesn't work even for older (at least for 3.*) as I know.
Comment 3 Ray Strode [halfline] 2012-05-18 19:24:05 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 675167 ***