Re: Weird mouse behaviour
On 2020-04-27 17:06, Malcolm Matalka wrote: Michael Gmelin writes: Could you share your setup by running pkg install ca_root_nss fetch \ https://raw.githubusercontent.com/grembo/xorg-udev-setup-check/master/xorg-udev-setup-check.sh ./xorg-udev-setup-check.sh -desk and mailing the resulting file to the list (or just me directly)? I ran this and emailed results to Michael. I fixed the issues it brought up and, tada, it's working. One thing I'm not sure about is: how do I persist the changes? I have done: xinput --set-prop "SynPS/2 Synaptics TouchPad" "libinput Tapping Enabled" 1 xinput --set-prop "SynPS/2 Synaptics TouchPad" "libinput Accel Speed" 0.3 I put these in my .xinitrc, before i start my window manager. xinitrc is read by startx. If you're using a session manager (gdm, sddm or similar) it should be possible to put the same commands in .xsession instead. But these names don't seem to directly correspond to names in man 4 libinput. Why the difference? I also noticed in xorg logs: [34.491] (EE) event6 - SynPS/2 Synaptics TouchPad: kernel bug: Touch jump detected and discarded. See https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html for details [34.491] (EE) event6 - SynPS/2 Synaptics TouchPad: WARNING: log rate limit exceeded (5 msgs per 720ms). Discarding future messages. Those warnings can be disregarded. They're not great, but I see them too and I haven't found any ill effects. Regards -- Niclas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
On Mon, 27 Apr 2020 17:06:28 +0200 Malcolm Matalka wrote: > Michael Gmelin writes: > > > > > Could you share your setup by running > > > > pkg install ca_root_nss > > fetch \ > > > > https://raw.githubusercontent.com/grembo/xorg-udev-setup-check/master/xorg-udev-setup-check.sh > > ./xorg-udev-setup-check.sh -desk > > > > and mailing the resulting file to the list (or just me directly)? > > I ran this and emailed results to Michael. I fixed the issues it > brought up and, tada, it's working. > > One thing I'm not sure about is: how do I persist the changes? I have > done: > > xinput --set-prop "SynPS/2 Synaptics TouchPad" "libinput Tapping > Enabled" 1 > > xinput --set-prop "SynPS/2 Synaptics TouchPad" "libinput Accel Speed" > 0.3 > There are two fundamental ways: 1. Place a configuration file in /usr/local/etc/X11/xorg.conf.d 2. Add the xinput commands to ~/.xinitrc I usually go with option 2 these days whenever possible (unless it's something that can only be done in Xorg's configuration files). So a typical ~/.xinitrc would look like this: setxkbmap -model pc105 -layout de xmodmap $HOME/.Xmodmap xinput --set-prop "xyz" "0 0 0" xsetroot ... /path/to/my/windowmanager You can find the one I used a few years ago here as an example: https://blog.grem.de/pages/t470s.html#my-home-xinitrc That way it's also part of my home directory and I can easily take it to another machine. It also means I don't change Xorg's default configs directly, which makes updating easier. The best part is, that once I found the right tweak, I can simply copy and paste the command that fixed the issue in there and call it a day. And if anyone asks for help, I can consult my ~/.xinitrc and ask them to execute the commands to test if it fixes their ache - which is easier and often doesn't require to restart X. > But these names don't seem to directly correspond to names in man 4 > libinput. Why the difference? That's kind of an upstream question, but you can see at least where it's done it in the source of xf86-input-libinput[0]. Basically it's done that way for pragmatic reasons (unifying xf86 input section config vs xinput ABI would probably violate the Pareto principle). It's a bit confusing, but as most things that you can configure and their current configuration vales can be seen and tweaked by calling xinput on the command line, I barely visit that man page. One more reason why I tweak these things in ~/.xinitrc. > > I also noticed in xorg logs: > > [34.491] (EE) event6 - SynPS/2 Synaptics TouchPad: kernel bug: > Touch jump detected and discarded. See > https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html > for details [34.491] (EE) event6 - SynPS/2 Synaptics TouchPad: > WARNING: log rate limit exceeded (5 msgs per 720ms). Discarding That's to be expected and can be ignored, unless you notice any usability problems. Cheers, Michael [0] cd /usr/ports/x11-drivers/xf86-input-libinput make patch cd work/xf86-input-libinput* see src/xf86libinput.c and include/libinput-properties.h -- Michael Gmelin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
Michael Gmelin writes: > > Could you share your setup by running > > pkg install ca_root_nss > fetch \ > > https://raw.githubusercontent.com/grembo/xorg-udev-setup-check/master/xorg-udev-setup-check.sh > ./xorg-udev-setup-check.sh -desk > > and mailing the resulting file to the list (or just me directly)? I ran this and emailed results to Michael. I fixed the issues it brought up and, tada, it's working. One thing I'm not sure about is: how do I persist the changes? I have done: xinput --set-prop "SynPS/2 Synaptics TouchPad" "libinput Tapping Enabled" 1 xinput --set-prop "SynPS/2 Synaptics TouchPad" "libinput Accel Speed" 0.3 But these names don't seem to directly correspond to names in man 4 libinput. Why the difference? I also noticed in xorg logs: [34.491] (EE) event6 - SynPS/2 Synaptics TouchPad: kernel bug: Touch jump detected and discarded. See https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html for details [34.491] (EE) event6 - SynPS/2 Synaptics TouchPad: WARNING: log rate limit exceeded (5 msgs per 720ms). Discarding future messages. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
On Mon, 27 Apr 2020 12:55:57 +0200 Malcolm Matalka wrote: > Niclas Zeising writes: > > > On 2020-04-27 10:14, Malcolm Matalka wrote: > >> > >> > >> Niclas Zeising writes: > >> > >>> On 2020-04-27 08:03, Malcolm Matalka wrote: > I saw that there was another thread on this and I wanted to > throw my experience in: my mouse was sluggish and tap-to-click > did not work. I set the evdev mask back to 3 and it worked. > > I am on a Dell XPS 13. > >>> > >>> Hi! > >>> Is this on CURRENT? When using X? > >>> Can you verify that you have xf86-input-libinput installed? > >>> You can change sensitivity and enable tap to click using xinput. > >>> Regards > >> > >> Yes this is current, and I'm on commit 360355. Yes I do have it > >> installed. And yes I am on X. > >> > >> The situation I was in this morning after installing the new > >> kernel was things that previously worked no longer worked so I did > >> the shortest path I could find to get them working, which was > >> modifying this evdev. > >> > >> Is there a document on how one is supposed to configure their > >> system in X? I have never used xinput, instead I have configured > >> my trackpad through sysctl. I'm happy to do it the way that is > >> considered correct but I've sort of pieced together how to get my > >> system setup. > > > > First off, do you have any local xorg conf? That's generally not > > needed any more. > > No I don't. I just did a bunch of sysctls to configure the mouse (it > was very sensitive to touch such that if my palm grazed the trackpad > it became a click). > Could you share your setup by running pkg install ca_root_nss fetch \ https://raw.githubusercontent.com/grembo/xorg-udev-setup-check/master/xorg-udev-setup-check.sh ./xorg-udev-setup-check.sh -desk and mailing the resulting file to the list (or just me directly)? Cheers, Michael -- Michael Gmelin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
Niclas Zeising writes: > On 2020-04-27 10:14, Malcolm Matalka wrote: >> >> >> Niclas Zeising writes: >> >>> On 2020-04-27 08:03, Malcolm Matalka wrote: I saw that there was another thread on this and I wanted to throw my experience in: my mouse was sluggish and tap-to-click did not work. I set the evdev mask back to 3 and it worked. I am on a Dell XPS 13. >>> >>> Hi! >>> Is this on CURRENT? When using X? >>> Can you verify that you have xf86-input-libinput installed? >>> You can change sensitivity and enable tap to click using xinput. >>> Regards >> >> Yes this is current, and I'm on commit 360355. Yes I do have it >> installed. And yes I am on X. >> >> The situation I was in this morning after installing the new kernel was >> things that previously worked no longer worked so I did the shortest >> path I could find to get them working, which was modifying this evdev. >> >> Is there a document on how one is supposed to configure their system in >> X? I have never used xinput, instead I have configured my trackpad >> through sysctl. I'm happy to do it the way that is considered correct >> but I've sort of pieced together how to get my system setup. >> > > First off, do you have any local xorg conf? That's generally not needed any > more. No I don't. I just did a bunch of sysctls to configure the mouse (it was very sensitive to touch such that if my palm grazed the trackpad it became a click). > For xinput, I suggest start with the manual. > Regards ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
On 2020-04-27 11:29, Michael Gmelin wrote: On Mon, 27 Apr 2020 08:28:50 + "Poul-Henning Kamp" wrote: In message <65670198-e725-5b66-646c-5b147c943...@daemonic.se>, Niclas Zeising writes: With my touchpad, ctrl left click and ctrl right click opens two different menus in xterm, main menu and vt font menu, respectively. ctrl-middle should open "VT Options" I could reproduce this on my laptop and found the fix. The problem is, that the middle mouse button only generates a key press/key release event pair once its released (can be seen using xev and `libinput debug-events'). This is caused by the trackpoint driver using one-button scrolling by default (that is, you can hold the middle mouse button and move the trackpoint - even though this didn't work for me). You can disable on-button scrolling using xinput, e.g. xinput set-prop 'TPPS/2 IBM TrackPoint' \ 'libinput Scroll Method Enabled' 0 0 0 After this, Ctrl+middle works as expected in xterm. Note: Check `xinput' output to get the correct device name for your trackpoint (you can also use its numeric identifier, but the name is supposed to be more stable). Nice catch! I tried looking at xev myself, but apparently, I didn't look closely enough. Now when I know what to look for, I see it clearly. Thanks for your help! Regards -- Niclas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
On Mon, 27 Apr 2020 08:28:50 + "Poul-Henning Kamp" wrote: > > In message <65670198-e725-5b66-646c-5b147c943...@daemonic.se>, Niclas > Zeising writes: > > >With my touchpad, ctrl left click and ctrl right click opens two > >different menus in xterm, main menu and vt font menu, respectively. > > ctrl-middle should open "VT Options" > I could reproduce this on my laptop and found the fix. The problem is, that the middle mouse button only generates a key press/key release event pair once its released (can be seen using xev and `libinput debug-events'). This is caused by the trackpoint driver using one-button scrolling by default (that is, you can hold the middle mouse button and move the trackpoint - even though this didn't work for me). You can disable on-button scrolling using xinput, e.g. xinput set-prop 'TPPS/2 IBM TrackPoint' \ 'libinput Scroll Method Enabled' 0 0 0 After this, Ctrl+middle works as expected in xterm. Note: Check `xinput' output to get the correct device name for your trackpoint (you can also use its numeric identifier, but the name is supposed to be more stable). Cheers, Michael p.s. I also learned that using the trackpoint and the trackpad in parallel (and thus having buttons) works okay now - it didn't when I configured that laptop two years ago - \o/ -- Michael Gmelin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
## Niclas Zeising (zeising+free...@daemonic.se): > This could be an upstream issue. I did a quick test on a linux system I > had close by, and ctrl+middle click doesn't open a menu there either. FWIW on this FreeBSD desktop (12.1) and xterm-353, all three menus work with an external pointing device (this is not a mobile unit, so no "internal" device available). Regards, Christoph -- Spare Space ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
> On 27. Apr 2020, at 10:43, Niclas Zeising wrote: > > On 2020-04-27 10:28, Poul-Henning Kamp wrote: >> >> In message <65670198-e725-5b66-646c-5b147c943...@daemonic.se>, Niclas >> Zeising writes: >>> With my touchpad, ctrl left click and ctrl right click opens two >>> different menus in xterm, main menu and vt font menu, respectively. >> ctrl-middle should open "VT Options" > > This could be an upstream issue. I did a quick test on a linux system I had > close by, and ctrl+middle click doesn't open a menu there either. I’ll look into this later on mine. Besides pasting, this menu is my main use of the middle mouse button. Related question: I usually have the trackpoint disabled and therefore the physical mouse buttons don’t work. I would like to map some modifier+left mouse click to be middle mouse, but I couldn’t really figure out how to do it. Ideally I would like to be able to press ctrl+somemodifier+leftclick to get and operate that menu (and somemodifier+leftclick to paste). -m > Regards > -- > Niclas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
On 2020-04-27 10:28, Poul-Henning Kamp wrote: In message <65670198-e725-5b66-646c-5b147c943...@daemonic.se>, Niclas Zeising writes: With my touchpad, ctrl left click and ctrl right click opens two different menus in xterm, main menu and vt font menu, respectively. ctrl-middle should open "VT Options" This could be an upstream issue. I did a quick test on a linux system I had close by, and ctrl+middle click doesn't open a menu there either. Regards -- Niclas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
On 2020-04-27 10:14, Malcolm Matalka wrote: Niclas Zeising writes: On 2020-04-27 08:03, Malcolm Matalka wrote: I saw that there was another thread on this and I wanted to throw my experience in: my mouse was sluggish and tap-to-click did not work. I set the evdev mask back to 3 and it worked. I am on a Dell XPS 13. Hi! Is this on CURRENT? When using X? Can you verify that you have xf86-input-libinput installed? You can change sensitivity and enable tap to click using xinput. Regards Yes this is current, and I'm on commit 360355. Yes I do have it installed. And yes I am on X. The situation I was in this morning after installing the new kernel was things that previously worked no longer worked so I did the shortest path I could find to get them working, which was modifying this evdev. Is there a document on how one is supposed to configure their system in X? I have never used xinput, instead I have configured my trackpad through sysctl. I'm happy to do it the way that is considered correct but I've sort of pieced together how to get my system setup. First off, do you have any local xorg conf? That's generally not needed any more. For xinput, I suggest start with the manual. Regards -- Niclas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
In message <65670198-e725-5b66-646c-5b147c943...@daemonic.se>, Niclas Zeising writes: >With my touchpad, ctrl left click and ctrl right click opens two >different menus in xterm, main menu and vt font menu, respectively. ctrl-middle should open "VT Options" -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
Niclas Zeising writes: > On 2020-04-27 08:03, Malcolm Matalka wrote: >> I saw that there was another thread on this and I wanted to throw my >> experience in: my mouse was sluggish and tap-to-click did not work. I >> set the evdev mask back to 3 and it worked. >> >> I am on a Dell XPS 13. > > Hi! > Is this on CURRENT? When using X? > Can you verify that you have xf86-input-libinput installed? > You can change sensitivity and enable tap to click using xinput. > Regards Yes this is current, and I'm on commit 360355. Yes I do have it installed. And yes I am on X. The situation I was in this morning after installing the new kernel was things that previously worked no longer worked so I did the shortest path I could find to get them working, which was modifying this evdev. Is there a document on how one is supposed to configure their system in X? I have never used xinput, instead I have configured my trackpad through sysctl. I'm happy to do it the way that is considered correct but I've sort of pieced together how to get my system setup. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
On 2020-04-27 09:26, Poul-Henning Kamp wrote: In message <7549a5dd-3edc-4efd-bc0b-4d67232b4...@grem.de>, Michael Gmelin writes: In my case, with the default sysctl kern.evdev.rcpt_mask=12 CTRL + middle button would not activate the menu in xterm. Are you using the trackpoint? No, the touchpad. Did you set the trackpoint sysctl? (hw.psm.trackpoint_support=1) That seems to default to one ? It's the default on current and stable, but not any release (yet). With my touchpad, ctrl left click and ctrl right click opens two different menus in xterm, main menu and vt font menu, respectively. Regards -- Niclas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
> On 27. Apr 2020, at 09:26, Poul-Henning Kamp wrote: > > > In message <7549a5dd-3edc-4efd-bc0b-4d67232b4...@grem.de>, Michael Gmelin > writes: > >>> In my case, with the default >>> >>> sysctl kern.evdev.rcpt_mask=12 >>> >>> CTRL + middle button would not activate the menu in xterm. >>> >> >> Are you using the trackpoint? > > No, the touchpad. > >> Did you set the trackpoint sysctl? >> (hw.psm.trackpoint_support=1) > > That seems to default to one ? > I thought it wasn’t. I’m on a t470s, but I have the trackpoint disabled (and therefore the physical mouse buttons next to the touchpad don’t work). You could try running a little script I wrote to check your setup, it’s described here (it‘s not perfect, but might help): https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245800#c3 Best, Michael > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > p...@freebsd.org | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
In message <7549a5dd-3edc-4efd-bc0b-4d67232b4...@grem.de>, Michael Gmelin writes: >> In my case, with the default >> >>sysctl kern.evdev.rcpt_mask=12 >> >> CTRL + middle button would not activate the menu in xterm. >> > >Are you using the trackpoint? No, the touchpad. >Did you set the trackpoint sysctl? >(hw.psm.trackpoint_support=1) That seems to default to one ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
> On 27. Apr 2020, at 08:55, Poul-Henning Kamp wrote: > > > In message <6dfad31c-68f2-c38f-28ac-0696e73b4...@daemonic.se>, Niclas Zeising > writes: >>> On 2020-04-27 08:03, Malcolm Matalka wrote: >>> I saw that there was another thread on this and I wanted to throw my >>> experience in: my mouse was sluggish and tap-to-click did not work. I >>> set the evdev mask back to 3 and it worked. >>> >>> I am on a Dell XPS 13. >> >> Hi! >> Is this on CURRENT? When using X? >> Can you verify that you have xf86-input-libinput installed? > > In my case yes, this is CURRENt and I have xf86-input-libinput-0.29.0 > > In my case, with the default > >sysctl kern.evdev.rcpt_mask=12 > > CTRL + middle button would not activate the menu in xterm. > Are you using the trackpoint? Did you set the trackpoint sysctl? (hw.psm.trackpoint_support=1) Cheers, Michael > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > p...@freebsd.org | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
In message <6dfad31c-68f2-c38f-28ac-0696e73b4...@daemonic.se>, Niclas Zeising writes: >On 2020-04-27 08:03, Malcolm Matalka wrote: >> I saw that there was another thread on this and I wanted to throw my >> experience in: my mouse was sluggish and tap-to-click did not work. I >> set the evdev mask back to 3 and it worked. >> >> I am on a Dell XPS 13. > >Hi! >Is this on CURRENT? When using X? >Can you verify that you have xf86-input-libinput installed? In my case yes, this is CURRENt and I have xf86-input-libinput-0.29.0 In my case, with the default sysctl kern.evdev.rcpt_mask=12 CTRL + middle button would not activate the menu in xterm. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
On 2020-04-27 08:03, Malcolm Matalka wrote: I saw that there was another thread on this and I wanted to throw my experience in: my mouse was sluggish and tap-to-click did not work. I set the evdev mask back to 3 and it worked. I am on a Dell XPS 13. Hi! Is this on CURRENT? When using X? Can you verify that you have xf86-input-libinput installed? You can change sensitivity and enable tap to click using xinput. Regards -- Niclas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Weird mouse behaviour
In message <86imhlv518@gmail.com>, Malcolm Matalka writes: >I saw that there was another thread on this and I wanted to throw my >experience in: my mouse was sluggish and tap-to-click did not work. I >set the evdev mask back to 3 and it worked. Thanks! That helped a lot with my sanity on my T480 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
