Bug 1398724 - GDM on Wayland no longer shows CAPS LOCK Warning
Summary: GDM on Wayland no longer shows CAPS LOCK Warning
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 27
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1398662 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-25 16:56 UTC by Vasco Rodrigues
Modified: 2018-12-03 03:40 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
: 1655372 (view as bug list)
Environment:
Last Closed: 2018-11-30 22:12:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 775100 0 None None None 2016-11-25 17:00:53 UTC

Description Vasco Rodrigues 2016-11-25 16:56:30 UTC
Description of problem:
On the login screen, GDM no longer shows the CAPS LOCK Warning, when it's on.

Version-Release number of selected component (if applicable):
Version     : 3.22.1
Release     : 1.fc25


How reproducible:
Every time

Steps to Reproduce:
1. At login
2. Press CAPS LOCK
or
1. Lock Screen
2. Press CAPS LOCK

Actual results:
Nothing happens

Expected results:
Warning displaying CAPS LOCK is on.

Additional info:
Could be related to the switch from X to Wayland.

Don't understand why people are unable to look at the keyboard leds...

Comment 1 dezotti.alexandre 2017-03-28 19:53:30 UTC
Still there on GDM 3.22.3.

And no, I can look at my keyboard. Consider that, among the 2 previous laptops I've had, none of them had caps lock led.

Comment 2 Andy Wang 2017-07-13 03:32:46 UTC
I have a microsoft sculpt ergonomic keyboard.  No LEDs :(

I've been using the gnome shell extension lockkeys to get some feedback in gnome-shell but that's been broken in wayland too.  

https://github.com/kazysmaster/gnome-shell-extension-lockkeys/issues/32

They link to a different upstream gnome bug that might be relevant to the GDM issue as well, or not.

Comment 3 Przemyslaw Szypowicz 2017-10-08 17:36:28 UTC
It's still happening on F26.

Also this seems to be a duplicate of: 
https://bugzilla.redhat.com/show_bug.cgi?id=1398662

Comment 4 Fedora End Of Life 2017-11-16 18:45:19 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 5 Robert de Rooy 2017-11-30 04:52:02 UTC
*** Bug 1398662 has been marked as a duplicate of this bug. ***

Comment 6 Andrew Cowie 2018-07-18 11:15:53 UTC
Occurring in Fedora 28.

This is an accessibility problem; the user I am supporting needs sticky keys and can't hold down the shift key to enter her password. She's continually losing track of whether or not Caps Lock is on (and the keyboard doesn't have an indicator, unhelpfuly).

I'm heistant to report this as the same bug as we only just recently upgraded her system to F28; it's possible it is an unrelated issue, but regardless, we need the Caps Lock is on warning back if at all possible.

Let me know if there's anything I can do to help diagnose.

AfC

Comment 7 Ben Cotton 2018-11-27 14:58:38 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 8 Ben Cotton 2018-11-30 22:12:04 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.

Comment 9 Andy Wang 2018-12-03 03:40:43 UTC
I can't reopen this bug so cloned it under Bug 1655372 for F29


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