Page 1 sur 1
[Korganizer] - Impossible d'ajouter une tâche...(résolu)
Publié : jeu. 21 févr. 2013, 09:32
par Origyne
Salut,
Ce n'a pourtant pas l'air compliqué, mais dans Korganizer, lorsque j'ajoute une tâche ou un évènement, j'ai le panneau de cela qui s'affiche et quand j'applique ma tâche rédigée, cela me remet dans le panneau "titre" et surligne ce que j'ai écrit. Si je ne mets pas de titre, cela me dit qu'il faut un titre...
Quelqu'un a une idée ?
EDIT : IL FAUT TOUT D'ABORD CRÉER UN CALENDRIER.
Re: [Korganizer] - Impossible d'ajouter une tâche/évènement.
Publié : jeu. 21 févr. 2013, 11:39
par FoolEcho
Pas clair...
Tu peux nous faire des captures d'écran pour bien visualiser ce qu'il se passe ?
Re: [Korganizer] - Impossible d'ajouter une tâche/évènement.
Publié : jeu. 21 févr. 2013, 12:43
par Origyne
> Je fais ce qui est montré dans l'image.
> Au moment où je clique sur "Appliquer" ou "Ok", cela surligne mon titre, comme si je devais le retaper, de la sorte :
Et aucun moyen de faire accepter...Si je ne mets pas de titre, korganizer me demande d'en mettre un...:/

Re: [Korganizer] - Impossible d'ajouter une tâche/évènement.
Publié : jeu. 21 févr. 2013, 12:56
par FoolEcho
Tu as besoin de créer au moins un calendrier (dans les ressources akonadi/fichier iCal ou dans le cadre en bas à gauche de korganizer) et de le spécifier.

Re: [Korganizer] - Impossible d'ajouter une tâche/évènement.
Publié : jeu. 21 févr. 2013, 13:17
par Origyne
J'obtiens une erreur en installant un calendrier traditionnel (j'ai installé akonadi), mais je devrai peut-être redémarrer...j'ai une page vierge qui me demande de cliquer sur "Suivant" et qui me lance une fenêtre de rapport de bug me disant que Agenda KDE (traditionnel) s'est subitement arrêté. Je te tiens au courant. Merci pour le moment. :)
EDIT : Pareil si je m'essaye à la configuration d'akonadi.
Re: [Korganizer] - Impossible d'ajouter une tâche/évènement.
Publié : jeu. 21 févr. 2013, 14:05
par FoolEcho
Si ça le fait encore après reconnexion (pas besoin de redémarrer), faudrait tester le serveur akonadi et éventuellement nous poster son résultat (accessible dans sa partie configuration).
(à tout hasard, mais vraiment à tout hasard, tu n'as pas fait de "su sans tiret" depuis ton compte utilisateur dès fois ? -- à vérifier avec find /home/ton_utilisateur ! -user ton_utilisateur
, si ça te sort des choses il faudra rectifier en consultant les sujets chown/user/root)
Re: [Korganizer] - Impossible d'ajouter une tâche/évènement.
Publié : jeu. 21 févr. 2013, 17:46
par Origyne
Rien de spécial à propos de mon utilisateur...Je poste le rapport d'erreur.

