Bug 241883 - Akonadi registration or initialization fails
Summary: Akonadi registration or initialization fails
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: server (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Volker Krause
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-06-16 07:54 UTC by Martin L ü c h e m
Modified: 2018-10-21 04:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin L ü c h e m 2010-06-16 07:54:50 UTC
Version:           unspecified (using Devel) 
OS:                Linux

This is far away from beiing able to describe correctly. When starting KMail I get a message from the Akonadi test console like that:

"Der QtSQL-Treiber „QMYSQL“ wird von Ihrer aktuellen Akonadi-Serverkonfiguration benötigt und er wurde auf Ihrem System gefunden."

The message is absolutely sensless and seems to be wrong even when I interpret it the other way around. I checked my Debian ressources for QMYSQL and nothing is found. This for sure should not be a bug with my installation because I never installed Akonadi packages as local ressources. No, it is obviously that the configuration / registration of Akonadi was not initialized correctly. But I try to use this system productively and need a solution like providing a packages that fixes this bug. 

Sorry but messing arond with this every time the system is started is annoying!

Regards, Martin

Reproducible: Sometimes

Steps to Reproduce:
nothing special Ijust start my system

Actual Results:  
not really possible. Maybe thereis a difference when starting kontact or starting kmail or first starting kaddressbook.

Expected Results:  
some times the error described above sometimes another one with akonadi

OS: Linux (x86_64) release 2.6.32-5-amd64
Compiler: cc
Comment 1 Martin L ü c h e m 2010-06-16 07:56:15 UTC
sorry, I forgot: Which applications crash? KMail, KAdressbook, Akonadi itself, all, some of them and/or in different order.
Comment 2 Martin L ü c h e m 2010-06-16 07:57:18 UTC
This is KDE 4.4.4. Sorry, I always forget that bugs.kde.org does not list thsi version of KDE
Comment 3 Nicolas L. 2010-06-17 10:46:48 UTC
please add the backtrace of the crash in this bugreport
Comment 4 Martin L ü c h e m 2010-07-04 11:45:13 UTC
Hallo Nicolas,

Am Donnerstag, 17. Juni 2010, um 10:47:12 schrieb Nicolas Lécureuil:
> please add the backtrace of the crash in this bugreport

sorry but I cannot add a crash report because sometimes it happens and 
somtimes it does not happen. May be it has somthing to do with the 
chronological order while starting kde and kmail. If it happens from time to 
time the situation is even worse and I absolutely cannot send in meaningful 
information.

What I really wonder is, why there is no defined order of starting kde and its 
resources and a way to control this. Controlling it does NOT mean that I as a 
user have to play around with this but that there is a defined order and this 
is described so that I can find a solution or even a hint, whatthe reason 
might be.

disillusioned, Martin
Comment 5 Andrew Crouthamel 2018-09-20 22:03:41 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 6 Andrew Crouthamel 2018-10-21 04:36:52 UTC
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!