Summary: | Akonadi control process not registered at D-Bus/Akonadi server process not registered at D-Bus | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | David A. Smith <dasmith> |
Component: | general | Assignee: | Volker Krause <vkrause> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dasmith, kde, kdepim-bugs, l.prugger |
Priority: | NOR | Keywords: | investigated, triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mandriva RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Akonadi Self-Test Report Log |
Description
David A. Smith
2010-03-06 03:35:24 UTC
Created attachment 41370 [details]
Akonadi Self-Test Report Log
i think this is a mdv issue please do : - install mysql-core - remove old akonadi config stuff with the command: mv ~/.local/share/akonadi/ mv ~/.local/share/akonadi-old/ restart KDE I have mysql-5.1.42-0.2mdv2010.0-i586.rpm currently installed. Is there a newer version? David i told about mysql-core ;) Dear Nicolas, I have done the following with no difference. Akonadi still reports D-Bus isn't registered. David A. Smith Nicolas Lécureuil wrote: > https://bugs.kde.org/show_bug.cgi?id=229644 > > > Nicolas Lécureuil <nlecureuil@mandriva.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |nlecureuil@mandriva.com > > > > > --- Comment #2 from Nicolas Lécureuil <nlecureuil mandriva com> 2010-03-13 10:25:27 --- > i think this is a mdv issue please do : > > - install mysql-core > > - remove old akonadi config stuff with the command: > mv ~/.local/share/akonadi/ mv ~/.local/share/akonadi-old/ > > restart KDE > > is /etc/my.cnf file installed on your machine ? Yes, this file was created when I installed Mandriva Linux 2010.0 PowerPack. David A. Smith Yes, this file was created when I installed Mandriva Linux 2010.0 PowerPack. David A. Smith This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change. |