kdenlive_render crashed with SIGSEGV in QString::toUtf8_helper()

[Jack Pogorelsky Jr.]

kdenlive_render crashed with SIGSEGV in QString::toUtf8_helper()

ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: kdenlive 4:23.08.4-0ubuntu1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu7
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: XFCE
Date: Tue Feb 20 17:14:47 2024
ExecutablePath: /usr/bin/kdenlive_render
InstallationDate: Installed on 2024-02-02 (18 days ago)
InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240202)
JournalErrors: -- No entries --
ProcCmdline: /usr/bin/kdenlive_render delivery /usr/bin/melt-7 /tmp/kdenlive-AnKBuA-1.mlt --pid 3919
SegvAnalysis:
 Segfault happened at: 0x7259aa336810: movdqu (%rbx),%xmm0
 PC (0x7259aa336810) ok
 source "(%rbx)" (0x725988021000) in non-readable VMA region: 0x725988021000-0x72598c000000 ---p None
 destination "%xmm0" ok
SegvReason: reading VMA None
Signal: 11
SourcePackage: kdenlive
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
 QString::toUtf8_helper(QString const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
 ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
 ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
 QDBusConnection::call(QDBusMessage const&, QDBus::CallMode, int) const () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
Title: kdenlive_render crashed with SIGSEGV in QString::toUtf8_helper()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip fax floppy lpadmin plugdev sambashare sudo tape users video
separator:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2052365, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.