Summary: | akonadictl fsck seems to hang | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Knut Hildebrandt <post> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dvratil, freekdekruijf |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Chakra | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/akonadi/aebf8a1b727c81cb317cebf712dc19a8ec3e5944 | Version Fixed In: | 5.6.2 |
Description
Knut Hildebrandt
2016-04-09 05:38:33 UTC
The error still persists. No I'm having this setup on my machine: Plasma 5.7.2 Applications 16.04.3 Qt 5.7.0 But I noticed one thing. After stopping Akonadi there are still Akonadi related processes running on my machine. They all are called http.so and somehow seem to have to do with the DAV-resources I set up to synchronize my calendar and address book. Might it be that these processes prevent "akonadictl fsck" from doing it's job? I had the same problem after "akonadictl stop". There was no CPU activity related to an akonadi process. However the command works when the status is "running". BTW. same for "akonadictl vacuum". akonadictl fsck is supposed to be run when Akonadi is running. Admittably, running it against stopped Akonadi should produce an error and quit, not hang. I'll work on that. http.so are KIO slaves, they are kept around for a while so they can be effectively reused, but should eventually die on their own if they are unused for longer period of time. Git commit aebf8a1b727c81cb317cebf712dc19a8ec3e5944 by Daniel Vrátil. Committed on 02/10/2017 at 12:23. Pushed by dvratil into branch 'Applications/17.08'. akonadictl: fsck and vacuum require running Akonadi FIXED-IN: 5.6.2 M +11 -1 src/akonadictl/main.cpp https://commits.kde.org/akonadi/aebf8a1b727c81cb317cebf712dc19a8ec3e5944 |