How to fix this error every time I start up Kontact

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/barry/.config/akonadi/akonadiserverrc':
[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/barry/.local/share/akonadi/socket-goduskyb.pcprotechs/mysql.socket"
ServerPath=/usr/libexec/mysqld
StartServer=true

[Debug]
Tracer=null

[%General]
Driver=QMYSQL


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

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

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

MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server '/usr/libexec/mysqld'.
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 location varies depending on the distribution.

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

MySQL server is executable.
Details: MySQL server found: /usr/libexec/mysqld Ver 5.1.55 for redhat-linux-gnu on i386 (Source distribution)


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

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

File content of '/home/barry/.local/share/akonadi/db_data/mysql.err':
110317 18:13:49 InnoDB: Initializing buffer pool, size = 80.0M
110317 18:13:49 InnoDB: Completed initialization of buffer pool
110317 18:13:49 InnoDB: Started; log sequence number 0 891838
110317 18:13:50 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.55' socket: '/home/barry/.local/share/akonadi/socket-goduskyb.pcprotechs/mysql.socket' port: 0 Source distribution


Test 6: 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,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_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=utf8
collation_server=utf8_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=8M
innodb_flush_log_at_trx_commit=2

# Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=1296000

[client]
default-character-set=utf8


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

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

File content of '/etc/akonadi/mysql-local.conf':


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

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

File content of '/home/barry/.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,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_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=utf8
collation_server=utf8_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=8M
innodb_flush_log_at_trx_commit=2

# Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=1296000

[client]
default-character-set=utf8


Test 9: 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.5.1


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

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

Test 14: 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 15: SUCCESS
--------

Resource agents found.
Details: At least one resource agent has been found.

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/kde-settings/kde-profile/default/share:/usr/local/share:/usr/share'

Test 16: SUCCESS
--------

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

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

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

Test 18: SUCCESS
--------

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

Test 19: SUCCESS
--------

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

Just started getting these errors about a week or two ago after an update.

I have searched the web and added it to the startup group but to no avail the error still persists!

Any help would be greatly appreciated.

That is simply a startup report indicating full and correct operation, and can be safely ignored.

How do I stop it from popping up? It never used to do this.

Also it says it can not determine the protocol and further down there are two more errors, that says it found a previous error log after claiming it couldn't find one.

All i want is this very annoying diagnostic window from popping up every time I start-up Kontact like it used to before the updates without the protocol and previous error logs found!

Being unable to determine the protocol version likely means that the Akonadi server is failing to start up, or it's socket is otherwise not accessible by your user (which shouldn't happen)

Please post the content of the file located at ~/.local/share/akonadi/akonadiserver.error.

bcooksley wrote:Being unable to determine the protocol version likely means that the Akonadi server is failing to start up, or it's socket is otherwise not accessible by your user (which shouldn't happen)

Please post the content of the file located at ~/.local/share/akonadi/akonadiserver.error.

