Bug 238491 - x11-drivers/xf86-input-mouse: avoid the need of moused if using a touchpad
Summary: x11-drivers/xf86-input-mouse: avoid the need of moused if using a touchpad
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-x11 (Nobody)
Depends on:
Reported: 2019-06-11 09:27 UTC by Lorenzo Salvadore
Modified: 2020-02-25 10:51 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (x11)

xf86-input-mouse: no moused required (439 bytes, patch)
2019-06-11 09:28 UTC, Lorenzo Salvadore
salvadore: maintainer-approval? (x11)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Lorenzo Salvadore freebsd_committer 2019-06-11 09:27:47 UTC
Recently review D20507 was commited: it enables touchpad by default.

As it can be read in the review, using the touchpad at the moment requires moused to be started before Xorg, at least for some users such as myself.

wulf proposed a patch to fix the problem, so that now moused is not required anymore: I propose to commit this patch. (wulf also proposes other ideas, but this one seems to be the easiest to implement, it avoids running the process moused and showing the mouse pointer in consoles.)

The attached patch is exactly what wulf suggested. In the review it was said that it is unlikely that it could bring any side effect to anyone, however, if someone has some concern about it, I can modify it so that the patch is applied only if a given option is enabled or disabled.

I tested successfully on 12-STABLE r348603 (I applied manually the patch that enables touchpad by default; I believe this is only commited in CURRENT at least for now).
Comment 1 Lorenzo Salvadore freebsd_committer 2019-06-11 09:28:45 UTC
Created attachment 204980 [details]
xf86-input-mouse: no moused required
Comment 2 Lorenzo Salvadore freebsd_committer 2020-02-25 10:51:01 UTC
After r526589, this patch is not needed any more.