Re: xfce4 does not see up arrow after reinstall/xorg update

On Sat, Feb 22, 2020 at 10:31 PM Michael Gmelin <[email protected]> wrote:

>
>
> On Sat, 22 Feb 2020 21:32:03 -0500
> Aryeh Friedman <[email protected]> wrote:
>
> > On Sat, Feb 22, 2020 at 9:04 PM Michael Gmelin <[email protected]>
> > wrote:
> >
> > >
> > >
> > > On Sat, 22 Feb 2020 20:54:34 -0500
> > > Aryeh Friedman <[email protected]> wrote:
> > >
> > > > On Sat, Feb 22, 2020 at 8:37 PM Michael Gmelin <[email protected]>
> > > > wrote:
> > > >
> > > > >
> > > > >
> > > > > On Sat, 22 Feb 2020 20:20:01 -0500
> > > > > Aryeh Friedman <[email protected]> wrote:
> > > > >
> > > > > > On Sat, Feb 22, 2020 at 8:15 PM Michael Gmelin
> > > > > > <[email protected]> wrote:
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Sat, 22 Feb 2020 20:00:17 -0500
> > > > > > > Aryeh Friedman <[email protected]> wrote:
> > > > > > >
> > > > > > > > On Sat, Feb 22, 2020 at 7:46 PM Michael Gmelin
> > > > > > > > <[email protected]> wrote:
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Sun, 23 Feb 2020 01:29:19 +0100
> > > > > > > > > Michael Gmelin <[email protected]> wrote:
> > > > > > > > >
> > > > > > > > > > On Sat, 22 Feb 2020 19:18:19 -0500
> > > > > > > > > > Aryeh Friedman <[email protected]> wrote:
> > > > > > > > > >
> > > > > > > > > > > On Sat, Feb 22, 2020 at 6:45 PM Michael Gmelin
> > > > > > > > > > > <[email protected]> wrote:
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Sat, 22 Feb 2020 18:22:07 -0500
> > > > > > > > > > > > Aryeh Friedman <[email protected]> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > On Sat, Feb 22, 2020 at 5:56 PM Michael Gmelin
> > > > > > > > > > > > > <[email protected]> wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > I would like to make a side comment on the
> > > > > > > > > > > > > > > latest xorg update in general: WHAT A
> > > > > > > > > > > > > > > CLUSTERF*CK this is no where near ready for
> > > > > > > > > > > > > > > production based on the number of people
> > > > > > > > > > > > > > > complaining about basic I/O problems.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > You already made that comment yesterday :)
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > The point is, cursing won't motivate anyone to
> > > > > > > > > > > > > > help you.
> > > > > > > > > > > > >
> > > > > > > > > > > > > You try losing 3 days of paid work due to
> > > > > > > > > > > > > something that claimed to be production ready
> > > > > > > > > > > > > and not pull your hair out. Due to lack of
> > > > > > > > > > > > > money my desktop and test machine are one in
> > > > > > > > > > > > > the same so any serious hiccups in ports and/or
> > > > > > > > > > > > > the base system seriously harm my freelancing
> > > > > > > > > > > > > (sole source of income).
> > > > > > > > > > > >
> > > > > > > > > > > > As you use nvidia, you can remove the kld_list etc
> > > > > > > > > > > > (intel won't help you).
> > > > > > > > > > > >
> > > > > > > > > > > > You seem to have *a lot* of duplicated inputclass
> > > > > > > > > > > > match rules in your configuration files. Not sure
> > > > > > > > > > > > how they ended up in there, but in the past they
> > > > > > > > > > > > probably didn't matter, as you didn't have a UDEV
> > > > > > > > > > > > enabled Xorg server installed.
> > > > > > > > > > > >
> > > > > > > > > > > > So what I asked you to test in 20-edev-kbd.conf
> > > > > > > > > > > > was overwritten by later rules in other
> > > > > > > > > > > > configuration files.
> > > > > > > > > > > >
> > > > > > > > > > > > In general, the way to approach this is to move
> > > > > > > > > > > > all those configuration files (except
> > > > > > > > > > > > 20-edev-kbd.conf) out of xorg.conf.d.
> > > > > > > > > > > >
> > > > > > > > > > > > So you start with a system that has no xorg.conf
> > > > > > > > > > > > files and only xorg.conf.d/20-edev-kbd.conf.
> > > > > > > > > > > >
> > > > > > > > > > > > Now check if this works.
> > > > > > > > > > > >
> > > > > > > > > > > > If it doesn't, replace the contents of
> > > > > > > > > > > > 20-edev-kbd.conf with what I asked you to test
> > > > > > > > > > > > earlier.
> > > > > > > > > > > >
> > > > > > > > > > > > Then report back the results (shouldn't take more
> > > > > > > > > > > > than a couple of minutes).
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Impossible to test either one because mouse is
> > > > > > > > > > > frozen under both.
> > > > > > > > > >
> > > > > > > > > > Based on your tree output below, you don't have
> > > > > > > > > >
> > > > > > > > > > /usr/local/etc/X11/xorg.conf.d/20-evdev-kbd.conf in
> > > > > > > > > > place any more.
> > > > > > > > > >
> > > > > > > > > > Please create it and put the following content in it:
> > > > > > > > > >
> > > > > > > > > > Section "InputClass"
> > > > > > > > > >   Identifier "libinput keyboard catchall"
> > > > > > > > > >   MatchIsKeyboard "on"
> > > > > > > > > >   MatchDevicePath "/dev/input/event*"
> > > > > > > > > >   Driver "libinput"
> > > > > > > > > >   Option "XkbRules" "evdev"
> > > > > > > > > > EndSection
> > > > > > > > > >
> > > > > > > > > > Section "InputClass"
> > > > > > > > > >   Identifier "libinput touchpad catchall"
> > > > > > > > > >   MatchIsTouchpad "on"
> > > > > > > > > >   MatchDevicePath "/dev/input/event*"
> > > > > > > > > >   Driver "libinput"
> > > > > > > > > >   Option "MiddleEmulation" "on"
> > > > > > > > > >   Option "DisableWhileTyping" "off"
> > > > > > > > > > EndSection
> > > > > > > > > >
> > > > > > > > > > Also, please make sure moused isn't running
> > > > > > > > > > (killall moused)
> > > > > > > > > >
> > > > > > > > > > Then test again, report back and include the output of
> > > > > > > > > >
> > > > > > > > > > tree /usr/local/etc/X11/
> > > > > > > > >
> > > > > > > >
> > > > > > > > No luck on up arrow.
> > > > > > > >
> > > > > > > > /usr/local/etc/X11/
> > > > > > > > |-- fontpath.d
> > > > > > > > |-- xinit
> > > > > > > > |   |-- xinitrc
> > > > > > > > |   `-- xinitrc.d
> > > > > > > > |       `-- 90-consolekit
> > > > > > > > `-- xorg.conf.d
> > > > > > > >     |-- 99-myinput.conf
> > > > > > > >     `-- driver-nvidia.conf
> > > > > > > >
> > > > > > > > 4 directories, 4 files
> > > > > > > >
> > > > > > > > Since you asked for in the email you said to ignore here
> > > > > > > > is what nvidia-driver has in it:
> > > > > > > >
> > > > > > > > Section "Device"
> > > > > > > >         Identifier "NVIDIA Card"
> > > > > > > >         VendorName "NVIDIA Corporation"
> > > > > > > >         Driver "nvidia"
> > > > > > > > Option "RandRRotation" "True"
> > > > > > > > EndSection
> > > > > > >
> > > > > > > Last things I can think of from the top of my head is
> > > > > > > running:
> > > > > > >
> > > > > > > setxkbmap -model pc105 -layout us
> > > > > > >
> > > > > > > in a terminal and see if that makes a difference (that
> > > > > > > command comes from the setxkbmap package and should be
> > > > > > > installed).
> > > > > > >
> > > > > > > (I assume you use a US USB keyboard USB and a USB mouse?
> > > > > > > Anything special there or just standard material?)
> > > > > > >
> > > > > >
> > > > > > No luck.... Yes USB on both and as far I know nothing special
> > > > > > (don't see how their could be on a $5 mouse [store brand,
> > > > > > Staples, no model number] and a $15 keyboard [Logitech k120])
> > > > > >
> > > > >
> > > > > Very strange.
> > > > >
> > > > > Like I said, I have an old macbook here that has some nvidia
> > > > > gfx in it - I could try setting that up with an external
> > > > > keyboard and mouse and see what happens.
> > > > >
> > > > > What I find strange is that this only happens with xfce4 and not
> > > > > with twm.
> > > > >
> > > > >
> > > > > Do you get actually get any keyboard events when pressing the
> > > > > arrow key in xev? (from "pkg install xev")
> > > > >
> > > >
> > > > KeymapNotify event, serial 37, synthetic NO, window 0x0,
> > > >     keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0
> > > > 0   0 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
> > > > 0
> > >
> > > But no keydown/keyup events it seems.
> > >
> > > > The cursor also flashes when I do it in a terminal so clearly it
> > > > is getting something.
> > > >
> > >
> > > I'm installing xfce4 on my old macbook here now (12.1-RELEASE,
> > > packages from latest). Let's see if I can reproduce it (easily?).
> > > It has an nvidia 9400M.
> > >
> > > Could you try one more thing in the meantime:
> > > Add another unprivileged user to your machine (let's say: "xtester")
> > > and copy your .xinitrc to that new user. Then login as that user
> > > and start X as that new user and see if it's the same problem (just
> > > to rule out anything special in your normal user's settings).
> > >
> >
> > As expected no luck.
> >
>
> I installed all of this on the old macbook now. Similar setup to yours,
> nvidia graphics adapter.
>
> Used all standard .conf files (including those
> in /usr/local/share/X11/xorg.conf.d - those were a read herring,
> sorry).
>
> Also have one nvivida.conf file there to load the driver.
>
> I installed xfce4-wm and xfce4-desktop and used your .xinitrc.
>
> There was only one difference:
>
> I added
>
> setxkbmap -model pc105 -layout de
>
> as the first line of my ~/.xinitrc.
> I always do that to get the correct keyboard layout (de).
>
> Everything seemed to work just fine, no problems, arrow keys work etc.
>
> Now, when I remove that line from .xinitrc, the keyboard starts to act
> up like you described (e.g. arrow up doesn't show the history in xterm).
>
> Interestingly, it didn't always work immediately after re-adding the
> line, I had to restart X a few times.
>
> So what I would recommend to test is:
>
> Assuming that you're using an US keyboard, add:
>
> setxkbmap -model pc105 -layout us
>
> as the first line of your ~/.xinitrc
>
> Then reboot your machine (to be safe) and try to run startx.
>
> Interestingly, running the command after xfce started doesn't fix the
> problem, that's probably why my your previous tests with this command
> didn't help. Also, changing the keyboard layout using xfce's settings
> dialog doesn't fix it either. So it needs to be set before xfce-wm is
> started (first line of .xinitrc).
>
> Let's hope this fixes the issue for you.
>
> Best,
> Michael
>
> p.s.
> # cat ~/.xinitrc
> setxkbmap -model pc105 -layout de
> xset -dpms
> xset s off
> nvidia-settings --load-config-only
> xhost +
> . /usr/local/etc/xdg/xfce4/xinitrc
>

Works now who/how do I report this in such a way that it will be fixed the
right way and/or note added to /usr/ports/UPDATES so the next person
doesn't have to deal with it?


>
>
> --
> Michael Gmelin
>


-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-x11
To unsubscribe, send any mail to "[email protected]"