https://bugs.kde.org/show_bug.cgi?id=453612
kfjel...@hotmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|DUPLICATE |---
Ever confirmed|0 |1
Status|RESOLVED |REOPENED
--- Comment #4 from kfjel...@hotmail.com ---
This bug isn't a duplicate of that one, and has nothing to do with window
geometry. It wasn't due to libinput either. Why does "tap-to-drag" have to be
automatically enabled when you select "tap-to-click" anyways? It's another
function entirely, isn't it? Perhaps it should be opt in in the first place?
(especially if it can, in some/many cases, create the issue described)
I beg you to do some more testing. I know the solution to this issue in my case
so it doesn't matter to me personally, but it was incredibly frustrating for
quite a long time, every time I tested KDE on Wayland. I don't want anyone else
to experience that same trouble. Please if you have the option and time to do
more extensive testing.
I have no idea why it is not reproducible, I can reproduce 100%. I can't think
that hardware issues should cause this. But I am using Acer machines, and I am
using Acer WMI, and that could potentially have something to say? That's the
only potential "difference" I can think of, if this has been tested in general,
and with Elan, and in particular if it was tested on Slackware/Mageia.
Have a nice day!
(I condsider this fully closed from my side now, I've done what I can, so I'm
not going to continue this unless someone have questions and answers would be
really helpful in reproducing it)
--
You are receiving this mail because:
You are watching all bug changes.
