Looking at the linked log it looks like the uefi self tests are failing
somehow with an invalid ESRT GUID of all zeros.
# FuDevice-DEBUG: using 2c1302f31806a0e0d57c377d99e18dae56351413 for
UEFI-ddc0ee61-e7f0-4e7d-acc5-c070a398838e-dev0
(/<>/obj-x86_64-linux-gnu/plugins/uefi/uefi-self-test:10011):
@juliank,
If it's unlikely that this is done before the release can we revert back
to the older shim for release and bump up to this new one after it comes
through?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
*** This bug is a duplicate of bug 1864223 ***
https://bugs.launchpad.net/bugs/1864223
Right now there is a regression in shim in Ubuntu 20.04. I've marked
this as a duplicate accordingly.
** This bug has been marked a duplicate of bug 1864223
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to
*** This bug is a duplicate of bug 1864223 ***
https://bugs.launchpad.net/bugs/1864223
Right now there is a regression in shim in Ubuntu 20.04. I've marked
this as a duplicate accordingly.
** This bug has been marked a duplicate of bug 1864223
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to
As confirmed on the upstream bug:
Commit
https://github.com/rhboot/shim/commit/e563bc3dcd17d91861d3b363ed19d30228f409e1
caused the issue, and it was already fixed by upstream commit
https://github.com/rhboot/shim/commit/1870bae796022f8bbf60465352eac329ff1d6ffd
--
You received this bug notificati
@Steve
Yes; from what I can gather this will definitely require source
modifications to shim.
The concern I have is that beta is the milestone that many more people
start to download and actually start testing Ubuntu images. With how
widely OEMs support UEFI firmware updates now, I expect a larg
*** This bug is a duplicate of bug 1864223 ***
https://bugs.launchpad.net/bugs/1864223
** This bug has been marked a duplicate of bug 1864223
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Changed in: shim (Ubuntu)
Milestone: None => ubuntu-20.04-beta
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
To manage
Public bug reported:
Starting today fwupd 1.3.9-2 can't build due to unable to find limits.h
on ppc64el and s390x.
cc -Ilibfwupd/ec37581@@fwupd@sha -Ilibfwupd -I../libfwupd -I. -I../
-I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid
-I/usr/include/glib-2.0 -I/usr/lib/s390
Felix:
I doubt it was 1.3.7-2 that worked last for you.
1.3.7-1 and 1.3.7-2 had a very significant bug where updates would hang due to
a bad commit introduced
(https://github.com/fwupd/fwupd/commit/44f55e2ee6df0b317df3029675afce86219cd9cd#diff-2f5c39c775e4cac7ebbeabed4cefca6a).
These were fixed
Public bug reported:
I have a fresh focal installation that I was attempting to do an apt
dist-upgrade.
As part of the upgrade, it was hung here:
Setting up snapd (2.44~pre1+20.04) ...
Installing new version of config file
/etc/apparmor.d/usr.lib.snapd.snap-confine.real ...
Created symlink
/et
If it does end up being boot order lock; there is nothing fwupd can do about
it. The kernel doesn't currently have the ability to notify fwupd that boot
order lock has been enabled in BIOS setup by this
vendor (see https://github.com/fwupd/fwupd/issues/1730)
** Bug watch added: github.com/fwup
@frio:
S3? Did you manually switch /sys/power/mem_sleep from s2idle to deep?
By default it should be going into suspend to idle (s2idle) not s3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855608
Check for boot order lock in your bios setup
On Wed, Mar 4, 2020, 06:30 Andreas Hasenack
wrote:
> Public bug reported:
>
> I got a notification (GUI) that a new firmware was available for my X1
> 5th gen. I selected to apply it, and rebooted. Usually I would see the
> update being applied while
Public bug reported:
Received during focal apt dist-upgrade
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libxvmc-dev 2:1.0.12-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
Boot
Public bug reported:
Running standard upgrades in focal.
Unpacking libip4tc-dev:amd64 (1.8.4-3ubuntu1) over (1.8.3-2ubuntu5) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-vyGukq/07-libip4tc-dev_1.8.4-3ubuntu1_amd64.deb
(--unpack):
trying to overwrite '/usr/include/libiptc/ipt_kernel
** Changed in: efibootmgr (Ubuntu Focal)
Status: Incomplete => Triaged
** Changed in: efibootmgr (Ubuntu Eoan)
Status: New => Triaged
** Changed in: efibootmgr (Ubuntu Bionic)
Status: New => Triaged
** Changed in: efibootmgr (Ubuntu Focal)
Importance: Undecided => Medium
Can you please confirm if this still happens with efibootmgr 17 (recently
uploaded to Focal)?
If so, this should probably be reported into the upstream bug tracker at
https://github.com/rhboot/efibootmgr/issues
** Changed in: efibootmgr (Ubuntu Focal)
Status: New => Incomplete
--
You re
This isn't really a feature request in efibootmgr as much as it would be
for GRUB.
** Changed in: efibootmgr (Ubuntu)
Importance: Undecided => Wishlist
** Package changed: efibootmgr (Ubuntu) => grub2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
I just confirmed with efibootmgr 17 in focal that this works properly.
I tested both the (-t) and (-T) arguments.
** Changed in: efibootmgr (Ubuntu)
Status: New => Fix Released
** Changed in: efibootmgr (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification becaus
I can see this fix is landed in the 0.9.0 release, so this is fixed in
Focal and later.
** Changed in: adcli (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: adcli (Ubuntu)
Status: New => Triaged
** Changed in: adcli (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: adcli (Ubuntu)
Status: Triaged => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
@Avery, there is a process for this, called the Ubuntu SRU process
(https://wiki.ubuntu.com/StableReleaseUpdates) that needs to be followed
to get a package updated in Ubuntu. Just filing the bug with the
problem will not make it happen.
** Also affects: adcli (Ubuntu Eoan)
Importance: Undecid
https://launchpad.net/ubuntu/+source/fwupd/1.3.7-2
** Changed in: fwupd (Ubuntu)
Status: Fix Committed => 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/1859180
Title:
Uninformat
I have to agree with Paul. This is a separate issue.
Issues like this often have a firmware component (such as the BIOS ACPI
primitives or touchpad firmware). Even if the messages are the same I
wouldn't categorize the error messages from another identically with the
problems from this specific
Upgrading python3-minimal to 3.8.0-3 which has been stuck in proposed
fixes this issue, but gobject-introspection doesn't reflect a
relationship upon this.
# apt show gobject-introspection |grep Dep
Depends: libc6 (>= 2.29), libffi7 (>= 3.3~20180313), libgirepository-1.0-1 (=
1.62.0-4ubuntu1), li
It appears to me to be happening because gobject-introspection only
ships a python file for python3.8 not python3.7 which is the default in
focal.
$ python3.7 /usr/bin/g-ir-scanner
Traceback (most recent call last):
File "/usr/bin/g-ir-scanner", line 99, in
from giscanner.scannermain import
Public bug reported:
Running g-ir-scanner doesn't work anymore after a recent upgrade with a
fully up to date focal:
Traceback (most recent call last):
File "/usr/bin/g-ir-scanner", line 99, in
from giscanner.scannermain import scanner_main
File
"/usr/lib/x86_64-linux-gnu/gobject-intros
Clevis release 12 has the fixes for this. When upgrading to clevis 12
this will be fixed.
** Changed in: clevis (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
I don't think that anyone should invest effort in sorting dracut unless
Ubuntu is actually going to be move to dracut.
Clevis 12 has initramfs support, so once that gets uploaded to Debian
and syncs from Debian to Ubuntu, you should be able to use that with
20.04 and later.
** Changed in: dracut
Regression for eoan: bug 1860536
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858590
Title:
fwupaa64.efi crashes on startup
To manage notifications about this bug go to:
https://bugs.launchpad.ne
This was fixed upstream as part of https://github.com/fwupd/fwupd/pull/1700.
It will be included in the 1.3.7 release.
** Changed in: fwupd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
When bringing this upstream, please include the following:
1) have you manually enabled fwupd-refresh.service? It's supposed to be
disabled by default (`systemctl show fwupd-refresh.service` output would
be useful)
2) Can you please attach your actual /run/private/motd.d/85-fwupd?
3) By the tim
Would your mind bringing this report upstream? It would be good to
discuss how to change this to make it more useful.
https://github.com/fwupd/fwupd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18591
> Is there any comment on why this issue only happened on the config
from customer, but not on our configs.
I would recommend to compare CPU stepping, perhaps a regression only
present in later CPU stepping after pre-production samples.
--
You received this bug notification because you are a mem
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813537
Title:
Wifi + bluetooth adapters are gone after sleep/wake
To manage notifica
IIRC xenial is not affected by this.
For bionic it would be good to either combine this with the existing SRU in
process or wait for that one to finish.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Here is the revised preinst that should cover the different problems outlined:
https://salsa.debian.org/efi-team/fwupdate/commit/85533b1f392399ee53f88e71091044a69dabbdc4
It hasn't yet been uploaded to unstable, would like to align the correct
thing to do with breaks/conflicts first and do upload w
> /boot/efi/EFI/ubuntu
'Yes, looks like that was missed in the conversion to a transition package.
It used to be cleaned up like this:
https://salsa.debian.org/efi-team/fwupdate/commit/b4daba89c567d4cf52f5deaab1ea2ee13039d03f#d0f1e7a780c0b1a978596fc9585a70ce84d2602d
I think we can bring that exa
The not-child extension is supported in fwupd 1.2.7 and later
(https://github.com/fwupd/fwupd/commit/b62c3a4fae1104c4a1052adc7b3196afa8c33307).
Ubuntu 18.04 currently contains fwupd 1.2.5.
There is currently an SRU in process to update to 1.2.10 as part of bug
1820768. This issue will be closed b
Archive administrator needs to release UEFI archives.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820768
Title:
[SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10
To manage n
Hello, any updates on this? It would be good to get any review comments
because the SRU will need to be modified again to include this as well:
https://github.com/fwupd/fwupd/commit/004a0624d05211e8436060bb7af6b0c6f2d805a3
(See https://blogs.gnome.org/hughsie/2019/12/11/improving-the-security-
mo
** Changed in: fwupd-signed (Ubuntu)
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/1852485
Title:
[SRU] Add AssumedAppArmorLabel to fwupd service
To manage notifi
I think for eoan this is missing a task for snapd to be successful. The
current snapd doesn't know anything about the fwupd interface
corresponding to a classic host system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Fixed in 0.3 release.
** Changed in: tpm-udev (Ubuntu)
Status: New => Fix Released
** Bug watch added: Debian Bug tracker #945362
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945362
** Also affects: tpm-udev (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945362
1.3.3-3 promoted to focal release pocket today fixes this, marking fix
released.
** Changed in: fwupd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Can we please follow up on this? This type of smooth upgrade stuff
needs to happen before focal too so that people can jump from
bionic->focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820768
T
1.3.3-3 promoted to focal release pocket today fixes this, marking focal
task as fix released.
** Changed in: fwupd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
s390x build problem is fixed and the new version migrated from proposed
into release pocket.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841595
Title:
[MIR] tpm2-tss
To manage notifications abou
That fix for fwupd to not use boltd on such systems is landed in fwupd
1.3.3 which is currently in focal-proposed.
** Changed in: bolt (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
> Note: The AAs might want to see this build error fixed before
promoting I guess.
The s390x build error solution is waiting to be merged upstream
(https://github.com/tpm2-software/tpm2-tss/pull/1549) and then will be
included.
--
You received this bug notification because you are a member of Ub
Focal has the fix coming in during Debian unstable sync. Setting this
task to fix committed.
** Changed in: fwupd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
[Availability]
Available in Ubuntu universe and Debian unstable, builds for all architectures
Ubuntu supports.
[Rationale]
tpm2-tss has an MIR in place
(https://bugs.launchpad.net/ubuntu/+source/tpm2-tss/+bug/1841595) that
requested that Debian bug
https://bugs.debian.or
As of tpm2-tss 2.3.1-2 all reported issues above should be resolved.
** Changed in: tpm2-tss (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Christian Ehrhardt
(paelzer)
** Changed in: tpm2-tss (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notificati
It appears tpm-udev was now accepted into unstable.
https://tracker.debian.org/pkg/tpm-udev
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841595
Title:
[MIR] tpm2-tss
To manage notifications abou
would you please try from the command line tool?
# fwupdmgr get-devices
# fwupdmgr update
Hopefully it will be more informative on the problem happening.
** Changed in: fwupd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs
Not from the SRU process. You would need to file something with bionic-
backports to get a backport done into the backports pocket.
** Changed in: clevis (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
The error comes from here:
https://github.com/rhboot/fwupdate/blob/master/linux/fwupdate.c#L417
I suspect your machine doesn't support this feature. Otherwise I would
recommend just going into BIOS setup and turning it on manually.
** Changed in: fwupdate (Ubuntu)
Status: Incomplete => In
Do you have bios admin password set? This tool can't work when it's
enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850285
Title:
Unable to enable (see error in description)
To manage notif
Assuming you ran that as root?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850285
Title:
Unable to enable (see error in description)
To manage notifications about this bug go to:
https://bugs.la
fwupd 1.3.2-5 is in focal proposed now and won't be able to migrate
until this MIR is finished.
CC @paulliu
I know that you had an ITP bug filed
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940807) for tpm-udev for
fixing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918973.
Can you p
Fixed in 1.3.2-5 in focal.
** Changed in: fwupd (Ubuntu)
Status: Fix Committed => 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/1793965
Title:
Firmware update daemon resets disp
@cyphermox,
Ping on this? fwupd 1.3.2 will sync to Ubuntu during focal cycle and
this MIR will become more important.
** Changed in: tpm2-tss (Ubuntu)
Assignee: Mario Limonciello (superm1) => Mathieu Trudel-Lapierre
(cyphermox)
--
You received this bug notification because you ar
5530 2-in-1 also isn't available for purchase with Ubuntu, so same boat.
It's (confusingly) a very different system than 5530 which /is/
available with Ubuntu.
** Summary changed:
- [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530] laptop keyboard &
touchpad not working at gdm screen af
XPS 9575 isn't (currently) available for purchase with Ubuntu. So yes,
it's below the radar for something that is typically tested, tracked, or
fixed from a BIOS or validation team perspective.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
In the 1.3.x release it moved to core18 and this problem seems to have
resolved itself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841630
Title:
snap version of fwupd prints tons of garbage
To
Setting up fonts-wqy-microhei (0.2.0-beta-3) ...
Setting up fwupdate (12-3bionic2) ...
Installing fwupx64.efi to EFI system partition.
cp: error writing '/boot/efi/EFI/ubuntu/fwupx64.efi': No space left on device
Not much that can be done from postinst scripts. But later versions of this
moved t
> It would be nice if one could boot the recovery, upgrade ubiquity,
from that ppa, and see if the autoinstall stuff still works correctly.
Yes confirmed that upgrading to ubiquity 19.10.20 from that PPA before
running installation works correctly now.
--
You received this bug notification becau
>I wonder if disks is preseeded or not.
Yes, a script detects the disk to install to, but it essentially ended up as:
d-i partman-auto/disk string /dev/sda
>It would be nice if one could boot the recovery, upgrade ubiquity, from
that ppa, and see if the autoinstall stuff still works correctly.
T
Ah right, so since we're using biggest_free that corrected line from xnox
wouldn't even run.
I opened up another bug for this regression so we don't lose it (bug 1847944),
so maybe we should move discussion there.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks for the quick turnaround! I was able to do some quick testing
with it, and it does fix the problem.
A few comments though:
* This line:
$(mount | grep -qF "$device on /cdrom ") && continue
Is what was in 134ubuntu10, so is that what you actually meant? It seems like
it might want to be:
Public bug reported:
Partman-auto 134ubuntu11 added a new check to try to resolve bug 1845571
but in doing so, broke OEM installation from hard disk.
OEM installation from hard disk will place the ubuntu ISO image into a
recovery partition and boot from that to install. It is preseeded such
that
Yes; I can confirm that is root cause; IE removing that new line in
/lib/partman/lib/auto-shared.sh resolves 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/1845571
Title:
ubiquity offers i
I think this change broke OEM installation from a recovery partition on
HDD. Can't seem to install to it anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845571
Title:
ubiquity offers instal
#1:
Thanks! I'll get that added to the default factory install kernel
command line.
Regarding how to find this out sooner, I think some discussions internal
to Canonical OEM services would be a good idea. Some automation in
continuous integration for daily images doing tests like how factory
in
Public bug reported:
OEM factory installation typically puts the Ubuntu media onto a recovery
partition and uses a preseeding recipe to install into the remaining
free space on the disk.
This casper change appears to have broken that behavior:
casper (1.415) eoan; urgency=medium
* Persist log
** Changed in: fwupd (Ubuntu Eoan)
Status: Confirmed => 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/1843735
Title:
fwupd ftbfs in eoan
To manage notifications about this bug g
Before I realized there was a second problem (since my local test build
worked) I uploaded 1.2.10-1ubuntu2. I fixed the second problem in a
second upload, same version with the expectation an archive
administrator would reject the first and accept the second.
Both are in the unapproved queue, so
Anyway, if that's the new environment to deal with, I'll open a PR
upstream to skip the test in that case too.
https://github.com/fwupd/fwupd/pull/1398
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/184
Did something change on some of the buildds to have a machine id but
make it empty? The self test code skips machine ID tests if it's not
present: https://github.com/fwupd/fwupd/blob/master/libfwupd/fwupd-self-
test.c#L532
--
You received this bug notification because you are a member of Ubuntu
Lots of people have used the logitech plugin now, and it's definitely
functional. Any other corner cases, please open new bugs, preferably
upstream (https://github.com/fwupd/fwupd).
** Changed in: fwupd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because
FYI That did sync back to Ubuntu eoan as well. I think that as part of
transitioning 18.04, it should come back to 18.04 with the updated SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820768
Ti
I'm marking eoan as fixed, as it has 1.2.10 which contains the
workaround to avoid using synaptics mst on amdgpu devices.
The kernel tasks is still open as this is still a real kernel problem.
** Changed in: fwupd (Ubuntu Eoan)
Status: Triaged => Fix Released
** Changed in: fwupd (Ubuntu
your platform is supported on fwupd it looks like from that picture. if
you build a cab, you can install it using # fwupdmgr install file.cab
If you have problems with fwupd, please report them to
https://github.com/fwupd/fwupd
closing "this" particular issue as won't fix because fwupdate is no
The fix actually has been re-directed to the 1.3 series; IE 1.3.1 has
it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793965
Title:
Firmware update daemon resets displays connected to Dell TB16 d
SRU for 1.2.10 is being tracked here:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1820768
** Changed in: fwupd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I would guess this needs to be backported.
https://github.com/fwupd/fwupd/commit/b4627629cdaadd1a75d7c650b7c5973fcd18dfb0
On Mon, Sep 16, 2019, 04:15 Brian Murray wrote:
> ** Also affects: fwupd (Ubuntu Eoan)
>Importance: High
>Status: Confirmed
>
> ** Tags removed: rls-ee-incoming
Here's link for what's happening in Debian at 12-6.
https://tracker.debian.org/news/1061561/accepted-fwupdate-12-6-source-into-unstable/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820768
Title:
I've added series for disco and bionic to track the same actions that
happen for eoan.
Also for eoan, fwupdate 12-6 as a transition package that removes all
fwupdate binaries during apt upgrade is in debian unstable now and in
Ubuntu NEW queue for eoan.
** Also affects: lubuntu-meta (Ubuntu Disco
Settings devices firmware? This sounds like it is running system 76
firmware manager GUI.
Can you please check fwupdmgr command line tool to see that it also agreed upon
updates?
fwupdmgr get-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
You're missing the changes that went in for 0.2 in your branch, at least the
changelog should be mentioned before the 0.3 release. I did send you these
over email in lieu of availability to commit to the branch yet.
Also you need to drop the non-x86 architectures in debian/control, and remove
t
@kurshid-alam:
>I did not respond because I was busy with breakage in other unity related
>packages. You should give us time to do that specially when you filed the bug
>one week ago.
This bug has been actually a response to bug #1820768 which has been
open a very long time. A simple "I'm worki
fwupdate 12-6 was uploaded into Debian to do a transition there->fwupd.
After bullseye release will propose it to remove from Debian archive.
It's up to Ubuntu archive admins to either accept the same transition
package (I tested it on Ubuntu w/ a local apt repo and it worked just
fine for me) or
Here is that uploaded package:
https://launchpad.net/ubuntu/+source/ubuntu-unity-meta/0.2
** Changed in: ubuntu-unity-meta (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
For ubuntu-unity-meta I asked the maintainer in #1842014 to update it
but they didn't yet. Considering the urgency here, I took matters into
my hands:
1) Ported https://code.launchpad.net/~unity7maintainers/ubuntu-seeds
/ubuntu-unity.cosmic -> https://code.launchpad.net/~ubuntu-core-dev
/ubuntu-s
Alternatively this commit I suspect should help:
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=1ffdb51f28e8ec6be0a2b812c1765b5cf5c44a8f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Sure, if you stage something in a PPA or so I can do some tests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841595
Title:
[MIR] tpm2-tss
To manage notifications about this bug go to:
https://bu
I would suspect that's no problem, but @cyphermox is actually maintainer
in Debian, so I think he should comment if those are doable :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841595
Title:
[
Christian,
Ff I realize was confusing. I meant FF release not feature freeze.
Sorry!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841595
Title:
[MIR] tpm2-tss
To manage notifications about this
At least for the 2.x release sapi.pc isn't included, so dropping this
bug against disco and eoan.
I also checked the version in bionic (1.0-1) and don't reproduce the
behavior.
$ cat usr/lib/x86_64-linux-gnu/pkgconfig/sapi.pc
Name: sapi
Description: TPM2 System API library.
URL: https://github.co
501 - 600 of 6946 matches
Mail list logo
