Bug 1614555 - touchpad & trackpoint stops working randomly in thinkpad helix
Summary: touchpad & trackpoint stops working randomly in thinkpad helix
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 29
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-09 22:13 UTC by lsg
Modified: 2019-02-21 21:07 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-02-21 21:07:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmidecode output (14.66 KB, text/plain)
2018-08-09 22:13 UTC, lsg
no flags Details

Description lsg 2018-08-09 22:13:19 UTC
Created attachment 1474836 [details]
dmidecode output

Description of problem:
Randomly, after some time of working correctly, touchpad (and trackpoint) stops working (doesn't seem to be recognized, suddenly) in thinkpad helix (convertible laptop) 

Version-Release number of selected component (if applicable):
Kernel 4.17.12-200.fc28.x86_64 #1 SMP Fri Aug 3 15:01:13 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


How reproducible:
Nothing special, just boot and wait a little bit

Steps to Reproduce:
1.
2.
3.

Actual results:
Trackpoint & touchpad not working

Expected results:
To have a working trackpoint and touchpad like I had with Kernel 4.9 in Fedora back at the time.

Additional info:
- fixed bug in Opensuse Leap 15
https://bugzilla.suse.com/show_bug.cgi?id=1090457

- workaround - related bug repport in Fedora
 https://bugzilla.redhat.com/show_bug.cgi?id=1442699

Comment 1 Laura Abbott 2018-10-01 21:33:00 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.
 
Fedora 28 has now been rebased to 4.18.10-300.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.
 
If you experience different issues, please open a new bug report for those.

Comment 2 Laura Abbott 2018-11-26 21:05:59 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and let us know if the bug is still present on the latest kernel.

(Please note: sometimes bugs get mistakenly closed during our mass closing. If you think your bug was closed in error please reopen)

Comment 3 lsg 2018-12-03 20:44:39 UTC
The bug is still there in F29 with kernel 4.19.4-300.fc29.x86_64

Comment 4 Justin M. Forbes 2019-01-29 16:13:50 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.

Fedora 29 has now been rebased to 4.20.5-200.fc29.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 5 Justin M. Forbes 2019-02-21 21:07:15 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.