[Bug 1263270] Re: akonadiserver and fcitx doesn't work after starting computer, both processes needs to get killed and restarted then they work fine

[Quinn Balazs]

*** This bug is a duplicate of bug 1245979 ***
    https://bugs.launchpad.net/bugs/1245979

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.

** Bug watch added: KDE Bug Tracking System #326480
   https://bugs.kde.org/show_bug.cgi?id=326480

** Also affects: akonadi via
   https://bugs.kde.org/show_bug.cgi?id=326480
   Importance: Unknown
       Status: Unknown

** This bug has been marked a duplicate of bug 1245979
   After Upgrade to Kubuntu 13.10 akondai fails to register at d-bus session, making kde-pim suit unusable

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1263270

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

Status in Akonadi - The PIM Storage Service:
  Unknown
Status in “dbus” package in Ubuntu:
  New

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!

To manage notifications about this bug go to:
https://bugs.launchpad.net/akonadi/+bug/1263270/+subscriptions