Version-Release number of selected component: tpm2-abrmd-2.4.0-1.fc34 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/system.slice/tpm2-abrmd.service cmdline: /usr/sbin/tpm2-abrmd crash_function: random_get_uint64 executable: /usr/sbin/tpm2-abrmd journald_cursor: s=1ff475feec864198851f6e2b301d4f94;i=2da5;b=9016c7e0c0404785b16544de5b81412e;m=1026ea665c;t=5c2c722463c21;x=4586d7e33ad2af88 kernel: 5.11.17-300.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 59 Truncated backtrace: Thread no. 1 (5 frames) #4 random_get_uint64 at src/random.c:148 #5 generate_id_pid_mix_from_invocation at src/ipc-frontend-dbus.c:281 #6 on_handle_create_connection at src/ipc-frontend-dbus.c:363 #7 ffi_call_unix64 at ../src/x86/unix64.S:76 #8 ffi_call at ../src/x86/ffi64.c:525
Created attachment 1785733 [details] File: backtrace
Created attachment 1785734 [details] File: core_backtrace
Created attachment 1785735 [details] File: cpuinfo
Created attachment 1785736 [details] File: dso_list
Created attachment 1785737 [details] File: environ
Created attachment 1785738 [details] File: limits
Created attachment 1785739 [details] File: maps
Created attachment 1785740 [details] File: mountinfo
Created attachment 1785741 [details] File: open_fds
Created attachment 1785742 [details] File: proc_pid_status
Created attachment 1785743 [details] File: var_log_messages
*** This bug has been marked as a duplicate of bug 1957774 ***
*** Bug 1986317 has been marked as a duplicate of this bug. ***
It seems pretty rude to close "publicly" viewable bugs as duplicates of private/restricted bugs. How are the unprivileged supposed to follow the progress of the issue and know when the issue is resolved?
*** Bug 2003435 has been marked as a duplicate of this bug. ***
*** Bug 2008372 has been marked as a duplicate of this bug. ***
*** Bug 2016772 has been marked as a duplicate of this bug. ***
*** Bug 2016958 has been marked as a duplicate of this bug. ***