| 2017-04-19 07:35:55 |
Zorro Zhang |
bug |
|
|
added bug |
| 2017-04-19 12:13:52 |
Mario Limonciello |
affects |
fwupd (Ubuntu) |
fwupdate (Ubuntu) |
|
| 2017-04-19 12:14:02 |
Mario Limonciello |
bug task added |
|
fwupdate-signed (Ubuntu) |
|
| 2017-04-19 12:14:12 |
Mario Limonciello |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-04-19 12:14:12 |
Mario Limonciello |
bug task added |
|
fwupdate (Ubuntu Zesty) |
|
| 2017-04-19 12:14:12 |
Mario Limonciello |
bug task added |
|
fwupdate-signed (Ubuntu Zesty) |
|
| 2017-04-19 12:14:12 |
Mario Limonciello |
nominated for series |
|
Ubuntu Yakkety |
|
| 2017-04-19 12:14:12 |
Mario Limonciello |
bug task added |
|
fwupdate (Ubuntu Yakkety) |
|
| 2017-04-19 12:14:12 |
Mario Limonciello |
bug task added |
|
fwupdate-signed (Ubuntu Yakkety) |
|
| 2017-04-19 12:14:12 |
Mario Limonciello |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-04-19 12:14:12 |
Mario Limonciello |
bug task added |
|
fwupdate (Ubuntu Xenial) |
|
| 2017-04-19 12:14:12 |
Mario Limonciello |
bug task added |
|
fwupdate-signed (Ubuntu Xenial) |
|
| 2017-04-19 12:14:21 |
Mario Limonciello |
fwupdate (Ubuntu Zesty): status |
New |
Fix Released |
|
| 2017-04-19 12:14:24 |
Mario Limonciello |
fwupdate-signed (Ubuntu Zesty): status |
New |
Fix Released |
|
| 2017-04-19 12:18:53 |
Mario Limonciello |
summary |
[Gamora AMD] Touchpad No Function After BIOS Capsule Update |
Dell Inspiron 5x65 touchpad doesn't work after BIOS Capsule Update |
|
| 2017-04-19 12:47:36 |
Mario Limonciello |
description |
This Bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
The newer version of capsule flashing tools in Ubuntu 17.04 supports the reset type from some querycapsuleinfo call.
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722 |
[Impact]
This Bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
The newer version of capsule flashing tools in Ubuntu 17.04 supports the reset type from some querycapsuleinfo call.
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722
[Test Case]
On a system with a capsule update available, perform capsule update using fwupdate. Verify the system works properly after the update.
[Regression Potential]
Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems. This is actually a BIOS
problem in those situations.
It's unlikely that this should happen though because querying for reset types more closely aligns to the implementations that other OSes use when applying capsule updates. |
|
| 2017-04-20 02:26:41 |
Launchpad Janitor |
fwupdate (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2017-04-20 02:26:41 |
Launchpad Janitor |
fwupdate-signed (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2017-04-20 02:26:41 |
Launchpad Janitor |
fwupdate (Ubuntu Yakkety): status |
New |
Confirmed |
|
| 2017-04-20 02:26:41 |
Launchpad Janitor |
fwupdate-signed (Ubuntu Yakkety): status |
New |
Confirmed |
|
| 2017-04-20 02:27:08 |
Mario Limonciello |
summary |
Dell Inspiron 5x65 touchpad doesn't work after BIOS Capsule Update |
Some dell and Lenovo systems doesn't work after BIOS Capsule Update |
|
| 2017-04-20 02:27:21 |
Mario Limonciello |
summary |
Some dell and Lenovo systems doesn't work after BIOS Capsule Update |
Some Dell and Lenovo systems do not work after BIOS Capsule Update |
|
| 2017-04-20 02:27:58 |
Mario Limonciello |
bug |
|
|
added subscriber Kent Lin |
| 2017-04-20 11:28:14 |
Anthony Wong |
bug |
|
|
added subscriber Anthony Wong |
| 2017-04-24 15:22:00 |
Mathieu Trudel-Lapierre |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-04-24 15:23:56 |
Mathieu Trudel-Lapierre |
fwupdate (Ubuntu Yakkety): status |
Confirmed |
In Progress |
|
| 2017-04-24 15:23:59 |
Mathieu Trudel-Lapierre |
fwupdate-signed (Ubuntu Yakkety): status |
Confirmed |
In Progress |
|
| 2017-04-24 15:24:01 |
Mathieu Trudel-Lapierre |
fwupdate-signed (Ubuntu Yakkety): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2017-04-24 15:24:03 |
Mathieu Trudel-Lapierre |
fwupdate (Ubuntu Yakkety): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2017-04-24 15:24:06 |
Mathieu Trudel-Lapierre |
fwupdate (Ubuntu Xenial): status |
Confirmed |
In Progress |
|
| 2017-04-24 15:24:09 |
Mathieu Trudel-Lapierre |
fwupdate-signed (Ubuntu Xenial): status |
Confirmed |
In Progress |
|
| 2017-04-24 15:24:11 |
Mathieu Trudel-Lapierre |
fwupdate (Ubuntu Xenial): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2017-04-24 15:24:13 |
Mathieu Trudel-Lapierre |
fwupdate-signed (Ubuntu Xenial): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2017-04-24 15:24:59 |
Mathieu Trudel-Lapierre |
fwupdate (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2017-04-24 15:25:00 |
Mathieu Trudel-Lapierre |
fwupdate (Ubuntu Yakkety): importance |
Undecided |
High |
|
| 2017-04-24 15:25:03 |
Mathieu Trudel-Lapierre |
fwupdate-signed (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2017-04-24 15:25:05 |
Mathieu Trudel-Lapierre |
fwupdate-signed (Ubuntu Yakkety): importance |
Undecided |
High |
|
| 2017-04-24 16:09:53 |
Mathieu Trudel-Lapierre |
description |
[Impact]
This Bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
The newer version of capsule flashing tools in Ubuntu 17.04 supports the reset type from some querycapsuleinfo call.
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722
[Test Case]
On a system with a capsule update available, perform capsule update using fwupdate. Verify the system works properly after the update.
[Regression Potential]
Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems. This is actually a BIOS
problem in those situations.
It's unlikely that this should happen though because querying for reset types more closely aligns to the implementations that other OSes use when applying capsule updates. |
[Impact]
This Bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
The newer version of capsule flashing tools in Ubuntu 17.04 supports the reset type from some querycapsuleinfo call.
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722
[Test Case]
== fwupdate ==
On a system with a capsule update available, perform capsule update using fwupdate. Verify the system works properly after the update.
== efivar ==
Validate that all efivar reverse-dependencies in a release still build correctly.
[Regression Potential]
Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems. This is actually a BIOS
problem in those situations.
It's unlikely that this should happen though because querying for reset types more closely aligns to the implementations that other OSes use when applying capsule updates. |
|
| 2017-05-06 16:04:46 |
Ian Li |
bug |
|
|
added subscriber Ian Li |
| 2017-05-22 12:24:28 |
Anthony Wong |
attachment added |
|
fwupdate.debdiff https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1684034/+attachment/4881350/+files/fwupdate.debdiff |
|
| 2017-05-22 12:24:50 |
Anthony Wong |
attachment added |
|
fwupd.debdiff https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1684034/+attachment/4881351/+files/fwupd.debdiff |
|
| 2017-05-22 12:35:59 |
Anthony Wong |
description |
[Impact]
This Bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
The newer version of capsule flashing tools in Ubuntu 17.04 supports the reset type from some querycapsuleinfo call.
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722
[Test Case]
== fwupdate ==
On a system with a capsule update available, perform capsule update using fwupdate. Verify the system works properly after the update.
== efivar ==
Validate that all efivar reverse-dependencies in a release still build correctly.
[Regression Potential]
Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems. This is actually a BIOS
problem in those situations.
It's unlikely that this should happen though because querying for reset types more closely aligns to the implementations that other OSes use when applying capsule updates. |
[Impact]
This Bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
The newer version of capsule flashing tools in Ubuntu 17.04 supports the reset type from some querycapsuleinfo call.
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722
[Test Case]
== fwupdate ==
On a system with a capsule update available, perform capsule update using fwupdate. Verify the system works properly after the update.
== fwupd ==
The soname version of libfwup has been increased to 1 in fwupdate 9. Since the current fwupd depends on libfwup0 so fwupd has to be rebuilt against the new libfwup1.
To test, perform firmware update with fwupdmgr and see if it works.
== efivar ==
We avoided the upgrade of efivar so we don't need to validate its reverse-dependencies.
[Regression Potential]
Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems. This is actually a BIOS
problem in those situations.
It's unlikely that this should happen though because querying for reset types more closely aligns to the implementations that other OSes use when applying capsule updates. |
|
| 2017-05-26 04:33:30 |
Mario Limonciello |
bug |
|
|
added subscriber Mario Limonciello |
| 2017-05-26 08:18:32 |
Anthony Wong |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2017-06-01 14:20:25 |
Timo Aaltonen |
bug task added |
|
fwupd (Ubuntu) |
|
| 2017-06-05 18:16:48 |
Anthony Wong |
description |
[Impact]
This Bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
The newer version of capsule flashing tools in Ubuntu 17.04 supports the reset type from some querycapsuleinfo call.
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722
[Test Case]
== fwupdate ==
On a system with a capsule update available, perform capsule update using fwupdate. Verify the system works properly after the update.
== fwupd ==
The soname version of libfwup has been increased to 1 in fwupdate 9. Since the current fwupd depends on libfwup0 so fwupd has to be rebuilt against the new libfwup1.
To test, perform firmware update with fwupdmgr and see if it works.
== efivar ==
We avoided the upgrade of efivar so we don't need to validate its reverse-dependencies.
[Regression Potential]
Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems. This is actually a BIOS
problem in those situations.
It's unlikely that this should happen though because querying for reset types more closely aligns to the implementations that other OSes use when applying capsule updates. |
[Impact]
This Bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
The newer version of capsule flashing tools in Ubuntu 17.04 supports the reset type from some querycapsuleinfo call：
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722
fwupdate 9-1 has other bugfixes that are important too:
- some memory leaks (eg: https://github.com/rhinstaller/fwupdate/commit/765bb7221af37ac56b11ef2253bf1bb3230ef589)
- some inconsistent behaviors due to ambiguous UEFI spec behavior (eg https://github.com/rhinstaller/fwupdate/commit/ba48ac4ed7329ae5beb44063dcbd3c424e11fc46)
- some other features that are going to be needed to be able to support newer fwupd (eg: https://github.com/rhinstaller/fwupdate/commit/64b4cd53baa57352fa9b2459e804c4ea50d40299)
[Test Case]
== fwupdate ==
On a system with a capsule update available, perform capsule update using fwupdate. Verify the system works properly after the update.
== fwupd ==
The soname version of libfwup has been increased to 1 in fwupdate 9. Since the current fwupd depends on libfwup0 so fwupd has to be rebuilt against the new libfwup1.
To test, perform firmware update with fwupdmgr and see if it works.
== efivar ==
We avoided the upgrade of efivar so we don't need to validate its reverse-dependencies.
[Regression Potential]
Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems. This is actually a BIOS
problem in those situations.
It's unlikely that this should happen though because querying for reset types more closely aligns to the implementations that other OSes use when applying capsule updates. |
|
| 2017-06-05 18:18:04 |
Anthony Wong |
description |
[Impact]
This Bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
The newer version of capsule flashing tools in Ubuntu 17.04 supports the reset type from some querycapsuleinfo call：
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722
fwupdate 9-1 has other bugfixes that are important too:
- some memory leaks (eg: https://github.com/rhinstaller/fwupdate/commit/765bb7221af37ac56b11ef2253bf1bb3230ef589)
- some inconsistent behaviors due to ambiguous UEFI spec behavior (eg https://github.com/rhinstaller/fwupdate/commit/ba48ac4ed7329ae5beb44063dcbd3c424e11fc46)
- some other features that are going to be needed to be able to support newer fwupd (eg: https://github.com/rhinstaller/fwupdate/commit/64b4cd53baa57352fa9b2459e804c4ea50d40299)
[Test Case]
== fwupdate ==
On a system with a capsule update available, perform capsule update using fwupdate. Verify the system works properly after the update.
== fwupd ==
The soname version of libfwup has been increased to 1 in fwupdate 9. Since the current fwupd depends on libfwup0 so fwupd has to be rebuilt against the new libfwup1.
To test, perform firmware update with fwupdmgr and see if it works.
== efivar ==
We avoided the upgrade of efivar so we don't need to validate its reverse-dependencies.
[Regression Potential]
Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems. This is actually a BIOS
problem in those situations.
It's unlikely that this should happen though because querying for reset types more closely aligns to the implementations that other OSes use when applying capsule updates. |
[Impact]
This bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
The newer version of capsule flashing tools in Ubuntu 17.04 supports the reset type from some querycapsuleinfo call：
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722
fwupdate 9-1 has other bugfixes that are important too:
- some memory leaks (eg: https://github.com/rhinstaller/fwupdate/commit/765bb7221af37ac56b11ef2253bf1bb3230ef589)
- some inconsistent behaviors due to ambiguous UEFI spec behavior (eg https://github.com/rhinstaller/fwupdate/commit/ba48ac4ed7329ae5beb44063dcbd3c424e11fc46)
- some other features that are going to be needed to be able to support newer fwupd (eg: https://github.com/rhinstaller/fwupdate/commit/64b4cd53baa57352fa9b2459e804c4ea50d40299)
[Test Case]
== fwupdate ==
On a system with a capsule update available, perform capsule update using fwupdate. Verify the system works properly after the update.
== fwupd ==
The soname version of libfwup has been increased to 1 in fwupdate 9. Since the current fwupd depends on libfwup0 so fwupd has to be rebuilt against the new libfwup1.
To test, perform firmware update with fwupdmgr and see if it works.
== efivar ==
We avoided the upgrade of efivar so we don't need to validate its reverse-dependencies.
[Regression Potential]
Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems. This is actually a BIOS
problem in those situations.
It's unlikely that this should happen though because querying for reset types more closely aligns to the implementations that other OSes use when applying capsule updates. |
|
| 2017-06-22 12:22:31 |
Anthony Wong |
description |
[Impact]
This bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
The newer version of capsule flashing tools in Ubuntu 17.04 supports the reset type from some querycapsuleinfo call：
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722
fwupdate 9-1 has other bugfixes that are important too:
- some memory leaks (eg: https://github.com/rhinstaller/fwupdate/commit/765bb7221af37ac56b11ef2253bf1bb3230ef589)
- some inconsistent behaviors due to ambiguous UEFI spec behavior (eg https://github.com/rhinstaller/fwupdate/commit/ba48ac4ed7329ae5beb44063dcbd3c424e11fc46)
- some other features that are going to be needed to be able to support newer fwupd (eg: https://github.com/rhinstaller/fwupdate/commit/64b4cd53baa57352fa9b2459e804c4ea50d40299)
[Test Case]
== fwupdate ==
On a system with a capsule update available, perform capsule update using fwupdate. Verify the system works properly after the update.
== fwupd ==
The soname version of libfwup has been increased to 1 in fwupdate 9. Since the current fwupd depends on libfwup0 so fwupd has to be rebuilt against the new libfwup1.
To test, perform firmware update with fwupdmgr and see if it works.
== efivar ==
We avoided the upgrade of efivar so we don't need to validate its reverse-dependencies.
[Regression Potential]
Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems. This is actually a BIOS
problem in those situations.
It's unlikely that this should happen though because querying for reset types more closely aligns to the implementations that other OSes use when applying capsule updates. |
[Impact]
This bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.
The newer version of capsule flashing tools in Ubuntu 17.04 supports the reset type from some querycapsuleinfo call：
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722
[Test Case]
== fwupdate ==
On a system with a capsule update available, perform capsule update using fwupdate. Verify the system works properly after the update.
== efivar ==
We avoided the upgrade of efivar so we don't need to validate its reverse-dependencies.
[Regression Potential]
Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems. This is actually a BIOS
problem in those situations.
It's unlikely that this should happen though because querying for reset types more closely aligns to the implementations that other OSes use when applying capsule updates. |
|
| 2017-06-22 12:24:19 |
Anthony Wong |
bug task deleted |
fwupd (Ubuntu) |
|
|
| 2017-06-22 12:24:35 |
Anthony Wong |
bug task deleted |
fwupd (Ubuntu Xenial) |
|
|
| 2017-06-22 12:24:41 |
Anthony Wong |
bug task deleted |
fwupd (Ubuntu Yakkety) |
|
|
| 2017-06-22 12:24:58 |
Anthony Wong |
bug task deleted |
fwupd (Ubuntu Zesty) |
|
|
| 2017-06-27 08:39:49 |
Anthony Wong |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2017-07-07 14:59:26 |
Anthony Wong |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2017-07-10 08:44:07 |
Timo Aaltonen |
fwupdate (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2017-07-10 08:44:13 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2017-07-10 08:44:19 |
Timo Aaltonen |
tags |
|
verification-needed |
|
| 2017-07-14 04:22:13 |
Adam Conrad |
fwupdate-signed (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2017-07-14 04:31:08 |
Adam Conrad |
fwupdate (Ubuntu Yakkety): status |
In Progress |
Won't Fix |
|
| 2017-07-14 04:31:11 |
Adam Conrad |
fwupdate-signed (Ubuntu Yakkety): status |
In Progress |
Won't Fix |
|
| 2017-07-19 07:38:21 |
Ivan Hu |
tags |
verification-needed |
verification-done-xenial |
|
| 2017-07-20 17:11:47 |
Brian Murray |
fwupdate (Ubuntu Xenial): status |
Fix Committed |
Incomplete |
|
| 2017-07-20 23:44:31 |
Launchpad Janitor |
fwupdate (Ubuntu Xenial): status |
Incomplete |
Fix Released |
|
| 2017-07-20 23:44:35 |
Adam Conrad |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-07-20 23:44:39 |
Launchpad Janitor |
fwupdate-signed (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
