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.
> >
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:
> > > >
> > > >
> > > >
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???
> > >
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
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,
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)
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
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
> 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
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
> 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
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
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
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
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
>> 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.
>
>
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
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
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
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:
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",
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
I just updated my laptop from source, and somewhere along the
way the key-codes Xorg sees changed.
I have the right Alt key mapped to "Multi_key", which is now
keycode 108 instead of 113, which is now arrow left instead.
I hope this email saves somebody else from the frustrating
morning I had...
23 matches
Mail list logo
