Version-Release number of selected component: PackageKit-1.2.6-6.fc38 Additional info: reporter: libreport-2.17.11 type: CCpp reason: packagekitd killed by SIGSEGV journald_cursor: s=a0dd4185c0834e46bf7af7432d421c45;i=1131d4;b=5692acdb91cc4f0d89d3418387152b82;m=2f2c202;t=602531975f2f4;x=2d0d61879aca620b executable: /usr/libexec/packagekitd cmdline: /usr/libexec/packagekitd cgroup: 0::/system.slice/packagekit.service rootdir: / uid: 0 kernel: 6.4.6-200.fc38.x86_64 package: PackageKit-1.2.6-6.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: yaml_parser_update_buffer Truncated backtrace: Thread no. 1 (22 frames) #0 yaml_parser_update_buffer at /usr/src/debug/libyaml-0.2.5-9.fc38.x86_64/src/reader.c:429 #1 yaml_parser_scan_plain_scalar at /usr/src/debug/libyaml-0.2.5-9.fc38.x86_64/src/scanner.c:3514 #2 yaml_parser_fetch_plain_scalar at /usr/src/debug/libyaml-0.2.5-9.fc38.x86_64/src/scanner.c:1904 #3 yaml_parser_fetch_next_token at /usr/src/debug/libyaml-0.2.5-9.fc38.x86_64/src/scanner.c:1040 #4 yaml_parser_fetch_more_tokens at /usr/src/debug/libyaml-0.2.5-9.fc38.x86_64/src/scanner.c:847 #5 yaml_parser_parse_indentless_sequence_entry at /usr/src/debug/libyaml-0.2.5-9.fc38.x86_64/src/parser.c:796 #6 yaml_parser_state_machine at /usr/src/debug/libyaml-0.2.5-9.fc38.x86_64/src/parser.c:261 #7 yaml_parser_parse at /usr/src/debug/libyaml-0.2.5-9.fc38.x86_64/src/parser.c:188 #8 modulemd_yaml_parse_document_type_internal at ../modulemd/modulemd-yaml-util.c:1066 #9 modulemd_yaml_parse_document_type at ../modulemd/modulemd-yaml-util.c:1269 #10 modulemd_module_index_update_from_parser at ../modulemd/modulemd-module-index.c:325 #11 modulemd_module_index_update_from_string at ../modulemd/modulemd-module-index.c:744 #12 libdnf::ModuleMetadata::addMetadataFromString(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int) at /usr/include/c++/13/bits/basic_string.h:222 #13 libdnf::ModulePackageContainer::add(_DnfSack*) at /usr/include/c++/13/bits/unique_ptr.h:199 #14 (anonymous namespace)::readModuleMetadataFromRepo at /usr/src/debug/libdnf-0.70.2-1.fc38.x86_64/libdnf/dnf-sack.cpp:2373 #15 dnf_sack_filter_modules_v2[abi:cxx11](_DnfSack*, libdnf::ModulePackageContainer*, char const**, char const*, char const*, bool, bool, bool) at /usr/src/debug/libdnf-0.70.2-1.fc38.x86_64/libdnf/dnf-sack.cpp:2591 #16 dnf_sack_filter_modules(DnfSack*, GPtrArray*, char const*, char const*) at /usr/src/debug/libdnf-0.70.2-1.fc38.x86_64/libdnf/dnf-sack.cpp:2570 #17 dnf_utils_create_sack_for_filters at ../backends/dnf/pk-backend-dnf.c:800 #18 pk_backend_search_thread at ../backends/dnf/pk-backend-dnf.c:1055 #19 pk_backend_job_thread_setup at ../src/pk-backend-job.c:728 #20 g_thread_proxy at ../glib/gthread.c:831 #22 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Created attachment 1982379 [details] File: proc_pid_status
Created attachment 1982380 [details] File: maps
Created attachment 1982381 [details] File: limits
Created attachment 1982382 [details] File: environ
Created attachment 1982383 [details] File: open_fds
Created attachment 1982384 [details] File: mountinfo
Created attachment 1982385 [details] File: os_info
Created attachment 1982386 [details] File: cpuinfo
Created attachment 1982387 [details] File: core_backtrace
Created attachment 1982388 [details] File: exploitable
Created attachment 1982389 [details] File: dso_list
Created attachment 1982390 [details] File: var_log_messages
Created attachment 1982391 [details] File: backtrace
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.