Menu->Setup->Mouse->Adjust doesn't work in Dunfell

[FeodorF]

I had to replace my old mouse with a new one otherwise I would have never noticed this problem.

As soon as you setup the new mouse parameters for acceleration and threshold you'll end up with a mismatch in /root/.xset.sh and /tmp/xerrs.log . The failing .xset.sh file reads:

'xset m /10 2 c off r rate 500 6 s 600 600 s blank s expose'

This problem doesn't exist in Quirky64-8.5 as well as EasyOS Buster 2.3.3 -> . The .xset.sh file reads:

'xset m 10/10 2 c off r rate 660 25 s 600 600 s blank s expose'

Adjusting the failing line doesn't help at all.

[FeodorF]

Good news over here - it is not Dunfell only related.
Fossapup64-9.5 has the same problem.
Guess it is 'xset' version related. The failing one is 1.2.4 for right now.
I'll keep digging into it.

[FeodorF]

@BarryK

I have downloaded xset from the source and compiled it with debug info enabled.

https://xorg.freedesktop.org/archive/in ... .4.tar.bz2

Code: Select all

Testing procedure:

. delete xset in /usr/bin
. copy the new xset to /usr/local/bin
. open Menu->Setup->Mouse->Adjust and click OK (values are kept at 2.0 and 4)
. /root/.xset.sh is being created (a faulty one) 'xset m /10 4 c off r rate 660 25 s 600 600 s blank s expose'

Code: Select all

Debug info from /tmp/xerrs.log:

dc: can't open '2': No such file or directory
KEYBOARDAUTO="true"
KEYBOARDDELAY="660"
KEYBOARDRATE="25"
KEYBOARDVOL="0"
MOUSEACCEL="2.0"
MOUSETHRESHOLD="4"
SCREENSAVERBLANKING="true"
SCREENSAVERCYCLE="600"
SCREENSAVERDELAY="600"
SCREENSAVEREXPOSURES="true"
SCREENSAVERFLAG="true"
EXIT="save settings"
dc: can't open '2.0': No such file or directory
xset:  unknown option /10

If I change /root/.xset.sh to: 'xset m 10/10 2 c off r rate 660 25 s 600 600 s blank s expose' and reboot xset will be able to read this file correctly.

Code: Select all

Entering 'xset q' in sakura shows:
Pointer Control:
  acceleration:  10/10    threshold:  2

at the same time

Menu->Setup->Mouse->Adjust fails by showing: (while '.x.set.sh' is still unchanged at 'm 10/10 2 ...')
  acceleration:   2.0     threshold:  2

'pupx' looks faulty.

[BarryK]

Preoccupied right now, just glancing at this thread...

Ah, dc, that would be the problem.

The busybox dc applet changed awhile back, has to be run with different commandline. I posted to my blog about that. Here it is:

https://bkhome.org/news/202007/busybox- ... -1320.html