Summary: | Search mail kills akonadi server | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Axel Braun <axel.braun> |
Component: | Indexer | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chrigi_1, dvratil |
Priority: | NOR | ||
Version: | 5.8.2 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Axel Braun
2018-07-19 06:13:51 UTC
After starting akonadi manually again: ---- docb@T520:~> akonadictl start Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadiserver: PostgreSQL for Akonadi is already running, trying to connect to it. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadicontrol: "AgentManager::agentInstanceSynchronizeCollection" Agent instance "akonadi_imap_resource_0" has no resource interface! org.kde.pim.akonadiserver: "Cannot connect to agent instance with identifier 'akonadi_imap_resource_0', error message: ''" true org.kde.kgapi.raw: CalendarFetchJob::url() QUrl("https://www.googleapis.com/calendar/v3/users/me/calendarList") org.kde.kgapi.raw: ("Authorization: Bearer ya29.Gl39BURP6bpxdY5X1azR1lZTt1E4ILmYggWfP7wqNGMTZYcS8zlL2iVKYainDKlbniMji2L2ulvEereyZYnCyAgherW8_K5d8q07p2dpZouQ3eQ8HwQKiO2TqwuqOwY", "GData-Version: 3") org.kde.kgapi: Queued QUrl("https://www.googleapis.com/calendar/v3/users/me/calendarList") org.kde.kgapi: KGAPI2::CalendarFetchJob(0x55660bdd7f70) Dispatching request to QUrl("https://www.googleapis.com/calendar/v3/users/me/calendarList") org.kde.kgapi.raw: "" true true ---- The mentioned akonadi_imap_resource_0 is shown in akonadiconsole as 'ready, idle'...so, is this a critical issue or not? Is this still happening? Can you get a backtrace of the crash from DrKonqi? I'm currently running kmail 5.6.3 and could not reproduce. Indexing-Window (needs reindex) comes up, reindex confirmed, and after a second the result is displayed. No crash anymore I think we've fixed this in 18.08, please do reopen if it starts happening again. |