Home / ubuntu / Questions

Questions[fwupd](ubuntu)

Martin Hope
Christian
Asked: 2020-10-29 08:53:41 +0800 CST
  • 6

I upgraded my Thinkpad laptop from Ubuntu 20.04 to 20.10. All went well. However, there's now firmware updates available but when I try to apply them I get an error saying:

Unable to update "System Firmware": missing signed bootloader for secure boot: /usr/libexec/fwupd/efi/-fwupdx64.efi.signed can not be found

How do I fix this so I can update firmware? Shouldn't this be taken care of during the system upgrade?

upgrade firmware fwupd
Martin Hope
Jaydin
Asked: 2020-05-25 19:03:45 +0800 CST
  • 11

Ubuntu Software (aka Gnome Software) on Ubuntu 18.04 has started giving the error message: Unable to get a list of updates: remote lvfs has no cache signature

Ubuntu Software error message

This issue started recently and, based on a bit of online research, it may be related to Linux Vendor Firmware Service (LVFS) and the fwupd application.

Here are the installed fwupd packages:

~$ apt list --installed | grep fwupd
fwupd/bionic-updates,now 1.2.10-1ubuntu2~ubuntu18.04.3 amd64 [installed]
fwupd-signed/bionic-updates,now 1.10~ubuntu18.04.3+1.2.10-1ubuntu2~ubuntu18.04.3 amd64 [installed,automatic]
fwupdate/bionic-updates,now 12-7~ubuntu18.04.3 amd64 [installed]
fwupdate-signed/bionic-updates,now 12-7~ubuntu18.04.3 amd64 [installed]
libfwupd2/bionic-updates,now 1.2.10-1ubuntu2~ubuntu18.04.3 amd64 [installed,automatic]

and

~$ snap list | grep fwupd
fwupd 1.4.2 2084  latest/stable    richard-hughes  classic
software-center gnome-software fwupd
Martin Hope
codear
Asked: 2019-08-18 13:20:44 +0800 CST
  • 11

I have been checking some systemd-analyze outputs and I actually don't have a crucial problem with my boot time but just wondering whether I can decrease it further. I'd like to mention that I'm using an SSD and Ubuntu is my only OS.

systemd-analyze
Startup finished in 5.450s (firmware) + 565ms (loader) + 2.632s (kernel) + 10.086s (userspace) = 18.734s 
graphical.target reached after 10.071s in userspace

systemd-analyze blame
          6.607s NetworkManager-wait-online.service
          5.660s fwupd.service
          5.042s bolt.service
          4.134s plymouth-quit-wait.service
          1.579s dev-sda2.device
          1.552s systemd-backlight@backlight:intel_backlight.service
          1.367s plymouth-read-write.service
          1.211s snapd.service
           903ms systemd-logind.service
           572ms systemd-journald.service
           555ms dev-loop9.device
           523ms dev-loop6.device
           515ms man-db.service
           499ms dev-loop8.device
           478ms dev-loop5.device
           472ms dev-loop13.device
           448ms dev-loop7.device
           441ms dev-loop11.device
           438ms dev-loop10.device
           432ms dev-loop12.device
           415ms udisks2.service
           406ms dev-loop14.device
           319ms snap-gnome\x2d3\x2d28\x2d1804-71.mount

graphical.target @10.071s
└─multi-user.target @10.071s
  └─kerneloops.service @10.042s +27ms
    └─network-online.target @10.032s
      └─NetworkManager-wait-online.service @3.422s +6.607s
        └─NetworkManager.service @3.224s +186ms
          └─dbus.service @3.218s
            └─basic.target @3.211s
              └─sockets.target @3.211s
                └─snapd.socket @3.208s +2ms
                  └─sysinit.target @3.205s
                    └─systemd-backlight@backlight:intel_backlight.service @1.468s +1.552s
                      └─system-systemd\x2dbacklight.slice @1.467s
                        └─system.slice @212ms
                          └─-.slice @212ms
boot network-manager thunderbolt fwupd 19.04
Martin Hope
Danie de Jager
Asked: 2018-05-04 23:38:53 +0800 CST
  • 13

When I run the command to update the firmware it states to manually be put in update mode. I've searched for an explanation but can't find anything that helps.

# fwupdmgr -v update
Downloading RQR12.07_B0029 for Unifying [runtime]...
Updating RQR12.07_B0029 on Unifying [runtime]...
Decompressing…         
Device Unifying [runtime] needs to manually be put in update mode

Output from fwupdmgr get-devices:

Unifying [runtime]
  Guid:                 9d131a0c-a606-580f-8eda-80587250b8d6
  UniqueID:             com.logitech.Unifying.RQR12.firmware
  DeviceID:             usb:00:01
  Description:          <p>A Unifying receiver allows you to connect multiple compatible keyboards and mice to a laptop or desktop computer with a single USB receiver. Updating the firmware on your Unifying receiver improves performance, adds new features and fixes security issues.</p>
  Plugin:               unifying
  Flags:                allow-online|supported|needs-bootloader
  DeviceVendor:         Logitech
  Version:              003.000.12003
  VersionBootloader:    BL.0aa.0aa
  Created:              2018-05-04
  AppstreamId:          com.logitech.Unifying.RQR12.firmware
  Summary:              Firmware for the Logitech Unifying receiver
  UpdateDescription:    <p>This release addresses an unencrypted keystroke injection issue known as Bastille security issue #11. The vulnerability is complex to replicate and would require a hacker to be physically close to a target.</p>
  UpdateVersion:        RQR12.07_B0029
  UpdateHash:           d0d33e760ab6eeed6f11b9f9bd7e83820b29e970
  UpdateChecksumKind:   sha1
  License:              Proprietary
  UpdateUri:            https://fwupd.org/downloads/938fec082652c603a1cdafde7cd25d76baadc70d-Logitech-Unifying-RQR12.07_B0029.cab
  UrlHomepage:          http://support.logitech.com/en-us/software/unifying
  Vendor:               Logitech
  Trusted:              none
logitech-unifying fwupd