Karabiner-elements: `grave_accent_and_tilde` key in reality prints `§` symbol

[DmytroYeremieiev]

grave_accent_and_tilde prints § in any editor. All custom configurations of modifications to Karabiner were disabled, which means the root cause is in program itself.

OS version:
Mac OS Mojave 10.14.6 (18G103)
Karabiner version:
12.7.0, but the same goes on lower versions as well

[thorehusfeldt]

I can confirm this. On a MacBook Pro laptop (13 inch, 2017) under macOS Mojave 10.14.6, US Keyboard.

Under “Show Keyboard Viewer”, with Karabiner Elements enabled, the system correctly show the laptop keyboard (Key to the left of 1 is GRAVE ACCENT, key to the right of LEFT SHIFT is Z, single-storey RETURN) As soon as I start typing, the keyboard changes to a US desktop keyboard (with num keys, two-storey RETURN, § to the left of 1, GRAVE ACCENT between left shift and Z.) Clearly the OS is confused about which keyboard is being used, and misrepresents the input.

Quitting Karabiner Elements unconfuses the OS again, and the Keyboard Viewer “sees” the correct keyboard.

The Event Viewer in Karabiner, on the other hand, correctly tells me that I’m pressing grave_accent_and_tilde.

[thorehusfeldt]

Half-baked analysis: With Karabiner Elements active, the OS fails to identify the keyboard correctly (the Keyboard Setup Assistant claims that the keyboard “cannot be identified”.) The OS then seems to incorrectly default to a wide US desktop keyboard.

Quick fix:

Select System Preferences… -> Keyboard -> Keyboard tab. Click “Change Keyboard Type…” and follows the Keyboard Setup Assistant.

I don’t know how persistent this solution is. But it makes Karabiner Elements usable again.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[thorehusfeldt]

I would prefer this issue to be addressed or fixed. If there is a way for us to help (beyond the hacky workaround I suggest above), please tell.

[ralfnitzer]

I would prefer this issue to be addressed or fixed. If there is a way for us to help (beyond the hacky workaround I suggest above), please tell.

Fixing this error would also fix a whole of other issues opened i think!

[JoseGuedes]

I have exactly the same issue with a Portuguese language keyboard layout.

With Karabiner-Elements app closed, macOS configured for Portuguese language input (pt-PT):

• Key1 = top left most physical key
  
  
  
  • No modifier key pressed = § (section sign)
    
    
    
    
    
    • Unicode = U+00A7
    
    
    
    • UTF-8 = C2 A7
    
    
    
  
  
  • Shift key pressed = ± (plus-minus sign)
    
    
    
    
    
    • Unicode = U+00B1
    
    
    
    • UTF-8 = C2 B1
    
    
    
  
  
• Key2 = second key from the left, second row from the bottom
  
  
  
  • No modifier key pressed = < (less-than sign)
    
    
    
    
    
    • Unicode = U+003C
    
    
    
    • UTF-8 = 3C
    
    
    
  
  
  • Shift key pressed = > (greater than)
    
    
    
    
    
    • Unicode = U+003E
    
    
    
    • UTF-8 = 3E
    
    
    
  
  
  • Option key pressed = ≤ (less-than or equal to)
    
    
    
    
    
    • Unicode = U+2264
    
    
    
    • UTF-8 = E2 89 A4
    
    
    
  
  
  • Shift+Option keys pressed = ≥ (greater-than or equal to)
    
    
    
    
    
    • Unicode = U+2265
    
    
    
    • UTF-8 = E2 89 A5
    
    
    
  
  

With Karabiner-Elements app active, Key1 and Key2 switch.

Using Karabiner EventViewer I can see the following:

• Key1 = top left most physical key
  
  
  
  • Code = 100
  
  
  • Name = non_us_backslash
  
  
• Key2 = second key from the left, second row from the bottom
  
  
  
  • Code = 53
  
  
  • Name = grave_accent_and_tilde
  
  

Is there a solution to fix this?

Useful information:

• macOS version = 10.14.6 (Mojave)
• Karabiner version = Karabiner-Elements 12.9.0
• Hardware: MacBook Pro (13-inch, 2017)
• Keyboard hardware:
  
  
  
  • Internal = Mac Portuguese layout (pt-PT)
  
  
  • External = Apple Magic Keyboard Portuguese layout (pt-PT)
  
  

[MTCoster]

Reproduced with en-GB keyboard layout on macOS Catalina 10.15.3 (19D76) with Karabiner-Elements 12.9.0

[ralfnitzer]

I have also an Apple USB Keyboard and I noticed that the quick fix (https://github.com/pqrs-org/Karabiner-Elements/issues/2027#issuecomment-550211764) just corrects one of the keyboards. Either the USB Keyboard is correct or the MacBook Pro Keyboard is correct, while the other isn't. Can anyone else confirm this or is this just me?
(I'm running Mojave 10.14.5)

[anton-forsberg]

I have also an Apple USB Keyboard and I noticed that the quick fix (#2027 (comment)) just corrects one of the keyboards. Either the USB Keyboard is correct or the MacBook Pro Keyboard is correct, while the other isn't. Can anyone else confirm this or is this just me?
(I'm running Mojave 10.14.5)

Yeah, I'm experiencing exactly the same. 10.14.5 as well.

[MClarke1991]

I am also experiencing this issue on Mojave 10.14.6 Karabiner 12.9.0. ~None of the fixes in issue #1028 help either~ EDIT: grave_accent_and_tilde -> non_us_backslash does work. Apologies and thanks to erwald.

[erwald]

You can work around this issue by manually mapping grave_accent_and_tilde -> non_us_backslash and vice versa in Karabiner.

[gegnew]

I actually have the problem that non_us_backslash prints §, but grave_accent_and_tilde prints a `. Unfortunately, I _still_ have no idea how to print a "<" symbol

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[thorehusfeldt]

I would prefer this issue to be addressed or fixed. If there is a way for us to help (beyond the hacky workaround I suggest above), please tell.

[smilexu]

I am also experiencing this issue on Mojave 10.14.6 Karabiner 12.9.0. ~None of the fixes in issue #1028 help either~ EDIT: grave_accent_and_tilde -> non_us_backslash does work. Apologies and thanks to erwald.

you saved my day :D, it works perfectly.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.