![]() Registered Member ![]()
|
Hello,
I'm running kde on debian stable and daily updates and one of the last updates caused some misbehaviour of kmail. As I use kmail for many years without major issues, I did not care much about configuration/updates ... Now it happens, that 3 out of 4 reboots kmail is blocked by a shaded rectangle telling me, that akonadi does not work. I really don't know much about kde, kmail and its internals - I'm just a kde user. So I tried a fresh installation of the whole system, but after mounting my (existing) home directory, its behaviour is as before. If kmail would fail on every reboot, I would state, that my system is broken. But if it fails only 3 out of 4 reboots ... ... there may be some timing issues, I don't know, how to get rid of. Looking at the log of kmail, test 10 is the first that fails:
Test 14 may be interesting too (don't know, whether they are related):
Checking akonadi as a root user results in these outputs:
Doing the same as desktop user:
It says - akonadi server is stopped. ... so I tried to start it:
Running qdbus as root fails like akonadictl:
... but running qdbus as desktop user shows these lines:
My kde desktop is configured to restore a saved session, which consists of 4 virtual screens and kmail is an opened app on one of these screens. Furthermore the saved session starts krusader and about 15 konsoles I don't know, how to get rid of the problem. So if anybody could shine me a light ... best regards Reinhard |
![]() Administrator ![]()
|
You can't use akonadictl as root because it needs a local DBus session, which is initiated by your user. When you see these errors in KMail, try, as regular user, to issue "akonadictl restart" in the terminal and report here any output (if too long, use a pastebin service).
"Violence is the last refuge of the incompetent."
![]() Plasma FAQ maintainer - Plasma programming with Python |
![]() Registered Member ![]()
|
Hello einar,
thanks for your attention! When I powered on my box, it came up with kmail locked. So I followed your advice ...
followed by a
So I did, what seems to work - sometimes:
and then login on console as root and issue a
After login to kdm, kmail works fine ![]() best regards Reinhard |
Registered users: Baidu [Spider], Bing [Bot], Google [Bot]