This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Can't get akonadi working

Tags: None
(comma "," separated)
petropolis
Registered Member
Posts
15
Karma
0
OS

Can't get akonadi working

Tue Mar 22, 2011 5:33 am
When I try to start it, I get

[akonadiserver] Failed to use database "akonadi"
[akonadiserver] Database error: "Access denied for user ''@'localhost' to database 'akonadi' QMYSQL: Unable to connect"
[akonadiserver] Trying to create database now...
[akonadiserver] Failed to create database
[akonadiserver] Query error: "Access denied for user ''@'localhost' to database 'akonadi' QMYSQL: Unable to execute query"
[akonadiserver] Database error: "Access denied for user ''@'localhost' to database 'akonadi' QMYSQL: Unable to connect"

Notice that the user is ''. Is this the problem? Also, what does the "Use internal mysql server" checkbox mean when you run "kcmshell4 kcm_akonadi"?
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Can't get akonadi working

Tue Mar 22, 2011 6:09 am
The "Internal MySQL server" means that Akonadi will look after running the components needed for it to store data. This should be ticked in most circumstances, unless you wish to use an alternate server.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
petropolis
Registered Member
Posts
15
Karma
0
OS

Re: Can't get akonadi working

Tue Mar 22, 2011 7:44 pm
OK. Thanks for the info. I'll leave the internal box checked. Is this the right forum for asking questions on Akonadi? My KMail is currently broken since Akonadi isn't working. I can't send mail. This is very distressing since I have all my information in KMail.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Can't get akonadi working

Wed Mar 23, 2011 5:53 am
I have moved it to the correct forum. If you have "Internal MySQL server" ticked, then it should operate. Please post the ~/.local/share/akonadi/akonadiserver.error file.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
petropolis
Registered Member
Posts
15
Karma
0
OS

Re: Can't get akonadi working

Wed Mar 23, 2011 6:15 pm
I got akonadi working by playing around with the mysql.conf file. However, nepomuk isn't working. I'm enclosing the log file when akonadi is starting 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 '/people/ssimpson/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
SizeThreshold=4096
ExternalPayload=false

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

[Debug]
Tracer=null

[QPSQL]
Name=akonadi
Host=
User=ssimpson
Password=
Port=5432


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/sbin/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/sbin/mysqld Ver 5.1.53 for suse-linux-gnu on x86_64 (SUSE MySQL RPM)


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

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

File content of '/people/ssimpson/.local/share/akonadi/db_data/mysql.err':
110323 11:11:48 InnoDB: Started; log sequence number 0 1352366
110323 11:11:48 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.53-log' socket: '/people/ssimpson/.local/share/akonadi/db_misc/mysql.socket' port: 0 SUSE MySQL RPM


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=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

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



Test 7: SKIP
--------

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

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

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

File content of '/people/ssimpson/.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=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

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



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.3.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: 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 13: 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 14: 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
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:/etc/opt/kde3/share:/opt/kde3/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 reported errors during its previous startup. The log can be found in <a href='/people/ssimpson/.local/share/akonadi/akonadiserver.error.old'>/people/ssimpson/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/people/ssimpson/.local/share/akonadi/akonadiserver.error.old':
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 reported errors during its previous startup. The log can be found in <a href='/people/ssimpson/.local/share/akonadi/akonadi_control.error.old'>/people/ssimpson/.local/share/akonadi/akonadi_control.error.old</a>.

File content of '/people/ssimpson/.local/share/akonadi/akonadi_control.error.old':
D-Bus session bus went down - quitting
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Can't get akonadi working

Thu Mar 24, 2011 4:25 am
Please remove the content of ~/.kde4/share/apps/nepomuk outside of KDE assuming you have no valuable information such as tags or ratings stored in Nepomuk.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
petropolis
Registered Member
Posts
15
Karma
0
OS

Re: Can't get akonadi working

Thu Mar 24, 2011 9:19 pm
That doesn't work. I still get the error "Nepomuk search service not registered at D-Bus" when starting up. It did recreate and repopulate the directory though.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Can't get akonadi working

Tue Mar 29, 2011 5:52 am
Do you have the soprano-backend-virtuoso package installed on your system?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
petropolis
Registered Member
Posts
15
Karma
0
OS

Re: Can't get akonadi working

Tue Mar 29, 2011 11:37 pm
It is installed.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Can't get akonadi working

Wed Mar 30, 2011 5:08 am
Unusual, I note you appear to have a similar skip rule to another user, using Fedora who has issues with Akonadi.

Does it work under a new user? Also, try disabling Apparmor if it is enabled (openSUSE ships with it disabled I believe)


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
petropolis
Registered Member
Posts
15
Karma
0
OS

Re: Can't get akonadi working

Thu Mar 31, 2011 12:21 am
AppArmor is off. I'm still "Nepomuk search service not registered at D-Bus" for a different user too.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Can't get akonadi working

Thu Mar 31, 2011 3:16 am
Is Test 13 skipped under the new user as well? If you upgraded KDE, can you please ensure all packages are up to date?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
petropolis
Registered Member
Posts
15
Karma
0
OS

Re: Can't get akonadi working

Thu Mar 31, 2011 4:08 am
Here is the output when I log in under the "scott" user rather than "ssimpson":

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 '/usr/scott/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
SizeThreshold=4096
ExternalPayload=false

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

[Debug]
Tracer=null


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/sbin/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/sbin/mysqld Ver 5.1.53 for suse-linux-gnu on x86_64 (SUSE MySQL RPM)


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

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

File content of '/usr/scott/.local/share/akonadi/db_data/mysql.err':
110330 21:04:12 InnoDB: Started; log sequence number 0 123073
110330 21:04:12 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.53-log' socket: '/usr/scott/.local/share/akonadi/db_misc/mysql.socket' port: 0 SUSE MySQL RPM


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=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

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



Test 7: SKIP
--------

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

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

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

File content of '/usr/scott/.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=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

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



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.3.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: 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 13: ERROR
--------

Server protocol version is too old.
Details: The server protocol version is 23, but at least version 28 is required. Install a newer version of the Akonadi server.

Test 14: 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
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:/etc/opt/kde3/share:/opt/kde3/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 reported errors during its previous startup. The log can be found in <a href='/usr/scott/.local/share/akonadi/akonadiserver.error.old'>/usr/scott/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/usr/scott/.local/share/akonadi/akonadiserver.error.old':
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 reported errors during its previous startup. The log can be found in <a href='/usr/scott/.local/share/akonadi/akonadi_control.error.old'>/usr/scott/.local/share/akonadi/akonadi_control.error.old</a>.

File content of '/usr/scott/.local/share/akonadi/akonadi_control.error.old':
D-Bus session bus went down - quitting
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Can't get akonadi working

Fri Apr 01, 2011 11:13 pm
It appears your system has mismatched packages.
Code: Select all
Details: The server protocol version is 23, but at least version 28 is required. Install a newer version of the Akonadi server.


Please ensure all packages on your system are up to date.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
petropolis
Registered Member
Posts
15
Karma
0
OS

Re: Can't get akonadi working

Mon Apr 04, 2011 6:12 pm
That seemed to fix it. It was odd though. I have all my packages up to date through "yast2 online_update" but when I selected the install of libakonadiprotocolinternals-devel it upgraded my kontact and a bunch of other packages. I think SuSE has some versioning issues.

Another question. All of this started when I upgraded from SuSE 11.3 to 11.4 Now that I've upgraded to SuSE 11.4, all my Contacts seem to have disappeared. Is there any way to recover them? Thanks.


Bookmarks



Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot]