Version-Release number of selected component: rarian-compat-0.8.1-30.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.kde.khelpcenter cmdline: /usr/bin/rarian-sk-get-cl en scrollkeeper_cl.xml crash_function: __strcmp_avx2 executable: /usr/bin/rarian-sk-get-cl journald_cursor: s=9c62206e08b64f979ae7ef9fbf796a40;i=58915;b=1a163d07f85347ab8c1973cea523d832;m=2e481edf3e;t=5e65c59536266;x=3a8a6fba31d3e95e kernel: 5.18.16-200.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #0 __strcmp_avx2 at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:284 #1 scan_directory at /usr/src/debug/rarian-0.8.1-30.fc36.x86_64/librarian/rarian-main.c:297 #6 scan_directories at /usr/src/debug/rarian-0.8.1-30.fc36.x86_64/librarian/rarian-main.c:237
Created attachment 1908779 [details] File: backtrace
Created attachment 1908780 [details] File: core_backtrace
Created attachment 1908781 [details] File: cpuinfo
Created attachment 1908782 [details] File: dso_list
Created attachment 1908783 [details] File: environ
Created attachment 1908784 [details] File: exploitable
Created attachment 1908785 [details] File: limits
Created attachment 1908786 [details] File: maps
Created attachment 1908787 [details] File: mountinfo
Created attachment 1908788 [details] File: open_fds
Created attachment 1908789 [details] File: proc_pid_status
*** Bug 2080611 has been marked as a duplicate of this bug. ***
Looks like use of an invalid pointer when scanning directories: suffix = strrchr (full_name, '.'); if (!strcmp (suffix, ".document")) { If the filename doesn't have a period, such as if it is "README" or similar, then "suffix" is NULL, and boom. I'm currently trying to figure out if I can find an upstream place to get a patch in.
FEDORA-2023-8db973b2bc has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-8db973b2bc
FEDORA-2023-8db973b2bc has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-e2438c189b has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e2438c189b
FEDORA-2023-e643e6375d has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e643e6375d
FEDORA-2023-e2438c189b has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-e2438c189b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e2438c189b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-e643e6375d has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-e643e6375d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e643e6375d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-e643e6375d has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-e2438c189b has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.