Bug 22721 - "baloosearch --type video/audio test" crash (SIGSEGV)
Summary: "baloosearch --type video/audio test" crash (SIGSEGV)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-08 17:46 CET by PC LX
Modified: 2018-05-02 14:53 CEST (History)
1 user (show)

See Also:
Source RPM: baloo-5.42.0-1.mga6.src.rpm
CVE:
Status comment:


Attachments

Description PC LX 2018-03-08 17:46:42 CET
I have made this same bug report upstream at:
https://bugs.kde.org/show_bug.cgi?id=391574


The commands:
- baloosearch --type video test
- baloosearch --type audio test
result in a crash (SIGSEGV) but the commands:
- baloosearch --type text test
- baloosearch --type document test
- baloosearch test
work as expected.

This also affects other programs that use baloosearch (e.g. KDE's dolphin).



The crash backtrace taken with gdb:
(gdb) run --type audio test
<SNIP>
Program received signal SIGSEGV, Segmentation fault.
<SNIP>
(gdb) bt
#0  0x00007ffff6e6e01e in __memcpy_sse2_unaligned () from /lib64/libc.so.6
#1  0x00007ffff723b851 in QByteArray::QByteArray(char const*, int) () from /lib64/libQt5Core.so.5
#2  0x00007ffff6462f97 in DBPostingIterator::DBPostingIterator (this=0x666a60, data=<optimized out>, size=<optimized out>) at /usr/src/debug/baloo-5.42.0/src/engine/postingdb.cpp:177
#3  0x00007ffff6463051 in Baloo::PostingDB::iter (this=this@entry=0x7fffffffd4f0, term=...) at /usr/src/debug/baloo-5.42.0/src/engine/postingdb.cpp:169
#4  0x00007ffff646d0ba in Baloo::Transaction::postingIterator (this=this@entry=0x7fffffffd820, query=...) at /usr/src/debug/baloo-5.42.0/src/engine/transaction.cpp:294
#5  0x00007ffff7bcfb8d in Baloo::SearchStore::constructQuery (this=this@entry=0x7fffffffd8d0, tr=tr@entry=0x7fffffffd820, term=...)
    at /usr/src/debug/baloo-5.42.0/src/lib/searchstore.cpp:190
#6  0x00007ffff7bcfdea in Baloo::SearchStore::constructQuery (this=this@entry=0x7fffffffd8d0, tr=tr@entry=0x7fffffffd820, term=...)
    at /usr/src/debug/baloo-5.42.0/src/lib/searchstore.cpp:164
#7  0x00007ffff7bd0ea0 in Baloo::SearchStore::exec (this=this@entry=0x7fffffffd8d0, term=..., offset=0, limit=-1, sortResults=<optimized out>)
    at /usr/src/debug/baloo-5.42.0/src/lib/searchstore.cpp:76
#8  0x00007ffff7bc01c6 in Baloo::Query::exec (this=this@entry=0x7fffffffd988) at /usr/src/debug/baloo-5.42.0/src/lib/query.cpp:210
#9  0x0000000000402488 in main (argc=4, argv=<optimized out>) at /usr/src/debug/baloo-5.42.0/src/tools/baloosearch/main.cpp:101




System information:

$ uname -a
Linux marte 4.14.20-desktop-1.mga6 #1 SMP Sun Feb 18 01:22:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/release 
Mageia release 6 (Official) for x86_64
$ baloosearch --version
Baloo 5.42.0
$ rpm -qf $(which baloosearch)
baloo-5.42.0-1.mga6
$ qtdiag | head -n 4
Qt 5.9.4 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.4.0) on "xcb" 
OS: Mageia 6 [linux version 4.14.20-desktop-1.mga6]

Architecture: x86_64; features: SSE2 SSE3 SSSE3 SSE4.1
Marja Van Waes 2018-03-08 18:25:39 CET

Assignee: bugsquad => kde
CC: (none) => marja11

Marja Van Waes 2018-03-08 18:26:07 CET

See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=391574

Comment 1 PC LX 2018-04-06 10:55:14 CEST
This issue seems to be resolved. It works from the command line and from dolphin.

I'm not certain what fixed it, with so many updates to Qt, KDE, Plasma and other stuff.

If someone else could confirm it works for them, this could be closed as resolved.

$ uname -a
Linux marte 4.14.30-desktop-3.mga6 #1 SMP Sun Mar 25 22:17:31 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ baloosearch --type audio test
<SNIP>
Elapsed: 0.697228 msecs
$ baloosearch --type video test
<SNIP>
Elapsed: 0.709497 msecs
$ baloosearch --type text test
Elapsed: 4.49988 msecs
$ baloosearch test
<SNIP>
Elapsed: 8.61201 msecs
Comment 2 PC LX 2018-05-02 14:53:35 CEST
Since no one else complained about this issue for the last month and it is working for me, I will be closing it as fixed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.