Bug 1662685

Summary: Gnome Know well the capslock status, but applications use inverse of this.
Product: [Fedora] Fedora Reporter: Mars <csiterallat>
Component: fedora-setup-keyboardAssignee: Orphan Owner <extras-orphan>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 29CC: adel.gadllah, extras-orphan, peter.hutterer
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-03 13:57:00 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:

Description Mars 2018-12-31 16:04:11 UTC
#Description of problem:

Gnome Know well the capslock status, but applications use inverse of this.

My caps-lock is off (default) and i can search and typing in gnome search (and login) well.
But all other application (gedit, Firefox, Terminal...) without capslock (on status), i typing with BIG CASE... I need to ON (led light is up) capslock for typing without big font case...

# Version-Release number of selected component (if applicable):
UpToDate Fedora 29 and I use flatpak applications. I remove my external gnome-shell extensions and only use fedoraproject.org extensions:
 Gsconnect, Alternatab, Place status Indicator, Topicon Plus, User Theme.

How reproducible:
I dont know. On Login (GDM) is work. After login (win+A ) search is work well, but all other app is use big cases....


Actual results:
NOW CAPSLOCK IS OFF AND MY TYPING IS BIG CASES

Expected results:
Now i turn on CapsLock (led is lights up) and now typing normal cases...
But if i typing to gnome search the FONTS ARE BIG BECAUSE CAPSLOCK IS ON...
Gnome Know well the capslock status, but applications use inverse of this.

Additional info:

Comment 1 Mars 2019-05-03 13:57:15 UTC
I think fixed. Thakns