Version-Release number of selected component: pcsc-lite-1.9.9-3.fc38 Additional info: reporter: libreport-2.17.10 type: CCpp reason: pcscd killed by SIGSEGV journald_cursor: s=c6a973168b244dfbb73324fedd0e36a4;i=632d75;b=8dbc8b87753d4a7ba0cb5d0748deda94;m=65bb51ad;t=5ff0093cefe2f;x=c84dbcf931eb5bb8 executable: /usr/sbin/pcscd cmdline: /usr/sbin/pcscd --foreground --auto-exit cgroup: 0::/system.slice/pcscd.service rootdir: / uid: 0 kernel: 6.3.8-200.fc38.x86_64 package: pcsc-lite-1.9.9-3.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: IsClientAuthorized Truncated backtrace: Thread no. 1 (3 frames) #0 IsClientAuthorized at /usr/src/debug/pcsc-lite-1.9.9-3.fc38.x86_64/src/auth.c:86 #1 ContextThread at /usr/src/debug/pcsc-lite-1.9.9-3.fc38.x86_64/src/winscard_svc.c:333 #3 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Created attachment 1973584 [details] File: proc_pid_status
Created attachment 1973585 [details] File: maps
Created attachment 1973586 [details] File: limits
Created attachment 1973587 [details] File: environ
Created attachment 1973588 [details] File: open_fds
Created attachment 1973589 [details] File: mountinfo
Created attachment 1973590 [details] File: os_info
Created attachment 1973591 [details] File: cpuinfo
Created attachment 1973592 [details] File: core_backtrace
Created attachment 1973593 [details] File: exploitable
Created attachment 1973594 [details] File: dso_list
Created attachment 1973595 [details] File: backtrace
Do you have some idea what was going on when you encountered this crash?
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.