Bonjour,

J'ai l'impression d'être complètement neuneu, mais je finis par poster pour un problème que je rencontre depuis au moins la précédente version d'openSUSE : je n'arrive pas à ajouter mon google calendar, configuré avec akonadi à la liste de calendrier KDE.

Je m'explique : j'ai créé un calendrier avec akonadi (après avoir installé le paquet akonadi-googledata). Je lance Kontact, vais dans la section calendrier, clique pour en ajouter un nouveau, indique Akonadi pour le type. Je me retrouve avec une nouvelle fenêtre appelée "gestion des ressources Kontact" dans laquelle mon agenda devrait être listé.
Ce n'est pas le cas, mais la fenêtre indique que dans ce cas, je dois cliquer sur "gérer mes sources de calendrier" pour ajouter une source. Ce que je fais. Une nouvelle fenêtre apparaît, dans laquelle figure bien mon calendrier google, mais je n'arrive pas à l'ajouter dans la liste de la fenêtre précédente.
C'est complètement stupide (je dois être stupide), mais dans la fenêtre où mon calendrier est listé, je n'ai que trois actions possibles : "ajouter" ce qui me créer un nouvel agenda akonadi, modifier et supprimer. Rien d'autre. J'ai tenté de faire un drag & drop, sans succès.

Une petite capture d'écran valant parfois mieux qu'un long discours :

(version plus lisible sur imageshack)

En fait, je n'arrive pas à faire passer le calendrier figurant dans la fenêtre la plus à droite dans celle du milieu ... J'ai le même souci avec mes contacts akonadi-google ...

J'ai posté sur les forums anglo et franophones d'openSUSE, sans avoir trop de réponse jusqu'à maintenant.

Des idées ??

Merci d'avance !

Antoine

Salut,
C'est peut-être dans les paramètres de ta configuration ? Il ne valide les paramètres que lorsqu'ils sont correctes.

Sinon, est-ce que le service akonadiserver est bien lancé sur ta machine ?

Voici la liste des services actifs chez moi :
akonadi_control
akonadiserver
akonadi_googled
akonadi_ical_re
akonadi_ical_re
akonadi_kabc_re
akonadi_kolabpr
akonadi_maildir
akonadi_maildis
akonadi_nepomuk
akonadi_vcard_r

@+

Merci pour cette réponse !

Alors, je pense que ma configuration est correcte, puisque l'outil de configuration d'Akonadi m'indique toutes les ressources sont ok (point vert à côté, onglet "configuration des ressources" et que dans l'onglet configuration du serveur akonadi il me dit que le service akonadi est lancé, et que quand je clique sur "test", j'ai : (en gros, tout va sauf éventuellement le test 14)
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/akoine/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/akoine/.local/share/akonadi/socket-linux-jcbv/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='/home/akoine/.local/share/akonadi/db_data/mysql.err'>/home/akoine/.local/share/akonadi/db_data/mysql.err</a>&apos; does not contain any errors or warnings.

File content of '/home/akoine/.local/share/akonadi/db_data/mysql.err':
110517 14:44:50 InnoDB: Started; log sequence number 0 41130144
110517 14:44:50 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.53' socket: '/home/akoine/.local/share/akonadi/socket-linux-jcbv/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=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=64M
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: 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='/home/akoine/.local/share/akonadi/mysql.conf'>/home/akoine/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/akoine/.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=64M
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.0


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
gcalresource.desktop
googledataresource.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'

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.




Par contre, j'ai pas trouvé comment lister les services akonadi actifs ...

Merci encore pour le coup de main !
@+

dans ton terminal, en sudo ou root tu tapes :

"ps -e | grep akonadi"

Pour le problème de version, est-ce que tu peux vérifier ce point qui semble suspect ?

@+

Bonjour,

Pour ce qui est du problème de version de protocole, ça semble pas être critique. Mais j'ai du mal à le confirmer. En fait, il m'indique que Akonadi est lancé, et dans les test, il indique qu'il a zappé le test, pas que c'est une erreur. Après, j'arrive pas à le confirmer en cherchant sur le net ...

Pour les services qui tournent :
akoine@linux-jcbv:~> ps -e | grep akonadi
9805 ? 00:00:00 akonadi_control
9807 ? 00:00:00 akonadiserver
9830 ? 00:00:00 akonadi_gcal_re
9831 ? 00:00:00 akonadi_googled
9832 ? 00:00:00 akonadi_kabc_re
9833 ? 00:00:00 akonadi_maildir
9834 ? 00:00:00 akonadi_maildis
9835 ? 00:00:00 akonadi_nepomuk
9836 ? 00:00:00 akonadi_vcarddi

Des idées ?? Merci en tout cas !