[kmail2] [Bug 335558] No results if I use full search to find emails in imap resources
https://bugs.kde.org/show_bug.cgi?id=335558 --- Comment #1 from Andrej R. --- Created attachment 86911 --> https://bugs.kde.org/attachment.cgi?id=86911&action=edit akonadi Debugger - KMail Search -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 335558] New: No results if I use full search to find emails in imap resources
https://bugs.kde.org/show_bug.cgi?id=335558 Bug ID: 335558 Summary: No results if I use full search to find emails in imap resources Classification: Unclassified Product: kmail2 Version: 4.12.4 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: search Assignee: kdepim-bugs@kde.org Reporter: andy_r...@online.de CC: m...@vhanda.in Search is completed after a second with no results. All mails are indexed with akonadi and I can access them in akonadi console. I tried several times to kill and restart the "Akonadi Nepomuk Feeder" but with no change in behavior. I even renamed the complete ~/.kde folder and reindexed one of my imap resources, still no search results. Quick search is working though. I can provide the output of akonadiconsole - Debugger for a search in KMail. Reproducible: Always Steps to Reproduce: 1. Open Full Search in KMail 2. Search for something (irrelevant which attribute or search term) 3. Get no results Expected Results: D -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 300141] Crash when saving an attachment
https://bugs.kde.org/show_bug.cgi?id=300141 --- Comment #4 from m...@christophschuette.com --- Created attachment 86904 --> https://bugs.kde.org/attachment.cgi?id=86904&action=edit New crash information added by DrKonqi kontact (4.13) on KDE Platform 4.13.0 using Qt 4.8.6 - What I was doing when the application crashed: I was trying to save a python .py file attached to an email. The directory selection popup opened, I selected a directory, hit OK and Kontact crashed. -- Backtrace (Reduced): #6 0x7f88bfc965bd in header (create=true, this=this@entry=0x29f0450) at ../../kmime/kmime_content.h:837 #7 KMime::Content::contentTransferEncoding (this=this@entry=0x29f0450, create=create@entry=true) at ../../kmime/kmime_content.cpp:1003 #8 0x7f88bfc9664d in KMime::Content::decodedContent (this=this@entry=0x29f0450) at ../../kmime/kmime_content.cpp:378 #9 0x7f885da9ab55 in MessageViewer::Util::saveContent (parent=parent@entry=0x24432a0, content=content@entry=0x29f0450, url=...) at ../../messageviewer/utils/util.cpp:369 #10 0x7f885da9c1d7 in MessageViewer::Util::saveContents (parent=0x24432a0, contents=...) at ../../messageviewer/utils/util.cpp:296 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 300141] Crash when saving an attachment
https://bugs.kde.org/show_bug.cgi?id=300141 m...@christophschuette.com changed: What|Removed |Added CC||m...@christophschuette.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 335090] Akonadi Dav Resource: Unexpected Error 401 after server downtime.
https://bugs.kde.org/show_bug.cgi?id=335090
Norbert Zawodsky changed:
What|Removed |Added
CC||norb...@zawodsky.at
--- Comment #2 from Norbert Zawodsky ---
Same here. openSuSE 13.1, KDE 4.13.0
I wanted to "copy" an old calender (several years, about 5000 entries) from
outlook into KDE.
I exported from outlook into an *.ics file, then imported ("merge" into an
owncloud calender) that ics file into Kontact.
Some entries (don't know how many) were merged and appeared at the owncloud
server side.
Then suddenly the ownloud-DAV-resource stopped silently with "unexpected error
401"
I used akonadiconsole to find the offending calender entry, deleted it and
restarted the DAV-resource. But it immediately stops at some other entry.
BTW: What does error 401 mean??
--
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 335531] New: KDE Kontact segmentation fault on exit
https://bugs.kde.org/show_bug.cgi?id=335531 Bug ID: 335531 Summary: KDE Kontact segmentation fault on exit Classification: Unclassified Product: kontact Version: 4.13.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: twtrough...@gmail.com Application: kontact (4.13.1) KDE Platform Version: 4.13.1 Qt Version: 4.8.6 Operating System: Linux 3.13.0-27-generic i686 Distribution: Ubuntu 14.04 LTS -- Information about the crash: I have had several problems with a google task akonadi resource. I was unable tyo modify the resource through the akonadi interface in Kontact, and finally deleted it. I then closed Kontact, and got this. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb1489740 (LWP 6709))] Thread 6 (Thread 0xae86db40 (LWP 6716)): #0 0xb77bc424 in __kernel_vsyscall () #1 0xb323dd4b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb61488ec in __pthread_cond_wait (cond=0xb5897cb0, mutex=0xb5897c98) at forward.c:149 #3 0xb501f9ac in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb501f9ff in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb3239f70 in start_thread (arg=0xae86db40) at pthread_create.c:312 #6 0xb613b70e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 Thread 5 (Thread 0xadf4cb40 (LWP 6758)): #0 0xb77bc424 in __kernel_vsyscall () #1 0xb323dd4b in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb61488ec in __pthread_cond_wait (cond=0xadfba7dc, mutex=0xadfba7c4) at forward.c:149 #3 0xb504e9f3 in WTF::ThreadCondition::wait(WTF::Mutex&) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb4d2a574 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb50357c6 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #6 0xb504e369 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #7 0xb3239f70 in start_thread (arg=0xadf4cb40) at pthread_create.c:312 #8 0xb613b70e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 Thread 4 (Thread 0xaaa3cb40 (LWP 6811)): #0 0xb77bc424 in __kernel_vsyscall () #1 0xb6149392 in __GI___clock_gettime (clock_id=1, tp=0xaaa3c028) at ../sysdeps/unix/clock_gettime.c:115 #2 0xb63a98cc in do_gettime (frac=0xaaa3c020, sec=0xaaa3c018) at tools/qelapsedtimer_unix.cpp:127 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:144 #4 0xb64922a2 in updateCurrentTime (this=0xaa1026e4) at kernel/qeventdispatcher_unix.cpp:354 #5 QTimerInfoList::timerWait (this=0xaa1026e4, tm=...) at kernel/qeventdispatcher_unix.cpp:460 #6 0xb649082b in timerSourcePrepareHelper (src=, timeout=0xaaa3c11c) at kernel/qeventdispatcher_glib.cpp:143 #7 0xb64908bd in timerSourcePrepare (source=0xaa1026b0, timeout=0xaaa3c11c) at kernel/qeventdispatcher_glib.cpp:176 #8 0xb31539b3 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0xb31542df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0xb3154528 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #11 0xb649095f in QEventDispatcherGlib::processEvents (this=0xaa100468, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #12 0xb645f823 in QEventLoop::processEvents (this=this@entry=0xaaa3c288, flags=...) at kernel/qeventloop.cpp:149 #13 0xb645fb49 in QEventLoop::exec (this=this@entry=0xaaa3c288, flags=...) at kernel/qeventloop.cpp:204 #14 0xb634c23d in QThread::exec (this=this@entry=0x8cb9728) at thread/qthread.cpp:537 #15 0xb634c38b in QThread::run (this=0x8cb9728) at thread/qthread.cpp:604 #16 0xb634eb6f in QThreadPrivate::start (arg=0x8cb9728) at thread/qthread_unix.cpp:349 #17 0xb3239f70 in start_thread (arg=0xaaa3cb40) at pthread_create.c:312 #18 0xb613b70e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 Thread 3 (Thread 0xa988fb40 (LWP 7055)): #0 0xb3198d2e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb31990f8 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb3153cc6 in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb315437a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb3154528 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb649095f in QEventDispatcherGlib::processEvents (this=0x8fd31b0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0xb645f823 in QEventLoop::processEvents (this=this@entry=0xa988f258, flags=...) at kernel/qeventloop.cpp:149 #7 0xb645fb49 in QEventLoop::exec (this=this@entry=0xa988f258, flags=...) at kernel/qeventloop.cpp:204 #8 0xb634c23d in QThread::exec (this=this@entry=0x8c9cc30) at
[kmail2] [Bug 335525] New: Option for how long store message bodies isn't avaible globally.
https://bugs.kde.org/show_bug.cgi?id=335525 Bug ID: 335525 Summary: Option for how long store message bodies isn't avaible globally. Classification: Unclassified Product: kmail2 Version: 4.13.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: grodnoo...@yandex.ru In folder properties there is an option for how long store message body localy. It would be nice to have this option somewhere in profile or account settings. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 335523] Akonadi::ProtocolHelper::parseItemFetchResult: Failed to open attribute file: "310312_r0" -- OutboxQueue::Private::addIfComplete: Item 103621 does not have the required attribut
https://bugs.kde.org/show_bug.cgi?id=335523 --- Comment #1 from Dennis Schridde --- The behaviour is reproducible. I created the email in the following way: * There is an email in my inbox with said 120 recipients. * Reply-To-All * Replace the text * Press send * Get a similar error message on the console -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 335523] New: Akonadi::ProtocolHelper::parseItemFetchResult: Failed to open attribute file: "310312_r0" -- OutboxQueue::Private::addIfComplete: Item 103621 does not have the required att
https://bugs.kde.org/show_bug.cgi?id=335523 Bug ID: 335523 Summary: Akonadi::ProtocolHelper::parseItemFetchResult: Failed to open attribute file: "310312_r0" -- OutboxQueue::Private::addIfComplete: Item 103621 does not have the required attribute Address. Classification: Unclassified Product: Akonadi Version: 4.13 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Mail Dispatcher Agent Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net CC: vkra...@kde.org I have an email with one To: and 120 Cc: recipients in my outbox, which KMail/Akonadi is refusing to send. There is no error message whatsoever, and judging from the status bar (where mail fetching progress bars are displayed), KMail/Akonadi never actually tries to connect to the server. Starting Akonadi on a console (akonadictl restart), I get the following output, which seems related: akonadi_maildispatcher_agent(8542)/libakonadi Akonadi::ProtocolHelper::parseItemFetchResult: Failed to open attribute file: "310312_r0" akonadi_maildispatcher_agent(8542) OutboxQueue::Private::addIfComplete: Item 103621 does not have the required attribute Address. It would be interesting to know what the "Address" attribute is and where that file went… Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334218] synchronizations of large folders with filesystem contents hogs a Sandybridge core for minutes
https://bugs.kde.org/show_bug.cgi?id=334218 --- Comment #18 from Martin Steigerwald --- Git commit afdc4bc8d85dbadfddd5d89169fede0f5a57317d by Martin Steigerwald. Committed on 03/05/2014 at 14:52. Pushed by steigerwald into branch 'KDE/4.13'. Do not sort the directory entry list in listNew() and listCurrent(): According to callgrind dumps at https://bugs.kde.org/show_bug.cgi?id=334218#c4 QDir sorts the list of directory entries unless specified otherwise. After disabling the sorting the callgrind is quite different already: https://bugs.kde.org/show_bug.cgi?id=334218#c7 This already helps shortening the time to synchronize folders visibly, but KMail gets still blocked for half a minute or more. There is another occurence of QDir entry sorting in keycache.cpp which the next commit will address. Thanks to Sergio and David for help and pointing out how to disable the sorting. REVIEW: 117975 DIGEST: Huge performance improvement for POP3 users with large maildir. M +2-0resources/maildir/libmaildir/maildir.cpp http://commits.kde.org/kdepim-runtime/afdc4bc8d85dbadfddd5d89169fede0f5a57317d --- Comment #19 from Martin Steigerwald --- Git commit ea0b761fbe3c43b42f83c5477018e10209f92ea3 by Martin Steigerwald. Committed on 03/05/2014 at 14:53. Pushed by steigerwald into branch 'KDE/4.13'. Also do not sort directory entries in listCurrent and listNew in key cache: QDir sorts the list of directory entries unless specified otherwise. The last commit already disabled the sorting in maildir.cpp. This commit completes the work and makes the remaining sorting calls in the callgrind dumps at https://bugs.kde.org/show_bug.cgi?id=334218#c7 go away completely as demonstrated in the callgrind dumps at: https://bugs.kde.org/show_bug.cgi?id=334218#c12 Subjectively this has a huge impact on the performance of KMail with huge maildir. KMail hardly blocks anymore on folder changes and feels much more responsive now. Akonadi maildir resource went from hogging a Sandy Bridge core for minutes to not appearing using 100% of one core in even one averaged 10 second interval in atop. I hardly see it in atop at all anymore, except when accessing very large folders such as one with Linux Kernel mailing list and more than 245000 unread mails. Thanks to Sergio for pointing out the remaining sorting calls in the second callgrind dump and for help. Now the bottleneck appears to be MaildirResource::listRecursive but I do not know whether further optimization is necessary at this point. Both changes tested with kdepimlibs master as of today and KMail 4.12.4 from Debian unstable packages with an enormous maildir including a folder for Linux Kernel mailing list with more than 245000 unread mails. REVIEW: 117975 DIGEST: Huge performance improvement for POP3 users with large maildirs. M +2-0resources/maildir/libmaildir/keycache.cpp http://commits.kde.org/kdepim-runtime/ea0b761fbe3c43b42f83c5477018e10209f92ea3 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334218] synchronizations of large folders with filesystem contents hogs a Sandybridge core for minutes
https://bugs.kde.org/show_bug.cgi?id=334218 --- Comment #18 from Martin Steigerwald --- Git commit afdc4bc8d85dbadfddd5d89169fede0f5a57317d by Martin Steigerwald. Committed on 03/05/2014 at 14:52. Pushed by steigerwald into branch 'KDE/4.13'. Do not sort the directory entry list in listNew() and listCurrent(): According to callgrind dumps at https://bugs.kde.org/show_bug.cgi?id=334218#c4 QDir sorts the list of directory entries unless specified otherwise. After disabling the sorting the callgrind is quite different already: https://bugs.kde.org/show_bug.cgi?id=334218#c7 This already helps shortening the time to synchronize folders visibly, but KMail gets still blocked for half a minute or more. There is another occurence of QDir entry sorting in keycache.cpp which the next commit will address. Thanks to Sergio and David for help and pointing out how to disable the sorting. REVIEW: 117975 DIGEST: Huge performance improvement for POP3 users with large maildir. M +2-0resources/maildir/libmaildir/maildir.cpp http://commits.kde.org/kdepim-runtime/afdc4bc8d85dbadfddd5d89169fede0f5a57317d --- Comment #19 from Martin Steigerwald --- Git commit ea0b761fbe3c43b42f83c5477018e10209f92ea3 by Martin Steigerwald. Committed on 03/05/2014 at 14:53. Pushed by steigerwald into branch 'KDE/4.13'. Also do not sort directory entries in listCurrent and listNew in key cache: QDir sorts the list of directory entries unless specified otherwise. The last commit already disabled the sorting in maildir.cpp. This commit completes the work and makes the remaining sorting calls in the callgrind dumps at https://bugs.kde.org/show_bug.cgi?id=334218#c7 go away completely as demonstrated in the callgrind dumps at: https://bugs.kde.org/show_bug.cgi?id=334218#c12 Subjectively this has a huge impact on the performance of KMail with huge maildir. KMail hardly blocks anymore on folder changes and feels much more responsive now. Akonadi maildir resource went from hogging a Sandy Bridge core for minutes to not appearing using 100% of one core in even one averaged 10 second interval in atop. I hardly see it in atop at all anymore, except when accessing very large folders such as one with Linux Kernel mailing list and more than 245000 unread mails. Thanks to Sergio for pointing out the remaining sorting calls in the second callgrind dump and for help. Now the bottleneck appears to be MaildirResource::listRecursive but I do not know whether further optimization is necessary at this point. Both changes tested with kdepimlibs master as of today and KMail 4.12.4 from Debian unstable packages with an enormous maildir including a folder for Linux Kernel mailing list with more than 245000 unread mails. REVIEW: 117975 DIGEST: Huge performance improvement for POP3 users with large maildirs. M +2-0resources/maildir/libmaildir/keycache.cpp http://commits.kde.org/kdepim-runtime/ea0b761fbe3c43b42f83c5477018e10209f92ea3 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[knotes] [Bug 334357] knotes migration fails if akonadi is not running
https://bugs.kde.org/show_bug.cgi?id=334357 Myriam Schweingruber changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Myriam Schweingruber --- This is definitely fixed in the 4.13.1 version, you should upgrade. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 258340] Akonadi config crashes if closed while Akonadi is restarting
https://bugs.kde.org/show_bug.cgi?id=258340 Christoph Feck changed: What|Removed |Added CC||emu...@netscape.net --- Comment #12 from Christoph Feck --- *** Bug 335505 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 335511] Akonadi crash with control and server process not registered at D-Bus but only for domain users
https://bugs.kde.org/show_bug.cgi?id=335511 --- Comment #1 from Ivo Smelhaus --- Created attachment 86894 --> https://bugs.kde.org/attachment.cgi?id=86894&action=edit Akonadi bug report -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 335511] New: Akonadi crash with control and server process not registered at D-Bus but only for domain users
https://bugs.kde.org/show_bug.cgi?id=335511
Bug ID: 335511
Summary: Akonadi crash with control and server process not
registered at D-Bus but only for domain users
Classification: Unclassified
Product: Akonadi
Version: 4.13
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: grave
Priority: NOR
Component: server
Assignee: kdepim-bugs@kde.org
Reporter: ivo.smelh...@gmail.com
Akonadi server crash all the time with control and server process not
registered at D-Bus.
It happen every time and no kill, delete directory or any other suggestion
from similar bugs works. It occures only for Kubuntu 14.04 (both fresh install
and upgraded from 13.10) BUT ONLY for domain users. For local users everything
works without errors. But for domain users it happens for winbind and pbis
(likewise) as well. Domain server is in all cases Zentyal with samba 4.
Reproducible: Always
Steps to Reproduce:
1. Fresh install of Kubuntu 14.04
2. set standard winbind for auth. on samba 4 as an AD
3. login as a domain user and start akonadi results with crash
Actual Results:
Crash with
Expected Results:
Akonadi running
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/KSAT/ismelhaus/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-ismelhaus.vtQZxY/mysql.socket"
ServerPath=/usr/sbin/mysqld-akonadi
StartServer=true
User=
Password=
[QPSQL]
StartServer=true
Name=akonadi
Host=
User=
Password=
Port=5432
[SQLITE]
Name=akonadi
[QSQLITE3]
Name=/home/KSAT/ismelhaus/.local/share/akonadi/akonadi.db
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: 140529 11:39:40 [Warning] Using unique option
prefix key_buffer instead of key_buffer_size is deprecated and will be removed
in a future release. Please use the full name instead.
/usr/sbin/mysqld Ver 5.5.37-0ubuntu0.14.04.1 for debian-linux-gnu on x86_64
((Ubuntu))
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/KSAT/ismelhaus/.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 /etc/akonadi/mysql-global.conf.
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
#
[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 in
[knotes] [Bug 265557] Option for clicking tray icon to toggle all notes
https://bugs.kde.org/show_bug.cgi?id=265557 Holger changed: What|Removed |Added CC||private_l...@yahoo.com --- Comment #1 from Holger --- If you've opened several notes in a row, you can close them also by pressing ESC on the keyboard. As the focus transfers to the previously active window, this can rapidly close many notes. In addition now in 4.13 there are options in the rightclick menu of the tray-icon to show all and to hide all notes. I believe this bug can be closed. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 317743] Akonadi Console crash at exit
https://bugs.kde.org/show_bug.cgi?id=317743 Daniel Vrátil changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||dvra...@redhat.com Ever confirmed|0 |1 --- Comment #8 from Daniel Vrátil --- Akonadi::Monitor probably should not emit any more pending notifications when the application is shutting down. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334824] When upgrading akonadi from 1.11.0 to 1.12.1, mail search no longer works
https://bugs.kde.org/show_bug.cgi?id=334824 --- Comment #5 from Daniel Vrátil --- Sorry, to be completely honest, with Baloo coming in, Nepomuk went to second, maybe even third rail and the not really maintained anymore (not in upstream, not much in Akonadi either). In one of next version of Akonadi we are going to kill Nepomuk support for good. If you really want your search back, you can either downgrade (but you need to wipe your DB), but I would much much more recommend upgrading to 4.13 and getting Baloo. You will be amazed by the speed :-) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[knotes] [Bug 334357] knotes migration fails if akonadi is not running
https://bugs.kde.org/show_bug.cgi?id=334357 Holger changed: What|Removed |Added CC||private_l...@yahoo.com --- Comment #3 from Holger --- Laurent promised the migration should be fixed in 4.13.1 http://www.aegiap.eu/kdeblog/2014/03/whats-new-in-kdepim-4-13-knotes/comment-page-1/#comment-12105 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 335118] Contacts and Mail components are trying to use the same template disregarding user settings
https://bugs.kde.org/show_bug.cgi?id=335118 Laurent Montel changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- Ever confirmed|0 |1 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 335118] Contacts and Mail components are trying to use the same template disregarding user settings
https://bugs.kde.org/show_bug.cgi?id=335118 --- Comment #3 from Laurent Montel --- Ok I was able to show bug. I will investigate soon ! -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
