https://bugs.kde.org/show_bug.cgi?id=393981
Bug ID: 393981
Summary: Baloo File Extractor crash after desktop environment
session login
Product: frameworks-baloo
Version: 5.44.0
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: vjose...@gmail.com
Target Milestone: ---
Application: baloo_file_extractor (5.44.0)
Qt Version: 5.10.1
Frameworks Version: 5.44.0
Operating System: Linux 4.16.6-302.fc28.x86_64 x86_64
Distribution (Platform): Fedora RPMs
-- Information about the crash:
- What I was doing when the application crashed: login into whatever destkop
environment session (Plasma, XFCE, GNOME, ...) both interactive or remote way.
The crash can be reproduced every time.
-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1926c73940 (LWP 6916))]
Thread 2 (Thread 0x7f190321c700 (LWP 6919)):
#0 0x00007f1923a75929 in poll () from /lib64/libc.so.6
#1 0x00007f191efbdb06 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2 0x00007f191efbdc30 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3 0x00007f1924941c2b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /lib64/libQt5Core.so.5
#4 0x00007f19248f012b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib64/libQt5Core.so.5
#5 0x00007f192473e9c6 in QThread::exec() () from /lib64/libQt5Core.so.5
#6 0x00007f1926ce9299 in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#7 0x00007f192474311d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8 0x00007f1922da8564 in start_thread () from /lib64/libpthread.so.0
#9 0x00007f1923a8031f in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x7f1926c73940 (LWP 6916)):
[KCrash Handler]
#4 0x00007f1923ae321b in __memmove_avx_unaligned_erms () from /lib64/libc.so.6
#5 0x00007f1925fc4791 in Baloo::PostingCodec::decode(QByteArray const&) ()
from /lib64/libKF5BalooEngine.so.5
#6 0x00007f1925fb1e61 in Baloo::PostingDB::get(QByteArray const&) () from
/lib64/libKF5BalooEngine.so.5
#7 0x00007f1925fc1fa2 in Baloo::WriteTransaction::commit() () from
/lib64/libKF5BalooEngine.so.5
#8 0x00007f1925fb8726 in Baloo::Transaction::commit() () from
/lib64/libKF5BalooEngine.so.5
#9 0x000055a6fef6736c in Baloo::App::processNextFile() ()
#10 0x00007f1924925eba in QSingleShotTimer::timerEvent(QTimerEvent*) () from
/lib64/libQt5Core.so.5
#11 0x00007f192491a9db in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#12 0x00007f19251b8e95 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#13 0x00007f19251c083a in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQt5Widgets.so.5
#14 0x00007f19248f1376 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#15 0x00007f1924940f19 in QTimerInfoList::activateTimers() () from
/lib64/libQt5Core.so.5
#16 0x00007f1924941804 in idleTimerSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#17 0x00007f191efbd7cd in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#18 0x00007f191efbdb98 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#19 0x00007f191efbdc30 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#20 0x00007f1924941c13 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /lib64/libQt5Core.so.5
#21 0x00007f190f594065 in
QPAEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /lib64/libQt5XcbQpa.so.5
#22 0x00007f19248f012b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib64/libQt5Core.so.5
#23 0x00007f19248f85b6 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#24 0x000055a6fef64af2 in main ()
Possible duplicates by query: bug 393281, bug 392701, bug 391803, bug 391345,
bug 390610.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
