Bug 273274

Summary:	akonadi crashes after upgrade to natty
Product:	[Frameworks and Libraries] Akonadi	Reporter:	j.w.ott
Component:	akonadiconsole	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	crash	Keywords:	investigated, triaged
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description j.w.ott 2011-05-14 17:10:14 UTC

Application: akonadiconsole (0.99)
KDE Platform Version: 4.6.2 (4.6.2)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-8-generic x86_64
Distribution: Ubuntu 11.04

-- Information about the crash:
Tried everything from userbase.kde.org/Akonadi

>ran Kcmshell4 kcm_akonadi
>ran mysql_upgrade as user (suggested) and as root since there were also error messages

with maverick I also got akonadi errors with kmail sitting on the couch and running kmail via ssh -Y  on our main computer as long as the error messages wasn't closed kmail was working anyway.

With the latest version Kmail is grey and cannot be used :-(

I know there is an configuration that has to be deleted but I don know where I can find it

Had to struggle with akonadi before I' m about to give up

-- Backtrace:
Application: Akonadi Console (akonadiconsole), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f1ee23a67a0 (LWP 15546))]

Thread 2 (Thread 0x7f1ec6286700 (LWP 15593)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f1ec6285ac0 in ?? ()
#2  0x00007ffff13a77b2 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7f1ee23a67a0 (LWP 15546)):
[KCrash Handler]
#6  0x00007f1ec54e744b in mysql_get_server_version () from /usr/lib/libmysqlclient_r.so.16
#7  0x00007f1ec587e4e2 in QMYSQLDriver::tables (this=0x2b162a0, type=QSql::AllTables) at ../../../sql/drivers/mysql/qsql_mysql.cpp:1353
#8  0x00007f1ee0641c94 in QSqlDatabase::tables (this=<value optimized out>, type=<value optimized out>) at kernel/qsqldatabase.cpp:1170
#9  0x00000000004304fc in DbBrowser::DbBrowser (this=0x2ad1a80, parent=<value optimized out>) at ../../akonadiconsole/dbbrowser.cpp:32
#10 0x0000000000433eb8 in MainWidget::MainWidget (this=0x267ec40, parent=0x26e9a00) at ../../akonadiconsole/mainwidget.cpp:62
#11 0x0000000000434f21 in MainWindow::MainWindow (this=0x26e9a00, parent=<value optimized out>, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at ../../akonadiconsole/mainwindow.cpp:41
#12 0x0000000000433863 in main (argc=1, argv=0x7ffff12c96e8) at ../../akonadiconsole/main.cpp:45

Possible duplicates by query: bug 262173, bug 242778.

Reported using DrKonqi

Comment 1 Christophe Marin 2011-05-18 14:49:26 UTC

> >ran Kcmshell4 kcm_akonadi
> >ran mysql_upgrade as user (suggested) and as root since there were also error messages
> 

erm.. the userbase page doesn't mention it needs to be executed as root (hopefully)

make sure you didn't break it more than it was before. 
you must be the owner of all the files under ~/.local/share/akonadi

Comment 2 Christophe Marin 2011-07-13 15:56:51 UTC

changing status

Comment 3 Andrew Crouthamel 2018-09-22 02:03:36 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Andrew Crouthamel 2018-10-27 04:03:50 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!