Bug 370903 - Baloo broken when connecting with x2go client
Summary: Baloo broken when connecting with x2go client
Status: RESOLVED DUPLICATE of bug 389848
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.18.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-10-15 08:10 UTC by Konstantin Nekrasov
Modified: 2018-04-14 01:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Konstantin Nekrasov 2016-10-15 08:10:32 UTC
Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-43-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I was connecting to a remote KUbuntu 15.10 with x2go. At the remote host I got this issue. Previously the remote machine was upgraded from Kubuntu 14.04 (where x2go worked like a charm)

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc6ca0da8c0 (LWP 25100))]

Thread 2 (Thread 0x7fc57eef1700 (LWP 29282)):
[KCrash Handler]
#6  0x00007fc6c691dbfd in mdb_cursor_put () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#7  0x00007fc6c6920260 in mdb_put () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#8  0x00007fc6c92b0edd in Baloo::IdTreeDB::put(unsigned long long, QVector<unsigned long long>) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#9  0x00007fc6c92ae540 in Baloo::DocumentUrlDB::add(unsigned long long, unsigned long long, QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#10 0x00007fc6c92ae916 in Baloo::DocumentUrlDB::put(unsigned long long, QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x00007fc6c92c60ea in Baloo::WriteTransaction::addDocument(Baloo::Document const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#12 0x000000000041cc86 in Baloo::NewFileIndexer::run() ()
#13 0x00007fc6c8bde343 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007fc6c8be184e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007fc6c78456fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#16 0x00007fc6c81eeb5d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7fc6ca0da8c0 (LWP 25100)):
#0  0x00007fc6c81de9cd in read () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007fc6c53f6740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fc6c53b2e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fc6c53b3340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fc6c53b34ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fc6c8e18a7f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007fc6c8dbfdea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fc6c8dc7e8c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x000000000041698c in main ()

Reported using DrKonqi
Comment 1 Dominik Haumann 2018-04-14 01:53:32 UTC

*** This bug has been marked as a duplicate of bug 389848 ***