Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 Dec 2020 16:23:08 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 252235] x11/xorg: MacBook Pro 8,3 faulty key mapping
Message-ID:  <bug-252235-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252235

            Bug ID: 252235
           Summary: x11/xorg: MacBook Pro 8,3 faulty key mapping
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: x11@FreeBSD.org
          Reporter: jwb@freebsd.org
             Flags: maintainer-feedback?(x11@FreeBSD.org)
          Assignee: x11@FreeBSD.org

Under X11, the ` and ~ keys return < and > by default.

Found a fix in this thread:

https://unix.stackexchange.com/questions/33528/setxkbmap-for-macbook-pro-us

The problem is the TLDE and LSGT mappings are switched in
/usr/local/share/X11/xkb/symbols/us.

Problem does not occur on a MacBook Pro 2,2.  Maybe the keyboard scan codes=
 are
different in newer models?

Key mappings are correct in a vt console using keymap=3D"us.macbook".

The following does NOT fix the issue:

<<<ROOT@beluga.acadix>>> /home/bacon 48 # cat
/etc/X11/xorg.conf.d/macbook-xkb.conf=20
Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "kbd"
        Option "XkbRules" "xorg"
        Option "XkbLayout" "us"
        Option "XkbVariant" "mac"
EndSection

I hacked around it for now by adding

setxkbmap -layout us -variant mac

to the Xsession file, but this of course only works after login.  Keyboard =
is
still confused in the xdm panel, so passwords constaining ~ or ` won't work.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252235-7788>