Bug 1940872 - Lenovo: Upstream libwacom fix for X1 Yoga6
Summary: Lenovo: Upstream libwacom fix for X1 Yoga6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libwacom
Version: 34
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1816645 1816768
TreeView+ depends on / blocked
 
Reported: 2021-03-19 12:48 UTC by Mark Pearson
Modified: 2021-04-21 21:40 UTC (History)
4 users (show)

Fixed In Version: libwacom-1.9-2.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1914409
Environment:
Last Closed: 2021-03-31 00:15:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mark Pearson 2021-03-19 12:48:49 UTC
Description of problem: Patch upstream in libwacom for adding X1 Yoga 6 panel IDs for Wacom support.
https://github.com/linuxwacom/libwacom/pull/370

Hi Peter - afraid more panel IDs - can we get this into Fedora please when convenient?

Version-Release number of selected component (if applicable):


How reproducible: 100%


Steps to Reproduce:
1. Use stylus with X1Y6 - it's not shown under wacom device setting
2.
3.

Actual results: No stylus shown


Expected results: Stylus shown


Additional info:

Comment 1 Peter Hutterer 2021-03-25 05:29:16 UTC
done, sorry, friday late night email slipped through  :)

Comment 2 Fedora Update System 2021-03-25 05:31:01 UTC
FEDORA-2021-a036356461 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-a036356461

Comment 3 Fedora Update System 2021-03-26 18:33:34 UTC
FEDORA-2021-a036356461 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-a036356461`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-a036356461

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Mark Pearson 2021-03-30 12:27:48 UTC
Thanks Peter!

The team tested it and confirmed it worked on Fedora34.
Will we be able to get this in F33 as well? Curious as to how that works

Mark

Comment 5 Fedora Update System 2021-03-31 00:15:41 UTC
FEDORA-2021-a036356461 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2021-04-06 03:14:59 UTC
FEDORA-2021-8d4429eb47 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-8d4429eb47

Comment 7 Peter Hutterer 2021-04-06 03:21:02 UTC
As a general handwavy rule, I usually push updates to both the N and N+1 until a few weeks or months after N+1 was released. After that, it's by-demand only and depending on the changes. libwacom is mostly harmless so updating f33 is fine (esp. now since F34 isn't out yet). F32 isn't quite worth the hassle though.

libwacom 1.9 had a few other changes which is why I didn't immediately push to both but there hasn't been any bugs about those so it's safe to update F33 as well. Build is in the updates now, expect it to hit F33 stable once the karma goes past the thresholds, etc.

Comment 8 Mark Pearson 2021-04-06 16:19:52 UTC
Thanks Peter - much appreciated.
Mark

Comment 9 Fedora Update System 2021-04-07 15:17:14 UTC
FEDORA-2021-8d4429eb47 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-8d4429eb47`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8d4429eb47

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2021-04-21 21:40:02 UTC
FEDORA-2021-8d4429eb47 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.


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