[kmail]Problème au lancement[Résolu]

[Mimi]

Bonjour, je suis débutante, je suis sous chakra. Depuis quelques temps, Kmail ne se lance plus il y a marqué:
Échec de la récupération de la collection de la ressource. Je ne sais pas comment c'est arrivé, merci de votre aide.

[davidvs]

je vois pas le rapport !
Lance kmail en console et poste les erreurs

[Mimi]

Merci beacoup

[davidvs]

ok !

ce que je voulais dire :
1/ tu ouvres un terminal (konsole si KDE)
2/ tu tapes

Code : Tout sélectionner

kmail

3/ tu nous copies | colles les messages inscrits dans le terminal.

OK ?

[Mimi]

Merci et sinon avec cette commande j'obtiens ce message:
L'erreur est :
Échec de la récupération de la collection de la ressource."
kmail2(9852)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::resourceScanResult: Failed to request resource "akonadi_maildir_resource_0" : "Erreur inconnue. (Échec de la récupération de la collection de la ressource.)"


P.S:akonadi se lance normalement

[davidvs]

Essaie de te débarasser d'Akonadi

Pour info :
http://fr.wikipedia.org/wiki/Akonadi

[FoolEcho]

Salut,

Attention, attention, Chakra fait son bonhomme de chemin de son côté et n'est plus lié à Arch ! ... donc déjà il faut savoir de quelle version de kmail on parle ! (pareil, je ne suis pas convaincu de l'impact de cairo-dock là-dedans...)

Je dis ça à plus forte raison car je vois:

kmail2(9852)/libakonadi Akonadi::SpecialCollectionsRequestJobPrivate::resourceScanResult: Failed to request resource "akonadi_maildir_resource_0" : "Erreur inconnue. (Échec de la récupération de la collection de la ressource.)"

kmail2 !
Sur Arch, on attend encore les mises à niveau de kdepim (y a du testing en cours, je crois...) ... c'est-à-dire que notre kmail est 1.13.7 !

Maintenant, c'est peut-être un problème au niveau d'akonadi... il faut vérifier sa configuration et son bon fonctionnement (et au besoin nous fournir le résultat des tests):

Code : Tout sélectionner

kcmshell4 kcm_akonadi #ou akonaditray si tu as une boîte de miniatures

[Mimi]

O.K Je vais essayer de voir si il y a un problème au niveau d'Akonadi.Merci beaucoup pour votre aide.

[Ypnose]

Bonjour, je suis débutante, je suis sous chakra.

Très bon choix. Ma meilleure expérience de KDE.

[Mimi]

Voici le rapport:

Code : Tout sélectionner

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/elena/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/elena/.local/share/akonadi/socket-chakra-pc/mysql.socket"
ServerPath=/usr/bin/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/bin/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/bin/mysqld  Ver 5.5.11-log for Linux on x86_64 (Source distribution)


Test 5:  ERROR
--------

MySQL server log contains errors.
Details: The MySQL server error log file &apos;<a href='/home/elena/.local/share/akonadi/db_data/mysql.err'>/home/elena/.local/share/akonadi/db_data/mysql.err</a>&apos; contains errors.

File content of '/home/elena/.local/share/akonadi/db_data/mysql.err':
110627 20:13:18 InnoDB: The InnoDB memory heap is disabled
110627 20:13:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110627 20:13:18 InnoDB: Compressed tables use zlib 1.2.5
110627 20:13:18 InnoDB: Initializing buffer pool, size = 80.0M
110627 20:13:18 InnoDB: Completed initialization of buffer pool
110627 20:13:18 InnoDB: highest supported file format is Barracuda.
110627 20:13:18  InnoDB: Waiting for the background threads to start
110627 20:13:19 InnoDB: 1.1.6 started; log sequence number 1729855
110627 20:13:19 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
110627 20:13:19 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
110627 20:13:19 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
110627 20:13:19 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
110627 20:13:19 [Note] /usr/bin/mysqld: ready for connections.
Version: '5.5.11'  socket: '/home/elena/.local/share/akonadi/socket-chakra-pc/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='/usr/share/config/akonadi/mysql-global.conf'>/usr/share/config/akonadi/mysql-global.conf</a>.

File content of '/usr/share/config/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/elena/.local/share/akonadi/mysql.conf'>/home/elena/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/elena/.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.2


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':
akonotesresource.desktop
birthdaysresource.desktop
calendarsearchagent.desktop
contactsresource.desktop
davgroupwareresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
knutresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
microblog.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomukcalendarfeeder.desktop
nepomukcontactfeeder.desktop
nepomukemailfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share/:/usr/local/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.

P.S: comment se débarasse-t'on d'Akonadi?

[benjarobin]

Code : Tout sélectionner

110627 20:13:19 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
110627 20:13:19 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
110627 20:13:19 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure...

Les messages d'erreur sont assez claire...
La solution la plus simple est de supprimer toutes la base d'akonadi (A faire juste après un démarrage du PC avant de s'être connecté/loggué avec KDM, donc depuis un tty) :

Code : Tout sélectionner

rm -Rf /home/elena/.local/share/akonadi/

Au démarrage suivant il devrai remettre tout en ordre

[Mimi]

Merci beacoup pour le renseignement.Par contre comment supprimer toute la base d'Akonadi?
P.S:Je vais me déconnecter du coup je ne répondrai que demain.

[davidvs]

Bon : reprenons histoire de fournir un tuto clé en mains pour notre Mimi (un rapport avec la chanson et la Marseillaise ??? )

1/ tu reboot ton ordi
2/ normalement tu arrives à ton gestionnaire de connexion (KDM) où tu entres d'habitude ton login et MDP.... et ben... tu ne le fais pas
3/ tu fais un

Code : Tout sélectionner

ALT + CTRL + F1

=> tu te trouves en TTY
4/ tu te log + MDP puis tu tapes :

Code : Tout sélectionner

rm -Rf /home/elena/.local/share/akonadi
exit

5/ tu repasses à ton gestionnaire de connexion :

Code : Tout sélectionner

ALT + F7

[FoolEcho]

Pas besoin de redémarrer, l'étape 5 est à remplacer par (donc pas besoin de 'su'):

Code : Tout sélectionner

exit

Puis ALT+F7 (ou F8 selon...) pour revenir au gestionnaire de connexion graphique et se connecter normalement.

EDIT: (et bien sûr, sur l'étape 4, il faut se connecter avec ton login/mdp pour faire le "rm")

[davidvs]

oups !
et oui ! il faut d'abord se connecter avec son login en TTY : effectivement.

[davidvs]

MODIFS APPORTÉES APRÈS PRÉCISIONS DE Foolecho : cf. ci-dessous

[Mimi]

J'ai appellé quelqu'un de plus expérimenté que moi en informatique et il m'a aidé, mais votre aide m'a quand même été précieuse. Merci beaucoup.
P.S: problème résolu après vos instructions et après avoir lancé: akonadictl start puis kmail.