Bug 274035 - Akonadi stops responding after kontact crash
Summary: Akonadi stops responding after kontact crash
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 1.5.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-24 15:51 UTC by Christoph Wickert
Modified: 2011-07-13 15:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 1.5.3


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Wickert 2011-05-24 15:51:40 UTC
Version:           1.5.2 (using KDE 4.6.3) 
OS:                Linux

I am using Kontact with a KOlab account. After I have configured the addressbook as described in the KDE userbase, Kontact often crashes. After the crash I cannot restart it because it cannot connect to akondi through dbus.


Reproducible: Sometimes

Steps to Reproduce:
Configure Kontact with the kolabwizard, then configure the address book as described in http://userbase.kde.org/KAddressBook_4.4. Kontact then frequently crashes.
One it crashes, It cannot be started again and akonadi refuses to do anything.

Actual Results:  
$ akonadiserver stop
search paths:  ("/usr/lib64/qt-3.3/bin", "/usr/lib64/ccache", "/usr/local/bin", "/usr/bin", "/bin", "/usr/local/sbin", "/usr/sbin", "/sbin", "/home/chris/.bin", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin") 
Found mysql_install_db:  "/usr/bin/mysql_install_db" 
Found mysqlcheck:  "/usr/bin/mysqlcheck" 
akonadi.collectionattributetable                   OK
akonadi.collectionmimetyperelation                 OK
akonadi.collectionpimitemrelation                  OK
akonadi.collectiontable                            OK
akonadi.flagtable                                  OK
akonadi.mimetypetable                              OK
akonadi.parttable                                  OK
akonadi.pimitemflagrelation                        OK
akonadi.pimitemtable                               OK
akonadi.resourcetable                              OK
akonadi.schemaversiontable                         OK
mysql.columns_priv                                 OK
mysql.db                                           OK
mysql.event                                        OK
mysql.func                                         OK
mysql.general_log
Error    : You can't use locks with log tables.
status   : OK
mysql.help_category                                OK
mysql.help_keyword                                 OK
mysql.help_relation                                OK
mysql.help_topic                                   OK
mysql.host                                         OK
mysql.ndb_binlog_index                             OK
mysql.plugin                                       OK
mysql.proc                                         OK
mysql.procs_priv                                   OK
mysql.servers                                      OK
mysql.slow_log
Error    : You can't use locks with log tables.
status   : OK
mysql.tables_priv                                  OK
mysql.time_zone                                    OK
mysql.time_zone_leap_second                        OK
mysql.time_zone_name                               OK
mysql.time_zone_transition                         OK
mysql.time_zone_transition_type                    OK
mysql.user                                         OK
Database "akonadi" opened using driver "QMYSQL" 
DbInitializer::run() 
checking table  "SchemaVersionTable" 
checking table  "ResourceTable" 
checking table  "CollectionTable" 
checking table  "MimeTypeTable" 
checking table  "PimItemTable" 
checking table  "FlagTable" 
checking table  "PartTable" 
checking table  "CollectionAttributeTable" 
checking relation  "PimItemFlagRelation" 
checking relation  "CollectionMimeTypeRelation" 
checking relation  "CollectionPimItemRelation" 
DbInitializer::run() done 
skipping update 2 
skipping update 3 
skipping update 4 
skipping update 8 
skipping update 10 
skipping update 12 
skipping update 13 
skipping update 14 
skipping update 15 
skipping update 16 
skipping update 17 
skipping update 18 
skipping update 19 
Database "akonadi" opened using driver "QMYSQL" 
Database "akonadi" opened using driver "QMYSQL" 
Akonadi::NepomukSearchEngine(0x2721450) QObject(0x0)  
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
DataStore::unhideAllPimItems() 
Unable to connect to dbus service:  ""
"[
0: akonadiserver(_Z11akBacktracev+0x39) [0x44af89]
1: akonadiserver() [0x44b4f2]
2: /lib64/libc.so.6() [0x37d2233140]
3: /lib64/libc.so.6(gsignal+0x35) [0x37d22330c5]
4: /lib64/libc.so.6(abort+0x186) [0x37d2234a76]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x30e166a784]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xab) [0x44ce7b]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x77) [0x30e16f85c7]
8: /usr/lib64/libQtCore.so.4() [0x30e17009f6]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3b) [0x30e17098db]
10: akonadiserver(main+0x41c) [0x44614c]
11: /lib64/libc.so.6(__libc_start_main+0xfd) [0x37d221ee5d]
12: akonadiserver() [0x445c39]
]
"


Expected Results:  
$ akonadiserver stop
should just shutdown akonadi and I should be able to start kontact again.
Comment 1 Christophe Marin 2011-05-24 18:23:36 UTC
note that 'akonadiserver stop' is not a valid command.

akonadictl stop is.
Comment 2 Christoph Wickert 2011-05-24 19:13:54 UTC
You are right, sorry. However 'akonadictl stop' gives me exactly the same backtrace.
Comment 3 Christoph Wickert 2011-06-03 11:30:39 UTC
It looks like this is fixed in akonadi-1.5.3-1.fc15 and kdepim-4.4.11.1-4.fc15: Kontact still becomes unresponsive from time to time, but at least I can kill it and akonadi still responds.

$ killall kontact
$ akonatictl stop
(wait 5 seconds)
$ akonadictl status (to verify)
$ akonadictl start

... and kontact works again.

I'll keep an eye on this and close this bug if the behavior doesn't change.
Comment 4 Christophe Marin 2011-07-13 15:17:15 UTC
Changing status. Please close with RESOLVED/WORKSFORME if applicable