[
Date Prev
][
Date Next
] [
Thread Prev
][
Thread Next
] [
Date Index
] [
Thread Index
]
Bug#1089119: I can confirm this bug
To
:
1089119@bugs.debian.org
Subject
: Bug#1089119: I can confirm this bug
From
: Mario Limonciello <
superm1@gmail.com
>
Date
: Sun, 26 Oct 2025 13:01:17 -0500
Message-id
: <
[🔎]
29bc98fe-414e-413d-bc4a-289414e9db6c@gmail.com
>
Reply-to
: Mario Limonciello <
superm1@gmail.com
>,
1089119@bugs.debian.org
In-reply-to
: <26646.11929.782876.974303@cs.uni-koeln.de>
References
: <26646.11929.782876.974303@cs.uni-koeln.de> <26646.11929.782876.974303@cs.uni-koeln.de> <173343262849.114654.9679038379646285589.reportbug@gympie-lx2>
I believe this issue should be fixed in the current version. We had
some plugins overzealously probing devices they shouldn't. Can you
please confirm?
Reply to:
debian-efi@lists.debian.org
Mario Limonciello (on-list)
Mario Limonciello (off-list)
Prev by Date:
Bug#1119064: fwupd: fails to start with undefinded symbol
Next by Date:
Bug#1112464: fwupdmgr: "Secure boot is enabled, but shim isn't installed to EFI/systemd/shimx64.efi" when updating firmware
Previous by thread:
Bug#1119064: marked as done (fwupd: fails to start with undefinded symbol)
Next by thread:
Bug#1112464: fwupdmgr: "Secure boot is enabled, but shim isn't installed to EFI/systemd/shimx64.efi" when updating firmware
Index(es):
Date
Thread