From: haunma <haunma@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] fwupd refresh fails with "signatures were required, but none supplied"
Date: Thu, 28 Dec 2023 01:30:31 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47932@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
New issue by haunma on void-packages repository
https://github.com/void-linux/void-packages/issues/47932
Description:
### Is this a new report?
Yes
### System Info
Void 6.7.0-rc6_1 x86_64 AuthenticAMD uptodate rFF
### Package(s) Affected
fwupd-1.9.10
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
After installing fwupd, it should be possible to check for firmware updates using
`fwupdmgr refresh`
without error.
### Actual behaviour
```
$ sudo fwupdmgr refresh
WARNING: UEFI capsule updates not available or enabled in firmware setup
See https://github.com/fwupd/fwupd/wiki/PluginFlag:capsules-unsupported for more information.
Updating lvfs
Downloading… [ \ ]
(fwupdmgr:2222): Fwupd-CRITICAL **: 16:25:28.943: fwupd_checksum_guess_kind: assertion 'checksum != NULL' failed
Downloading… [***************************************]
Failed to update metadata for lvfs: signatures were required, but none supplied
```
### Steps to reproduce
As root,
1. xbps-install fwupd
2. fwupdmgr refresh
next reply other threads:[~2023-12-28 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 0:30 haunma [this message]
2023-12-29 9:17 ` sgn
2023-12-29 21:01 ` haunma
2023-12-31 16:15 ` [ISSUE] [CLOSED] " sgn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47932@inbox.vuxu.org \
--to=haunma@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).