Bug 807603 - Problems with entering non-US (diacritic) characters to password field
Summary: Problems with entering non-US (diacritic) characters to password field
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xscreensaver
Version: 17
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Mamoru TASAKA
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-28 10:20 UTC by Filip Skola
Modified: 2016-05-05 04:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-01 05:23:13 UTC
Type: ---


Attachments (Terms of Use)

Description Filip Skola 2012-03-28 10:20:32 UTC
Description of problem:
I have problems with entering some Czech characters to password field in xscreensaver. There are two ways of typing Czech chars on Czech keyboard: directly by hitting the key with char and caron/acute accent (ě, ž, á .. etc) or hitting the diacritic button (ˇ, ') first and then the character. The second way doesn't work in xscreensaver. Instead of typing diacritic character, č for example, two chars are typed, so I assume something like ˇc is mistaken.

Not all diacritic characters can be accessed directly with a key, so there's possibility you can't unlock your screen then.


Version-Release number of selected component (if applicable):
Fedora Beta RC1
xscreensaver-base-5.15-5.fc17.x86_64


How reproducible: always


Steps to Reproduce:
1. Lock screen somewhere where it's handled by xscreensaver (XFCE)
2. Try to unlock it with your login and diacritic password using the method described
3.
  
Actual results: you password is not taken


Expected results: screen unlock


Additional info: -

Comment 1 Mamoru TASAKA 2012-04-02 09:02:25 UTC
Sorry, however for now I don't understand Czech keyboard at all, and I don't know how to reproduce your issue with what I have, either...

Comment 2 Mamoru TASAKA 2012-04-02 09:06:56 UTC
(By the way, is it common that Czech people use Czech specific characters on password? I have never thought to use hiragana/katakana/kanji on password...)

Comment 3 Filip Skola 2012-04-03 08:41:02 UTC
I think you're right. Users are at least warned that situation when entering password won't be possible may occur. I just thought this is worth a bug though.

Comment 4 Fedora End Of Life 2013-07-04 01:11:53 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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 5 Fedora End Of Life 2013-08-01 05:23:19 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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


Note You need to log in before you can comment on or make changes to this bug.