Today i found an unexpected problem with missing mouse settings in my Tower’s real KDE Stable, & both my KDE VMs in Tower [one Stable, one Testing]. In contrast, Lappy’s KDE Stable has the correct settings. I am referring to KDE System Settings - Hardware - Input Devices - Mouse.
This describes what should be present… https://docs.kde.org/trunk5/en/kde-workspace/kcontrol/mouse/index.html … three tabs; General, Advanced and Keyboard Navigation. They are present & functional in Lappy:
Puzzlingly all three installations in Tower as listed above, have a completely different & much more restricted suite:
Initially i wondered if this was yet another hallmark of the impending Wayland code simplification of xf86-input-libinput over xf86-input-synaptics, but this seems untrue when i checked what is currently installed. Compare the above pair of pics; the same packages are present in Lappy [good] & Tower+VMs [bad].
When i researched this in the Manjaro forum, i found these;
a. Mouse wheel only scrolls half a line
sudo pacman -Rns xf86-input-libinput sudo pacman -S xf86-input-synaptics reboot
…but when i tried the first command with Konsole in one of those VMs [which i carefully Snapshotted first as precaution] it refused to proceed:
~ >>> sudo pacman -Rns xf86-input-libinput [sudo] password for kdemeoz: checking dependencies... error: failed to prepare transaction (could not satisfy dependencies) :: xorg-server: removing xf86-input-libinput breaks dependency 'xf86-input-libinput'
So after creating the VM snapshot i decided to force it with Pamac:
Post-reboot it was the disaster i expected; no graphical session available. Rolled back the snapshot.
b. Pad and mouse "no shared library" issue after today's - 19.06.2018 unstable update … but it did not seem to have a relevant solution for me.
c. Plasma 5.13.0 and KDE Framework 5.47 bugs … which also seemed to have no applicable solution for me. It referenced the preceding link.
A general DDG web search found this… https://www.youtube.com/watch?v=XzoOdIbWcj8 [watch only from 2’10"] … which is old [obsolete?], & in any event its “solution” of reverting to xf86-input-mouse is unproductive for me given that package is already installed in all my systems.
If it was not for the first link in this post, & Lappy’s physical corroboration of that, i’d be tempted to assume that 5.13.x had permanently removed this functionality, but clearly that is untrue. How Tower’s real & VM KDEs can so badly disagree with Lappy’s KDE, despite them all appearing to have the same relevant packages installed, confuses me. Is there another necessary package that i have not checked? Even if there is, it would be plain odd for it to have been omitted on all three of these independent installations.