Bug 1496650

Summary:	Fix hang after unplugging a device
Product:	Red Hat Enterprise Linux 7	Reporter:	Peter Hutterer <peter.hutterer>
Component:	xorg-x11-drv-wacom	Assignee:	Peter Hutterer <peter.hutterer>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	mboisver, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	xorg-x11-drv-wacom-0.34.2-3.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 11:52:21 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 Peter Hutterer 2017-09-28 04:22:53 UTC

Description of problem:
Unplugging a device may cause a hang and a log filling up with "Error reading wacom device : No such device". This is caused by the fd still being read by the input thread in the server even when all we get are ENODEV errors.

Version-Release number of selected component (if applicable):
xorg-x11-drv-wacom-0.34.2

How reproducible:
Plug in a device, use it, unplug. Look for "Error reading wacom device : No such device" in the log. This message should occur once per device, anything more is a bug.

This is a race condition and can be more difficult to trigger on some devices. Once the udev device removal event is received by the server, the device will be removed and the messages will stop.


Additional info:
Upstream bug https://bugzilla.redhat.com/show_bug.cgi?id=1478397

Comment 1 Peter Hutterer 2017-10-05 04:10:08 UTC

xorg-x11-drv-wacom-0.34.2-3.el7 is available in brew

Comment 4 Michael Boisvert 2018-02-07 17:24:21 UTC

I was able to reproduce the log fill up using xorg-x11-drv-wacom-0.34.2-2 and verified the log contained only one message per device upon disconnecting a Wacom 22HDT on xorg-x11-drv-wacom-0.34.2-4.

Comment 7 errata-xmlrpc 2018-04-10 11:52:21 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0736