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 355004 - Screensaver password dialog does not indicate keyboard layout
Screensaver password dialog does not indicate keyboard layout
Status: RESOLVED DUPLICATE of bug 327056
Product: gnome-screensaver
Classification: Deprecated
Component: dialog
2.14.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on: 355003
Blocks:
 
 
Reported: 2006-09-08 18:45 UTC by Simos Xenitellis
Modified: 2006-09-08 18:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Simos Xenitellis 2006-09-08 18:45:47 UTC
Copying from 
https://launchpad.net/distros/ubuntu/+source/gnome-screensaver/+bug/49222/

The screensaver password dialog, that is produced whenever you want to resume
your work after a screensaver (or hibernate etc), does not indicate which
keyboard layout is active. As I use several ones at the same time, I find it
hard to know which layout is supposed to be active in GDM, and often I don't
even remember which one I used last. There is no way of finding out the layout
as the only thing showing is black dots in the input field.

This "bug" have made me loose work due to that I cannot enter my password at
times, even though I thought I correctly guessed different layouts. I do run
two different types of Dvorak on my Qwerty keyboard, so it is not easy to
guess.

Proposal:
* At least a keyboard indicator and switcher as can be seen in Gnome Panel
should be present in the password dialog.
* Possibly also a field where one can test a layout (but not in the dialog
itself, perhaps as a button) to see if it is the one expected.
Comment 1 William Jon McCann 2006-09-08 18:48:36 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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