Bug 1164283

Summary: unable to login with special characters in password
Product: [Fedora] Fedora Reporter: udo.rader
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 21CC: goeran, normand, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 04:59:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
regional settings with gdm keyboard layout displayed none

Description udo.rader 2014-11-14 14:40:50 UTC
Created attachment 957615 [details]
regional settings with gdm keyboard layout displayed

My box is configured to run under en_US locale in general, but since I live in Austria, my keyboard layout is German, however.

My password contains special characters and after my upgrade to FC21, I am no longer able to login using this password.

After temporarily changing the password to one without special characters, I checked the regional settings and changed the input sources for the login keyboard to German again (see screenshot).

That however does not seem to work either, I still cannot login using any special characters.

Comment 1 Göran Uddeborg 2014-11-25 14:29:52 UTC
This is probably not due to your mixed locale/layout setup.  I see the same problem in a pure Swedish setup.  (sv_SE locale, Swedish keyboard layout.)

In the logs, it seems that the X server is aware of the Swedish keyboard.  And after logging in, I have a Swedish keyboard.  I get the impression it is something strange gdm does.

nov 24 23:46:22 mimmi gdm-Xorg-:0[3315]: (**) Option "xkb_rules" "evdev"
nov 24 23:46:22 mimmi gdm-Xorg-:0[3315]: (**) Option "xkb_model" "evdev"
nov 24 23:46:22 mimmi gdm-Xorg-:0[3315]: (**) Option "xkb_layout" "se"

Comment 2 udo.rader 2014-12-21 12:27:31 UTC
I've filed the bug upstream now:

https://bugzilla.gnome.org/show_bug.cgi?id=741833

Comment 3 Fedora End Of Life 2015-11-04 14:36:14 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Göran Uddeborg 2015-11-09 19:51:09 UTC
The upstreams bug remains in the "new" state, but with gdm-3.18.0-1.fc23.x86_64 from Fedora 23 I can again use non-ASCII in passwords.

Comment 5 Fedora End Of Life 2015-12-02 04:59:30 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.