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 775100 - GDM on Wayland no longer shows CAPS LOCK Warning
GDM on Wayland no longer shows CAPS LOCK Warning
Status: RESOLVED DUPLICATE of bug 762881
Product: mutter
Classification: Core
Component: wayland
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2016-11-25 17:00 UTC by v
Modified: 2016-11-28 15:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description v 2016-11-25 17:00:28 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.
Comment 1 v 2016-11-25 17:02:52 UTC 
Reported in Fedora.
https://bugzilla.redhat.com/show_bug.cgi?id=1398724
Comment 2 Ray Strode [halfline] 2016-11-28 15:25:56 UTC 
i think there's a duplicate of this, but I can't find it.  The problem is that mutter uses the X11 gtk+ backend, so caps lock state isn't accurately represented.  Fixing this the right way, probably requires creating some sort of NULL ("compositor" ?) backend for gtk+ to use, but gnome-shell/mutter could probably be fixed in the interim by side stepping gdk to get caps lock state on wayland.
Comment 3 Florian Müllner 2016-11-28 15:31:16 UTC 
(In reply to Ray Strode [halfline] from comment #2)
> i think there's a duplicate of this, but I can't find it.

I think I did.

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