Ubuntu-fr

pierpiotr

[RESOLU]Knotes ne s'affiche plus

Bonjour,
J'ai perdu mes anciennes notes (mais C pas trop grave).
Par contre si j'ai besoin d'une nouvelle, elle n'apparaît pas non plus. J'ai purgé et réinstallé, mais sans succès.
C'est pourtant bien pratique ces petites bêtes là...
Qq'un aurait une idée SVP ?

Dernière modification par pierpiotr (Le 18/04/2016, à 08:09)

---

Kubuntu 24.04 LTS sur DELL Inspiron 7490 - i7 - RAM 16Go - SSD 500Go - nVidia GeForce MX250
Au bureau : Kubuntu 24.04 LTS  (64b) - PC tour LDLC PC Zi-Artist - i7-3770 @ 3.4/3.9Ghz - RAM 16Go - SSD 120Go - DD 1To - nVidia GEForce GT 640 1Go

abecidofugy

Re : [RESOLU]Knotes ne s'affiche plus

Salut,

Et Knotes dans Kontact, ça s'affiche pas non plus ?

Dernière modification par abecidofugy (Le 09/04/2016, à 12:35)

bruno

Re : [RESOLU]Knotes ne s'affiche plus

Il y a des bugs dans les dernières versions de knotes. On peut aller dans configuration 6> Préférence de Knotes > Collections > Comptes et recharger (ou restart) puis valider pour voir les notes mais il faudra le refaire à chaque redémarrage…

Pour info les notes sont normalement stockées dans ~/.local/share/notes

Django84

Re : [RESOLU]Knotes ne s'affiche plus

Effectivement c'est bogué à mort ! Mais encore heureux qu'elles ne soient pas effacées !
Bonjour la prochaine LTS ! c'est mal parti !

Dernière modification par Django84 (Le 14/04/2016, à 21:35)

---

GA-H170-D3HP ; i5 6600 NeonKDE ver:6.0 sur SSD Nvme

bruno

Re : [RESOLU]Knotes ne s'affiche plus

Les bogues de knotes semblent corrigés dans kdepim 15.12 qui devrait être fourni avec la prochaine LTS.

En fait, non… Ce bogue est toujours d'actualité :

https://bugs.kde.org/show_bug.cgi?id=352011

Dernière modification par bruno (Le 15/04/2016, à 09:15)

pierpiotr

Re : [RESOLU]Knotes ne s'affiche plus

Bjr à tous,
Merci Bruno, mais je ne trouve pas Knotes ou ses Préférences dans la config systeme...? Mm avec une recherche sur Knotes. Ça se trouve ou STP?

---

Kubuntu 24.04 LTS sur DELL Inspiron 7490 - i7 - RAM 16Go - SSD 500Go - nVidia GeForce MX250
Au bureau : Kubuntu 24.04 LTS  (64b) - PC tour LDLC PC Zi-Artist - i7-3770 @ 3.4/3.9Ghz - RAM 16Go - SSD 120Go - DD 1To - nVidia GEForce GT 640 1Go

bruno

Re : [RESOLU]Knotes ne s'affiche plus

Quand tu es dans knotes : Configuration > Préférences de knotes

pierpiotr

Re : [RESOLU]Knotes ne s'affiche plus

J'aurais du y penser.
Cependant le bouton restart est grisé, non cliquable.
Sur l'onglet folders j'ai l'indicatiuon de démarrer le service de gestion des info personnelles et j'ai fait démarrer : un message d'erreur s'ensuit :

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/pier/.config/akonadi/akonadiserverrc':
[Debug]
Tracer=null

[%General]
Driver=QMYSQL

[QMYSQL]
Host=
Name=akonadi
Options="UNIX_SOCKET=/tmp/akonadi-pier.QPCNZm/mysql.socket"
ServerPath=/usr/sbin/mysqld-akonadi
StartServer=true


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-akonadi'.
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-akonadi: 3: exec: /usr/sbin/mysqld: not found


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

