Summary: | Akonadi crashes often and can't be restarted | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Andreas Hencke <andreas.hencke> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | REPORTED --- | ||
Severity: | grave | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Backtrace from Dr Konqi
Here is the missing backtrace |
Description
Andreas Hencke
2020-05-28 08:41:30 UTC
Do you have a backtrace? Not yet, because of the backtraces were marked as useless so I didn't saved one. Right now akonadi crashed again, this time dr. konqi didn't start aswell. I tryed to start akonadi via Konsole and got this output: andreas@rex-PC:~$ akonadictl stop Akonadi is not running. andreas@rex-PC:~$ akonadictl start org.kde.pim.akonadicontrol: Service org.freedesktop.Akonadi.Control.lock already registered, terminating now. Error: akonadi_control was started but didn't register at D-Bus session bus. Make sure your system is set up correctly! I'll report a backtrace asap! Created attachment 128899 [details]
Backtrace from Dr Konqi
This is a backtrace from my other Desktop machine. It has a MSI A320m motherboard and a Ryzen5 2400G CPU. / and /home are splitted as in the other machine. One point might be importandt: On this machine I installed Kubuntu 20.04 in January from a daily iso, Up to the official release of Kubuntu 20.04 akonadi was working prperly without an issue. (In reply to Andreas Hencke from comment #3) > Created attachment 128899 [details] > Backtrace from Dr Konqi there is no backtrace in this attachment Created attachment 128920 [details]
Here is the missing backtrace
Sorry, forr sending the the wrong content as an attachment.
|