- This topic has 18 replies, 5 voices, and was last updated Apr 27-6:22 am by Xunzi_23.
-
Posts
-
Dr.X
Searching the forum turned up nothing — but perhaps I was not using the correct search terms. At any rate, I did the following to get my mouse settings changed to left-hand usage by adding the following line to the file “startup” found in the user’s home “.icewm” directory:
xmodmap -e “pointer = 3 2 1 4 5”
This is for a wheel mouse and can be modified for other mice if needed.
- This topic was modified 5 months, 2 weeks ago by Dr.X.
antiX 23.2 / CPU: Intel Atom 330 @ 1.60GHz / RAM: 4 GiB / Graphics: NVIDIA C79 [ION]
Robin
Searching the forum turned up nothing
Didn’t work the antiX PDM from antiX Control Centre, section Hardware for you? It has a left hand mouse option included. (to make the setting permanent, don’t forget to tick the respective checkbox in its GUI before applying the changes.)
Windows is like a submarine. Open a window and serious problems will start.
the antiX PDM from antiX Control Centre, section Hardware (…)? It has a left hand mouse option included.
Of course, that was the first place I attempted — but it seems to be broken. It recognizes my ‘Pointing Device to be configured:’ correctly as a Logitech M185. No other option is available. Then I clicked on the ‘OK’ button and in the resulting window (antiX pointing device manager) the first 3 options (‘Device status’, ‘Reverse Scroll’ and ‘Left handed buttons’) are all dead (i.e. not active, and do not show any values).
This would be a convenient and logical tool — if it would work.
antiX 23.2 / CPU: Intel Atom 330 @ 1.60GHz / RAM: 4 GiB / Graphics: NVIDIA C79 [ION]
sybok
@dr-x: Which version of antiX do you use? Did you search packages for additional drivers and or control programs that may not be included in your antiX version?
E.g. my search (terminal command ‘apt-cache search logitech’) show ‘logiops’ might be of interest.Xunzi_23
Logitech M185, worst mouse I ever owned.
Anyway please try sudo apt install solaar, that gives you a graphical setup
that should work.my present travel mouse: TECKNET Model MS015
Does not eat batterys and has survived several falls, it took one fall to
kill the logitech rodent.my search (terminal command ‘apt-cache search logitech’) show ‘logiops’ might be of interest.
Thank you for your time and effort, @sybok — unfortunately logiops seems to not include support for the M185 mouse. My solution (given in my original post) works. I guess, as noted by many others, that the Logitech mice are not to be recommended …
antiX 23.2 / CPU: Intel Atom 330 @ 1.60GHz / RAM: 4 GiB / Graphics: NVIDIA C79 [ION]
try sudo apt install solaar
Thank you also for your time and effort, @Xunzi_23 — I did the install of solaar and it reports:
“Found a Logitech Receiver (/dev/hidraw2), but did not have permission to open it.
If you’ve just installed Solaar, try removing the receiver and plugging it back in.”But that did not work either. Because my initial solution (given in my original post) works to my satisfaction, I guess I will uninstall solaar and stop trying to find other solutions. I hope that my solution can help someone who also has a similar problem with a Logitech M185 mouse.
- This reply was modified 5 months, 2 weeks ago by Dr.X.
antiX 23.2 / CPU: Intel Atom 330 @ 1.60GHz / RAM: 4 GiB / Graphics: NVIDIA C79 [ION]
sybok
@dr-x: My bad, I did not see ‘[SOLVED]’ in the topic title and I got confused about a (proper) solution or at least a workaround not being found yet.
Please edit your 1st post, if possible, and either prepend or append ‘[SOLVED]’ to it to mark as solved.
bci
As an aside to this thread, I’d add some two cents:
I use a Bluetooth mouse with my current antiX (still on 23 right now). It’s a Logitech M240. As Robin pointed out, the Hardware settings in the Control Centre work just fine for configuring left-handedness. However, sometimes I find the bluetooth connection on desktop startup wonky and unreliable, as if the setting doesn’t kick in on time, and I have to then enable left-handedness manually. In these cases, I like the xinput program (available via sudo apt install xinput).
So in other words I have this command saved in my shell history:
xinput set-prop “LOGI M240 Mouse” “libinput Left Handed Enabled” “1”
I actually took this from the config automatically generated by the relevant antiX utility.
– Brandon
I did not see ‘[SOLVED]’ in the topic title
Oops !! My bad !
It’s been a long time (about three years) since I last posted to any linux distro forums and I completely forgot about doing that !! And I used to be a co-admin for one linux distro forum ! Totally embarrassing !!!
- This reply was modified 5 months, 2 weeks ago by Dr.X.
antiX 23.2 / CPU: Intel Atom 330 @ 1.60GHz / RAM: 4 GiB / Graphics: NVIDIA C79 [ION]
@dr-x Even when resolved by a workaround, the underlying issue is still present in antiX PDM from Control Centre. While checking I ran into the very same behaviour after disabling the internal touchpad of my notebook in the GUI, which works initially. But once the device is inactive, antiX PDM greys out the fields for re-enabling this device. Single way to resume is to manually enter the xinput command for activating it on console, after which the fields in antiX PDM no longer are greyed out when reopening, being functional for another deactivation… This circus can be reproduced perpetual.
I’m not sure when this issue has been introduced, and by what system upgrade, but the behaviour of xinput must have changed, since this tool initially had worked reliable.
So what you have raised here is actually a bug report for antiX PDM in antiX 23 and 26, not resolved still. (While functionally resolved by a workaround).
Since @PPC, the original author of this antiX script, isn’t around currently, I’ll see what I can do.
For a true fix of antiX PDM, could you please try the following?
Hotfix:Edit line 151 in /usr/local/bin/antiX-pdm from
150 #remove empty lines: 151 sed -i '/^$/d' /tmp/check-ds-mouseso it reads ↓↓↓
150 #remove empty lines, and also additional invald characters from the names: 151 sed -i '/^$/d;s/^[∼⎡⎜⎣↳]*[[:space:]]*\(..*\)/\1/' /tmp/check-ds-mouseFor me this fix works, but I’d need to know whether this works for your device / other devices as well, or whether it breaks something for you or whether some additional special characters are to be excluded. (Maybe switching to using the ID-# instead of the ID-Name could be more robust. But this adds another layer of complexity to this simple script, having to sync then the internally used ID-# to the ID-Name to be displayed in the GUI menus…, so let’s stick to how it was designed originally.)
Additional consideration: Maybe the output of xinput is meanwhile translated, so the expected snippets (e.g. »Device Enabled«, »libinput Natural Scrolling Enabled«, …) are no longer guaranteed. Will see whether an additional preceeding LANG=C in the respective commands is necessary. Currently for me this seems still untranslated, so no need for immediate action.
Could you please provide the output of:
$ xinput list
and
$ LANG=C xinput list
to learn what additional special characters might show up in your output / language.
(Please wrap it into code tags found at top of the input field here, so the forum won’t mangle/replace any special characters in the lines nor break the line structure.)Windows is like a submarine. Open a window and serious problems will start.
Hello @Robin
Here are the requested outputs:
$ xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Logitech M185 id=9 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Power Button id=7 [slave keyboard (3)] ↳ Dell Dell USB Keyboard id=8 [slave keyboard (3)] ↳ Logitech M185 id=10 [slave keyboard (3)]and:
$ LANG=C xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Logitech M185 id=9 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Power Button id=7 [slave keyboard (3)] ↳ Dell Dell USB Keyboard id=8 [slave keyboard (3)] ↳ Logitech M185 id=10 [slave keyboard (3)]antiX 23.2 / CPU: Intel Atom 330 @ 1.60GHz / RAM: 4 GiB / Graphics: NVIDIA C79 [ION]
For a true fix of antiX PDM, could you please try the following?
Hotfix:Edit line 151 in /usr/local/bin/antiX-pdm from (…)
OK, I just did this and now opening the antiX PDM shows all fields as before the line change (i.e. the little arrow heads in the selection boxes are black). However, the only fields that respond to my mouse clicks are still these: “Acceleration”, “Speed” and “Slow double click”
antiX 23.2 / CPU: Intel Atom 330 @ 1.60GHz / RAM: 4 GiB / Graphics: NVIDIA C79 [ION]
antiX PDM shows all fields as before the line change
Many thanks @dr-x !
This means I have goofed the hotfix, sorry. My original sed regex:
150 #remove empty lines, and also additional invald characters from the names: 151 sed -i '/^$/d;s/^[∼⎡⎜⎣↳]*[[:space:]]*\(..*\)/\1/' /tmp/check-ds-mouseThis can’t still work, since the line where your mouse (and other devices) reside in have additional heading blanks, and another set of these additional prettyprint stuff in it, while my sed regex looks only for these characters at line start. Seems xinput doesn’t know a clean and stable output mode for scripting which could be activated by a command lne option, so we’ll have to follow again and again their design changes of these output lines.
Please change the line once more. Make it read:
150 #remove empty lines, and also additional invald characters from the names: 151 sed -i '/^$/d;s/^[[:space:]]*[∼⎡⎜⎣↳]*[[:space:]]*[∼⎡⎜⎣↳]*[[:space:]]*\(..*\)/\1/' /tmp/check-ds-mouse(note: the end of the second line may be hidden by the forum, so scroll to the right end when copying, to get actually the full line)
and recheck please. Should work now for you also.
If not, please post the output of the command:
$ xinput list-props 'Logitech M185'
for further diagnois.Thanks for all your patience!
Windows is like a submarine. Open a window and serious problems will start.
Please change the line once more.
Sorry, @Robin — the new version performs just like the old version => it also does not work.
please post the output of the command:
$ xinput list-props 'Logitech M185'The results:
$ xinput list-props 'Logitech M185' Warning: There are multiple devices matching 'Logitech M185'. To ensure the correct one is selected, please use the device ID, or prefix the device name with 'pointer:' or 'keyboard:' as appropriate. unable to find device Logitech M185and:
$ xinput list-props 'pointer Logitech M185' unable to find device pointer Logitech M185antiX 23.2 / CPU: Intel Atom 330 @ 1.60GHz / RAM: 4 GiB / Graphics: NVIDIA C79 [ION]
- You must be logged in to reply to this topic.