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-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
> 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? -m ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-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-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
> 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. Best, Michael ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-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-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-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-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
Hi! > 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. Thanks. I was wondering myself, what/where there's mention of this. -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-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 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) -m ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
In message , Niclas Zeising w rites: >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 don't think I would have thought the rather counter-intuitive behaviour I saw yesterday, even if you had told me in those very words that the scan-codes had changed :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
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-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-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-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-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-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-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-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
r358858: ipfw: bad destination address any
After upgrading to r358858, CURRENT boxes secured by IPFW failed to handle keyword "any" as source and destination and rc script fails to init the filter correctly: [...] ipfw: bad destination address any [...] This renders any box running CURRENT and ipfw startig filter rules via rc.conf or using own scripts containing "any" as keyword for either source or destination to brick the system. Kind regards, O. Hartmann ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
