Announcement

Collapse
No announcement yet.

KAddressBook problems

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    KAddressBook problems

    The first time I run Kontact after starting a new session, the Contacts page is grayed out and superimposed is the message "Akonadi not operational". When I click on Details, I get a popup with this 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/jeffbarish/.config/akonadi/akonadiserverrc':
    [%General]
    Driver=QMYSQL
    SizeThreshold=4096
    ExternalPayload=false

    [QMYSQL]
    Name=akonadi
    Host=
    User=
    Password=
    Options="UNIX_SOCKET=/home/jeffbarish/.local/share/akonadi/db_misc/mysql.socket"
    ServerPath=/usr/sbin/mysqld-akonadi
    StartServer=true

    [Debug]
    Tracer=null


    Test 2: SUCCESS
    --------

    MySQL server found.
    Details: You currently have configured Akonadi to use the MySQL server '/usr/sbin/mysqld-akonadi'.
    Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld', its locations varies depending on the distribution.

    Test 3: SUCCESS
    --------

    MySQL server is executable.
    Details: MySQL server found: /usr/sbin/mysqld-akonadi Ver 5.1.41-3ubuntu11 for debian-linux-gnu on i486 ((Ubuntu))


    Test 4: SUCCESS
    --------

    MySQL server log contains no errors.
    Details: The MySQL server log file &apos;<a href='/home/jeffbarish/.local/share/akonadi/db_data/mysql.err'>/home/jeffbarish/.local/share/akonadi/db_data/mysql.err</a>&apos; does not contain any errors or warnings.

    File content of '/home/jeffbarish/.local/share/akonadi/db_data/mysql.err':
    100723 16:16:19 [Note] Plugin 'FEDERATED' is disabled.
    100723 16:16:20 InnoDB: Started; log sequence number 0 11890620
    100723 16:16:21 [Note] /usr/sbin/mysqld-akonadi: ready for connections.
    Version: '5.1.41-3ubuntu11-log' socket: '/home/jeffbarish/.local/share/akonadi/db_misc/mysql.socket' port: 0 (Ubuntu)


    Test 5: SUCCESS
    --------

    MySQL server default configuration found.
    Details: The default configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-global.conf'>/etc/akonadi/mysql-global.conf</a>.

    File content of '/etc/akonadi/mysql-global.conf':
    #
    # Global Akonadi MySQL server settings,
    # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
    #
    # Based on advice by Kris Köhntopp <kris@mysql.com>
    #
    [mysqld]
    skip_grant_tables
    skip_networking

    # strict query parsing/interpretation
    # TODO: make Akonadi work with those settings enabled
    #sql_mode=strict_trans_tables,strict_all_tables,st rict_error_for_division_by_zero,no_auto_create_use r,
    no_auto_value_on_zero,no_engine_substitution,no_ze ro_date,no_zero_in_date,only_full_group_by,
    pipes_as_concat
    #sql_mode=strict_trans_tables

    # use InnoDB for transactions and better crash recovery
    default_storage_engine=innodb
    # case-insensitive table names, avoids trouble on windows
    lower_case_table_names=1
    character_set_server=latin1
    collation_server=latin1_general_ci
    table_cache=200
    thread_cache_size=3
    log_bin=mysql-bin
    expire_logs_days=3
    #sync_bin_log=0
    # error log file name, relative to datadir
    log_error=mysql.err
    log_warnings=2
    # log all queries, useful for debugging but generates an enormous amount of data
    #log=mysql.full
    # log queries slower than n seconds, log file name relative to datadir (for debugging only)
    #log_slow_queries=mysql.slow
    #long_query_time=1
    # log queries not using indices, debug only, disable for production use
    #log_queries_not_using_indexes=1
    # maximum blob size
    max_allowed_packet=32M
    max_connections=256
    # makes sense when having the same query multiple times
    # makes no sense with prepared statements and/or transactions
    query_cache_type=0
    query_cache_size=0

    innodb_file_per_table=1
    innodb_log_buffer_size=1M
    innodb_additional_mem_pool_size=1M
    # messure database size and adjust
    # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
    innodb_buffer_pool_size=80M
    # size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
    innodb_log_file_size=64M
    innodb_flush_log_at_trx_commit=2



    Test 6: SKIP
    --------

    MySQL server custom configuration not available.
    Details: The custom configuration for the MySQL server was not found but is optional.

    Test 7: SUCCESS
    --------

    MySQL server configuration is usable.
    Details: The MySQL server configuration was found at <a href='/home/jeffbarish/.local/share/akonadi/mysql.conf'>/home/jeffbarish/.local/share/akonadi/mysql.conf</a> and is readable.

    File content of '/home/jeffbarish/.local/share/akonadi/mysql.conf':
    #
    # Global Akonadi MySQL server settings,
    # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
    #
    # Based on advice by Kris Köhntopp <kris@mysql.com>
    #
    [mysqld]
    skip_grant_tables
    skip_networking

    # strict query parsing/interpretation
    # TODO: make Akonadi work with those settings enabled
    #sql_mode=strict_trans_tables,strict_all_tables,st rict_error_for_division_by_zero,no_auto_create_use r,
    no_auto_value_on_zero,no_engine_substitution,no_ze ro_date,no_zero_in_date,only_full_group_by,
    pipes_as_concat
    #sql_mode=strict_trans_tables

    # use InnoDB for transactions and better crash recovery
    default_storage_engine=innodb
    # case-insensitive table names, avoids trouble on windows
    lower_case_table_names=1
    character_set_server=latin1
    collation_server=latin1_general_ci
    table_cache=200
    thread_cache_size=3
    log_bin=mysql-bin
    expire_logs_days=3
    #sync_bin_log=0
    # error log file name, relative to datadir
    log_error=mysql.err
    log_warnings=2
    # log all queries, useful for debugging but generates an enormous amount of data
    #log=mysql.full
    # log queries slower than n seconds, log file name relative to datadir (for debugging only)
    #log_slow_queries=mysql.slow
    #long_query_time=1
    # log queries not using indices, debug only, disable for production use
    #log_queries_not_using_indexes=1
    # maximum blob size
    max_allowed_packet=32M
    max_connections=256
    # makes sense when having the same query multiple times
    # makes no sense with prepared statements and/or transactions
    query_cache_type=0
    query_cache_size=0

    innodb_file_per_table=1
    innodb_log_buffer_size=1M
    innodb_additional_mem_pool_size=1M
    # messure database size and adjust
    # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
    innodb_buffer_pool_size=80M
    # size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
    innodb_log_file_size=64M
    innodb_flush_log_at_trx_commit=2



    Test 8: SUCCESS
    --------

    akonadictl found and usable
    Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
    Result:
    Akonadi 1.3.1


    Test 9: SUCCESS
    --------

    Akonadi control process registered at D-Bus.
    Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational.

    Test 10: SUCCESS
    --------

    Akonadi server process registered at D-Bus.
    Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational.

    Test 11: 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 12: SUCCESS
    --------

    Nepomuk search service uses an appropriate backend.
    Details: The Nepomuk search service uses one of the recommended backends.

    Test 13: SUCCESS
    --------

    Server protocol version is recent enough.
    Details: The server Protocol version is 23, which equal or newer than the required version 23.

    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 /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 to.

    Directory listing of '/usr/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
    Directory listing of '/usr/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/share:/usr/share:/usr/local/share'

    Test 15: SUCCESS
    --------

    No current Akonadi server error log found.
    Details: The Akonadi server did not report any errors during its current startup.

    Test 16: ERROR
    --------

    Previous Akonadi server error log found.
    Details: The Akonadi server did report error during its previous startup into <a href='/home/jeffbarish/.local/share/akonadi/akonadiserver.error.old'>/home/jeffbarish/.local/share/akonadi/akonadiserver.error.old</a>.

    File content of '/home/jeffbarish/.local/share/akonadi/akonadiserver.error.old':
    Database error: DataStore::beginTransaction
    Last driver error: "QMYSQL: Unable to begin transaction"
    Last database error: "MySQL server has gone away"
    Database error: DataStore::beginTransaction
    Last driver error: "QMYSQL: Unable to begin transaction"
    Last database error: "MySQL server has gone away"
    Database error: DataStore::beginTransaction
    Last driver error: "QMYSQL: Unable to begin transaction"
    Last database error: "MySQL server has gone away"
    Database error: DataStore::beginTransaction
    Last driver error: "QMYSQL: Unable to begin transaction"
    Last database error: "MySQL server has gone away"
    Control process died, committing suicide!
    D-Bus session bus went down - quitting


    Test 17: SUCCESS
    --------

    No current Akonadi control error log found.
    Details: The Akonadi control process did not report any errors during its current startup.

    Test 18: ERROR
    --------

    Previous Akonadi control error log found.
    Details: The Akonadi control process did report error during its previous startup into <a href='/home/jeffbarish/.local/share/akonadi/akonadi_control.error.old'>/home/jeffbarish/.local/share/akonadi/akonadi_control.error.old</a>.

    File content of '/home/jeffbarish/.local/share/akonadi/akonadi_control.error.old':
    D-Bus session bus went down - quitting


    If I then quit Kontact and restart it from the K button, Kontact doesn't run at all. If I type kontact at a command prompt, the command returns immediately. I keep trying to restart it from the K button or by typing kontact, kmail, kaddressbook, or knode at a command prompt. Eventually, I get a message that kontact crashed. I can then restart kontact and kaddressbook looks fine. However, I usually get one chance to use it. Once I have selected a contact and the details appear, I can select other contacts, but the details for the first contact remain. Sometimes kaddressbook works correctly, though. Any idea what's going on?

    And another thing about kaddressbook: I assigned categories to all my contacts. Since upgrading, I get all my contacts regardless of category. That's annoying because most of my contacts were in the category "obsolete", indicating that I rarely wanted to view them. I have to scroll through hundreds of contacts now to find the ones in which I am interested.

    #2
    Re: KAddressBook problems

    Good luck with finding a solution. I had the same problems with Kontact and then just gave up on it.

    I believe that Snowhog has some posts on the same subject. Akonadi expects the "resources" to be in a specific location, and doesn't like it when they are not in that location. Why files like the .vcf don't get copied during an upgrade, or aren't found by Akonadi is simply beyond my understanding. But, IIRC, Snowhog resolved his problem by placing the address book files in the correct location.

    I resolved my problem by moving on to Thunderbird and Lightning.

    In the meantime, try to search for kaddressbook, akonadi, and the user "snowhog". I don't know where the fix was posted.

    EDIT: I found the thread, it's in the How-To area.
    HOWTO Configure KDE and Akonadi so it just works
    The next brick house on the left
    Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.27.11​| Kubuntu 24.04 | 6.8.0-31-generic



    Comment


      #3
      Re: KAddressBook problems

      If the problem is that files are not in the right place, it seems odd that KAddressBook does eventually run, but I will investigate further when I return from travels. Thanks for the pointer.

      Comment


        #4
        Re: KAddressBook problems

        You may find this post useful:
        http://kubuntuforums.net/forums/inde...opic=3112175.0

        Regards .....
        Kubuntu User #9802
        Linux Registered User #357086

        Comment


          #5
          Re: KAddressBook problems

          Originally posted by bitzbox
          You may find this post useful:
          http://kubuntuforums.net/forums/inde...opic=3112175.0

          Regards .....
          Yes, that would be the same one
          The next brick house on the left
          Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.27.11​| Kubuntu 24.04 | 6.8.0-31-generic



          Comment

          Working...
          X