I have Xubuntu 18.04 in a VM (virtualbox)
I noted that the mouse action, "double-click" did not work and after tweaking mouse configs, eventually got to almost something workable
I say "almost" because sometimes that may work on the titlebar but never for a selection--say of text--elsewhere
On a whim, I installed Ubuntu and Kubuntu in VMs and noted that same mouse behavior
On further research, it appears that Ubuntu have opted for "double-click" as the default file selection method
That's OK except it doesn't work--at least on this Logitech K400+--even though those distros recognized and listed the input device

SO... when Neon transitions to 18.04 LTS...
it will be with some trepidation on my part to see if this problem carries over into Neon
but to clarify... there are workarounds
but it's not that simple method of "double-click" that I'm accustomed to!

I have not seen any difference in mouse double click actions in my Kubuntu 18.04 PC, using either of my two mice (both logitech)
I imagine it may be a quirk of the VM - are the guest additions installed on the VM ? Xubuntu is not using wayland, is it?

claydoh wrote:I imagine it may be a quirk of the VM...

Yes... guest additions are always installed
and yes, I had considered that this was maybe a quirk of VM
EDIT: and no, Xubuntu was using xcb windowing

So last night, I went thru the toilsome schlep of backing up my Neon and then installing Xubuntu, then Ubuntu and eventually Kubuntu...
same result on each distro, as in the VMs previously!

The fact that so far I haven't seen this issue being reported elsewhere... seems that this problem is related to my hardware somehow
my next step is to get another keyboard/mouse... and see what happens!

EDIT: add Lubuntu... there's no double-click by default

abury wrote:... seems that this problem is related to my hardware somehow

Rubbish!
(I know, me critiquing my post... but it is so to make a point)
iF my keyboard has been working--since forever--and the only thing that has changed is the next Ubuntu version
then the implication is that this version, i.e. software is the problem, not the hardware... surely...

Now how to determine where the problem is?

Assuming you installed the 18.04 version of each, you for all intents and purposes have installed the same exact OS three times.

It may be a bug with your particular hardware, but as such this is sort of out of the scope of most of the people on this forum - an ubuntu specific one will probably have more users familiar at the hardware level, and maybe with yours in particular.


Buuuut .......having said that look at what I found:
https://bugs.launchpad.net/ubuntu/+sour ... ug/1762536
Reported upstream here:
https://bugs.freedesktop.org/show_bug.cgi?id=105974

and a little tidbit of relevance to another of your threads:
https://bugs.freedesktop.org/show_bug.cgi?id=105974#c3

So it is a bug upstream in libinput, any distro using that version will be affected by it. How quickly the fixed library gets applied to Ubuntu is the unknown.
I suggest going to the Launchpad bug, creating an account so you can log in and click the "does this bug affect me" option at the top of the page.

claydoh wrote:... but as such this is sort of out of the scope of most of the people on this forum...

A big thank you for your input; those urls were really helpful
I have a launchpad acct so I added myself to that affected bug list

I only installed Xubuntu and then Neon afterwards...
while in Xubuntu, technically all I did was make Live USBs of the other distros and tested them accordingly
which in turn led me--with your input--to this discovery of a kernel and libinput bugs

It seems this touchpad was filtered by some debouncing code; which is now fixed in upstream ubuntu (dailys) but the 18.04 LTS release still uses an old libinput version and a bug fix release has yet to occur; which brings me to my original post and its intent... "that when Neon transitions to 18.04 LTS..." :
that JR and his dev team are aware of this and would ensure that our next LTS version would include those Ubuntu daily fixes!

I'm pretty sure that if this was not done... that this particular forum would be inundated with similar posts re double-clicks

Here is the final resolution of this Ubuntu bug
Given that this is an unresolved Ubuntu bug, my options are:
(1) buy another keyboard
(2) use another KDE not based on Ubuntu

So... bye bye Neon!
This really was the best of Linux experiences!

You mean one not based on 16.04, don't you

claydoh wrote:You mean one not based on 16.04...)

I don't get your meaning...
Actually all Ubuntu releases up until and including 17.10 are okay
It's 18.04--and 18.10 as well--that have broken libinput somewhat
I get the drift from the Wayland guys (see that Ubuntu bug link above) that they are not happy with Ubuntu's quality control

When Neon gets on the 18.n release, it'll be interesting to see what bugs pop out the woodwork then
We've been sheltered by the 16.04 foundation...
At least up until now...

And to clarify--and compliment JR and the dev team--why there is no "bye bye Neon!"... on my part at least

I had previously filed a bug report for libinput and was content to see that updates eventually appeared in 18.10 that resolved my issues
So for now I'm okay with the team's evdev X11 driver solution... (at least until 18.04 catches up with those 18.10 fixes)
And with the latest 5.14 update... Plasma just makes it so much harder to work with other DEs let alone distro hop!