This bug was fixed in the package fwupdate-signed - 1.11.3
---
fwupdate-signed (1.11.3) xenial; urgency=medium
* Build-depend on fwupdate 0.5-2ubuntu7 (LP: #1730343)
-- Mario Limonciello Mon, 15 Jan 2018
23:06:45 -0600
--
You received this bug notification because you are a me
This bug was fixed in the package fwupdate - 0.5-2ubuntu7
---
fwupdate (0.5-2ubuntu7) xenial; urgency=medium
* Redo patch series. (LP: #1730343)
- Backport ALL patches to EFI application up through the "9" release.
- The last two attempts have introduced unobvious bugs due t
For me the update was also successful. Went from bios version 1.7.5 to
1.8.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730343
Title:
firmware update breaks Ubuntu
To manage notifications about
I've downloaded the fwupdate 0.5-2ubuntu7/fwupdate-signed 1.11.3
proposed from an XPS 9350 running BIOS 1.5.0 on Ubuntu 16.04.
I successfully upgraded to 1.6.1 via UEFI capsule and booted back into Ubuntu.
I also confirmed that there is no remaining Linux Firmware Updater \fwupx64.efi
NVRAM EFI e
Unfortunately moving libfwup to 9 also means backporting newer efivar, so
that's why it makes more sense to only update EFI application.
Thanks for reviewing and accepting.
On Thu, Jan 18, 2018, 02:36 Łukasz Zemczak <1730...@bugs.launchpad.net>
wrote:
> The latest upload consists of a very high
The latest upload consists of a very high number of patches which might
quickly get hard to maintain. For the future maybe it would make sense
to backport the whole 9 version to xenial instead of patching just one
component with the code from the 9-codebase.
** Changed in: fwupdate-signed (Ubuntu
Hello Merlijn, or anyone else affected,
Accepted fwupdate into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/fwupdate/0.5-2ubuntu7 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Thank for the feedback Koen. Considering the failure there are other
intermediary patches causing problems in less obvious ways.
Since the "9" release is stable in all these other Ubuntu releases with
no other major complaints, I'm instead pulling in all changes to
efi/fwupdate.c from 0.5 to 9 re
** Changed in: fwupd
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730343
Title:
firmware update breaks Ubuntu
To manage notifications about this bug go to:
http
Hello all,
I just tried the proposed package on 16.04 and it failed.
I took this picture with my phone:
https://www.dropbox.com/s/6r6zeadqakbtjg5/2018-01-04%2023.35.59-1.jpg?dl=0
After that screen it just continued with a regular boot.
** Tags removed: verification-needed-xenial
** Tags added:
Hello Merlijn, or anyone else affected,
Accepted fwupdate into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/fwupdate/0.5-2ubuntu6 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Can someone from the SRU team please tell me what needs to happen in
order to get this release out to Xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730343
Title:
firmware update breaks Ubun
Hello Merlijn, or anyone else affected,
Accepted fwupdate-signed into zesty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/fwupdate-
signed/1.13.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Many people have commented on the bug reports, and more people have
given a "thumbs up" to my comment explaining the workaround to get their
system booting again.
This is an issue that is actively bricking many people's machines. The
only reason why we haven't yet seen thousands of people having t
Hello, it was requested I also leave a comment here. Yesterday I
experienced this issue on Ubuntu 16.04 LTS.
I then found this github ticket:
https://github.com/rhboot/fwupdate/issues/86
Which had a workaround that got my machine working again.
I was told that "The Ubuntu archive admin needs to
This bug was fixed in the package fwupdate - 9-2ubuntu0.17.10.1
---
fwupdate (9-2ubuntu0.17.10.1) artful; urgency=medium
* Disable "Linux Firmware Updater" boot entry after installation
(LP: #1730343)
-- Mario Limonciello Mon, 06 Nov 2017
09:52:16 -0600
** Changed in: fwupd
This bug was fixed in the package fwupdate-signed - 1.14.1
---
fwupdate-signed (1.14.1) artful; urgency=medium
* Build-depend on fwupdate 9-2ubuntu0.17.10.1 (LP: #1730343).
-- Mario Limonciello Mon, 20 Nov 2017
17:08:04 -0600
** Changed in: fwupdate-signed (Ubuntu Artful)
OK so I got xenial compiling by a few extra backported patches. I've
uploaded fwupdate and fwupdate-signed for xenial to proposed.
** Changed in: fwupdate (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: fwupdate-signed (Ubuntu Xenial)
Status: Triaged => In Progress
-
I was having some trouble with patching xenial and got busy with something
else, let me try one more time.
On Fri, Dec 1, 2017, 13:40 Mathieu Trudel-Lapierre
wrote:
> There's also a fwupdate-signed waiting in the zesty queue; that should
> fix the current failed-to-upload.
>
> Xenial indeed need
There's also a fwupdate-signed waiting in the zesty queue; that should
fix the current failed-to-upload.
Xenial indeed needs to be updated; perhaps the simplest in this case is
to bring it to the same version as in zesty?
Mario, what do you think?
--
You received this bug notification because y
This package fixes the bug.
Package: fwupdate-signed
Version: 1.14.1+9-2ubuntu0.17.10.1
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
And what about Xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730343
Title:
firmware update breaks Ubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug
Ah, I see it now. Let me review/approve that.
** Changed in: fwupdate-signed (Ubuntu Artful)
Status: In Progress => Fix Committed
** Tags removed: verification-failed-artful
** Tags added: verification-needed-artful
--
You received this bug notification because you are a member of Ubuntu
So that should be what I uploaded now. Can you look at what's in unapproved
queue?
On Thu, Nov 30, 2017, 08:35 Łukasz Zemczak <1730...@bugs.launchpad.net>
wrote:
> Ok, I was scratching my head what happened, but it seems the fwupdate-
> signed upload failed to upload because we seemed to have had
Ok, I was scratching my head what happened, but it seems the fwupdate-
signed upload failed to upload because we seemed to have had fwupdate-
signed version 1.14+9-2 published in artful at some point. See the
following link to the binary:
https://launchpad.net/ubuntu/artful/amd64/fwupdate-signed/1
** Tags removed: verification-done-artful
** Tags added: verification-failed-artful
** Changed in: fwupdate-signed (Ubuntu Artful)
Status: Fix Committed => In Progress
** Changed in: fwupdate (Ubuntu Artful)
Status: Fix Committed => In Progress
--
You received this bug notificatio
It failed for artful.. we're waiting for the signed package to be accepted
again.
On Sun, Nov 26, 2017, 05:52 Merlijn Sebrechts
wrote:
> Just imagine what will happen if Dell releases a new firmware update for
> one of their laptops... We've been lucky this hasn't happened yet, so
> the only peo
Can we please get this moving forward. Even more users have reported to
have killed their system with this bug, and we can expect many many more
who haven't reported it. Why is this still "triaged" for Xenial? Xenial
is the current LTS so the bug there affects 20x the amount of users as
artful and
Just imagine what will happen if Dell releases a new firmware update for
one of their laptops... We've been lucky this hasn't happened yet, so
the only people running into this bug are people who have upgraded from
a version where fwupd wasn't enabled or new users.
--
You received this bug notifi
(Without secure boot that comment means)
On Tue, Nov 21, 2017, 02:11 Merlijn Sebrechts
wrote:
> I tested fwupdate in artful-proposed and it works and fixes the issue.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/173
I tested fwupdate in artful-proposed and it works and fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730343
Title:
firmware update breaks Ubuntu
To manage notifications about this
I've done uploads for 1.14.1 and 1.13.1 for artful and zesty
respectively.
** Tags removed: verification-needed-artful verification-needed-zesty
** Tags added: verification-failed-artful verification-failed-zesty
** Changed in: fwupdate-signed (Ubuntu Xenial)
Status: New => Triaged
** Cha
Maybe 1.14.1 and 1.13.1 (like done in xenial for 1.11)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730343
Title:
firmware update breaks Ubuntu
To manage notifications about this bug go to:
https
Xenial I was running into problems. thanks for rejecting the fwupdate-
signed package there until it's ready.
@Lukasz, it seems that fwupdate-signed isn't uploading from the feedback
on the upstream issue.
DEBUG Considering changefile
1/ubuntu/fwupdate-signed_1.14ubuntu0.2_amd64.changes
DEBUG F
Hello Merlijn, or anyone else affected,
Accepted fwupdate-signed into zesty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/fwupdate-
signed/1.13ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package
Hello Merlijn, or anyone else affected,
Accepted fwupdate into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/fwupdate/9-1ubuntu0.17.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
This bug was fixed in the package fwupdate - 9-3
---
fwupdate (9-3) unstable; urgency=medium
* Disable "Linux Firmware Updater" boot entry after installation
(LP: #1730343)
* update standards version
* Turn on hardening flags
-- Mario Limonciello Mon, 06 Nov 2017
09:17:1
@Lukasz,
It looks like it's in unapproved for both artful and bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730343
Title:
firmware update breaks Ubuntu
To manage notifications about this b
Hello Merlijn, or anyone else affected,
Accepted fwupdate-signed into artful-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fwupdate-
signed/1.14ubuntu0.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packag
Hello Merlijn, or anyone else affected,
Accepted fwupdate into artful-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/fwupdate/9-2ubuntu0.17.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
** Changed in: fwupdate (Ubuntu Xenial)
Status: New => Triaged
** Changed in: fwupdate (Ubuntu Zesty)
Status: New => Triaged
** Changed in: fwupdate (Ubuntu Artful)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Description changed:
- Two users have reported that fwupd breaks their Ubuntu installation
- because the "Ubuntu" EFI boot option disappears after an update.
+ [Impact]
- It might be best to consider turning off firmware updates until this
- issue is fixed.
+ * A few users have reported ins
Adding a fwupdate-signed task since this will require re-spinning all
fwup EFI binaries
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730343
Title:
firmware update breaks Ubuntu
To manage notifica
fixed in unstable via
https://anonscm.debian.org/cgit/uefi/fwupdate.git/commit/?id=7b6d96818db166456bbd9aafb031e7d990e06ef8,
should sync to ubuntu for bionic
** Changed in: fwupdate (Ubuntu Bionic)
Status: New => Fix Committed
** Also affects: fwupdate-signed (Ubuntu)
Importance: Undeci
Yeah I agree it's better avoided. It should SRU to 16.04's 05-2ubuntu5
too actually.
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
** Bug watch removed: github.com/juju-solutions/charms.reactive/issues #139
https://github.com/juju-solutions/charms.reactive/issues/139
** Also af
Would it make sense to SRU those fixes to 17.10 in any case? The
regression might be only in some situations but that's still rather
annoying and better to be avoided if we can...
** Changed in: fwupdate (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you
Adjusting various tasks for the relevant components. I'm pretty sure
this is a regression that is only getting exercised in certain
situations of boot entries.
Most notably there was a change was that fwupdate was effectively
updated to the "9" release in 0.5-2ubuntu5. This version adds the
"Lin
** Changed in: fwupd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730343
Title:
firmware update breaks Ubuntu
To manage notifications about this bug go to:
https://b
** Bug watch added: github.com/rhboot/fwupdate/issues #86
https://github.com/rhboot/fwupdate/issues/86
** Changed in: fwupd
Status: New => Unknown
** Changed in: fwupd
Remote watch: github.com/juju-solutions/charms.reactive/issues #139 =>
github.com/rhboot/fwupdate/issues #86
** Desc
** Changed in: fwupd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730343
Title:
firmware update breaks Ubuntu
To manage notifications about this bug go to:
https://b
50 matches
Mail list logo