Bug 1760671 - during update, scriptlet fails: pesign.service not found
Summary: during update, scriptlet fails: pesign.service not found
Keywords:
Status: CLOSED DUPLICATE of bug 1776680
Alias: None
Product: Fedora
Classification: Fedora
Component: fwupd
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-11 05:37 UTC by D. Hugh Redelmeier
Modified: 2020-09-14 19:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-14 19:15:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description D. Hugh Redelmeier 2019-10-11 05:37:34 UTC
Description of problem:

update to fwupd-1.2.11-1.fc31.x86_64, scriptlet fails.
Version-Release number of selected component (if applicable):

fwupd-1.2.11-1.fc31.x86_64

How reproducible:
unknown

Steps to Reproduce:

1. sudo dnf update fwupd


Actual results:
  Running scriptlet: fwupd-1.2.11-1.fc31.x86_64                         132/230 
  Cleanup          : fwupd-1.2.11-1.fc31.x86_64                         132/230 
  Running scriptlet: fwupd-1.2.11-1.fc31.x86_64                         132/230 
Failed to try-restart pesign.service: Unit pesign.service not found.


Expected results:

no diagnostic

Additional info:

Comment 1 james 2020-01-06 18:44:11 UTC
I have this issue as well.

During update I get the following message:
  Running scriptlet: fwupd-1.3.5-1.fc31.x86_64                            38/40 
  Cleanup          : fwupd-1.3.5-1.fc31.x86_64                            38/40 
  Running scriptlet: fwupd-1.3.5-1.fc31.x86_64                            38/40 
Failed to try-restart pesign.service: Unit pesign.service not found

Should I be alarmed?  It is the UEFI signing service, and so I would have thought that it would be installed on my machine.  I have checked and pesign is not installed, but I have never had the error before.

Comment 2 Mark Harig 2020-01-13 15:52:11 UTC
This appears to be a duplicate of bug #1776680, which has a description of the source of the problem.

Comment 3 Richard Hughes 2020-09-14 19:15:30 UTC

*** This bug has been marked as a duplicate of bug 1776680 ***


Note You need to log in before you can comment on or make changes to this bug.