akonadiserver and fcitx doesn't work after starting computer, both processes needs to get killed and restarted then they work fine

Bug #1263270 reported by webmarwell on 2013-12-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Akonadi
Unknown
Unknown
dbus (Ubuntu)
Undecided
Unassigned

Bug Description

Since updating to Kubuntu 13.10 I have two problems with these programmes:

akonadiserver starts but doesn't work
A workaround is:
pkill akonadiserver
pkill akonadi-control
aconadictl start

fcitx (an input method for languages, here chinese) starts but doesn't work
A workaround is:
killall fcitx
fcitx

Both programs use dbus. Both problems started after upgrading to 13.10.
Might there be any connection to dBus? It seems, that they start too early, but without any message, that something is missing.

There is as well a bug report at kde.org:
https://bugs.kde.org/show_bug.cgi?id=326480

Diverse questions and bug reports mention that Akonadi Server Self-Test Report shows:

Test 10: ERROR -------- Akonadi control process not registered at D-Bus. Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.
Test 11: ERROR -------- Akonadi server process not registered at D-Bus. Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.
Test 12: ERROR -------- Nepomuk search service not registered at D-Bus. Details: The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.
Test 14: ERROR -------- No resource agents found. Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share:/usr/share:/usr/local/share'; make sure this includes all paths where Akonadi agents are installed.
Directory listing of '/usr/share/akonadi/agents':
(...here the installed agents, I didn't check if they are everywhere the same)

I use the above mentioned workarounds since two month, every 1-2 of 4 times after booting akonadi has this problem. Fcitx input method always has this problem.

I was using KDE 4.11., now using 4.12. I found the problem on the web, appearing in Fedora, Debian, Mageia, OpenSUSE, Kubuntu.
If I can help with any more informations, please let me know how to do it. Thank you!

Quinn Balazs (qbalazs) wrote :

Open a new ticket for your issues with fcitx. Lumping more than one program into a bug report tends to make things complicated, as the problems may be completely unrelated.

webmarwell (webmarwell) wrote :

Well, the Fcitx part here:
http://code.google.com/p/fcitx/issues/detail?id=716&thanks=716&ts=1386304850

The Akonadi part here:
https://bugs.kde.org/show_bug.cgi?id=326480

I thought two programs having a kind of similar problem might be a hint, that it's not one of them, but dBus. The bug report here has explicitly that meaning. If that is true, the bug #1245979 is not an akonadi bug. If you can exclude this, please let me know. As I cant know, I am not shure if this is a duplicate or not.

Thank you!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.