Description of problem: When attempting to install some packages (for example fail2ban) in Fedora IoT on armhfp, rpm-ostree crashes PID: 809 (rpm-ostree) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Wed 2020-12-09 18:19:28 UTC (1h 56min ago) Command Line: /usr/bin/rpm-ostree start-daemon Executable: /usr/bin/rpm-ostree Control Group: /system.slice/rpm-ostreed.service Unit: rpm-ostreed.service Slice: system.slice Boot ID: 82496955662b438ea4667e4b59858df0 Machine ID: 6868294b3ee1441ea7778fdaa16a5283 Hostname: rpi3-2 Storage: /var/lib/systemd/coredump/core.rpm-ostree.0.82496955662b438ea4667e4b59858df0.809.1607537968000000.zst Message: Process 809 (rpm-ostree) of user 0 dumped core. Stack trace of thread 1735: #0 0x00000000b62d3d60 strchrnul (libc.so.6 + 0x80d60) Program terminated with signal SIGSEGV, Segmentation fault. #0 0xb62d3d60 in __strchrnul (s=<optimized out>, c_in=<optimized out>) at strchrnul.c:118 118 longword = *longword_ptr++; Version-Release number of selected component (if applicable): rpm-ostree-2020.8-1.fc33.armv7hl How reproducible: Happens everytime with fail2ban on armhfp Steps to Reproduce: 1. rpm-ostree install fail2ban
Created attachment 1738027 [details] rpm-ostree backtrace
Created attachment 1738053 [details] updated rpm-ostree backtrace
Thanks, this is the first usable backtraces we have for this! I opened https://github.com/coreos/rpm-ostree/pull/2369 which I think might address this.
*** Bug 1900382 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
This is fixed, closing.
*** Bug 1906054 has been marked as a duplicate of this bug. ***