http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c2 --- Comment #2 from Rihards Olups <richlv@nakts.net> --- Yes, all further clicks went to that first location. For example, if I click on klauncher first, all further clicks would open that menu. Same with taskbar or any other place on the desktop. Mouse cursor was moving around as usual, and mouseover actions also worked (tooltips appeared etc). I didn't mean to suggest commenting out that section as a generic solution, just as something that helped me and could point (ha) at the cause. Before that, two packages were uninstalled, but this made no difference: * xf86-input-mouse * xf86-input-libinput -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c4 --- Comment #4 from Rihards Olups <richlv@nakts.net> --- Logfile says: [ 1622.008] (II) Using input driver 'evdev' for 'VirtualBox mouse integration' Please let me know if full logfile is still needed. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c6 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Larry.Finger@gmail.com Flags| |needinfo?(Larry.Finger@gmai | |l.com) --- Comment #6 from Stefan Dirsch <sndirsch@suse.com> --- Larry, as bugowner/maintainer of virtualbox. Can you easily reproduce this issue when installing TW in a virtualbox VM? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c8 Achim Gratz <Stromeko@NexGo.DE> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Stromeko@NexGo.DE --- Comment #8 from Achim Gratz <Stromeko@NexGo.DE> --- This can not be related to VirtualBox (although that might be a good way to reproduce the bug), I have the exact same problem on bare iron (a Dell T20). Going back to kernel version 4.16.12-3 fixes the problem, so it can't be a problem in libinput alone, either. The Xorg log on the working configuration shows this: [ 17.501] (II) event0 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard [ 17.501] (II) event0 - AT Translated Set 2 keyboard: device is a keyboard [ 17.502] (II) config/udev: Adding input device ImExPS/2 Logitech Explorer Mouse (/dev/input/event1) [ 17.502] (**) ImExPS/2 Logitech Explorer Mouse: Applying InputClass "evdev pointer catchall" [ 17.502] (**) ImExPS/2 Logitech Explorer Mouse: Applying InputClass "evdev pointer catchall" [ 17.502] (**) ImExPS/2 Logitech Explorer Mouse: Applying InputClass "libinput pointer catchall" [ 17.502] (II) Using input driver 'libinput' for 'ImExPS/2 Logitech Explorer Mouse' [ 17.502] (**) ImExPS/2 Logitech Explorer Mouse: always reports core events [ 17.502] (**) Option "Device" "/dev/input/event1" [ 17.502] (**) Option "_source" "server/udev" [ 17.503] (II) event1 - ImExPS/2 Logitech Explorer Mouse: is tagged by udev as: Mouse [ 17.503] (II) event1 - ImExPS/2 Logitech Explorer Mouse: device is a pointer [ 17.503] (II) event1 - ImExPS/2 Logitech Explorer Mouse: device removed [ 17.544] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input2/event1" [ 17.544] (II) XINPUT: Adding extended input device "ImExPS/2 Logitech Explorer Mouse" (type: MOUSE, id 11) [ 17.544] (**) Option "AccelerationScheme" "none" [ 17.544] (**) ImExPS/2 Logitech Explorer Mouse: (accel) selected scheme none/0 [ 17.544] (**) ImExPS/2 Logitech Explorer Mouse: (accel) acceleration factor: 2.000 [ 17.544] (**) ImExPS/2 Logitech Explorer Mouse: (accel) acceleration threshold: 4 [ 17.545] (II) event1 - ImExPS/2 Logitech Explorer Mouse: is tagged by udev as: Mouse [ 17.545] (II) event1 - ImExPS/2 Logitech Explorer Mouse: device is a pointer [ 17.546] (II) config/udev: Adding input device ImExPS/2 Logitech Explorer Mouse (/dev/input/mouse0) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c10 --- Comment #10 from Larry Finger <Larry.Finger@gmail.com> --- The problem also occurs with kernel 4.17.0 from mainline. I am currently bisecting to find the offending commit. It will take a while (13 builds estimated). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c13 Michal Srb <msrb@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msrb@suse.com --- Comment #13 from Michal Srb <msrb@suse.com> --- Created attachment 774812 --> http://bugzilla.opensuse.org/attachment.cgi?id=774812&action=edit lsusb -v I was also able to reproduce it with Tumbleweed in Virtualbox. The lsusb -v out is attached. These devices are reported by evtest: /dev/input/event0: AT Translated Set 2 keyboard /dev/input/event1: ImExPS/2 Generic Explorer Mouse /dev/input/event2: VirtualBox mouse integration /dev/input/event3: PC Speaker /dev/input/event4: Power Button /dev/input/event5: Sleep Button /dev/input/event6: Video Bus /dev/input/event7: VirtualBox USB Tablet The event7 produces no events. The event1 produces only BTN_LEFT, BTN_RIGHT, REL_WHEEL events, but no motion events at all. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c14 --- Comment #14 from Michal Srb <msrb@suse.com> --- PS: And event2 gives only ABS_X, ABS_Y events. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c16 --- Comment #16 from Larry Finger <Larry.Finger@gmail.com> --- I have completed the bisection. Although it sounds improbable, the bad commit is commit 04bb1719c4de94700056241d4c0fe3c1413f5aff Author: Ondrej Zary <linux@rainbow-software.org> Date: Tue Apr 3 10:24:34 2018 -0700 Input: i8042 - enable MUX on Sony VAIO VGN-CS series to fix touchpad The touch sensor buttons on Sony VAIO VGN-CS series laptops (e.g. VGN-CS31S) are a separate PS/2 device. As the MUX is disabled for all VAIO machines by the nomux blacklist, the data from touch sensor buttons and touchpad are combined. The protocol used by the buttons is probably similar to the touchpad protocol (both are Synaptics) so both devices get enabled. The controller combines the data, creating a mess which results in random button clicks, touchpad stopping working and lost sync error messages: psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 4 psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 psmouse serio1: issuing reconnect request Add a new i8042_dmi_forcemux_table whitelist with VGN-CS. With MUX enabled, touch sensor buttons are detected as separate device (and left disabled as there's currently no driver), fixing all touchpad problems. Signed-off-by: Ondrej Zary <linux@rainbow-software.org> Cc: stable@vger.kernel.org Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> At this point, I have no idea how a fix for Sony VAIO boxes affects my Toshiba hardware, but the bisection was straight forward. Apparently, the patch affects more touchpads than that of Sony. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c18 --- Comment #18 from Achim Gratz <Stromeko@NexGo.DE> --- I've just updated Tumbleweed to kernel 4.17.2 and as expected the problem persists. Some more details: I've connected three different mice now (Generic PS/2, Primax USB and Primax USB wireless). These all work, but if I connect the Logitech and move it just once, all mice stop working. That's probably the part where libinput is involved and runs into the weeds. I figured out that I can get mouse operation back by restarting the graphical environment (Ctrl-Alt-Backspace on the login screen) without a reboot. Here's what the kernel saw: Jun 23 11:57:59 Gertrud kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Jun 23 11:57:59 Gertrud kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 Jun 23 11:57:59 Gertrud kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 Jun 23 11:57:59 Gertrud kernel: psmouse serio1: logips2pp: Detected unknown Logitech mouse model 62 Jun 23 11:57:59 Gertrud kernel: input: ImExPS/2 Logitech Explorer Mouse as /devices/platform/i8042/serio1/input/input2 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This mouse doesn't work and stops all other mice from working. Jun 23 12:00:17 Gertrud kernel: input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input15 ^^^^^^^^^^^^^^^^^^^^^^^^^^ Replaced with different PS/2 mouse and restarted login screen. The other two mice are connected via USB: Bus 003 Device 002: ID 0461:4dfb Primax Electronics, Ltd Bus 003 Device 003: ID 0461:4d23 Primax Electronics, Ltd evtest sees the three working mice at the moment as: /dev/input/event1: ImPS/2 Generic Wheel Mouse /dev/input/event5: USB Optical Mouse /dev/input/event6: Primax Electronics Wireless Mini Mouse -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c20 --- Comment #20 from Achim Gratz <Stromeko@NexGo.DE> --- Going back to PS/2 connection: evtest: /dev/input/event0: AT Translated Set 2 keyboard /dev/input/event1: ImExPS/2 Logitech Explorer Mouse [15141.640865] input: ImExPS/2 Logitech Explorer Mouse as /devices/platform/i8042/serio1/input/input21 Running evtest on the mouse works, but I have just lost all other mice, this time completeley. After some seconds and switching screens, they are back to working order, clicking and scrolling still works. So beyond all other things it seems the error only triggers when the device is already present when the graphical desktop gets initialized? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c22 --- Comment #22 from Larry Finger <Larry.Finger@gmail.com> --- (In reply to Achim Gratz from comment #17)