No current MySQL error log found.
Details: The MySQL server did not report any errors during this startup. The log can be found in '/home/pier/.local/share/akonadi/db_data/mysql.err'.

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]

# 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)
# Deprecated in MySQL >= 5.6.3
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_open_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

# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K

[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/pier/.local/share/akonadi/mysql.conf'>/home/pier/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/pier/.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)
# Deprecated in MySQL >= 5.6.3
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_open_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

# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K

[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.13.0


Test 10:  ERROR
--------

Akonadi control process not registered at D-Bus.
Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 11:  ERROR
--------

Akonadi server process not registered at D-Bus.
Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 12:  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 13:  ERROR
--------

No resource agents found.
Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share:/usr/share/kde-plasma:/usr/local/share/:/usr/share/'; make sure this includes all paths where Akonadi agents are installed.

Directory listing of '/usr/share/akonadi/agents':
akonadibalooindexingagent.desktop
akonadinepomukfeederagent.desktop
akonotesresource.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
facebookresource.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
kolabproxyresource.desktop
kolabresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
migrationagent.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
newmailnotifieragent.desktop
nntpresource.desktop
notesagent.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share/kde-plasma:/usr/local/share/:/usr/share/'

Test 14:  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/pier/.local/share/akonadi/akonadiserver.error'>/home/pier/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/pier/.local/share/akonadi/akonadiserver.error':
Database process exited unexpectedly during initial connection! 
executable: "/usr/sbin/mysqld-akonadi" 
arguments: ("--defaults-file=/home/pier/.local/share/akonadi/mysql.conf", "--datadir=/home/pier/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-pier.QPCNZm/mysql.socket") 
stdout: "" 
stderr: "/usr/sbin/mysqld-akonadi: 3: exec: /usr/sbin/mysqld: not found
" 
exit code: 127 
process error: "Unknown error" 
"[
0: akonadiserver() [0x418937]
1: akonadiserver() [0x418b92]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x36d40) [0x7f6c56c81d40]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39) [0x7f6c56c81cc9]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f6c56c850d8]
5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x102) [0x7f6c58483c92]
6: akonadiserver() [0x41aa3d]
7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f6c5851e470]
8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x11ab3d) [0x7f6c5852db3d]
9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7f6c58536721]
10: akonadiserver() [0x47fa69]
11: akonadiserver() [0x41b687]
12: akonadiserver() [0x41dd15]
13: akonadiserver() [0x4e23d4]
14: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f6c585a8c1e]
15: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f6c585904dd]
16: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ed) [0x7f6c58593b3d]
17: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1aaf83) [0x7f6c585bdf83]
18: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x254) [0x7f6c56350e04]
19: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49048) [0x7f6c56351048]
20: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f6c563510ec]
21: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x71) [0x7f6c585bd7a1]
22: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f6c5858f0af]
23: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f6c5858f3a5]
24: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x89) [0x7f6c58594b79]
25: akonadiserver() [0x412ec5]
26: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f6c56c6cec5]
27: akonadiserver() [0x41388e]
]
" 


Test 15:  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/pier/.local/share/akonadi/akonadiserver.error.old'>/home/pier/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/pier/.local/share/akonadi/akonadiserver.error.old':
Database process exited unexpectedly during initial connection! 
executable: "/usr/sbin/mysqld-akonadi" 
arguments: ("--defaults-file=/home/pier/.local/share/akonadi/mysql.conf", "--datadir=/home/pier/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-pier.QPCNZm/mysql.socket") 
stdout: "" 
stderr: "/usr/sbin/mysqld-akonadi: 3: exec: /usr/sbin/mysqld: not found
" 
exit code: 127 
process error: "Unknown error" 
"[
0: akonadiserver() [0x418937]
1: akonadiserver() [0x418b92]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x36d40) [0x7f40c9460d40]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39) [0x7f40c9460cc9]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f40c94640d8]
5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x102) [0x7f40cac62c92]
6: akonadiserver() [0x41aa3d]
7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f40cacfd470]
8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x11ab3d) [0x7f40cad0cb3d]
9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7f40cad15721]
10: akonadiserver() [0x47fa69]
11: akonadiserver() [0x41b687]
12: akonadiserver() [0x41dd15]
13: akonadiserver() [0x4e23d4]
14: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f40cad87c1e]
15: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f40cad6f4dd]
16: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ed) [0x7f40cad72b3d]
17: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1aaf83) [0x7f40cad9cf83]
18: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x254) [0x7f40c8b2fe04]
19: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49048) [0x7f40c8b30048]
20: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f40c8b300ec]
21: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x71) [0x7f40cad9c7a1]
22: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f40cad6e0af]
23: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f40cad6e3a5]
24: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x89) [0x7f40cad73b79]
25: akonadiserver() [0x412ec5]
26: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f40c944bec5]
27: akonadiserver() [0x41388e]
]
" 


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

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

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

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

