baloo_file crashed with SIGSEGV in __memmove_avx_unaligned_erms()

[Nils Büchner]

sorry. no details available :(

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: baloo-kf5 5.43.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
CurrentDesktop: KDE
Date: Wed Feb 28 23:37:29 2018
ExecutablePath: /usr/bin/baloo_file
ProcCmdline: /usr/bin/baloo_file
Signal: 11
SourcePackage: baloo-kf5
StacktraceTop:
 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:431
 ?? () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
 Baloo::PostingDB::get(QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
 Baloo::WriteTransaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
 Baloo::Transaction::commit() () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
Title: baloo_file crashed with SIGSEGV in __memmove_avx_unaligned_erms()
UpgradeStatus: Upgraded to bionic on 2018-02-17 (11 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #1749569, 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.

[Lorenzo Bettini (bettini)]

but the original bug #1749569 is not accessible, is it?