I have no idea how this can happen either, but I note that the _initconst pragma qualifier is in a different place than for all other tables in that file. Maybe it mucks up compilation and produces a different table than what was intended?

Something with this patch is definitely flaky. I tried debugging it, but once I changed anything, then it stopped failing, even when I returned it to its original form. At the moment, commit 04bb1719c4de9 is running correctly, even though it failed earlier. :( Is it too late to change my interests to basket weaving? :) The placement of the __initconst in the dmi_system_id struct seems to vary widely. It is placed before, and after the variable name, and many do not use the qualifier at all. If the placement were an issue, I would expect more failures, but I'm still not sure that we are not seeing a compiler issue with gcc8. That brings up the question "Why is my TW KDE instance in a guest using gcc8, while my host TW KDE uses gcc7?" I will send mail to LKML, the patch author, and the subsystem maintainer to see if anyone can shed some light on this issue. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c24 --- Comment #24 from Larry Finger <Larry.Finger@gmail.com> --- I now know a bit more about this problem. Firstly, your revised kernel did not fix this problem. In fact, a kernel 4.18-rc1 generated from the HEAD of Linus' tree has the same problem, thus the regression has not yet been fixed, and likely not recognized as a bug by the community. I then added an external trackball to my VM and got the same result. I re-verified that if I checkout commit 04bb1719, the resulting kernel is faulty, and that the one built from commit adf313f is OK. As they are sequential, this seemed to confirm that 04bb1719 is indeed triggering the problem. I then used adf313f as a base and added the patch from 04bb1719, and found that the resulting kernel is OK! :( I am redoing the entire bisection just to make sure that my results for that part are OK. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c40 --- Comment #40 from Raymond Wooninck <tittiatcoke@gmail.com> --- (In reply to Jiri Slaby from comment #31)

So we have a first fix here: https://lore.kernel.org/lkml/20180625190957.GA187975@dtor-ws/T/#u

Hi Jiri, I believe that you also added this commit to Kernel:HEAD which delivered the kernel 4.18.0-rc2-2.gbe969c3-default. This kernel resolves for me the issue on first login. With this kernel, the mouse works normal on first login. Also the Xorg.0.log file shows now that libinput is loaded. Seems that this commit still did the magic -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c45 Larry Finger <Larry.Finger@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #45 from Larry Finger <Larry.Finger@gmail.com> --- No, I have avoided updating Tumbleweed until this issue is resolved. I am running version 1.11.0-1.1 of libinput. Of course, YaST tells me that 1.11.1 is available, but not yet installed. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1098392 http://bugzilla.opensuse.org/show_bug.cgi?id=1098392#c48 --- Comment #48 from Achim Gratz <Stromeko@NexGo.DE> --- I confirm that since snapshot 20180628 things are back to normal, I've switched the keyboard/mouse back from USB to PS/2 and it's working OK. -- You are receiving this mail because: You are on the CC list for the bug.