stable
FEDORA-2022-e4be550a47 created by pjones a month ago for Fedora 36

Fixes a command line handling bug.

How to install

sudo dnf upgrade --refresh --advisory=FEDORA-2022-e4be550a47

This update has been submitted for testing by pjones.

a month ago

This update's test gating status has been changed to 'ignored'.

a month ago
User Icon vwbusguy commented & provided feedback a month ago

$ sudo mokutil -s Aborted

$ sudo mokutil --sb-state​ mokutil: unrecognized option '--sb-state​' Usage: mokutil OPTIONS [ARGS...] ...

$ rpm -q mokutil mokutil-0.6.0-2.fc36.x86_64

BZ#2087066 mokutil -s aborts without error message
User Icon vwbusguy commented & provided feedback a month ago

I'm guessing it's related to the recent usage patch. Seems to work fine compiled from scratch against upstream.

src]$ sudo ./mokutil --sb-state
SecureBoot disabled

src]$ sudo ./mokutil -s
Usage:
  mokutil OPTIONS [ARGS...]

Options:
  --help                Show help
  --list-enrolled           List the enrolled keys
User Icon vwbusguy commented & provided feedback a month ago

So, after compiling and running mokutil from upstream source and running it, the Fedora RPM command also oddly started working. I did not sudo make install and rpm -V mokutil returns empty. I also removed the two build deps I installed (efivar-devel keyutils-libs-devel) and it still works.

In order to rule out a random fluke on my laptop, I ran sudo mokutil --bs-state on another f36 laptop and it returned the original error and usage instead of the secureboot status. It working after compiling it locally as a non-root user without make install makes no sense to me, but I can reproduce it on multiple f36 machines of different brands.

This update has been pushed to testing.

a month ago
User Icon geraldosimiao commented & provided feedback a month ago
karma

Generally funcional yes, but the coredump bug still there:


rpm -qa|grep mokutil ==> mokutil-0.6.0-2.fc36.x86_64
mokutil --sb-state ==> SecureBoot disabled
mokutil -s ==> Abortado (imagem do núcleo gravada)

coredumpctl info
       PID: 6979 (mokutil)
       UID: 1000 (geraldo)
       GID: 1000 (geraldo)
    Signal: 6 (ABRT)
 Timestamp: Wed 2022-05-25 15:17:48 -03 (56s ago)
Command Line: mokutil -s
Executable: /usr/bin/mokutil
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.konsole-cc4451fdcc194b2e98e5b50fe77f9a23.scope
      Unit: user@1000.service
 User Unit: app-org.kde.konsole-cc4451fdcc194b2e98e5b50fe77f9a23.scope
     Slice: user-1000.slice
 Owner UID: 1000 (geraldo)
         Storage: /var/lib/systemd/coredump/core.mokutil.1000.613f9a483d494871ad63650de27d7ad0.6979.1653502668000000.zst (present)
 Disk Size: 78.9K
   Message: Process 6979 (mokutil) of user 1000 dumped core.
BZ#2087066 mokutil -s aborts without error message

pjones edited this update.

New build(s):

  • mokutil-0.6.0-3.fc36

Removed build(s):

  • mokutil-0.6.0-2.fc36

Karma has been reset.

a month ago

This update has been submitted for testing by pjones.

a month ago
User Icon pjones commented & provided feedback a month ago

Yeah, so what happened here is someone cleaned up the spec file and accidentally broke patch application when they did. Should be right in -3.

This update has been pushed to testing.

a month ago
User Icon pbrobinson commented & provided feedback a month ago
karma

Works on x86 and aarch64

BZ#2087066 mokutil -s aborts without error message
User Icon pwalter commented & provided feedback a month ago
karma

Works

This update can be pushed to stable now if the maintainer wishes

a month ago

This update has been submitted for stable by pjones.

a month ago

This update has been pushed to stable.

a month ago

Please login to add feedback.

Metadata
Type
bugfix
Severity
low
Karma
2
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
7 days
Dates
submitted
a month ago
in testing
a month ago
in stable
a month ago
modified
a month ago
BZ#2087066 mokutil -s aborts without error message
0
1

Automated Test Results