On Thursday 01 July 2010 13:07:19 Jerry wrote: > I have spent a month, on and off, attempting to get this to work > without success. The 'akonadi server' crashes every time I start KDE4. > The Akonadi Server Self-Test Report follows. In particular, numbers: 6, > 7 and 11 always fail although I can not fathom why. An > "akonadiserver.core" file is created although I am not sure how I could > use it to gather any useful information. > > > Akonadi Server Self-Test Report > =============================== > > Test 1: SUCCESS > -------- > > Database driver found. > Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi > server configuration and was found on your system. > > File content of '/home/gerard/.config/akonadi/akonadiserverrc': > [%General] > Driver=QMYSQL > SizeThreshold=4096 > ExternalPayload=false > > [QMYSQL] > Name=akonadi > Host=localhost > User=gerard > Password=blacktop > Options="UNIX_SOCKET=/home/gerard/.local/share/akonadi/db_misc/mysql.socket > " ServerPath=/usr/local/bin/mysqld_safe > StartServer=false > > [QPSQL] > Name=akonadi > Host= > User= > Password= > Port=5432 > > > Test 2: SKIP > -------- > > MySQL server executable not tested. > Details: The current configuration does not require an internal MySQL > server. > > Test 3: SKIP > -------- > > MySQL server error log not tested. > Details: The current configuration does not require an internal MySQL > server. > > Test 4: SKIP > -------- > > MySQL server configuration not tested. > Details: The current configuration does not require an internal MySQL > server. > > Test 5: SUCCESS > -------- > > akonadictl found and usable > Details: The program '/usr/local/kde4/bin/akonadictl' to control the > Akonadi server was found and could be executed successfully. Result: > Akonadi 1.3.1 > > > Test 6: 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 7: 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 8: SUCCESS > -------- > > Nepomuk search service registered at D-Bus. > Details: The Nepomuk search service is registered at D-Bus which > typically indicates it is operational. > > Test 9: SUCCESS > -------- > > Nepomuk search service uses an appropriate backend. > Details: The Nepomuk search service uses one of the recommended > backends. > > Test 10: SKIP > -------- > > Protocol version check not possible. > Details: Without a connection to the server it is not possible to check > if the protocol version meets the requirements. > > Test 11: 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/local/kde4/share/akonadi/agents'. The > XDG_DATA_DIRS environment variable is set to > '/usr/local/kde4/share::/usr/share:/usr/local/share:/usr/local/share/gnome' > , make sure this includes all paths where Akonadi agents are installed to. > > Directory listing of '/usr/local/kde4/share/akonadi/agents': > birthdaysresource.desktop > contactsresource.desktop > icalresource.desktop > imapresource.desktop > kabcresource.desktop > kcalresource.desktop > knutresource.desktop > kolabproxyresource.desktop > localbookmarksresource.desktop > maildirresource.desktop > maildispatcheragent.desktop > mboxresource.desktop > microblog.desktop > mtdummyresource.desktop > nepomukcalendarfeeder.desktop > nepomukcontactfeeder.desktop > nepomuktagresource.desktop > nntpresource.desktop > notesresource.desktop > pop3resource.desktop > vcarddirresource.desktop > vcardresource.desktop > > Environment variable XDG_DATA_DIRS is set to > '/usr/local/kde4/share::/usr/share:/usr/local/share:/usr/local/share/gnome' > > Test 12: SUCCESS > -------- > > No current Akonadi server error log found. > Details: The Akonadi server did not report any errors during its > current startup. > > Test 13: SUCCESS > -------- > > No previous Akonadi server error log found. > Details: The Akonadi server did not report any errors during its > previous startup. > > Test 14: SUCCESS > -------- > > No current Akonadi control error log found. > Details: The Akonadi control process did not report any errors during > its current startup. > > Test 15: SUCCESS > -------- > > No previous Akonadi control error log found. > Details: The Akonadi control process did not report any errors during > its previous startup.
Well, I've spoken to the Akonadi guys on IRC, and they said the best thing to do in this case is to file a new bug report via https://bugs.kde.org with the results of this self test. You could also include the output of akonadictl start. Jerry and others who are having woes with Akonadi+MySQL, can you guys please do that? I think it'll be better than if we stay here trying to find out what's wrong. _______________________________________________ kde-freebsd mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
