http://bugzilla.opensuse.org/show_bug.cgi?id=1193213 http://bugzilla.opensuse.org/show_bug.cgi?id=1193213#c2 --- Comment #2 from Marco Varlese --- Actually, this turns out to be not an issue with the latest kernel only. It happens also with 5.14 apparently. Rebooting the machine with the very same kernel then results in the bug not to show up anymore. The output of hwinfo has been attached. I will provide the dmesg output in the next run when the bug shows up. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193213 http://bugzilla.opensuse.org/show_bug.cgi?id=1193213#c4 --- Comment #4 from Marco Varlese --- Created attachment 854268 --> http://bugzilla.opensuse.org/attachment.cgi?id=854268&action=edit dmesg output with touchpad issue experienced -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193213 http://bugzilla.opensuse.org/show_bug.cgi?id=1193213#c7 --- Comment #7 from Takashi Iwai --- Could you give also the dmesg output from the working case, too? Judging from the hwinfo outputs, the working case seems to have the elantech touchpad, and the broken case doesn't have it. The dmesg output shows some error from elantech driver, but it's not clear whether it's the fatal error that leaded the the lack of the device itself. My wild guess is that, due to the failure from the elantech driver initialization, it falls back to the legacy mouse that has no multi-finger support. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193213 http://bugzilla.opensuse.org/show_bug.cgi?id=1193213#c13 Marco Varlese changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #13 from Marco Varlese --- I have been waiting to provide feedback on this bug-report as I wanted to experiment further with it. For the past two months I have not observed the misbehavior any longer. I believe the issue has been addressed upstream and it eventually landed in our TW kernel. With all that, I would consider this bug resolved. -- You are receiving this mail because: You are the assignee for the bug.