Support to upgrade Synaptic fingerprint firmware from LVFS
Bug #1900935 reported by
jeremyszu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OEM Priority Project |
Fix Released
|
Low
|
jeremyszu | ||
fwupd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Won't Fix
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned | ||
Hirsute |
Fix Released
|
Undecided
|
Unassigned | ||
fwupd-signed (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Won't Fix
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned | ||
Hirsute |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Versions of fwupd older than 1.4.6 can not support upgrading Synaptics fingerprint readers.
[Test Case]
Try to update firmware from a synaptics fingerprint reader.
[Regression Potential]
This will require moving to fwupd 1.4.6 which is newer than the release in focal. The patches for Synaptics fingerprint reader support depend upon daemon code that is not present in the 1.3.x series.
There may be potentially other bugs with moving to this release. More devices are supported which might mean exercising extra code paths.
tags: | added: oem-priority originate-from-1866761 stella |
Changed in oem-priority: | |
assignee: | nobody → jeremyszu (os369510) |
status: | New → In Progress |
status: | In Progress → Confirmed |
importance: | Undecided → Low |
Changed in fwupd (Ubuntu): | |
status: | New → Triaged |
tags: | added: fwupd |
Changed in fwupd (Ubuntu Bionic): | |
status: | New → Won't Fix |
Changed in fwupd (Ubuntu Hirsute): | |
status: | Triaged → Fix Released |
Changed in fwupd (Ubuntu Bionic): | |
status: | Won't Fix → In Progress |
status: | In Progress → Won't Fix |
Changed in fwupd (Ubuntu Focal): | |
status: | New → In Progress |
Changed in fwupd (Ubuntu Groovy): | |
status: | New → In Progress |
Changed in fwupd-signed (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in fwupd-signed (Ubuntu Focal): | |
status: | New → In Progress |
Changed in fwupd-signed (Ubuntu Bionic): | |
status: | In Progress → Won't Fix |
Changed in fwupd-signed (Ubuntu Groovy): | |
status: | New → In Progress |
Changed in fwupd-signed (Ubuntu Hirsute): | |
status: | New → In Progress |
description: | updated |
tags: |
added: verification-done-groovy removed: verification-needed-groovy |
tags: | removed: verification-needed |
Changed in fwupd-signed (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in fwupd-signed (Ubuntu Hirsute): | |
status: | In Progress → Fix Released |
Changed in fwupd (Ubuntu Groovy): | |
status: | In Progress → Fix Committed |
Changed in fwupd (Ubuntu Groovy): | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
As per currently agreed SRU policy exception for fwupd: https:/ /wiki.ubuntu. com/firmware- updates focal launched with 1.3.x, so only the 1_3_X branch should be added into focal archive.
As mentioned there we track the stable branch in Ubuntu, so we shouldn't be backporting a plugin without associated other changes. This is very important as often daemon changes that are not obviously tied to the plugin may need to backport at the same time.
So the options are either:
1) Get the synaptics fingerprint plugin backported into 1_3_X branch upstream and a new upstream 1.3.x release tagged.
2) Discuss with technical board to request to modify the exception to allow moving to the 1.4.x or 1.5.x release stream. In "general" I'm supportive of this direction, there are certainly other devices that are supported in upstream that it would be nice to support in LTS as well.