https://bugs.kde.org/show_bug.cgi?id=453084
--- Comment #4 from Tom Hughes <t...@compton.nu> --- I've managed to reproduce it on Fedora 34 and it does seem to be linked to use __memmove_chk and __memmove_chk and __memcpy_chkdo seem to be different symbols in glibc (sometimes the two are the same if memcpy is known to be overlap safe) so it does seem a bit odd. -- You are receiving this mail because: You are watching all bug changes.
