Bug 20021

Summary: kde desktop occasionally refuses to recognize trackpad clicks
Product: Mageia Reporter: w unruh <unruh>
Component: RPM PackagesAssignee: KDE maintainers <kde>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: marja11, maurice77
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: kd CVE:
Status comment:

Description w unruh 2016-12-24 10:18:15 CET
Description : I am working on various applications when the kde desktop will suddenly refuse to recognize all clicks. If I do alt-ctrl-F2 to get a console, and then alt-ctrl-F1 to get back to the kde desktop, clicks resume working as they should. I have now had this happen to me at least twice. (once is a fluke, twice indicates a bug).

Did I do something strange. I certainly do not remember doing so. the desktop just suddenly stopped accepting clicks.

Dell XPS13 9360 . Cauldron updated as of Dec 19. I tried left clicking on all many icons and nothing  happened. 
 right clicking on destop itself does nothing rather than bringing up 
desktop menu.It is as if all clicks are ignored.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Marja Van Waes 2016-12-24 10:52:48 CET

CC: (none) => marja11
Assignee: bugsquad => kde

Comment 1 w unruh 2016-12-24 20:43:08 CET
In addition at least twice the trackpad has gone completely dead (Ie no cursor movement either). In both cases it resolved itself in about 1 min. Whether it was what I did (Ie, trying to move it madly, clicking both with taps and clicks, go to console and back) or if it would have done it on its own I do not know. When you are in the middle of working and the mouse cursor disappears, waiting calmly is not my natural reaction. I Think this is related to the click bug, but cannot be sure.
Comment 2 w unruh 2017-01-01 22:57:49 CET
Again today, the mouse pointer froze. at-ctrl-F2, alt-ctrl-F1 did not unfreeze it.

Plugging in a usb mouse made botht he trackpad and the mouse work, but when I unplugged the usbmouse, the desktop often did not respond to clicks. If I clicked on some desktop icon, nothing would happen, but if I did AC-F2, AC-F1 suddenly that thing that I clicked on would open. Ie, the system would remember that I did click but did nothing with it, until I did the AC-F2, AC-F1 dance. 

