| Summary: | KDE Contacts List never opens when Akonadi fails to start | ||
|---|---|---|---|
| Product: | [Unmaintained] telepathy | Reporter: | Smittie <bugs.kde> |
| Component: | contactlist | Assignee: | Telepathy Bugs <kde-telepathy-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | dvratil, gena.kazachek, kde, martin.holec, mklapetek, whatifgodwasoneofus |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 0.8.0 | ||
| Target Milestone: | Future | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/telepathy-contact-list/ea3fbd1e816a62b9b31c87e90763087e6229dda8 | Version Fixed In: | 0.9.0 |
| Sentry Crash Report: | |||
|
Description
Smittie
2014-03-26 17:22:29 UTC
#79 0x000000000041d925 in ~ContactListApplication (this=0x7fffb2af3370, __in_chrg=<optimized out>) at /usr/src/debug/ktp-contact-list-0.8.0/contact-list-application.h:26 This appears to be a crash on closing the application, is that correct? The crash occurs on system shutdown, so yes on closing the application. However, some related condition exists for the entire time the system is running. KDE IM Contacts never works. If I close the KDE IM Contacts window using the (x) button, the window will never re-open. I see the spinning arrows in the system bar but it eventually quits without opening. Looking at the backtrace: - Akonadi's job to load contacts never finishes - we don't show contacts because we're waiting - when you kill the app, that kills the akonadi job - we then think "oh, I have all the contacts now, I'll process everything" - the crash is a byproduce of that, we don't expect to be processing things like that during shutdown. Looking at the backtrace: - Akonadi's job to load contacts never finishes - we don't show contacts because we're waiting - when you kill the app, that kills the akonadi job - we then think "oh, I have all the contacts now, I'll process everything" - the crash is a byproduct of that, we don't expect to be processing things like that during shutdown. Smittie, do you have Google Contacts or Facebook resource added in Akonadi? Please start Akonadi Console, enable Job Tracker and Debugger tabs, start the Contact List and then provide output from both tabs (paste output from the "All" tab in Browser and make a screenshot of the Job Tracker tab, we don't have any other way to export the data in 4.12 unfortunately). Well then, maybe this is the problem: Akonadi Server Self-Test Report =============================== Test 1: SUCCESS -------- Database driver found. Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system. File content of '/home/smittie/.config/akonadi/akonadiserverrc': [%General] Driver=QMYSQL [QMYSQL] Name=akonadi Host= Options="UNIX_SOCKET=/tmp/akonadi-smittie.GszaRn/mysql.socket" ServerPath=/usr/libexec/mysqld StartServer=false [Debug] Tracer=null Test 2: SUCCESS -------- Akonadi is not running as root Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system. Test 3: SKIP -------- MySQL server executable not tested. Details: The current configuration does not require an internal MySQL server. Test 4: SKIP -------- MySQL server error log not tested. Details: The current configuration does not require an internal MySQL server. Test 5: SKIP -------- MySQL server configuration not tested. Details: The current configuration does not require an internal MySQL server. Test 6: SUCCESS -------- akonadictl found and usable Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully. Result: Akonadi 1.11.0 Test 7: ERROR -------- Akonadi control process not registered at D-Bus. Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 8: ERROR -------- Akonadi server process not registered at D-Bus. Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 9: SUCCESS -------- Nepomuk search service registered at D-Bus. Details: The Nepomuk search service is registered at D-Bus which typically indicates it is operational. Test 10: SUCCESS -------- Nepomuk search service uses an appropriate backend. Details: The Nepomuk search service uses one of the recommended backends. Test 11: SKIP -------- Protocol version check not possible. Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements. Test 12: ERROR -------- No resource agents found. Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share:/usr/share/kde-settings/kde-profile/default/share:/usr/local/share:/usr/share'; make sure this includes all paths where Akonadi agents are installed. Directory listing of '/usr/share/akonadi/agents': akonadinepomukfeederagent.desktop akonotesresource.desktop archivemailagent.desktop birthdaysresource.desktop contactsresource.desktop davgroupwareresource.desktop facebookresource.desktop folderarchiveagent.desktop googlecalendarresource.desktop googlecontactsresource.desktop icaldirresource.desktop icalresource.desktop imapresource.desktop invitationsagent.desktop kabcresource.desktop kalarmdirresource.desktop kalarmresource.desktop kcalresource.desktop kdeaccountsresource.desktop kolabproxyresource.desktop localbookmarksresource.desktop maildirresource.desktop maildispatcheragent.desktop mailfilteragent.desktop mboxresource.desktop microblog.desktop migrationagent.desktop mixedmaildirresource.desktop mtdummyresource.desktop nepomuktagresource.desktop newmailnotifieragent.desktop nntpresource.desktop notesresource.desktop openxchangeresource.desktop pop3resource.desktop sendlateragent.desktop vcarddirresource.desktop vcardresource.desktop Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share/kde-settings/kde-profile/default/share:/usr/local/share:/usr/share' Test 13: ERROR -------- Current Akonadi server error log found. Details: The Akonadi server reported errors during its current startup. The log can be found in <a href='/home/smittie/.local/share/akonadi/akonadiserver.error'>/home/smittie/.local/share/akonadi/akonadiserver.error</a>. File content of '/home/smittie/.local/share/akonadi/akonadiserver.error': Database error: Cannot open database. Last driver error: "QMYSQL: Unable to connect" Last database error: "Can't connect to local MySQL server through socket '/tmp/akonadi-smittie.GszaRn/mysql.socket' (2)" Unable to open database "Can't connect to local MySQL server through socket '/tmp/akonadi-smittie.GszaRn/mysql.socket' (2) QMYSQL: Unable to connect" "[ 0: akonadiserver(_Z11akBacktracev+0x4a) [0x454a2a] 1: akonadiserver() [0x454ca2] 2: /lib64/libc.so.6() [0x328f235cb0] 3: /lib64/libc.so.6(gsignal+0x39) [0x328f235c39] 4: /lib64/libc.so.6(abort+0x148) [0x328f237348] 5: /lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x84) [0x3eeb271a44] 6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xad) [0x45697d] 7: /lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x3eeb310c60] 8: /lib64/libQtCore.so.4() [0x3eeb31e5f5] 9: /lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x3eeb3277c1] 10: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x508) [0x459648] 11: /lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x26e) [0x3eeb39d27e] 12: /lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8d) [0x3eeb38439d] 13: /lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x205) [0x3eeb387485] 14: /lib64/libQtCore.so.4() [0x3eeb3b3623] 15: /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x166) [0x3291a492a6] 16: /lib64/libglib-2.0.so.0() [0x3291a49628] 17: /lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x3291a496dc] 18: /lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x3eeb3b2ea5] 19: /lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x3f) [0x3eeb382edf] 20: /lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x19d) [0x3eeb38322d] 21: /lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x99) [0x3eeb388749] 22: akonadiserver(main+0x263) [0x44f033] 23: /lib64/libc.so.6(__libc_start_main+0xf5) [0x328f221d65] 24: akonadiserver() [0x44f859] ] " Test 14: ERROR -------- Previous Akonadi server error log found. Details: The Akonadi server reported errors during its previous startup. The log can be found in <a href='/home/smittie/.local/share/akonadi/akonadiserver.error.old'>/home/smittie/.local/share/akonadi/akonadiserver.error.old</a>. File content of '/home/smittie/.local/share/akonadi/akonadiserver.error.old': Database error: Cannot open database. Last driver error: "QMYSQL: Unable to connect" Last database error: "Can't connect to local MySQL server through socket '/tmp/akonadi-smittie.GszaRn/mysql.socket' (2)" Unable to open database "Can't connect to local MySQL server through socket '/tmp/akonadi-smittie.GszaRn/mysql.socket' (2) QMYSQL: Unable to connect" "[ 0: akonadiserver(_Z11akBacktracev+0x4a) [0x454a2a] 1: akonadiserver() [0x454ca2] 2: /lib64/libc.so.6() [0x328f235cb0] 3: /lib64/libc.so.6(gsignal+0x39) [0x328f235c39] 4: /lib64/libc.so.6(abort+0x148) [0x328f237348] 5: /lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x84) [0x3eeb271a44] 6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xad) [0x45697d] 7: /lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x3eeb310c60] 8: /lib64/libQtCore.so.4() [0x3eeb31e5f5] 9: /lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x3eeb3277c1] 10: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0x508) [0x459648] 11: /lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x26e) [0x3eeb39d27e] 12: /lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8d) [0x3eeb38439d] 13: /lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x205) [0x3eeb387485] 14: /lib64/libQtCore.so.4() [0x3eeb3b3623] 15: /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x166) [0x3291a492a6] 16: /lib64/libglib-2.0.so.0() [0x3291a49628] 17: /lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x3291a496dc] 18: /lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x3eeb3b2ea5] 19: /lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x3f) [0x3eeb382edf] 20: /lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x19d) [0x3eeb38322d] 21: /lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x99) [0x3eeb388749] 22: akonadiserver(main+0x263) [0x44f033] 23: /lib64/libc.so.6(__libc_start_main+0xf5) [0x328f221d65] 24: akonadiserver() [0x44f859] ] " Test 15: SUCCESS -------- No current Akonadi control error log found. Details: The Akonadi control process did not report any errors during its current startup. Test 16: SUCCESS -------- No previous Akonadi control error log found. Details: The Akonadi control process did not report any errors during its previous startup. Akonadi is not able to start. My may have done something to cause that but not intentionally and I really have no idea what. Moreover, I think that there could be some better error handling to inform the user that there is a problem and maybe even donate a clue as to what to do next. Reset Akonadi to defaults in System Settings and restarted Akonadi server. Second attempt got it started. KDE IM Contacts list now appears to work normally. In answer to an earlier question, I do have Facebook entries in KDE IM Contacts. They appear to be working correctly now. I still think there could be better messaging about there being a problem rather than waiting forever and crashing on shutdown. Just my opinion. > I still think there could be better messaging about there being a problem rather than waiting forever and crashing on shutdown. Just my opinion.
Ideally we need to detect this and update the AkonadiAllContactsMonitor to emit "initialised()" immediately.
Worst case I can have a timer in the ContactsModel that goes off if one of the datasources is being slow, but I don't really like that approach.
In my case, Akonadi Server was not running at all. Seems like AkonadiAllContactsMonitor should detect that. But, maybe I don't understand enough about how Akonadi works. The Akonadi self-test told me there was a problem straight away. Once I understood that the server wasn't running, it was fairly academic to resolve the issue. Entirely through the GUI. There's ServerManager class in kdepimlibs that can monitor and report server state. We could connect to ServerManager::stateChanged() before starting any Akonadi jobs and in case the state changes to ServerManager::Broken after the initial fetch is started, we can abort it and call initialised() manually. However it would be much better to handle this generically in Akonadi: if a Job fails to start Akonadi server or Akonadi is in Broken state, the Job should quit immediately with an error message. This would also fix the way David reproduced behaviour described in this bug. For reference, my chat log with Dan. I have a way to reproduce it in my kf5 env, I have a differnet KDE home so when I run ktp-contactlist I get ktp-contactlist(12806)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Invalid name" and then the behaviour is like reported @Smittie > Seems like AkonadiAllContactsMonitor should detect that Absolutely. We however had no idea this situation can even happen, otherwise we would have handled it already :) @Dan > if a Job fails to start Akonadi server or Akonadi is in Broken state, the Job should quit immediately with an error message. +1 on that Do we really need the error message? As long as we don't block waiting we don't /need/ the akonadi stuff. The user will just not see any akonadi merged contacts. ...and we can warn about that. That seems fine imo. And we should definitely not block. *** Bug 332585 has been marked as a duplicate of this bug. *** Git commit 6b81500cb3c7134eb06a7a93b3fbe9ff9c9fc463 by Dan Vrátil. Committed on 28/03/2014 at 23:02. Pushed by dvratil into branch 'master'. Handle Akonadi::Job errors in AllContactsMonitor This patch will check for errors from Akonadi jobs and adds bool argument to emitInitialFetchComplete() method to say whether the initial fetch was successful, or a Job failed. REVIEW: 117141 M +2 -2 src/allcontactsmonitor.cpp M +6 -2 src/allcontactsmonitor.h M +4 -4 src/personsmodel.cpp M +2 -2 src/personsmodel.h M +32 -20 src/plugins/akonadi/akonadidatasource.cpp http://commits.kde.org/libkpeople/6b81500cb3c7134eb06a7a93b3fbe9ff9c9fc463 The blocking problem has been fixed in Akonadi and will be available in KDE 4.13. http://commits.kde.org/kdepimlibs/c94b74eaf747150e5f5c1a6f53f5a995569102da Warning message about possibly incomplete contact list has been added to ktp-contact-list master and will be available in KTp 0.9. http://commits.kde.org/telepathy-contact-list/ea3fbd1e816a62b9b31c87e90763087e6229dda8 David will push a temporary solution for the blocking problem into KTp 0.8.1. Still happening with KDE 4.13, akonadi 1.12.1 and ktp 0.8, with google contacts (no FB at all). Thanks! :) (manjaro linux/KDE, x86_64) I upgraded yesterday to ktp 0.8.1 and the problem is still there.
However, it's sufficient to restart the googlecontacts agent from the akonadiconsole.
> Still happening with KDE 4.13, akonadi 1.12.1 and ktp 0.8, with google
> contacts (no FB at all).
>
> Thanks! :)
>
> (manjaro linux/KDE, x86_64)
It is supposed to be fixed with the upcoming KTP 0.9.0 release. If you still see an issue with that version, please file a new ticket. It should have been fixed with libkpeople 0.2.2 mostly the libkpeople change. Can you confirm you have 0.2.2? I got libkpeople 0.2.2, ktp 0.8.1 - problem is still there Do you also have KDE 4.13? Nope. KDE 4.12.5 Actually that still wouldn't make much sense, unless Akonadi breaks so much it blocks. Can you paste the output from the contact list when you start it from the command line. Please open kdebugdialog first and enable everything. 0: akonadiserver(_Z11akBacktracev+0x34) [0x45de14] 1: akonadiserver() [0x45e231] 2: /lib64/libc.so.6(+0x360f0) [0x7ff2449d60f0] 3: /lib64/libc.so.6(gsignal+0x35) [0x7ff2449d6075] 4: /lib64/libc.so.6(abort+0x186) [0x7ff2449d74f6] 5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7ff2464c96f4] 6: /usr/lib64/qt4/libQtCore.so.4(+0x7788d) [0x7ff2464c988d] 7: /usr/lib64/qt4/libQtCore.so.4(_Z6qFatalPKcz+0x99) [0x7ff2464c9a29] 8: akonadiserver(_ZN7Akonadi13AkonadiServer14createDatabaseEv+0x94) [0x461104] 9: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0xd75) [0x463905] 10: /usr/lib64/qt4/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x376) [0x7ff2465ebfb6] 11: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8c) [0x7ff2465d72ec] 12: /usr/lib64/qt4/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x320) [0x7ff2465da8e0] 13: /usr/lib64/qt4/libQtCore.so.4(+0x1b4783) [0x7ff246606783] 14: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x135) [0x7ff2444a5615] 15: /usr/lib64/libglib-2.0.so.0(+0x4a958) [0x7ff2444a5958] 16: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x34) [0x7ff2444a5a14] 17: /usr/lib64/qt4/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x6f) [0x7ff24660691f] 18: /usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x32) [0x7ff2465d5fa2] 19: /usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x14d) [0x7ff2465d625d] 20: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication4execEv+0xbb) [0x7ff2465dad7b] 21: akonadiserver(main+0x1b3) [0x458ba3] 22: /lib64/libc.so.6(__libc_start_main+0xfd) [0x7ff2449c295d] 23: akonadiserver() [0x459221] ] " ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error) QSqlDatabase: QSQLITE3 driver not loaded QSqlDatabase: available drivers: QSQLITE QMYSQL3 QMYSQL ASSERT: "database.driver()->hasFeature( QSqlDriver::LastInsertId )" in file /var/tmp/portage/app-office/akonadi-server-1.11.0/work/akonadi-1.11.0/server/src/storage/dbconfigsqlite.cpp, line 122 "[ 0: akonadiserver(_Z11akBacktracev+0x34) [0x45de14] 1: akonadiserver() [0x45e231] 2: /lib64/libc.so.6(+0x360f0) [0x7f844c9830f0] 3: /lib64/libc.so.6(gsignal+0x35) [0x7f844c983075] 4: /lib64/libc.so.6(abort+0x186) [0x7f844c9844f6] 5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7f844e4766f4] 6: /usr/lib64/qt4/libQtCore.so.4(+0x7788d) [0x7f844e47688d] 7: /usr/lib64/qt4/libQtCore.so.4(_Z6qFatalPKcz+0x99) [0x7f844e476a29] 8: akonadiserver(_ZN7Akonadi13AkonadiServer14createDatabaseEv+0x94) [0x461104] 9: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0xd75) [0x463905] 10: /usr/lib64/qt4/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x376) [0x7f844e598fb6] 11: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8c) [0x7f844e5842ec] 12: /usr/lib64/qt4/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x320) [0x7f844e5878e0] 13: /usr/lib64/qt4/libQtCore.so.4(+0x1b4783) [0x7f844e5b3783] 14: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x135) [0x7f844c452615] 15: /usr/lib64/libglib-2.0.so.0(+0x4a958) [0x7f844c452958] 16: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x34) [0x7f844c452a14] 17: /usr/lib64/qt4/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x6f) [0x7f844e5b391f] 18: /usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x32) [0x7f844e582fa2] 19: /usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x14d) [0x7f844e58325d] 20: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication4execEv+0xbb) [0x7f844e587d7b] 21: akonadiserver(main+0x1b3) [0x458ba3] 22: /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f844c96f95d] 23: akonadiserver() [0x459221] ] " ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error) QSqlDatabase: QSQLITE3 driver not loaded QSqlDatabase: available drivers: QSQLITE QMYSQL3 QMYSQL ASSERT: "database.driver()->hasFeature( QSqlDriver::LastInsertId )" in file /var/tmp/portage/app-office/akonadi-server-1.11.0/work/akonadi-1.11.0/server/src/storage/dbconfigsqlite.cpp, line 122 "[ 0: akonadiserver(_Z11akBacktracev+0x34) [0x45de14] 1: akonadiserver() [0x45e231] 2: /lib64/libc.so.6(+0x360f0) [0x7f72040710f0] 3: /lib64/libc.so.6(gsignal+0x35) [0x7f7204071075] 4: /lib64/libc.so.6(abort+0x186) [0x7f72040724f6] 5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7f7205b646f4] 6: /usr/lib64/qt4/libQtCore.so.4(+0x7788d) [0x7f7205b6488d] 7: /usr/lib64/qt4/libQtCore.so.4(_Z6qFatalPKcz+0x99) [0x7f7205b64a29] 8: akonadiserver(_ZN7Akonadi13AkonadiServer14createDatabaseEv+0x94) [0x461104] 9: akonadiserver(_ZN7Akonadi13AkonadiServer4initEv+0xd75) [0x463905] 10: /usr/lib64/qt4/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x376) [0x7f7205c86fb6] 11: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8c) [0x7f7205c722ec] 12: /usr/lib64/qt4/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x320) [0x7f7205c758e0] 13: /usr/lib64/qt4/libQtCore.so.4(+0x1b4783) [0x7f7205ca1783] 14: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x135) [0x7f7203b40615] 15: /usr/lib64/libglib-2.0.so.0(+0x4a958) [0x7f7203b40958] 16: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x34) [0x7f7203b40a14] 17: /usr/lib64/qt4/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x6f) [0x7f7205ca191f] 18: /usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x32) [0x7f7205c70fa2] 19: /usr/lib64/qt4/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x14d) [0x7f7205c7125d] 20: /usr/lib64/qt4/libQtCore.so.4(_ZN16QCoreApplication4execEv+0xbb) [0x7f7205c75d7b] 21: akonadiserver(main+0x1b3) [0x458ba3] 22: /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f720405d95d] 23: akonadiserver() [0x459221] ] " ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error) "akonadiserver" crashed too often and will not be restarted! ktp-contactlist(9467) KTpAllContacts::onAccountManagerReady: Account manager ready ktp-contactlist(9467) KPixmapSequence::Private::loadSequence: Invalid framesize. ktp-contactlist(9467) KPixmapSequence::Private::loadSequence: Invalid framesize. ktp-contactlist(9467) KTp::GlobalPresence::onCurrentPresenceChanged: Current presence changed ktp-contactlist(9467) KTp::GlobalPresence::onCurrentPresenceChanged: Current presence changed ktp-contactlist(9467) KTp::LogManager::Private::loadPlugins: loaded factory : KPluginFactory(0x9ec230) ktp-contactlist(9467) KTp::LogManager::Private::loadPlugins: loaded logger plugin : TpLoggerPlugin(0x88cf70) tp-qt4-tpl DEBUG: static Tpl::Utils* Tpl::Utils::instance() : Created Utils instance 2 more strings to previous output: Akonadi failed to load, some metacontact features may not be available For more information please load akonadi_console |