Re: New Xorg - different key-codes
On Thu, Mar 12, 2020 at 11:11:53AM +0100, Michael Gmelin wrote: > > > On Thu, 12 Mar 2020 10:31:40 +0100 > Alexander Leidinger wrote: > > > Hi, > > > > This command sets the keyboard layout. You are supposed to set the > > keyboard layout which matches the physical layout of the hardware. > > This hadn't changed, it's a fundamental part of X11 since I know it > > (X11 6.5) and even before... > > [snip] > > Exactly. I just personally prefer to use setxkbmap, as all my setups are > single user (one unprivileged user per machine that runs X, no shared > machines) and customization happens in $HOME that way. Makes it a > bit easier to setup a new machine (no digging in Xorg configs) and > reading ~/.xinitrc basically tells me all about my current config. > > Plus, setxkbmap makes it easy to experiment, as it's applies changes > while X is running, even if one makes the those changes permanently in > an xorg config file later. And the resulting command is just one line > (in my case as short as "setxkbmap -model pc105 -layout de"), makes it > easier to support people. > > Another useful application of the command is for debugging: > "setxkbmap -query" will tell you what's currently configured (regardless > how that configuration was done), e.g., > > On a machine running xorg 1.18: > > # setxkbmap -query > rules: base > model: pc105 > layout: de > > On a machine running xorg 1.20: > rules: evdev > model: pc105 > layout: de > > In both cases the same setxkbmap command was used in ~/.xinitrc to set > model and layout. Rules were taken from Xorg's default config, which > changed to evdev in 1.20. I ran "setxkbmap -query" on my home workstation that hasn't had X updated on it yet and this is what I got: rules: base model: pc105 layout: us So presumably that was the default setting from when I installed the system last April. I plan to run this again after I update xorg on this system, but not too sure when I'll get to that. Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Thu, Mar 12, 2020 at 04:53:32PM +0100, Michael Gmelin wrote: > > > On Thu, 12 Mar 2020 10:36:42 -0500 > Bob Willcox wrote: > > > On Thu, Mar 12, 2020 at 07:24:42AM -0500, Bob Willcox wrote: > > > On Wed, Mar 11, 2020 at 11:46:49PM +0100, Michael Gmelin wrote: > > > > > > > > > > > > SNIP SNAP > > > > >> It might fix the ???Down key opens application launcher??? > > > > >> problem by applying the correct keymap (you have to select the > > > > >> correct one, ???de??? probably won???t cut it for you). At > > > > >> least it did with xfce, where it was important to run it > > > > >> before the wm starts - you could also try running it > > > > >> afterwards to see if it makes a difference. > > > > > > > > > > I don't know about that problem. What I'm experiencing is the > > > > > Alt-up,down,left,right keys don't work as they used to in my > > > > > ctwm window manager. They used to move the current window to > > > > > the closest boundry in the direction indicated by the key that > > > > > is also pressed (while holding the Alt key down). Also, > > > > > Alt-shift-up,down,left,right would expand the window in the > > > > > direction indicated by the key. These actions seem to do > > > > > nothing now. > > > > > > > > I don???t know much about ctwm, but why don???t you give it a > > > > shot? > > > > > > I plan to sometime today when I get into the office. But since it's > > > my work system and I am dependent on it to do my job, I've just > > > been a little hesitant. > > > > Ok, I added this to my ~/.xinitrc file: > > > > setxkbmap -model pc105 -layout us > > > > and my ctwm window adjustment hot keys are working again. :) > > > > I do wonder why it was deemed ok to change the default behavior for > > the key mappings? Couldn't the default mappings have remained the > > same with change to evdev? This change certainly violated the > > "principle of least surprise" for me. > > > > > > I think the change was unavoidable, but it could've been communicated > better. Then again, time and resources are limited and I'm quite > grateful the graphics team finally made that necessary push forward. > > I'm curious how people set their keyboard layout in the past though, > is it possible that the defaults just worked for US users? I always had > to set it explicitly (setxkbmap or in Xorg.conf), so I was never really > affected by this change. > > -m > > p.s. What does "setxkbmap -query" show if you start X without setting > the keymap in .xinitrc? I'll have to try that when I get home tonight on one of my other systems as I really can't afford to take the time to restart X on this system now...got to get some work done. :) Bob > > -- > Michael Gmelin -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Thu, Mar 12, 2020 at 07:24:42AM -0500, Bob Willcox wrote: > On Wed, Mar 11, 2020 at 11:46:49PM +0100, Michael Gmelin wrote: > > > > > > > On 11. Mar 2020, at 23:25, Bob Willcox wrote: > > > > > > ???On Wed, Mar 11, 2020 at 11:04:18PM +0100, Michael Gmelin wrote: > > >> > > >> > > On 11. Mar 2020, at 22:58, Bob Willcox wrote: > > >>> > > >>> ???On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote: > > ??? > > >> On 11. Mar 2020, at 10:29, Mark Martinec > > >> wrote: > > > ??? > > >> > > >>> I just updated my laptop from source, and somewhere along the way > > >>> the key-codes Xorg sees changed. > > >> Indeed. This doesn't just affect -CURRENT: it happened to me on > > >> -STABLE last week, so I'm copying that list too. > > > > > > And a "Down" key now opens and closes a KDE "Application Launcher", > > > alternatively with its original function (which makes editing a > > > frustration). > > > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354 > > > > > > > > > > This *might* help you: > > > > https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/025046.html > > > > (Short version: run setxkbmap in ~/.xinitrc, e.g., > > setxkbmap -model pc105 -layout de) > > >>> > > >>> Will running that command return my key mappings back to what they use > > >>> to be? > > >>> > > >> > > >> It might fix the ???Down key opens application launcher??? problem by > > >> applying the correct keymap (you have to select the correct one, > > >> ???de??? probably won???t cut it for you). At least it did with xfce, > > >> where it was important to run it before the wm starts - you could also > > >> try running it afterwards to see if it makes a difference. > > > > > > I don't know about that problem. What I'm experiencing is the > > > Alt-up,down,left,right keys > > > don't work as they used to in my ctwm window manager. They used to move > > > the current window > > > to the closest boundry in the direction indicated by the key that is also > > > pressed (while > > > holding the Alt key down). Also, Alt-shift-up,down,left,right would > > > expand the window in > > > the direction indicated by the key. These actions seem to do nothing now. > > > > > > > I don???t know much about ctwm, but why don???t you give it a shot? > > I plan to sometime today when I get into the office. But since it's my work > system and I > am dependent on it to do my job, I've just been a little hesitant. Ok, I added this to my ~/.xinitrc file: setxkbmap -model pc105 -layout us and my ctwm window adjustment hot keys are working again. :) I do wonder why it was deemed ok to change the default behavior for the key mappings? Couldn't the default mappings have remained the same with change to evdev? This change certainly violated the "principle of least surprise" for me. > > Bob > > -- > Bob Willcox| It's possible that the whole purpose of your life is to > b...@immure.com | serve as a warning to others. > Austin, TX | -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Wed, Mar 11, 2020 at 11:46:49PM +0100, Michael Gmelin wrote: > > > > On 11. Mar 2020, at 23:25, Bob Willcox wrote: > > > > ???On Wed, Mar 11, 2020 at 11:04:18PM +0100, Michael Gmelin wrote: > >> > >> > On 11. Mar 2020, at 22:58, Bob Willcox wrote: > >>> > >>> ???On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote: > ??? > >> On 11. Mar 2020, at 10:29, Mark Martinec > >> wrote: > > ??? > >> > >>> I just updated my laptop from source, and somewhere along the way > >>> the key-codes Xorg sees changed. > >> Indeed. This doesn't just affect -CURRENT: it happened to me on > >> -STABLE last week, so I'm copying that list too. > > > > And a "Down" key now opens and closes a KDE "Application Launcher", > > alternatively with its original function (which makes editing a > > frustration). > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354 > > > > > > This *might* help you: > > https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/025046.html > > (Short version: run setxkbmap in ~/.xinitrc, e.g., > setxkbmap -model pc105 -layout de) > >>> > >>> Will running that command return my key mappings back to what they use to > >>> be? > >>> > >> > >> It might fix the ???Down key opens application launcher??? problem by > >> applying the correct keymap (you have to select the correct one, ???de??? > >> probably won???t cut it for you). At least it did with xfce, where it was > >> important to run it before the wm starts - you could also try running it > >> afterwards to see if it makes a difference. > > > > I don't know about that problem. What I'm experiencing is the > > Alt-up,down,left,right keys > > don't work as they used to in my ctwm window manager. They used to move the > > current window > > to the closest boundry in the direction indicated by the key that is also > > pressed (while > > holding the Alt key down). Also, Alt-shift-up,down,left,right would expand > > the window in > > the direction indicated by the key. These actions seem to do nothing now. > > > > I don???t know much about ctwm, but why don???t you give it a shot? I plan to sometime today when I get into the office. But since it's my work system and I am dependent on it to do my job, I've just been a little hesitant. Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
Hi,
This command sets the keyboard layout. You are supposed to set the keyboard
layout which matches the physical layout of the hardware. This hadn't
changed, it's a fundamental part of X11 since I know it (X11 6.5) and even
before...
For those which had an explicit setting in xorg.conf (like me) but switched
now to nothing or the "match" snippets for mouse or kbd: you can specify
this already in the config. Here is what I use:
---snip---
Donnerstag, 12. März 2020, 10:21:40
{1} [video:/]
(201) root@ttypts/1 # cat /usr/local/etc/X11/xorg.conf.d/kbd.conf Section
"InputClass"
Identifier "Keyboard0"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "libinput"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
Option "XkbRules" "evdev"
EndSection
Donnerstag, 12. März 2020, 10:22:05
{0} [video:/]
(202) root@ttypts/1 # cat /usr/local/etc/X11/xorg.conf.d/mouse.conf
Section "InputClass"
Identifier "Mouse0"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "libinput"
# Option "Protocol" "auto"
# Option "Device" "/dev/sysmouse"
Option "ZAxisMapping" "4 5 6 7"
EndSection
---snip---
Note, I use this in sysctl.conf:
---snip---
# enable hardware devices in evdev
kern.evdev.rcpt_mask=12
---snip---
When I did that, I just validated that I was able to login to KDE (the
particular X11 is feeding a home-cinema setup and is not used often, I just
decided to update it as long as I remembered there was a change to xorg
with a config impact). I didn't check any up/down/umlauts, I just plain
assumed it works (and I still assume it does). The above is just meant to
provide some info how to make it work globally instead of having a setting
in each local startup per user.
Bye,
Alexander.
--
Send from a mobile device, please forgive brevity and misspellings.
Am 11. März 2020 23:07:55 schrieb Bob Willcox :
On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote:
???
>> On 11. Mar 2020, at 10:29, Mark Martinec
>> wrote:
> ???
>>
>>> I just updated my laptop from source, and somewhere along the way
>>> the key-codes Xorg sees changed.
>> Indeed. This doesn't just affect -CURRENT: it happened to me on
>> -STABLE last week, so I'm copying that list too.
>
> And a "Down" key now opens and closes a KDE "Application Launcher",
> alternatively with its original function (which makes editing a
> frustration).
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354
>
>
This *might* help you:
https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/025046.html
(Short version: run setxkbmap in ~/.xinitrc, e.g.,
setxkbmap -model pc105 -layout de)
Will running that command return my key mappings back to what they use to be?
--
Bob Willcox| It's possible that the whole purpose of your life is to
b...@immure.com | serve as a warning to others.
Austin, TX |
___
freebsd-curr...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
Bob Willcox wrote in
<20200311214930.gc5...@rancor.immure.com>:
|On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote:
|>>> On 11. Mar 2020, at 10:29, Mark Martinec
|>>> wrote:
...
| I just updated my laptop from source, and somewhere along the way
| the key-codes Xorg sees changed.
...
|> This *might* help you:
|>
|> https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/025046.html
|>
|> (Short version: run setxkbmap in ~/.xinitrc, e.g.,
|> setxkbmap -model pc105 -layout de)
|
|Will running that command return my key mappings back to what they \
|use to be?
I for one am totally baffled that you all "just can go".
My ~/.xinitrc is (in parts)
if command -v setxkbmap >/dev/null 2>&1; then
if [ -f ~/.${HOSTNAME}.xkbmap ]; then
setxkbmap `cat ~/.${HOSTNAME}.xkbmap`
elif [ -f ~/.xkbmap ]; then
setxkbmap `cat ~/.xkbmap`
fi
fi
if command -v xmodmap >/dev/null 2>&1; then
[ -f ~/.xmodmaprc ] && xmodmap ~/.xmodmaprc
[ -f ~/.${HOSTNAME}.xmodmaprc ] && xmodmap ~/.${HOSTNAME}.xmodmaprc
fi
if command -v xrdb >/dev/null 2>&1; then
[ -f ~/.Xdefaults ] && xrdb -merge ~/.Xdefaults
[ -f ~/.${HOSTNAME}.Xdefaults ] && xrdb -merge ~/.${HOSTNAME}.Xdefaults
fi
and i (i think ever) had to _have_ those (former being
'de(nodeadkeys)', the middle one too long to paste, but also works
around the "g" key of that Lenovo notebook ever since that stopped
working).
--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Wed, Mar 11, 2020 at 11:04:18PM +0100, Michael Gmelin wrote: > > > > On 11. Mar 2020, at 22:58, Bob Willcox wrote: > > > > ???On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote: > >> ??? > On 11. Mar 2020, at 10:29, Mark Martinec > wrote: > >>> ??? > > > I just updated my laptop from source, and somewhere along the way > > the key-codes Xorg sees changed. > Indeed. This doesn't just affect -CURRENT: it happened to me on > -STABLE last week, so I'm copying that list too. > >>> > >>> And a "Down" key now opens and closes a KDE "Application Launcher", > >>> alternatively with its original function (which makes editing a > >>> frustration). > >>> > >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354 > >>> > >>> > >> > >> This *might* help you: > >> > >> https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/025046.html > >> > >> (Short version: run setxkbmap in ~/.xinitrc, e.g., > >> setxkbmap -model pc105 -layout de) > > > > Will running that command return my key mappings back to what they use to > > be? > > > > It might fix the ???Down key opens application launcher??? problem by > applying the correct keymap (you have to select the correct one, ???de??? > probably won???t cut it for you). At least it did with xfce, where it was > important to run it before the wm starts - you could also try running it > afterwards to see if it makes a difference. I don't know about that problem. What I'm experiencing is the Alt-up,down,left,right keys don't work as they used to in my ctwm window manager. They used to move the current window to the closest boundry in the direction indicated by the key that is also pressed (while holding the Alt key down). Also, Alt-shift-up,down,left,right would expand the window in the direction indicated by the key. These actions seem to do nothing now. Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote: > ??? > >> On 11. Mar 2020, at 10:29, Mark Martinec > >> wrote: > > ??? > >> > >>> I just updated my laptop from source, and somewhere along the way > >>> the key-codes Xorg sees changed. > >> Indeed. This doesn't just affect -CURRENT: it happened to me on > >> -STABLE last week, so I'm copying that list too. > > > > And a "Down" key now opens and closes a KDE "Application Launcher", > > alternatively with its original function (which makes editing a > > frustration). > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354 > > > > > > This *might* help you: > > https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/025046.html > > (Short version: run setxkbmap in ~/.xinitrc, e.g., > setxkbmap -model pc105 -layout de) Will running that command return my key mappings back to what they use to be? -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Wed, Mar 11, 2020 at 1:51 PM Greg Rivers wrote: > On Wednesday, 11 March 2020 13:53:45 CDT Peter Jeremy wrote: > > On 2020-Mar-11 10:29:08 +0100, Niclas Zeising > wrote: > > >This has to do with switching to using evdev to handle input devices on > > >FreeBSD 12 and CURRENT. There's been several reports, and suggested > > >solutions to this, as well as an UPDATING entry detailing the change. > > > > The UPDATING entry says that it's switched from devd to udev. There's no > > mention of evdev or that the keycodes have been roto-tilled. It's > basically > > a vanilla "things have been changed, see the documentation" entry. Given > > that entry, it's hardly surprising that people are confused. > > > Indeed, the change has been a bit inconvenient and time consuming to deal > with. > > But I don't think we should let this overshadow the dedication and very > hard work that Niclas and the graphics team have done and continue to do to > keep FreeBSD relevant on the desktop. I for one am very grateful for that. > > -- > Greg > And the people involved have been very active in helping people resolve the problems. In particular, Michael Gmelin had been very helpful in providing a workaround for the failure of the brightness control buttons on my rather ancient T520. He has also provided a solution for the failure of the volume control buttons that I've had since the last update to MATE. I have yet to try it as something else (no idea what) had magically fixed this after a couple of months of them not working. I can't figure out what "fixed" this, but it just started working a couple of weeks ago. Until/unless it fails, I'm not touching things. Also, my apologies to Michael as I have not responded to him with a status update for WAY too long. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Wednesday, 11 March 2020 13:53:45 CDT Peter Jeremy wrote: > On 2020-Mar-11 10:29:08 +0100, Niclas Zeising wrote: > >This has to do with switching to using evdev to handle input devices on > >FreeBSD 12 and CURRENT. There's been several reports, and suggested > >solutions to this, as well as an UPDATING entry detailing the change. > > The UPDATING entry says that it's switched from devd to udev. There's no > mention of evdev or that the keycodes have been roto-tilled. It's basically > a vanilla "things have been changed, see the documentation" entry. Given > that entry, it's hardly surprising that people are confused. > Indeed, the change has been a bit inconvenient and time consuming to deal with. But I don't think we should let this overshadow the dedication and very hard work that Niclas and the graphics team have done and continue to do to keep FreeBSD relevant on the desktop. I for one am very grateful for that. -- Greg ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On 2020-Mar-11 10:29:08 +0100, Niclas Zeising wrote: >This has to do with switching to using evdev to handle input devices on >FreeBSD 12 and CURRENT. There's been several reports, and suggested >solutions to this, as well as an UPDATING entry detailing the change. The UPDATING entry says that it's switched from devd to udev. There's no mention of evdev or that the keycodes have been roto-tilled. It's basically a vanilla "things have been changed, see the documentation" entry. Given that entry, it's hardly surprising that people are confused. -- Peter Jeremy signature.asc Description: PGP signature
Re: New Xorg - different key-codes
On 2020-03-11 10:29, Niclas Zeising wrote: On 2020-03-11 01:46, Greg 'groggy' Lehey wrote: Sorry. I should have thought of reporting it. For me, with a number of other issues, it was a frustrating week,some of which are still not resolved. As a side note, if it's not reported, it's very hard for us to be aware of issues, and to help out in resolving them. Regards -- Niclas Zeising ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On 2020-03-11 10:27, Mark Martinec wrote: I just updated my laptop from source, and somewhere along the way the key-codes Xorg sees changed. Indeed. This doesn't just affect -CURRENT: it happened to me on -STABLE last week, so I'm copying that list too. And a "Down" key now opens and closes a KDE "Application Launcher", alternatively with its original function (which makes editing a frustration). https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354 And that PR has a suggested solution for at least KDE users. Regards -- Niclas Zeising ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On 2020-03-11 01:46, Greg 'groggy' Lehey wrote:
On Wednesday, 11 March 2020 at 0:20:03 +, Poul-Henning Kamp wrote:
[originally sent to current@]
I just updated my laptop from source, and somewhere along the way
the key-codes Xorg sees changed.
Indeed. This doesn't just affect -CURRENT: it happened to me on
-STABLE last week, so I'm copying that list too. See
http://www.lemis.com/grog/diary-mar2020.php?topics=c=Daily%20teevee%20update=D-20200306-002910#D-20200306-002910
, not the first entry on the subject.
I have the right Alt key mapped to "Multi_key", which is now
keycode 108 instead of 113, which is now arrow left instead.
Interesting. Mine wandered from 117 to 147, with PageDown ("Next") as
collateral damage. It seems that there are a lot of strange new key
bindings (partial output of xmodmap -pk):
117 0xff56 (Next) 0x (NoSymbol) 0xff56 (Next)
130 0xff31 (Hangul) 0x (NoSymbol) 0xff31 (Hangul)
131 0xff34 (Hangul_Hanja) 0x (NoSymbol) 0xff34
(Hangul_Hanja)
135 0xff67 (Menu) 0x (NoSymbol) 0xff67 (Menu)
147 0x1008ff65 (XF86MenuKB) 0x (NoSymbol) 0x1008ff65
(XF86MenuKB)
Some of these may reflect other remappings that I have done.
I hope this email saves somebody else from the frustrating
morning I had...
Sorry. I should have thought of reporting it. For me, with a number
of other issues, it was a frustrating week,some of which are still not
resolved.
This has to do with switching to using evdev to handle input devices on
FreeBSD 12 and CURRENT. There's been several reports, and suggested
solutions to this, as well as an UPDATING entry detailing the change.
I'm sorry that it has caused fallout, but it is something that needs to
be done in order to keep up with upstream graphics stack, and to improve
FreeBSD desktop support in general.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196678 has some
discussions regarding input devices, as does the x11@ mailing list archives.
Regards
--
Niclas Zeising
FreeBSD Graphics Team
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
I just updated my laptop from source, and somewhere along the way the key-codes Xorg sees changed. Indeed. This doesn't just affect -CURRENT: it happened to me on -STABLE last week, so I'm copying that list too. And a "Down" key now opens and closes a KDE "Application Launcher", alternatively with its original function (which makes editing a frustration). https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354 Mark ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Wednesday, 11 March 2020 at 0:20:03 +, Poul-Henning Kamp wrote:
[originally sent to current@]
> I just updated my laptop from source, and somewhere along the way
> the key-codes Xorg sees changed.
Indeed. This doesn't just affect -CURRENT: it happened to me on
-STABLE last week, so I'm copying that list too. See
http://www.lemis.com/grog/diary-mar2020.php?topics=c=Daily%20teevee%20update=D-20200306-002910#D-20200306-002910
, not the first entry on the subject.
> I have the right Alt key mapped to "Multi_key", which is now
> keycode 108 instead of 113, which is now arrow left instead.
Interesting. Mine wandered from 117 to 147, with PageDown ("Next") as
collateral damage. It seems that there are a lot of strange new key
bindings (partial output of xmodmap -pk):
117 0xff56 (Next) 0x (NoSymbol) 0xff56 (Next)
130 0xff31 (Hangul) 0x (NoSymbol) 0xff31 (Hangul)
131 0xff34 (Hangul_Hanja) 0x (NoSymbol) 0xff34
(Hangul_Hanja)
135 0xff67 (Menu) 0x (NoSymbol) 0xff67 (Menu)
147 0x1008ff65 (XF86MenuKB) 0x (NoSymbol) 0x1008ff65
(XF86MenuKB)
Some of these may reflect other remappings that I have done.
> I hope this email saves somebody else from the frustrating
> morning I had...
Sorry. I should have thought of reporting it. For me, with a number
of other issues, it was a frustrating week,some of which are still not
resolved.
Greg
--
Sent from my desktop computer.
Finger g...@freebsd.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
signature.asc
Description: PGP signature
