baloo_file crashed with SIGSEGV in start_thread()

[Leo]

.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: baloo-kf5 5.92.0-0ubuntu1
Uname: Linux 5.17.2-051702-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue Apr 12 14:56:27 2022
ExecutablePath: /usr/lib/x86_64-linux-gnu/libexec/baloo_file
ProcCmdline: /usr/lib/x86_64-linux-gnu/libexec/baloo_file
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
 LANGUAGE=de:en_US
Signal: 11
SourcePackage: baloo-kf5
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
 ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
 start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
Title: baloo_file crashed with SIGSEGV in start_thread()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip fax floppy lpadmin lxd operator plugdev root sambashare sudo sys tape users video
separator:

[Apport retracing service (apport)]

StacktraceTop:
 std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=0x2b2b2b7370747468) at /usr/include/c++/11/bits/atomic_base.h:481
 QAtomicOps<int>::loadRelaxed<int> (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239
 QBasicAtomicInteger<int>::loadRelaxed (this=0x2b2b2b7370747468) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:107
 QtPrivate::RefCount::deref (this=0x2b2b2b7370747468) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:66
 QString::~QString (this=<optimized out>, this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1307

[Steve Beattie (sbeattie)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.