| Summary: | crash at the start of Korganizer. Impossible to use. Akonadi problem with D-Bus. | ||
|---|---|---|---|
| Product: | [Applications] korganizer | Reporter: | bobbyxh <hardy.xavier> |
| Component: | journalview | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | grave | CC: | francoismalias-fwd, smartins |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Akonadi self test log | ||
|
Description
bobbyxh
2015-04-08 09:16:43 UTC
I tried to reinstall korganizer but the problem is still the same Created attachment 92866 [details]
Akonadi self test log
Hello, I face the exact same issue: since I updated to KUbuntu 15.04, KOrganizer crashes at start up, with error message telling that personal data couln't be operated. The Akonadi self test report (attached) mentions an error in test #5 telling: "MySQL server log contains errors" etc. Would appreciate any help to fixing this blocking issue. Thanks in advance. Can you get a backtrace with symbols ? Sorry, I could neither find any korganizer-dbg package nor manage to build one (re: wiki.debian.org/HowToGetABacktrace) Could you please guide me a bit on the way to get the backtrace with symbols that you need, in the present case ? Hello, You can close it. I had to reinstall all my computer to make it work. There was certainly a conflict betwin akonadi and mysql workbench because it happened when i installed it. Thanks for your answer. De: "Sergio Martins" <iamsergio@gmail.com> À: "hardy xavier" <hardy.xavier@free.fr> Envoyé: Jeudi 28 Mai 2015 19:13:38 Objet: [korganizer] [Bug 345972] crash at the start of Korganizer. Impossible to use. Akonadi problem with D-Bus. https://bugs.kde.org/show_bug.cgi?id=345972 Sergio Martins <iamsergio@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iamsergio@gmail.com --- Comment #4 from Sergio Martins <iamsergio@gmail.com> --- Can you get a backtrace with symbols ? Good news for bobbyxh. But I'm not prepared to reinstall the whole system just to fix a conflict between Akonadi and MySql. Apparently, a lot of applications became dependant on Akonadi within the new KUbuntu 15.04. Then it would certainly be worth to understand this drawback. So, please keep it open. Thanks. ok -----Message d'origine----- De : bugzilla_noreply@kde.org [mailto:bugzilla_noreply@kde.org] De la part de Francois M Envoyé : vendredi 29 mai 2015 23:44 À : hardy.xavier@free.fr Objet : [korganizer] [Bug 345972] crash at the start of Korganizer. Impossible to use. Akonadi problem with D-Bus. https://bugs.kde.org/show_bug.cgi?id=345972 --- Comment #7 from Francois M <francoismalias-fwd@yahoo.fr> --- Good news for bobbyxh. But I'm not prepared to reinstall the whole system just to fix a conflict between Akonadi and MySql. Apparently, a lot of applications became dependant on Akonadi within the new KUbuntu 15.04. Then it would certainly be worth to understand this drawback. So, please keep it open. Thanks. -- You are receiving this mail because: You reported the bug. --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. http://www.avast.com This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input. |