Description of problem: When systemd starts the service an invalid argument error will shown. Version-Release number of selected component (if applicable): dbxtool-8-5.fc28.x86_64 How reproducible: Every time Steps to Reproduce: 1. Boot the system 2. systemctl status dbxtool Actual results: ● dbxtool.service - Secure Boot DBX (blacklist) updater Loaded: loaded (/usr/lib/systemd/system/dbxtool.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2018-07-22 14:44:06 CEST; 4min 49s ago Process: 1285 ExecStart=/usr/bin/dbxtool -a /usr/share/dbxtool/ -q (code=exited, status=1/FAILURE) Main PID: 1285 (code=exited, status=1/FAILURE) Jul 22 14:44:06 foo.foo.foo systemd[1]: Started Secure Boot DBX (blacklist) updater. Jul 22 14:44:06 foo.foo.foo dbxtool[1285]: Applying 1 updates Jul 22 14:44:06 foo.foo.foo dbxtool[1285]: Applying "DBXUpdate-2016-08-09-13-16-00.bin" 2010-3-6 19:17:21 Jul 22 14:44:06 foo.foo.foo dbxtool[1285]: Could not apply database update "DBXUpdate-2016-08-09-13-16-00.bin": Invalid argument Jul 22 14:44:06 foo.foo.foo dbxtool[1285]: Cannot Continue.: Invalid argument Jul 22 14:44:06 foo.foo.foo systemd[1]: dbxtool.service: Main process exited, code=exited, status=1/FAILURE Jul 22 14:44:06 foo.foo.foo systemd[1]: dbxtool.service: Failed with result 'exit-code'. Expected results: No error
I see the same problem on several machines. What's your output of /usr/bin/dbxtool -a /usr/share/dbxtool/ -v
/usr/bin/dbxtool -a /usr/share/dbxtool/ -v will return: Getting next EFI_SIGNATURE_DATA Getting next ESL buffer Getting next EFI_SIGNATURE_DATA Getting next EFI_SIGNATURE_LIST Attempting to identify filetype: va2 guid is {pkcs7_cert} guid table guid is {pkcs7_cert} ft_append_timestamp is 2010-03-06 19:17:21 Attempting to apply 1 updates Sorting updates list Checking if "DBXUpdate-2016-08-09-13-16-00.bin" has been applied. Getting next EFI_SIGNATURE_DATA Getting next ESL buffer Update entry is not applied. Update "DBXUpdate-2016-08-09-13-16-00.bin" is not applied Applying 1 updates Applying "DBXUpdate-2016-08-09-13-16-00.bin" 2010-3-6 19:17:21 Could not apply database update "DBXUpdate-2016-08-09-13-16-00.bin": Invalid argument Cannot Continue.: Invalid argument error trace: efivarfs.c:363 efivarfs_set_variable(): write failed: Bad file descriptor efivarfs.c:388 efivarfs_append_variable(): efivarfs_set_variable failed: Invalid argument lib.c:113 efi_append_variable(): ops->append_variable() failed: Invalid argument
This seems a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1593258
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Same on F29
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.