Il y a plusieurs erreurs...Test 5 notamment...J'imagine que le serveur mysql n'est pas installé. J'pensais pas que ça utilisait une base mysql korganizer...:/
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/edw/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/home/edw/.local/share/akonadi/socket-tolva/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.30-log for Linux on x86_64 (Source distribution)
Test 5: ERROR
--------
MySQL server log contains errors.
Details: The MySQL server error log file '<a href='/home/edw/.local/share/akonadi/db_data/mysql.err'>/home/edw/.local/share/akonadi/db_data/mysql.err</a>' contains errors.
File content of '/home/edw/.local/share/akonadi/db_data/mysql.err':
130221 19:00:18 InnoDB: The InnoDB memory heap is disabled
130221 19:00:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130221 19:00:18 InnoDB: Compressed tables use zlib 1.2.7
130221 19:00:18 InnoDB: Initializing buffer pool, size = 80.0M
130221 19:00:18 InnoDB: Completed initialization of buffer pool
130221 19:00:18 InnoDB: highest supported file format is Barracuda.
130221 19:00:18 InnoDB: Waiting for the background threads to start
130221 19:00:19 InnoDB: 5.5.30 started; log sequence number 2231344
130221 19:00:19 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
130221 19:00:19 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
130221 19:00:19 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
130221 19:00:19 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
130221 19:00:19 [Note] /usr/bin/mysqld: ready for connections.
Version: '5.5.30' socket: '/home/edw/.local/share/akonadi/socket-tolva/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]
# 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
# DEBUGGING:
# 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
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
#expire_logs_days=3
#sync_bin_log=0
# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci
# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
innodb_additional_mem_pool_size=1M
# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M
# Create a .ibd file for each table (default:0)
innodb_file_per_table=1
# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2
# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M
# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M
# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err
# print warnings and connection errors (default:1)
log_warnings=2
# Convert table named to lowercase
lower_case_table_names=1
# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M
# Maximum simultaneous connections allowed (default:100)
max_connections=256
# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)
# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0
# Do not cache results (default:1)
query_cache_type=0
# Do not use the privileges mechanisms
skip_grant_tables
# Do not listen for TCP/IP connections at all
skip_networking
# The number of open tables for all threads. (default:64)
table_cache=200
# How many threads the server should cache for reuse (default:0)
thread_cache_size=3
# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000
[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/edw/.local/share/akonadi/mysql.conf'>/home/edw/.local/share/akonadi/mysql.conf</a> and is readable.
File content of '/home/edw/.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]
# 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
# DEBUGGING:
# 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
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
#expire_logs_days=3
#sync_bin_log=0
# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci
# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
innodb_additional_mem_pool_size=1M
# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M
# Create a .ibd file for each table (default:0)
innodb_file_per_table=1
# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2
# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M
# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M
# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err
# print warnings and connection errors (default:1)
log_warnings=2
# Convert table named to lowercase
lower_case_table_names=1
# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M
# Maximum simultaneous connections allowed (default:100)
max_connections=256
# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)
# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0
# Do not cache results (default:1)
query_cache_type=0
# Do not use the privileges mechanisms
skip_grant_tables
# Do not listen for TCP/IP connections at all
skip_networking
# The number of open tables for all threads. (default:64)
table_cache=200
# How many threads the server should cache for reuse (default:0)
thread_cache_size=3
# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000
[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.9.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':
akonadinepomukfeederagent.desktop
akonotesresource.desktop
archivemailagent.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
knutresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
microblog.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop
Environment variable XDG_DATA_DIRS is set to '/usr/local/share/:/usr/share/'
Test 16: ERROR
--------
Current Akonadi server error log found.
Details: The Akonadi server reported errors during its current startup. The log can be found in <a href='/home/edw/.local/share/akonadi/akonadiserver.error'>/home/edw/.local/share/akonadi/akonadiserver.error</a>.
File content of '/home/edw/.local/share/akonadi/akonadiserver.error':
Nepomuk Query Server not available
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/edw/.local/share/akonadi/akonadiserver.error.old'>/home/edw/.local/share/akonadi/akonadiserver.error.old</a>.
File content of '/home/edw/.local/share/akonadi/akonadiserver.error.old':
Nepomuk Query Server not available
Control process died, committing suicide!
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.
Re: [Korganizer] - Impossible d'ajouter une tâche/évènement.
Publié : jeu. 21 févr. 2013, 18:39
par FoolEcho
L'erreur sur le test 5 n'est pas significative, je pense (pareil pour 16 et 17, j'ai les mêmes pour info).
Du coup... je ne sais pas trop...

C'est toi qui utilisais un home ou des données provenant d'une Debian ou je confonds ? Si c'est le cas, peut-être un problème de version.
Sinon... tu pourrais stopper le serveur akonadi et le démarrer depuis une console avec akonadictl start et voir ce que ça raconte quand tu essaies de créer ta ressource (ça doit aussi figurer dans le ~/.xsession-errors si tu démarres ta session avec kdm, mais ça risque d'être pénible à démêler).
(ou voir avec un utilisateur test)
Re: [Korganizer] - Impossible d'ajouter une tâche/évènement.
Publié : jeu. 21 févr. 2013, 18:51
par Origyne
Le /home est neuf, le matériel aussi.

Mais j'utilisais Debian avant.
Code : Tout sélectionner
NepomukServer(488)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
startkde: Running shutdown scripts...
startkde: Done.
Control process died, committing suicide!
KCrash: Attempting to start /usr/bin/kactivitymanagerd from kdeinit
Warning: connect() failed: : Aucun fichier ou dossier de ce type
KCrash: Attempting to start /usr/bin/kactivitymanagerd directly
KCrash: Application 'kactivitymanagerd' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
Warning: connect() failed: : Aucun fichier ou dossier de ce type
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kactivitymanagerd(9720): KUniqueApplication: Cannot find the D-Bus session server: "Failed to connect to socket /tmp/dbus-zsFGooDExX: Connexion refusée"
kactivitymanagerd(9718): KUniqueApplication: Pipe closed unexpectedly.
No protocol specified
drkonqi: cannot connect to X server :0
Application 'akonadiserver' exited normally...
D-Bus session bus went down - quitting
J'ai le même problème avec tous mes utilisateurs...

Re: [Korganizer] - Impossible d'ajouter une tâche/évènement.
Publié : jeu. 21 févr. 2013, 19:45
par FoolEcho
Origyne a écrit :Code : Tout sélectionner
kactivitymanagerd(9720): KUniqueApplication: Cannot find the D-Bus session server: "Failed to connect to socket /tmp/dbus-zsFGooDExX: Connexion refusée"
Même s'il y a crash, ceci m'étonne.

Ta session est lancée par KD
M ou via startx ?
Re: [Korganizer] - Impossible d'ajouter une tâche/évènement.
Publié : jeu. 21 févr. 2013, 20:36
par Origyne
Via KDM.
Re: [Korganizer] - Impossible d'ajouter une tâche/évènement.
Publié : mar. 26 févr. 2013, 15:34
par Origyne
Je suis dans l'incapacité d'ajouter un agenda traditionnel, et cela demeure.
Re: [Korganizer] - Impossible d'ajouter une tâche/évènement.
Publié : mar. 26 févr. 2013, 17:51
par FoolEcho
Je n'ai pas trop d'idée.

Tu as des ressources quand même dans akonadi ou pas du tout ?
As-tu testé avec un autre utilisateur ? ... poster le ~/.xsession-errors aussi, dès fois que...
Re: [Korganizer] - Impossible d'ajouter une tâche/évènement.
Publié : mar. 26 févr. 2013, 21:40
par Origyne
Je dois dire que je ne connais pas vraiment kdepim (korganizer, kontact, akonadi, kmail...)...on m'a juste assuré que c'était très bien, probablement ce qui se faisait de mieux en desktop dans l'organisation.
Je m'attendais un peu à lancer un de ces services et à l'utiliser de suite, très "clic-o-drome", du coup, je n'ai rien configuré et mon erreur est peut-être là...
Je n'ai aucune ressource dans akonadi pour le moment (je n'ai rien enregistré, puisque korganizer ne fonctionne pas)
Mon .xsession-errors concernant ça :
Code : Tout sélectionner
Object::connect: No such slot KDEBrowser::teardown()
Object::connect: (sender name: 'Bookmarks')
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Solid::Backends::UDisks2::Device(0x256ca40), parent's thread is QThread(0x2079320), current thread is ThreadWeaver::Thread(0x241b210)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Solid::Backends::UDisks2::Device(0x2629570), parent's thread is QThread(0x2079320), current thread is ThreadWeaver::Thread(0x241b210)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Solid::Backends::UDisks2::Device(0x256ca40), parent's thread is QThread(0x2079320), current thread is ThreadWeaver::Thread(0x26b4400)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Solid::Backends::UDisks2::Device(0x2629570), parent's thread is QThread(0x2079320), current thread is ThreadWeaver::Thread(0x26b4400)
AkonadiAgentServer(5261)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
Application '/usr/bin/akonadi_maildispatcher_agent' exited normally...
Application '/usr/bin/akonadi_agent_launcher' exited normally...
Application '/usr/bin/akonadi_kcal_resource' exited normally...
Application '/usr/bin/akonadi_mailfilter_agent' exited normally...
Application '/usr/bin/akonadi_archivemail_agent' exited normally...
Application '/usr/bin/akonadi_nepomuk_feeder' exited normally...
kontact(5168)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed"
kontact(5168)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed"
kontact(5168)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed"
kontact(5168)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed"
kontact(5168)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed"
korgac(578)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed"
korgac(578)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed"
krunner(484)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed"
plasma-desktop(437)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed"
plasma-desktop(437)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket: Remote closed"
Application 'akonadiserver' exited normally...
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths: ("/usr/local/bin", "/usr/bin", "/bin", "/usr/local/sbin", "/usr/sbin", "/sbin", "/usr/bin/core_perl", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.pimitemflagrelation OK
akonadi.pimitemtable OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths: ("/usr/local/bin", "/usr/bin", "/bin", "/usr/local/sbin", "/usr/sbin", "/sbin", "/usr/bin/core_perl")
search paths: ("/home/edw/.kde4/lib/kde4/plugins/", "/usr/lib/kde4/plugins/", "/usr/lib/qt/plugins", "/usr/bin", "/usr/lib/kde4/plugins", "/home/edw/.kde4/lib/kde4/", "/usr/lib/kde4/")
This is the current thread id for Activities 140709781157632 QThread(0x1a1a230)
Object::connect: No such slot KDEBrowser::teardown()
Object::connect: (sender name: 'Bookmarks')
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Solid::Backends::UDisks2::Device(0x256ca40), parent's thread is QThread(0x2079320), current thread is ThreadWeaver::Thread(0x231e870)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Solid::Backends::UDisks2::Device(0x2629570), parent's thread is QThread(0x2079320), current thread is ThreadWeaver::Thread(0x231e870)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Solid::Backends::UDisks2::Device(0x256ca40), parent's thread is QThread(0x2079320), current thread is ThreadWeaver::Thread(0x26b4400)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Solid::Backends::UDisks2::Device(0x2629570), parent's thread is QThread(0x2079320), current thread is ThreadWeaver::Thread(0x26b4400)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Solid::Backends::UDisks2::Device(0x256ca40), parent's thread is QThread(0x2079320), current thread is ThreadWeaver::Thread(0x22bfb20)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is Solid::Backends::UDisks2::Device(0x2629570), parent's thread is QThread(0x2079320), current thread is ThreadWeaver::Thread(0x22bfb20)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kontact(5168)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QCoreApplication::postEvent: Unexpected null receiver
kontact(5168)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
kontact(5168)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
KCrash: Application 'akonadi_kcal_resource' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
drkonqi(5403): Unable to find an internal debugger that can work with the KCrash backend
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x4200012
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x4200012
ProcessControl: Application '/usr/bin/akonadi_kcal_resource' returned with exit code 253 (Unknown error)
Object::connect: No such slot KDEBrowser::teardown()
Object::connect: (sender name: 'Bookmarks')
This is the current thread id for Activities 140709781157632 QThread(0x1a1a230)
Je clos ce sujet et j'en refais un avec le "vrai problème".

Re: [Korganizer] - Impossible d'ajouter une tâche...(résolu)
Publié : mer. 27 févr. 2013, 09:56
par FoolEcho
Origyne a écrit :Je clos ce sujet et j'en refais un avec le "vrai problème".

Si tu veux... mais je ne vois pas pourquoi... (de même que le résolu)
À suivre ici:
http://forums.archlinux.fr/post111695.html