Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
G
gnome-shell
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 422
    • Issues 422
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 91
    • Merge Requests 91
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • gnome-shell
  • Issues
  • #14

Closed
Open
Opened Jan 31, 2018 by Jehan@Jehan
  • Report abuse
  • New issue
Report abuse New issue

Compose option not properly set

Through the GNOME Tweak tool, I set a Compose key in place of CapsLock. Looking in dconf, it seems a key was properly set up, so I am assuming the issue is not within GNOME Tweak tool: org.gnome.desktop.input-sources xkb-options ['compose:caps']

The problem is that the CapsLock indeed now works as Compose key but it still also works as Caps Lock!

Steps:

  • Be in "English (US)".
  • Set 'compose:caps' in org.gnome.desktop.input-sources xkb-options (or just use GNOME Tweaks Tool, in the "Keyboard & Mouse" tab, there is a "Compose Key" option which does the work for you).
  • Hold CapsLock + o + e.

Expected result: the light on the CapsLock key must not switch on, Capitalization of letter must not be locked for subsequent letters, and "œ" must be outputted.

Actual result: the light on the CapsLock key goes on, Capitalization of letter is locked for subsequent letters, and "Œ" is outputted.

So "compose:caps" did not just override the CapsLock behavior but instead added the compose behavior (and the key does both at once, which is weird).

This could also be a bug in XKB, but if you run the following as command line:

setxkbmap -layout us -option compose:caps

Then CapsLock works only as Compose key, as expected. This tends to imply that maybe GNOME does not properly set the option. Also note that this used to work fine until Fedora 25, and stopped in Fedora 26 and higher (in case it helps with version numbers of packages in the input stack).

Finally if GNOME shell is not the component handling input sources in GNOME, I hope you can just re-assign this bug report (do we have the feature in gitlab?). Thanks!

Note: the issue does not happen as an exception with some layouts which override the CapsLock, for instance the Japanese layout. Yet it happens for most layouts. This is why my reproduction steps above use "English (US)" but the same issue happens anyway with most other layouts.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: GNOME/gnome-shell#14