Hi AJ,
You replied in your post #6 regarding this issue that “I have no default folder set up in my kmail/kontact profile”. I only use Thunderbird mail client, and nor familiar with Kontact. In fact I have never used it. So could you tell me exactly step by step what do I need to do to make Knotes operational? This is my last hurdle, and I can’t figure out how to make it to work!
You will need to fix the identity issue:
First delete both ~/.kde/share/config/emaildefaults and ~/.kde/share/config/emailidentities then open up kontact click on settings > configure kmail and edit the default identity name, this should fix your issue with knotes as well.
[hr]
I’ve been looking around for a while and I can’t seem to find the location to delete “~/.kde/share/config/emaildefaults and ~/.kde/share/config/emailidentities”. Where is this located at?
They’re hidden files in your home directory and to see them you need to press Alt+. in Dolphin.
[hr]
I’m in the home directory in Dolphin, and see all the hidden files, but still can’t find ~/.kde/share/config/emaildefaults and ~/.kde/share/config/emailidentities".
I even searched for it, and couldn’t find it.
Kontact should create those files as soon as you launch it for the first time.
You didn’t remove Kontact did you?
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/fred/.config/akonadi/akonadiserverrc’:
[%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
Host=
Options=“UNIX_SOCKET=/tmp/akonadi-fred.qRPRsF/mysql.socket”
ServerPath=/usr/bin/mysqld
StartServer=true
[Debug]
Tracer=null
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.
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.
MySQL server is executable.
Details: MySQL server found: /usr/bin/mysqld Ver 10.0.13-MariaDB-log for Linux on x86_64 (MariaDB Server)
MySQL server log contains errors.
Details: The MySQL server error log file ‘/home/fred/.local/share/akonadi/db_data/mysql.err’ contains errors.
File content of ‘/home/fred/.local/share/akonadi/db_data/mysql.err’:
2014-09-09 07:23:30 7fa71ef91780 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB’s internal memory allocator.
140909 7:23:30 [Note] InnoDB: Using mutexes to ref count buffer pool pages
140909 7:23:30 [Note] InnoDB: The InnoDB memory heap is disabled
140909 7:23:30 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
140909 7:23:30 [Note] InnoDB: Compressed tables use zlib 1.2.8
140909 7:23:30 [Note] InnoDB: Using Linux native AIO
140909 7:23:30 [Note] InnoDB: Using CPU crc32 instructions
140909 7:23:30 [Note] InnoDB: Initializing buffer pool, size = 80.0M
140909 7:23:30 [Note] InnoDB: Completed initialization of buffer pool
140909 7:23:30 [Note] InnoDB: Highest supported file format is Barracuda.
140909 7:23:30 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1763736 in the ib_logfiles!
140909 7:23:30 [Note] InnoDB: Database was not shutdown normally!
140909 7:23:30 [Note] InnoDB: Starting crash recovery.
140909 7:23:30 [Note] InnoDB: Reading tablespace information from the .ibd files…
140909 7:23:30 [Note] InnoDB: Restoring possible half-written data pages
140909 7:23:30 [Note] InnoDB: from the doublewrite buffer…
140909 7:23:30 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Server version: 10.0.13-MariaDB
key_buffer_size=16384
read_buffer_size=131072
max_used_connections=0
max_threads=258
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 566742 K bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong…
stack_bottom = 0x0 thread_stack 0x48000
/usr/bin/mysqld(my_print_stacktrace+0x3d)[0xba084d]
/usr/bin/mysqld(handle_fatal_signal+0x345)[0x70ea65]
/usr/lib/libpthread.so.0(+0xf4b0)[0x7fa71e2ed4b0]
/usr/bin/mysqld[0x9d7629]
/usr/bin/mysqld[0x9d8ee3]
/usr/bin/mysqld[0x938c85]
/usr/bin/mysqld[0x8724a3]
/usr/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x710c14]
/usr/bin/mysqld[0x5c4833]
/usr/bin/mysqld(_Z11plugin_initPiPPci+0x550)[0x5c5c60]
/usr/bin/mysqld[0x52a1c2]
/usr/bin/mysqld(_Z11mysqld_mainiPPc+0x5ad)[0x52e2dd]
/usr/lib/libc.so.6(__libc_start_main+0xf0)[0x7fa71d0b9000]
/usr/bin/mysqld[0x522ae1]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at /usr/share/config/akonadi/mysql-global.conf.
File content of ‘/usr/share/config/akonadi/mysql-global.conf’:
[mysqld]
#expire_logs_days=3
#sync_bin_log=0
character_set_server=utf8
collation_server=utf8_general_ci
default_storage_engine=innodb
innodb_additional_mem_pool_size=1M
innodb_buffer_pool_size=80M
innodb_file_per_table=1
innodb_flush_log_at_trx_commit=2
innodb_log_buffer_size=1M
innodb_log_file_size=64M
log_error=mysql.err
log_warnings=2
lower_case_table_names=1
max_allowed_packet=32M
max_connections=256
query_cache_size=0
query_cache_type=0
skip_grant_tables
skip_networking
table_open_cache=200
thread_cache_size=3
wait_timeout=31536000
key_buffer_size=16K
[client]
default-character-set=utf8
MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.
MySQL server configuration is usable.
Details: The MySQL server configuration was found at /home/fred/.local/share/akonadi/mysql.conf and is readable.
File content of ‘/home/fred/.local/share/akonadi/mysql.conf’:
[mysqld]
#expire_logs_days=3
#sync_bin_log=0
character_set_server=utf8
collation_server=utf8_general_ci
default_storage_engine=innodb
innodb_additional_mem_pool_size=1M
innodb_buffer_pool_size=80M
innodb_file_per_table=1
innodb_flush_log_at_trx_commit=2
innodb_log_buffer_size=1M
innodb_log_file_size=64M
log_error=mysql.err
log_warnings=2
lower_case_table_names=1
max_allowed_packet=32M
max_connections=256
query_cache_size=0
query_cache_type=0
skip_grant_tables
skip_networking
table_open_cache=200
thread_cache_size=3
wait_timeout=31536000
key_buffer_size=16K
[client]
default-character-set=utf8
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
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.
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.
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.
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:/usr/local/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
archivemailagent.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
knutresource.desktop
kolabproxyresource.desktop
kolabresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
migrationagent.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
newmailnotifieragent.desktop
nntpresource.desktop
notesagent.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
sendlateragent.desktop
vcarddirresource.desktop
vcardresource.desktop
Environment variable XDG_DATA_DIRS is set to ‘/usr/share:/usr/share:/usr/local/share’
Current Akonadi server error log found.
Details: The Akonadi server reported errors during its current startup. The log can be found in /home/fred/.local/share/akonadi/akonadiserver.error.
File content of ‘/home/fred/.local/share/akonadi/akonadiserver.error’:
Database process exited unexpectedly during initial connection!
executable: “/usr/bin/mysqld”
arguments: ("–defaults-file=/home/fred/.local/share/akonadi/mysql.conf", “–datadir=/home/fred/.local/share/akonadi/db_data/”, “–socket=/tmp/akonadi-fred.qRPRsF/mysql.socket”)
stdout: “”
stderr: “”
exit code: 1
process error: “Unknown error”
"[
0: akonadiserver(_Z11akBacktracev+0x4a) [0x462c1a]
1: akonadiserver() [0x462e89]
2: /usr/lib/libc.so.6(+0x33df0) [0x7f421235fdf0]
3: /usr/lib/libc.so.6(gsignal+0x37) [0x7f421235fd67]
4: /usr/lib/libc.so.6(abort+0x148) [0x7f4212361118]
5: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x5f) [0x7f4213b5c9ff]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xad) [0x46515d]
7: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f4213bf7560]
8: /usr/lib/libQtCore.so.4(+0x11ac2d) [0x7f4213c06c2d]
9: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7f4213c0f811]
10: akonadiserver(_ZN6QDebugD1Ev+0x49) [0x45cd29]
11: akonadiserver(_ZN7Akonadi6Server13DbConfigMysql19startInternalServerEv+0x1cd2) [0x4d2aa2]
12: akonadiserver(_ZN7Akonadi6Server13AkonadiServer20startDatabaseProcessEv+0xff) [0x465dff]
13: akonadiserver(_ZN7Akonadi6Server13AkonadiServer4initEv+0xba) [0x46866a]
14: akonadiserver() [0x542189]
15: /usr/lib/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f4213c816ae]
16: /usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f4213c6958d]
17: /usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ed) [0x7f4213c6c6dd]
18: /usr/lib/libQtCore.so.4(+0x1aa9e3) [0x7f4213c969e3]
19: /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x22d) [0x7f4211a33efd]
20: /usr/lib/libglib-2.0.so.0(+0x491a8) [0x7f4211a341a8]
21: /usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f4211a3424c]
22: /usr/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7f4213c962a5]
23: /usr/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f4213c6815f]
24: /usr/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f4213c68455]
25: /usr/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x89) [0x7f4213c6d719]
26: akonadiserver(main+0x1f2) [0x45c272]
27: /usr/lib/libc.so.6(__libc_start_main+0xf0) [0x7f421234c000]
28: akonadiserver() [0x45ca9e]
]
"
Previous Akonadi server error log found.
Details: The Akonadi server reported errors during its previous startup. The log can be found in /home/fred/.local/share/akonadi/akonadiserver.error.old.
File content of ‘/home/fred/.local/share/akonadi/akonadiserver.error.old’:
Database process exited unexpectedly during initial connection!
executable: “/usr/bin/mysqld”
arguments: ("–defaults-file=/home/fred/.local/share/akonadi/mysql.conf", “–datadir=/home/fred/.local/share/akonadi/db_data/”, “–socket=/tmp/akonadi-fred.qRPRsF/mysql.socket”)
stdout: “”
stderr: “”
exit code: 1
process error: “Unknown error”
"[
0: akonadiserver(_Z11akBacktracev+0x4a) [0x462c1a]
1: akonadiserver() [0x462e89]
2: /usr/lib/libc.so.6(+0x33df0) [0x7fad66119df0]
3: /usr/lib/libc.so.6(gsignal+0x37) [0x7fad66119d67]
4: /usr/lib/libc.so.6(abort+0x148) [0x7fad6611b118]
5: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x5f) [0x7fad679169ff]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xad) [0x46515d]
7: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7fad679b1560]
8: /usr/lib/libQtCore.so.4(+0x11ac2d) [0x7fad679c0c2d]
9: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7fad679c9811]
10: akonadiserver(_ZN6QDebugD1Ev+0x49) [0x45cd29]
11: akonadiserver(_ZN7Akonadi6Server13DbConfigMysql19startInternalServerEv+0x1cd2) [0x4d2aa2]
12: akonadiserver(_ZN7Akonadi6Server13AkonadiServer20startDatabaseProcessEv+0xff) [0x465dff]
13: akonadiserver(_ZN7Akonadi6Server13AkonadiServer4initEv+0xba) [0x46866a]
14: akonadiserver() [0x542189]
15: /usr/lib/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7fad67a3b6ae]
16: /usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7fad67a2358d]
17: /usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ed) [0x7fad67a266dd]
18: /usr/lib/libQtCore.so.4(+0x1aa9e3) [0x7fad67a509e3]
19: /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x22d) [0x7fad657edefd]
20: /usr/lib/libglib-2.0.so.0(+0x491a8) [0x7fad657ee1a8]
21: /usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fad657ee24c]
22: /usr/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7fad67a502a5]
23: /usr/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7fad67a2215f]
24: /usr/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7fad67a22455]
25: /usr/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x89) [0x7fad67a27719]
26: akonadiserver(main+0x1f2) [0x45c272]
27: /usr/lib/libc.so.6(__libc_start_main+0xf0) [0x7fad66106000]
28: akonadiserver() [0x45ca9e]
]
"
No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.
No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.
Please put that much information into a code box or the bot will kick you for spamming.
After looking at your post again and mine I realized I had given you the wrong location of those files, in Netrunner Rolling (Manjaro) those files are in the ~kde4 directory here:
~/.kde4/share/config/emaildefaults and ~/.kde4/share/config/emailidentities".I apologize, the ~kde directory is where Netrunner Standard (Ubuntu) and other Debian based systems keep those files, under Manjaro that directory is only there for compatibility sake.
[hr]
I have installed the Rolling version on two of my computers, including a laptop.
So do I simply run this command on both computers, and that hopefully that will do the trick?
~/.kde4/share/config/emaildefaults and ~/.kde4/share/config/emailidentities
Please disregard my reply to your post #51. I figured out where to go.
In home directory > hidden files, I deleted emaildefaults, and emailidentities (after backup on a stick), but still KNotes won’t create a note, when I click on the “new note”. That is strange! So what do I do now?
First could you tell me what kdepim packages you have installed on your system:
sudo pacman -Qg kdepim[hr]
I get the following packages when I type “sudo pacman -Qg kdepim”
kdepim kdepim-akonadiconsole
kdepim kdepim-console
kdepim kdepim-kaddressbook
kdepim kdepim-kalarm
kdepim kdepim-kmail
kdepim kdepim-knotes
kdepim kdepim-kontact
kdepim kdepim-korganizer
kdepim kdepim-kresources
Also, please keep in mind that I have deleted “.kde4/share/config/emaildefaults and ~/.kde4/share/config/emailidentities”, per your instruction, but I have a back up should we need it again.
OK, that looks right.
Man this took some research, I don’t know why your Kmail installation doesn’t have these by default but here is what you need to do, open dolphin and show hidden files, navigate to ~.local/share/local-mail if this folder is empty or doesn’t exist create them.
Here is what should be there:
[attachment=401]
Now you Knotes list should not be empty anymore, just select a location for storage of your notes and you should be good.
[hr]
I had to create 3 more folders, so now I have six folders, just likt the image you sent. I opened KNotes, and have chosen the note to be saved in the Downloads folder, the problem is that the OK button is greyed out, so I can’t click on Ok, and that has been the problem all along.
I don’t know then, I’ve been successful on three of my machines. There should be six folders like in the screen shot I posted, only those folders are acceptable. right click on the knotes icon and select configure knotes, the select collections make sure there is a check-mark next drafts and that down at the bottom of that window “Local Notes/drafts” is in that field then click OK. DO NOT select inbox unless you want all your e-mails in Kmail showing up as notes, but since you don’t actually use Kmail this should not be an issue.
[attachment=403]
Personally I would, boot a live ISO of Netrunner 14, open configure knotes then look to see what collections is set to on it.
The funny thing is that I’m trying to make KNotes work on two different computers with Rolling installed, and both have the same issue. I also have Frontier installed on 3 other computers that I can check the configuration with. But anyway, when I click on the collection I get the attached error message, and the 2nd image is the detail. My next step, like your suggested is to check the configure setting on Frontier, and compare, and that is if you can’t think of anything else that might have caused this on two different computers. I also know that I have mentioned this to you, but I only use Thunderbird mail, and contacts within Thunderbird.
Well then there’s your problem, you need to start Akonadi, KDEPIM applications use Akonadi for their database, this is a side effect of not using KDEPIM applications like Kmail or Konversation, etc. This is also why some people have issues with baloo not indexing properly is as well.
The easiest way to do have Akonadi running is to have any KDEPIM application or widget (like knotes) startup at login, optionally you can also tell the digital clock widget in the panels calendar settings to display events.
To start Akonadi yourself manually type this into Konsole or Yaquake:
akonadictl start
Well, I added KNotes to the startup, and got the same error. Added the calendar settings to display events from Widgets, and also got the same error. I guess I’m coming close to throw the twoel. If that doesn’t work I’ll use something eles like Xpad.
By the way, I typed “akonadictl start” in the Konsole, and got the following error.
ProcessControl: Application ‘akonadiserver’ returned with exit code 255 (Unknown error)
“akonadiserver” crashed too often and will not be restarted!
Try changing the akonadi backend in the akonadi settings from mysql to sqlite (if you have that backend installed, otherwise install it first)