r358858: ipfw: bad destination address any

2020-03-11 Thread O. Hartmann
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 us

Re: New Xorg - different key-codes

2020-03-11 Thread Mark Martinec
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

Re: New Xorg - different key-codes

2020-03-11 Thread Niclas Zeising
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:

Re: New Xorg - different key-codes

2020-03-11 Thread Niclas Zeising
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

Re: New Xorg - different key-codes

2020-03-11 Thread Niclas Zeising
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

Re: New Xorg - different key-codes

2020-03-11 Thread Poul-Henning Kamp
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

Re: New Xorg - different key-codes

2020-03-11 Thread Michael Gmelin
 >> 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. > > An

Re: New Xorg - different key-codes

2020-03-11 Thread Peter Jeremy
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

Re: New Xorg - different key-codes

2020-03-11 Thread Kurt Jaeger
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 UPDATIN

Re: New Xorg - different key-codes

2020-03-11 Thread Kevin Oberman
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 sev

Re: New Xorg - different key-codes

2020-03-11 Thread 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 -CURRE

Re: New Xorg - different key-codes

2020-03-11 Thread Michael Gmelin
> 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 s

Re: New Xorg - different key-codes

2020-03-11 Thread Bob Willcox
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 ju

Re: New Xorg - different key-codes

2020-03-11 Thread Michael Gmelin
> 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,

Re: New Xorg - different key-codes

2020-03-11 Thread Steffen Nurpmeso
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