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 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 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
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
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/03/20 16:50, Mario Olofo wrote:
> Hello,
>
> I configured the full system with pkg and only build the drm-kmod.
>
> I downloaded the img from the 12.0 stable version, don't know when or why
> it become release for me =X
This depends on how you updated it. I could guess you used
Hello,
I configured the full system with pkg and only build the drm-kmod.
I downloaded the img from the 12.0 stable version, don't know when or why
it become release for me =X
The pkg was downloaded the first time I used it, so I don't know what can
be wrong with it.
May you point me some link
On 11/03/20 02:20, Mario Olofo wrote:
> Hello,
>
> @Guido
> I tried to rebuild the xorg-server but it stoped to recognize all input
> devices even on Xfce4, I think I'm missing something.
> Tried to rebuild the xf86-input-evdev too but didn't work either.
> Had to revert to the pkg version to be
On Tue, 10 Mar 2020 at 19:15, Andy Farkas wrote:
>
> Is it just a matter of putting "syscons=[sc|vt]" in loader.conf
> to select whatever driver?
Have a look at sc(4) and vt(4) - in loader.conf:
kern.vty=sc
or
kern.vty=vt
And sysctl kern.vty will let you know which you're using.
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",
14 matches
Mail list logo
