[kde] [Bug 373519] New: baloo indexer crashed at restart akonadi
Christoph Thielecke
bugzilla_noreply at kde.org
Sun Dec 11 09:33:21 GMT 2016
https://bugs.kde.org/show_bug.cgi?id=373519
Bug ID: 373519
Summary: baloo indexer crashed at restart akonadi
Product: kde
Version: unspecified
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: crissi99 at gmx.de
Target Milestone: ---
Application: akonadi_baloo_indexer (4.14)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-47-generic x86_64
Distribution: Ubuntu 16.04.1 LTS
-- Information about the crash:
I restarted akonadi by "akonactl restart > akonadi.log 2>&1" to get a log file
written. There was mail indexing running anter after some time I got a crash
dialog.
Examining the log I found also:
Connected to "Akonadi" , using protocol version 52
akonadi_baloo_indexer(15659): "DatabaseLockError" "DatabaseLockError: Unable to
get write lock on /home/crissi/.local/share/baloo/email/: already locked"
akonadi_baloo_indexer(15659): "DatabaseLockError" "DatabaseLockError: Unable to
get write lock on /home/crissi/.local/share/baloo/emailContacts/: already
locked"
-- Backtrace:
Application: Akonadi-Indizierungsagent für Baloo (akonadi_baloo_indexer),
signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6 0x00007ff3a0a08428 in __GI_raise (sig=sig at entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7 0x00007ff3a0a0a02a in __GI_abort () at abort.c:89
#8 0x00007ff3a45dbf15 in qt_message_output(QtMsgType, char const*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9 0x00007ff3a3120d47 in ?? () from /usr/lib/libakonadi-kde.so.4
#10 0x00007ff3a312020a in ?? () from /usr/lib/libakonadi-kde.so.4
#11 0x00007ff3a4710db1 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x00007ff3a1c5efdc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x00007ff3a1c65f16 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x00007ff3a29c46aa in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#15 0x00007ff3a46f690d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#16 0x00007ff3a46fa3c6 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#17 0x00007ff3a472713e in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#18 0x00007ff3a00d11a7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ff3a00d1400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007ff3a00d14ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007ff3a47272ae in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#22 0x00007ff3a1d0c616 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#23 0x00007ff3a46f518f in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#24 0x00007ff3a46f54f5 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#25 0x00007ff3a46fb4b9 in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#26 0x00007ff3a311d4bd in Akonadi::AgentBase::init(Akonadi::AgentBase*) () from
/usr/lib/libakonadi-kde.so.4
#27 0x000000000041111e in ?? ()
#28 0x00007ff3a09f3830 in __libc_start_main (main=0x40a090, argc=3,
argv=0x7fffc5e505d8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffc5e505c8) at ../csu/libc-start.c:291
#29 0x000000000040a129 in _start ()
Possible duplicates by query: bug 364721, bug 364342, bug 362651, bug 362635,
bug 362228.
Reported using DrKonqi
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list