Something is seriously wrong with the trackpad handling. 
(Dell xps13-9360 synclient

---------------
Report from /var/log/X11.0.log[    17.202] (**) DLL075B:01 06CB:76AF Touchpad: Applying InputClass "evdev touchpad catchall"
[    17.202] (**) DLL075B:01 06CB:76AF Touchpad: Applying InputClass "evdev touchscreen catchall"
[    17.202] (**) DLL075B:01 06CB:76AF Touchpad: Applying InputClass "libinput touchpad catchall"
[    17.202] (**) DLL075B:01 06CB:76AF Touchpad: Applying InputClass "libinput touchscreen catchall"
[    17.202] (**) DLL075B:01 06CB:76AF Touchpad: Applying InputClass "touchpad catchall"
[    17.202] (**) DLL075B:01 06CB:76AF Touchpad: Applying InputClass "Default clickpad buttons"
[    17.202] (II) LoadModule: "synaptics"
[    17.203] (II) Loading /usr/lib64/xorg/modules/input/synaptics_drv.so
[    17.203] (II) Module synaptics: vendor="X.Org Foundation"
[    17.203]    compiled for 1.19.0, module version = 1.9.0
[    17.203]    Module class: X.Org XInput Driver
[    17.203]    ABI class: X.Org XInput driver, version 24.1
[    17.203] (II) Using input driver 'synaptics' for 'DLL075B:01 06CB:76AF Touchpad'
[    17.203] (**) DLL075B:01 06CB:76AF Touchpad: always reports core events
[    17.203] (**) Option "Device" "/dev/input/event15"
[    17.222] (II) synaptics: DLL075B:01 06CB:76AF Touchpad: found clickpad property
[    17.222] (--) synaptics: DLL075B:01 06CB:76AF Touchpad: x-axis range 0 - 1216 (res 12)
[    17.222] (--) synaptics: DLL075B:01 06CB:76AF Touchpad: y-axis range 0 - 680 (res 12)
[    17.222] (II) synaptics: DLL075B:01 06CB:76AF Touchpad: device does not report pressure, will use touch data.
[    17.222] (II) synaptics: DLL075B:01 06CB:76AF Touchpad: device does not report finger width.
[    17.222] (--) synaptics: DLL075B:01 06CB:76AF Touchpad: buttons: left double triple
[    17.222] (--) synaptics: DLL075B:01 06CB:76AF Touchpad: Vendor 0x6cb Product 0x76af
[    17.222] (--) synaptics: DLL075B:01 06CB:76AF Touchpad: invalid pressure range.  defaulting to 0 - 255
[    17.222] (--) synaptics: DLL075B:01 06CB:76AF Touchpad: invalid finger width range.  defaulting to 0 - 15
[    17.222] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[    17.222] (--) synaptics: DLL075B:01 06CB:76AF Touchpad: touchpad found
[    17.222] (**) DLL075B:01 06CB:76AF Touchpad: always reports core events
[    17.238] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-8/i2c-DLL075B:01/0018:06CB:76AF.0001/input/input16/event15"
[    17.238] (II) XINPUT: Adding extended input device "DLL075B:01 06CB:76AF Touchpad" (type: TOUCHPAD, id 11)
[    17.238] (**) synaptics: DLL075B:01 06CB:76AF Touchpad: (accel) MinSpeed is now constant deceleration 2.5[    17.238] (**) synaptics: DLL075B:01 06CB:76AF Touchpad: (accel) MaxSpeed is now 1.75
[    17.238] (**) synaptics: DLL075B:01 06CB:76AF Touchpad: (accel) AccelFactor is now 0.144
[    17.238] (**) DLL075B:01 06CB:76AF Touchpad: (accel) keeping acceleration scheme 1
[    17.238] (**) DLL075B:01 06CB:76AF Touchpad: (accel) acceleration profile 1
[    17.238] (**) DLL075B:01 06CB:76AF Touchpad: (accel) acceleration factor: 2.000
[    17.238] (**) DLL075B:01 06CB:76AF Touchpad: (accel) acceleration threshold: 4
[    17.238] (--) synaptics: DLL075B:01 06CB:76AF Touchpad: touchpad found
[    17.238] (II) config/udev: Adding input device DLL075B:01 06CB:76AF Touchpad (/dev/input/mouse0)
[    17.238] (II) No input driver specified, ignoring this device.
[    17.238] (II) This device may have been added with another device file.
[    17.239] (II) config/udev: Adding input device Intel Virtual Button driver (/dev/input/event8)
[    17.239] (**) Intel Virtual Button driver: Applying InputClass "evdev keyboard catchall"
[    17.239] (**) Intel Virtual Button driver: Applying InputClass "libinput keyboard catchall"
[    17.239] (**) Intel Virtual Button driver: Applying InputClass "system-keyboard"
[    17.239] (II) Using input driver 'libinput' for 'Intel Virtual Button driver'
[    17.239] (**) Intel Virtual Button driver: always reports core events
[    17.239] (**) Option "Device" "/dev/input/event8"
[    17.239] (**) Option "_source" "server/udev"
[    17.239] (II) input device 'Intel Virtual Button driver', /dev/input/event8 is tagged by udev as: Keyboard
[    17.239] (II) input device 'Intel Virtual Button driver', /dev/input/event8 is a keyboard
[    17.250] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/INT33D6:00/input/input9/event8"
[    17.250] (II) XINPUT: Adding extended input device "Intel Virtual Button driver" (type: KEYBOARD, id 12)
[    17.250] (**) Option "xkb_model" "pc105"
[    17.250] (**) Option "xkb_layout" "us"
[    17.250] (**) Option "xkb_options" "compose:rwin"
[    17.250] (II) input device 'Intel Virtual Button driver', /dev/input/event8 is tagged by udev as: Keyboard

-------------------------------------------
Comment 3 w unruh 2017-01-03 05:15:44 CET
Note that windows on the Desktop (KDE Plasm5) do respond to clicks. It is the icons on the desktop that do not. So it is not some generic trackpad issue. It is very specific to the Desktop.

And sometimes the trackpad pointer freezes. At least once it seemed to think there was already a finger on the trackpad (there wasn't) since moving my real finger scrolled the screen the cursor happened to be over when the pointer froze.
Comment 4 w unruh 2017-01-05 15:57:57 CET
Note-- an additional symptom. Usually when the trackpad pointer passes over an icon, that icon is "selected (greyed border surrounds the icon)"  When the above "non-responsiveness to clicks on the desktop", that icon selection also does not happen. Ie, there is no reponse of the desktop to having the cursor go over the icon. However as I said, if I click on the icon (noreponse) and then to AC-F2 AC-F1 that program associated with the icon I clicked on starts up. Ie, the touchpad actions seem to be being blocked, and are released on the cycling through the consoles.
Comment 5 w unruh 2017-01-09 10:09:50 CET
Well, its been acouple of days using libinput instead of synamptics as the x11-driver-input  and I have not seen this symptom reappear yet. 
synaptics was the default touchpad driver. Should this now be changed to libinput?
Of course I have tested only with one touchpad (Dell xps13 9360 version). But certainly people should be alerted to the possibility.
Comment 6 w unruh 2017-01-10 10:44:44 CET
And of course, using libinput the problem has sort of reappeared (much less severely) Ocasionally touchpad taps do not work, a number of times in succession. Ie it is not just a single tap that is missed. Clicking onthe lower part of the trackpad still works as a right button, but a single tap suddenly does not work. Then shortly thereafter it works again. ie, something seems to be blocking the touchpad taps as clicks for a short while. 
Note that though now the taps do not work on the programs they will sometimes still work on the desktop.
Comment 7 w unruh 2017-02-03 15:01:35 CET
*** Bug 20240 has been marked as a duplicate of this bug. ***
Comment 8 w unruh 2017-02-11 09:12:19 CET
It seems to be getting worse. About 1/4 of tap to click fail (lower left clicking still works). At least once the trackpad completely froze--no cursor movement no clicks, no tap to click. Ie, trackpad completely disabled. I had to reboot to  get back the trackpad. 
I have a-c-y setup to  disable the trackpod and a-c-t to enable it. typing a-c-t did nothing in that situation. a-c-bksp got me out of X but the trackpad was still disabled. Only reboot worked.

Something is flakey with the trackpad driver.
Comment 9 w unruh 2017-08-14 16:06:45 CEST
I have now been using libinput for about 6 months. It is really not up to the task of being a trackpad driver. It is far too sensitive and with the large trackpad on the Dell XPS13 I use the cursor is always being tapped (causing the cursor to jump all over the page I am typing leading to mistakes or destructions of commands I am trying to type in) or double tapped (causing random stuff to dumped into the cut and paste buffer and then being dumped onto where I am trying to type.) While synaptics had perhaps too many options, libinput has none, and the default is far from flawless or even very useable.
Comment 10 Maurice Batey 2018-08-29 11:49:46 CEST
Having never seen the problem of desktop icons that are invisible to the mouse/trackpad pointer, that's exacly my problem here on fully-updated Plasma 5
Mageia6.1 on HP450 Probook.
  The problem manifested itself after the latest s/w update just before leaving on a trip.

All desktop icons appear to be invisible w.r.t. selection by mouse and trackpad pointer, though no problem with icons in Panel, so can still get work done.
  Even if create new desktop icon, it is then unselectable (so cannot be removed!)  

  Clue: The other user on the system does not have the problem...

So question: What $HOME setting can make desktop icons unselectable?

[When I get back to base I will try a restore of both / and /home/user.]

CC: (none) => maurice

Comment 11 Aurelien Oudelet 2021-05-17 01:15:43 CEST
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Resolution: (none) => OLD
Status: NEW => RESOLVED