Description of problem: Just testing mokutil bug: typing mokutil -s Version-Release number of selected component: mokutil-2:0.6.0-2.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.konsole-571a982c77ef4adbaf67ad198a197ece.scope cmdline: mokutil -s crash_function: main executable: /usr/bin/mokutil journald_cursor: s=7deea851271e4a0e8abb299018619297;i=9cbb;b=613f9a483d494871ad63650de27d7ad0;m=5fd8c403;t=5dfda065550dc;x=e2ad4a5acbf27b81 kernel: 5.17.9-300.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (0 frames)
Created attachment 1883510 [details] File: backtrace
Created attachment 1883511 [details] File: core_backtrace
Created attachment 1883512 [details] File: cpuinfo
Created attachment 1883513 [details] File: dso_list
Created attachment 1883514 [details] File: environ
Created attachment 1883515 [details] File: limits
Created attachment 1883516 [details] File: maps
Created attachment 1883517 [details] File: mountinfo
Created attachment 1883518 [details] File: open_fds
Created attachment 1883519 [details] File: proc_pid_status
Sorry, ABRT created duplicate of this bug here https://bugzilla.redhat.com/show_bug.cgi?id=2087066 *** This bug has been marked as a duplicate of bug 2087066 ***