Re: New Xorg - different key-codes

[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 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

[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 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

[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-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

[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 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

[Greg Rivers]

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

[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 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: FBSD 12.1 - LightDM don't grab keyboard input & Xfce4 window decorator problem

[Guido Falsi via freebsd-stable]

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
freebsd-update at some point, but only you can know for sure.

> The pkg was downloaded the first time I used it, so I don't know what can
> be wrong with it.

Nothing wrong with it, that's not what I meant.

> May you point me some link to understand better how to see if i'm in
> stable/release and how to migrate from quarter to latest?


To check which version of FreeBSD you are using should be possible with
freebsd-version(1), check it's man page, I'm not using stable versions,
only releases and current, and I'm not sure what the output is on stable.

Migrating from quarterly to latest is done by configuring pkg, you
should read the full pkg.conf(5) man page. The EXAMPLES section has
examples clearly explaining what you are asking for.

> I'll see if I'm in latest and reinstall all with pkg

This all depends on what you did on your system, any suggestion can only
be generic. You need to know your system condition.

You stated that you mixed binary packages installed via pkg from the
official repositories with locally built ports. As I said this is not
really supported, and if you only compiled locally part of Xorg and
mixed it with quarterly packages you have an high risk of having
inconsistent binaries on your system.

Check your logs for useful errors.

-- 
Guido Falsi 
___
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: FBSD 12.1 - LightDM don't grab keyboard input & Xfce4 window decorator problem

[Mario Olofo]

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 to understand better how to see if i'm in
stable/release and how to migrate from quarter to latest?
I'll see if I'm in latest and reinstall all with pkg

Thank you,

Mario

Em qua., 11 de mar. de 2020 às 12:24, Guido Falsi 
escreveu:

> 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 able to send this email
>
> Before these rebuilds were you using packages? from quarterly or latest?
>
> AFAIK mixing packages and locally built packages isn't really supported.
> I works most of the time, but there are no warranties. Also it is
> especially prone to breaking when building parts that work with hardware
> drivers.
>
> So to properly upgrade your Xorg server if you're coming from quarterly
> packages the safe way is to configure your machine to use latest
> packages and perform a pkg upgrade. In rare cases you could need pkg
> upgrade -f.
>
> If you want to use ports and have been using packages, only safe way is
> to reinstall everything from ports, but I'd really suggest you use
> project provided packages or build your own package set using a tool
> like poudriere.
>
> Apart from this, new Xorg changes many things and upgrading only the
> server will not be enough anyway.
>
> Unluckily if you don't perform a proper upgrade it's difficult to tell
> if the problem is caused by a bug in some port or induced by some
> misalignment on your system software.
>
> >
> > @Ulf Rudolf 
> > Now knowing that the xorg-server is not recognizing any input devices
> > after rebuild the latest version, I have a feeling that this problem is
> > related, maybe the LightDM expects some specific device?
>
> LightDM uses Xorg for it's input, so, no it should work. Have you tried
> using "startx" as root to check that Xorg itself works fine?
>
> --
> Guido Falsi 
>
___
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: FBSD 12.1 - LightDM don't grab keyboard input & Xfce4 window decorator problem

[Guido Falsi via freebsd-stable]

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 able to send this email

Before these rebuilds were you using packages? from quarterly or latest?

AFAIK mixing packages and locally built packages isn't really supported.
I works most of the time, but there are no warranties. Also it is
especially prone to breaking when building parts that work with hardware
drivers.

So to properly upgrade your Xorg server if you're coming from quarterly
packages the safe way is to configure your machine to use latest
packages and perform a pkg upgrade. In rare cases you could need pkg
upgrade -f.

If you want to use ports and have been using packages, only safe way is
to reinstall everything from ports, but I'd really suggest you use
project provided packages or build your own package set using a tool
like poudriere.

Apart from this, new Xorg changes many things and upgrading only the
server will not be enough anyway.

Unluckily if you don't perform a proper upgrade it's difficult to tell
if the problem is caused by a bug in some port or induced by some
misalignment on your system software.

> 
> @Ulf Rudolf 
> Now knowing that the xorg-server is not recognizing any input devices
> after rebuild the latest version, I have a feeling that this problem is
> related, maybe the LightDM expects some specific device?

LightDM uses Xorg for it's input, so, no it should work. Have you tried
using "startx" as root to check that Xorg itself works fine?

-- 
Guido Falsi 
___
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: vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]

[Ed Maste]

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.
___
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

[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 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

[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 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

[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: 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

[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 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"