Bug 1659849
Summary: | Wacom Cintiq 13 Pro does not show up | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Peter Hutterer <peter.hutterer> |
Component: | fwupd | Assignee: | Richard Hughes <rhughes> |
Status: | CLOSED DUPLICATE | QA Contact: | Erico Nunes <ernunes> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.0 | CC: | jason.gerecke, mboisver, tpelka |
Target Milestone: | rc | ||
Target Release: | 8.2 | ||
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: | 2019-11-29 14:17:20 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1656965, 1656966, 1656968 |
Description
Peter Hutterer
2018-12-17 02:27:36 UTC
Punting to fwupd, Jason from Wacom writes: I've finally been able to reproduce the issues with the Cintiq Pro 13. In my case, at least, they seem to be fallout from the fwupd issue we reported to Richard (https://github.com/hughsie/fwupd/issues/882). As soon as the fwupd program talks to the Cintiq Pro 13 the device goes into a STALL state and is basically unusable. If G-C-C runs before fwupd then the device will show up; otherwise it doesn't. The pen stops working as soon as fwupd runs as well, which is probably why there wasn't any response. The Intuos Pro 2 is immune to the fwupd issue and so works fine. Disabling the fwupd plugin seems to have fixed things (though its hard to be sure since I was having trouble reproducing in the first place). Hopefully Richard's fixes are all that are necessary. Just for reference: Bug 1657623 which I could reproduce on the Intuos Pro I have may be related, but not sure. *** Bug 1656516 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 1680154 *** |