Que faire à partir de là ?

---

Kubuntu 24.04 LTS sur DELL Inspiron 7490 - i7 - RAM 16Go - SSD 500Go - nVidia GeForce MX250
Au bureau : Kubuntu 24.04 LTS  (64b) - PC tour LDLC PC Zi-Artist - i7-3770 @ 3.4/3.9Ghz - RAM 16Go - SSD 120Go - DD 1To - nVidia GEForce GT 640 1Go

bruno

Re : [RESOLU]Knotes ne s'affiche plus

Peux-tu donner le résultat de :

ls -l /usr/sbin/mysqld

Il semble qu'akonadi ne trouve pas le serveur MySQL :

stderr: "/usr/sbin/mysqld-akonadi: 3: exec: /usr/sbin/mysqld: not found

Le cas échéant il faudra (ré)-installer le paquet akonadi-server

Dernière modification par bruno (Le 15/04/2016, à 11:20)

pierpiotr

Re : [RESOLU]Knotes ne s'affiche plus

voici :

~$ ls -l /usr/sbin/mysqld
ls: impossible d'accéder à /usr/sbin/mysqld: Aucun fichier ou dossier de ce type

---

Kubuntu 24.04 LTS sur DELL Inspiron 7490 - i7 - RAM 16Go - SSD 500Go - nVidia GeForce MX250
Au bureau : Kubuntu 24.04 LTS  (64b) - PC tour LDLC PC Zi-Artist - i7-3770 @ 3.4/3.9Ghz - RAM 16Go - SSD 120Go - DD 1To - nVidia GEForce GT 640 1Go

bruno

Re : [RESOLU]Knotes ne s'affiche plus

C'est curieux… Normalement le serveur MySQL est installé automatiquement comme dépendance…

Je te suggère de tenter une (ré) installation des paquets indispensables (en ligne de commande ou via ton gestionnaire de paquets) :

sudo apt-get install akonadi-server akonadi-backend-mysql mysql-server

pierpiotr

Re : [RESOLU]Knotes ne s'affiche plus

C'est fait. Maintenant on a :

~$ ls -l /usr/sbin/mysqld
-rwxr-xr-x 1 root root 11771008 janv. 25 20:32 /usr/sbin/mysqld

J'ai quitté et redémarré Knotes et mes notes sont réapparues. J'ai pu en créer une nouvelle.
Merci beaucoup. Je crois que c'est résolu. Je vais partir qq heures pendant lesquelles je vais éteindre mon PC. Au retour je verrai si les notes sont toujours là.
Si c'est bien le cas je confirmerai et j'indiquerai [résolu] dans le titre du fil.
À tt à l'H.
[Edit] En effet, tout fonctionne A-OK.
Merci encore et bonne semaine.

Dernière modification par pierpiotr (Le 18/04/2016, à 08:10)

---

Kubuntu 24.04 LTS sur DELL Inspiron 7490 - i7 - RAM 16Go - SSD 500Go - nVidia GeForce MX250
Au bureau : Kubuntu 24.04 LTS  (64b) - PC tour LDLC PC Zi-Artist - i7-3770 @ 3.4/3.9Ghz - RAM 16Go - SSD 120Go - DD 1To - nVidia GEForce GT 640 1Go