Sorry for the delay. But here is the initial report when Akonadi starts up.
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/barry/.config/akonadi/akonadiserverrc':
[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/barry/.local/share/akonadi/socket-goduskyb.pcprotechs/mysql.socket"
ServerPath=/usr/libexec/mysqld
StartServer=true

[Debug]
Tracer=null

[%General]
Driver=QMYSQL


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

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

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

MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server '/usr/libexec/mysqld'.
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 location varies depending on the distribution.

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

MySQL server is executable.
Details: MySQL server found: /usr/libexec/mysqld Ver 5.1.55 for redhat-linux-gnu on i386 (Source distribution)


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

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

File content of '/home/barry/.local/share/akonadi/db_data/mysql.err':
110324 20:29:53 InnoDB: Initializing buffer pool, size = 80.0M
110324 20:29:53 InnoDB: Completed initialization of buffer pool
110324 20:29:53 InnoDB: Started; log sequence number 0 1004522
110324 20:29:54 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.55' socket: '/home/barry/.local/share/akonadi/socket-goduskyb.pcprotechs/mysql.socket' port: 0 Source distribution


Test 6: 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,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_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=utf8
collation_server=utf8_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=8M
innodb_flush_log_at_trx_commit=2

# Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=1296000

[client]
default-character-set=utf8


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

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

File content of '/etc/akonadi/mysql-local.conf':


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

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

File content of '/home/barry/.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,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_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=utf8
collation_server=utf8_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=8M
innodb_flush_log_at_trx_commit=2

# Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=1296000

[client]
default-character-set=utf8


Test 9: 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.5.1


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

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

Test 14: 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 15: SUCCESS
--------

Resource agents found.
Details: At least one resource agent has been found.

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/kde-settings/kde-profile/default/share:/usr/local/share:/usr/share'

Test 16: SUCCESS
--------

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

Test 17: ERROR
--------

Previous Akonadi server error log found.
Details: The Akonadi server reported errors during its previous startup. The log can be found in <a href='/home/barry/.local/share/akonadi/akonadiserver.error.old'>/home/barry/.local/share/akonadi/akonadiserver.error.old</a>.

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


Test 18: SUCCESS
--------

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

Test 19: ERROR
--------

Previous Akonadi control error log found.
Details: The Akonadi control process reported errors during its previous startup. The log can be found in <a href='/home/barry/.local/share/akonadi/akonadi_control.error.old'>/home/barry/.local/share/akonadi/akonadi_control.error.old</a>.

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

My previous post of the errors was after it was running so it did not show all the errors that are happening.

And here is a copy of the requested file:

D-Bus session bus went down - quitting

This file is always listed as being a .old file. Even if I delete this file and reboot the system and start Kontact I get the errors listed above in the corrected start up message!

Now after I close the start up message all appears to be working fine with Kontact and all of it's plugins from email to calender including my personal contacts list.

Any assistance in solving this annoying problem would be greatly appreciated!

This is extremely unusual, as it seems that Akonadi starts fine, yet fails to listen on it's socket (causing the protocol check to skip)

Please remove ~/.config/akonadi/akonadiconnectionrc and ensure that you have full ability to read and write under ~/.local/share/akonadi/socket-$(hostname)/ (which is a symlink to a location at /tmp/akonadi-$USER.<random string>)

bcooksley wrote:This is extremely unusual, as it seems that Akonadi starts fine, yet fails to listen on it's socket (causing the protocol check to skip)

Please remove ~/.config/akonadi/akonadiconnectionrc and ensure that you have full ability to read and write under ~/.local/share/akonadi/socket-$(hostname)/ (which is a symlink to a location at /tmp/akonadi-$USER.<random string>)

I have tried both of your suggestions and am able to read/write into the directory you mentioned. And deleted the file you mentioned and the errors still persist.

Not sure why this occurs... very odd. If you have SELinux or Apparmor present, please disable them (completely) as they may be interfering.

bcooksley wrote:Not sure why this occurs... very odd. If you have SELinux or Apparmor present, please disable them (completely) as they may be interfering.

Ok disabled SELinux and still have the problem and apparmor is not loaded on this machine.

This error is rather troublesome not to mention annoying as heck since everything works as it should in Kontact.

If you execute "akonadictl status" in Konsole, does it indicate Akonadi is running? If it does, then this dialog can be ignored and dismissed, as there is no problem in reality.

bcooksley wrote:If you execute "akonadictl status" in Konsole, does it indicate Akonadi is running? If it does, then this dialog can be ignored and dismissed, as there is no problem in reality.

Yes it is running. I have been ignoring it but it is still very annoying to have to close that darn window every time I open Kontact for the first time every day!

TO: bcooksley / Administrator; and All -

bcooksley wrote: ~snip~ Please post the content of the file located at ~/.local/share/akonadi/akonadiserver.error.

Should I start a separate thread, or just post here? So far, I haven't used Kontact. I have a Post titled: "KNotes: Need Path to Find Actual KNotes Files"

In searching for an answer, I thought KNotes works with Kontact, so I tried to start Kontact. What I get is a horizontal box titled: Starting Akonadi server... There is an icon that slowly moves back and forth as the Akonadi is searching, loading or buffering...

It has been doing that for a least an hour. At this time it is NOT important for me to get Kontact running, unless it helps me find my actual KNotes files.

Above was the instruction to: "Please post the content of the file located at ~/.local/share/akonadi/akonadiserver.error"

Here is my file contents. (If there is some obvious / easy fix, please let me know.)

Database process exited unexpectedly during initial connection!
executable: "/usr/local/bin/mysqld_safe"
arguments: ("--defaults-file=/home/1/.local/share/akonadi//mysql.conf", "--datadir=/home/1/.local/share/akonadi/db_data/", "--socket=/home/1/.local/share/akonadi/db_misc/mysql.socket")
stdout: "110403 10:02:27 mysqld_safe Logging to '/home/1/.local/share/akonadi/db_data//pcbsd-5856.err'.
110403 10:02:27 mysqld_safe Starting mysqld daemon with databases from /home/1/.local/share/akonadi/db_data/
110403 10:02:28 mysqld_safe mysqld from pid file /home/1/.local/share/akonadi/db_data//pcbsd-5856.pid ended
"
stderr: ""
exit code: 0
process error: "Unknown error"

---------------

Thanks for any help. Eric7

Please start a seperate thread for that, and include the output of "akonadictl start" from the console. If it indicates that it is running, please run "akonadictl stop", then try again.

bcooksley wrote:If you execute "akonadictl status" in Konsole, does it indicate Akonadi is running? If it does, then this dialog can be ignored and dismissed, as there is no problem in reality.

Thanks for your help.

This problem has been resolved with the last set of updates that installed today from the KDE test repo.

Again thanks for all your help.