Bug 1919199

Summary:	System freezes when screen is touched
Product:	[Fedora] Fedora	Reporter:	Matthew Saltzman <mjs>
Component:	libwacom	Assignee:	Peter Hutterer <peter.hutterer>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	33	CC:	btissoir, peter.hutterer
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-04 05:53:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matthew Saltzman 2021-01-22 11:38:20 UTC

Description of problem:
After updating to kernel-5.10.8, touching the screen of my Lenovo Yoga X1 2nd generation causes the system to instantly freeze, requiring hard reset.

Version-Release number of selected component (if applicable):
libwacom-1.7-2.fc33.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Touch the screen
2.
3.

Actual results:
Total lockup requiring hard reset

Expected results:
Functional system

Additional info:
Downgrading to kernel 5.10.7 is a workaround.

Apparently, there is a patch in the works. 

Upstream bug report: https://github.com/linuxwacom/input-wacom/issues/230#issuecomment-764589102

Bug report against kernel with additional documentation is Bug 1918486, but I wanted to get the attention of the appropriate maintainer ASAP.

Comment 1 Peter Hutterer 2021-02-03 05:34:48 UTC

Does the kernel update in Bug 1918486 fix the issue? libwacom is just a glorified text file database so it's not the cause of this issue.

Comment 2 Matthew Saltzman 2021-02-03 19:59:26 UTC

(In reply to Peter Hutterer from comment #1)
> Does the kernel update in Bug 1918486 fix the issue? libwacom is just a
> glorified text file database so it's not the cause of this issue.

Yes, that update solves the problem. I posted here because of the link in the other report to a patch to libwacom that indicated it was the fix.

Thanks.

Comment 3 Peter Hutterer 2021-02-04 05:53:38 UTC

unfortunately, libwacom is the first place people file bugs and it's virtually never the actual cause of the bug, so any bug linking to libwacom is usually a false positive. Thanks for the update though, I'm marking this as duplicate.

*** This bug has been marked as a duplicate of bug 1918486 ***