Summary: | akonadi_baloo_indexer crashes on akonadi start | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Luis Silva <lacsilva> |
Component: | Indexer | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | amos.elberg, chookstwoemus, chrigi_1, dvratil, kfunk, vit |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
Luis Silva
2016-01-04 19:40:32 UTC
*** Bug 358314 has been marked as a duplicate of this bug. *** Looks like there's either some problem with your DBus, or that somehow something is already occupying the org.freedesktop.Akonadi.Agent.akonadi_baloo_indexer service on the bus - possibly another instance running (which should NOT be possible). Can you check if this is still happening in KDE PIM 15.12 or 16.04? The agent there is called akonadi_indexing_agent (we removed "Baloo" from the name). The crash is no longer happening in KDEPIM 15.12. However, I just realised that I still had the two agents installed (akonadi_indexing and akonadi_baloo) and this error message keeps showing up in the console even after I deactivated the akonadi_baloo_indexer and restarted akonadi. akonadi_baloo_indexer(5300): Could not obtain lock for Xapian Database. This is bad akonadi_baloo_indexer(5300): "DatabaseLockError" "DatabaseLockError: Unable to get write lock on /home/lacsilva/.local/share/baloo/notes/: already locked" akonadi_baloo_indexer(5300): "DatabaseLockError" "DatabaseLockError: Unable to get write lock on /home/lacsilva/.local/share/baloo/calendars/: already locked" Created attachment 98484 [details]
New crash information added by DrKonqi
akonadi_baloo_indexer (4.14) on KDE Platform 4.14.16 using Qt 4.8.7
- What I was doing when the application crashed:
Starting akonadi with akonadictl. Also happens if I run kontact. Happens essentially every time.
-- Backtrace (Reduced):
#6 0x00007f7554a1a418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7 0x00007f7554a1c01a in __GI_abort () at abort.c:89
[...]
#11 0x00007f7558722db1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x00007f7555c70fdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x00007f7555c77f16 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
Work-around from comment #3 solved the problem for me: Start akonadiconsole, observe there are two agents running called "Akonadi Indexing Agent" and "Akonadi Baloo Indexer". Remove the latter. I no longer get the crash notification on akonadi restart. Created attachment 101577 [details]
New crash information added by DrKonqi
akonadi_baloo_indexer (4.14) on KDE Platform 4.14.16 using Qt 4.8.7
- What I was doing when the application crashed:
Started my system and logged into kde, crash of application occurred before I did anything.
-- Backtrace (Reduced):
#6 0x00007f54a3009418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7 0x00007f54a300b01a in __GI_abort () at abort.c:89
[...]
#11 0x00007f54a6d11db1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x00007f54a425ffdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x00007f54a4266f16 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
The 'akonadi_baloo_indexer' is part of the KDEPIM 4 packages that is no longer maintained. Please ask in a forum of your distribution how to uninstall all KDEPIM 4 packages and only use KDEPIM 5 packages. |