[kontact] [Bug 383107] Crash when writing new mail

2017-09-15 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=383107

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 CC||mon...@kde.org
 Status|UNCONFIRMED |RESOLVED

--- Comment #7 from Laurent Montel  ---
"terminate called after throwing an instance of 'Xapian::DatabaseCorruptError'"
You need to remove you database
we can"t fix it for you:)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 382252] "On you wrote:" has wrong timezone

2017-09-15 Thread Charles Samuels
https://bugs.kde.org/show_bug.cgi?id=382252

Charles Samuels  changed:

   What|Removed |Added

   Platform|Other   |Debian stable

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 384749] New: Kmail crashed after switching to inbox.

2017-09-15 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=384749

Bug ID: 384749
   Summary: Kmail crashed after switching to inbox.
   Product: kmail2
   Version: 5.5.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: vbabu...@gmail.com
  Target Milestone: ---

Application: kmail (5.5.2)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.85-22-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
I have started Kmail and pre-selected directory was Outbox. When I tried to
click on Inbox the Kmail displayed e-mails in Inbox but crashed immediately.
The same happened when switching to Inbox from other locations like Trash,
Sent-mail, Kmail-Import etc.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f93d827c940 (LWP 15939))]

Thread 23 (Thread 0x7f93337aa700 (LWP 15996)):
#0  0x7f93cb13c0bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f93bda9393b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f93bda93969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f93cb137744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f93d53c5aad in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f935d7fa700 (LWP 15969)):
#0  0x7f93cb13c0bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f93c20f8d10 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f93c20e67bb in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f93c20e6a35 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f93c20e3327 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f93c39be1ca in  () at /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f93c39be4e1 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f93c39be5d2 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f93c2286c12 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#9  0x7f93c22726b5 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#10 0x7f93c229e4f0 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#11 0x7f93c229aece in  () at /usr/lib64/libQt5WebEngineCore.so.5
#12 0x7f93cb137744 in start_thread () at /lib64/libpthread.so.0
#13 0x7f93d53c5aad in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f935dffb700 (LWP 15968)):
#0  0x7f93cb13c0bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f93c229d189 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f93c229d94d in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f93c229e170 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f93c229aece in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f93cb137744 in start_thread () at /lib64/libpthread.so.0
#6  0x7f93d53c5aad in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f935e7fc700 (LWP 15967)):
#0  0x7f93d53b928d in read () at /lib64/libc.so.6
#1  0x7f93b5602931 in pa_read () at
/usr/lib64/pulseaudio/libpulsecommon-9.0.so
#2  0x7f93ba8c43be in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0
#3  0x7f93ba8c4dd2 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7f93ba8c4e90 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7f93ba8d3006 in  () at /usr/lib64/libpulse.so.0
#6  0x7f93b5631408 in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#7  0x7f93cb137744 in start_thread () at /lib64/libpthread.so.0
#8  0x7f93d53c5aad in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f935effd700 (LWP 15966)):
#0  0x7f93cb13c0bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f93c2293cbf in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f93c2293d94 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f93c227662b in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f93c2286c12 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f93c22726b5 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f93c229e4f0 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f93c229aece in  () at /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f93cb137744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f93d53c5aad in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7f935f7fe700 (LWP 15965)):
#0  0x7f93cb13c0bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f93c1c99979 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f93c229e170 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f93c229aece in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f93cb137744 in start_thread () at /lib64/libpthread.so.0
#5  0x7f93d53c5aad in clone () at /lib64/libc.so.6

Thread 17 (Thread 

[kontact] [Bug 383107] Crash when writing new mail

2017-09-15 Thread Axel Braun
https://bugs.kde.org/show_bug.cgi?id=383107

--- Comment #6 from Axel Braun  ---
Still an issue on 5.6.1: First two characters work fine, but 3rd character - no
match - crashes Kmail

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

2017-09-15 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=338658

harbin...@gmail.com changed:

   What|Removed |Added

 CC|harbin...@gmail.com |

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

2017-09-15 Thread Francis Herne
https://bugs.kde.org/show_bug.cgi?id=338658

Francis Herne  changed:

   What|Removed |Added

Version|5.5.1   |5.6.1
 CC||m...@flherne.uk

--- Comment #79 from Francis Herne  ---
Still reproducible on Arch with KMail 5.6.1 and Akonadi 17.08.

Akonadi hangs after each "Check Mail" and must be restarted to receive any more
mail. The steps described here
https://www.dvratil.cz/2017/01/kmail-multiple-merge-candidates-error-and-how-to-fix-it/
don't permanently fix the problem, it recurs soon after.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.

[kmail2] [Bug 384112] Kmail crashes when logging out of plasma

2017-09-15 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=384112

tro...@free.fr changed:

   What|Removed |Added

 CC||tro...@free.fr

--- Comment #1 from tro...@free.fr ---
I can confirm this bug. Kmail always crashes when logging out of Plasma.
Up-to-date packages on Arch Linux.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 352701] Kontact forgets how to download messages

2017-09-15 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=352701

--- Comment #10 from Nick  ---
And if you have rebuild your database but find new mail isn't showing up in the
inbox then this is the fix.

You will need to correct the destination folders in any filters you created in
kmail as they are now probably pointing to the wrong folders. In kmail
[Settings]>[Configure Filters] and if the filter uses a 'move into folder'
action, check it's moving to the correct folder.

This also applies to any account destination folders, ie my gmail pop3 account
was saving into a zoneminder folder I'd created. In kmail,
[Settings]>[Configure Kmail]>[Accounts]>[Receiving Tab] click on your account,
check destination folder.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 352701] Kontact forgets how to download messages

2017-09-15 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=352701

--- Comment #9 from Nick  ---
BTW I'm running KDE Neon LTS 5.8
KDE Plasma Version 5.8.7
KDE Frameworks Version 5.38.0
QT Version 5.7.1
Kernel Version 4.10.0-33-generic
OS Type 64-bit

Processors 8x Intel Core I7 @ 2.2GHz
Memory 16GB

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 352701] Kontact forgets how to download messages

2017-09-15 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=352701

--- Comment #8 from Nick  ---
Interesting

Quote
You should execute mysql_upgrade each time you upgrade MySQL.

https://dev.mysql.com/doc/refman/5.7/en/mysql-upgrade.html

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 352701] Kontact forgets how to download messages

2017-09-15 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=352701

--- Comment #7 from Nick  ---
Doing a more /var/log/apt/history.log | grep mysql I can see that
akonadi-backend-mysql was updated just before I started getting this problem.
I'm almost certain that's what messed up the mysql database and was the answer
to run mysql_upgrade as described here ?
https://dev.mysql.com/doc/refman/5.5/en/performance-schema-build-configuration.html

At least I'm feeling a little more confident about the akonadi-backend-mysql
update having triggered this problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 384739] New: Kmail crashes when trying to preview an e-mail

2017-09-15 Thread Frank Danapfel
https://bugs.kde.org/show_bug.cgi?id=384739

Bug ID: 384739
   Summary: Kmail crashes when trying to preview an e-mail
   Product: kmail2
   Version: 5.5.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: frank.danap...@googlemail.com
  Target Milestone: ---

Application: kmail (5.5.1)

Qt Version: 5.7.1
Frameworks Version: 5.36.0
Operating System: Linux 4.12.11-300.fc26.x86_64 x86_64
Distribution: "Fedora release 26 (Twenty Six)"

-- Information about the crash:
- Selecting a e-mail to be able to see it in the preview pane

This has started after upgrading from Fedora 25 to 26. The system is using an
Nvidia graphics card wit the Nouveau driver provided by F26 (the reason I
mention this is that on F25 there was an issue with Kmail related to some
locking routines of the mesa packages related to nouveau).

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7face7d83940 (LWP 1568))]

Thread 27 (Thread 0x7fac4c881700 (LWP 1644)):
#0  0x7fad0615090b in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7facfd8fa725 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() from /lib64/libQt5WebEngineCore.so.5
#2  0x7facfd8fac07 in base::SequencedWorkerPool::Worker::Run() () from
/lib64/libQt5WebEngineCore.so.5
#3  0x7facfd8fb9a1 in base::SimpleThread::ThreadMain() () from
/lib64/libQt5WebEngineCore.so.5
#4  0x7facfd8f806b in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#5  0x7fad0614a36d in start_thread () from /lib64/libpthread.so.0
#6  0x7fad0a1f9bbf in clone () from /lib64/libc.so.6

Thread 26 (Thread 0x7fac4d8b2700 (LWP 1643)):
#0  0x7fad0615090b in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7faced387534 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQt5Script.so.5
#2  0x7faced387579 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQt5Script.so.5
#3  0x7fad0614a36d in start_thread () from /lib64/libpthread.so.0
#4  0x7fad0a1f9bbf in clone () from /lib64/libc.so.6

Thread 25 (Thread 0x7fac4eb2d700 (LWP 1629)):
#0  0x7ffcdddbab52 in clock_gettime ()
#1  0x7fad0a208ca6 in clock_gettime () from /lib64/libc.so.6
#2  0x7fad0aea8a91 in qt_gettime() () from /lib64/libQt5Core.so.5
#3  0x7fad0b003539 in QTimerInfoList::updateCurrentTime() () from
/lib64/libQt5Core.so.5
#4  0x7fad0b003935 in QTimerInfoList::timerWait(timespec&) () from
/lib64/libQt5Core.so.5
#5  0x7fad0b004b0c in timerSourcePrepareHelper(GTimerSource*, int*) () from
/lib64/libQt5Core.so.5
#6  0x7fad0b004bae in timerSourcePrepare(_GSource*, int*) () from
/lib64/libQt5Core.so.5
#7  0x7facf61a3ac9 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#8  0x7facf61a449b in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#9  0x7facf61a467c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#10 0x7fad0b004e6b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#11 0x7fad0afb560a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#12 0x7fad0ae0d99a in QThread::exec() () from /lib64/libQt5Core.so.5
#13 0x7fad0ae11c9e in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#14 0x7fad0614a36d in start_thread () from /lib64/libpthread.so.0
#15 0x7fad0a1f9bbf in clone () from /lib64/libc.so.6

Thread 24 (Thread 0x7fac857fa700 (LWP 1604)):
#0  0x7face95c45b3 in do_write () from
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#1  0x7face95c5578 in do_pstream_read_write () from
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#2  0x7face95c5899 in srb_callback () from
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#3  0x7face95c611f in srbchannel_rwloop () from
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#4  0x7faceb4b07f8 in pa_mainloop_dispatch () from /lib64/libpulse.so.0
#5  0x7faceb4b0bce in pa_mainloop_iterate () from /lib64/libpulse.so.0
#6  0x7faceb4b0c50 in pa_mainloop_run () from /lib64/libpulse.so.0
#7  0x7faceb4beab9 in thread () from /lib64/libpulse.so.0
#8  0x7face95d6078 in internal_thread_func () from
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#9  0x7fad0614a36d in start_thread () from /lib64/libpthread.so.0
#10 0x7fad0a1f9bbf in clone () from /lib64/libc.so.6

Thread 23 (Thread 0x7fac85ffb700 (LWP 1603)):
#0  0x7fad0a2084bc in __lll_lock_wait_private () from /lib64/libc.so.6
#1  0x7fad0a20a284 in __fprintf_chk () from /lib64/libc.so.6
#2  0x7facf06f8880 in _warn_helper () from 

[kontact] [Bug 352701] Kontact forgets how to download messages

2017-09-15 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=352701

--- Comment #6 from Nick  ---
Interesting regarding the mysql performance schema issue. I do remember doing a
very large update prior to this problem that maybe includeded a mysql update.
Could the fix have been as simple as running mysql_upgrade as described below ?

If you install MySQL over a previous installation that was configured without
the Performance Schema (or with an older version of the Performance Schema that
may not have all the current tables), run mysql_upgrade after starting the
server to ensure that the performance_schema database exists with all current
tables. Then restart the server. One indication that you need to do this is the
presence of messages such as the following in the error log:

[ERROR] Native table 'performance_schema'.'events_waits_history'
has the wrong structure
[ERROR] Native table 'performance_schema'.'events_waits_history_long'
has the wrong structure
...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 352701] Kontact forgets how to download messages

2017-09-15 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=352701

--- Comment #5 from Nick  ---
Regarding the native table has the wrong structure error. Here's a link that
references this mysql error here
https://dev.mysql.com/doc/refman/5.5/en/performance-schema-build-configuration.html

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 352701] Kontact forgets how to download messages

2017-09-15 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=352701

--- Comment #4 from Nick  ---
This fixed it for me .. (until the next time the akonadi database gets
corrupted)

This involves removing the old akonadi database and letting akonadi construct
and reindex a new one.

First exit kmail
then as normal user
akonadi stop

mv /home/jbloggs/.local/share/akonadi /home/jbloggs/.local/share/akonadi.orig
(This is where akonadi stores it's mysql database)

akonadi start

You may get the following messages, but then nothing while it's reindexing.
akonadictl start
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
nick@nick-X681X:~/.local/share$ /usr/bin/mysqlcheck: Got error: 1049: Unknown
database 'akonadi' when selecting the database
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
"No file selected."
org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult
"Failed to fetch the resource collection."
org.kde.pim.maildispatcher: Failed to get outbox folder. Retrying in:  5000
org.kde.pim.akonadicore: Failed to request resource
"akonadi_maildir_resource_0" : "Failed to fetch the resource collection."
org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult
"Failed to fetch the resource collection."
org.kde.pim.akonadicore: Failed to request resource
"akonadi_maildir_resource_0" : "Failed to fetch the resource collection."
org.kde.akonadi.ETM: GEN true false false
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: 
org.kde.akonadi.ETM: Fetch job took  31 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 0
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Fetch job took  39 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 2
org.kde.akonadi.ETM: first fetched collection: "Search"
org.kde.akonadi.ETM: Fetch job took  2 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 0
org.kde.akonadi.ETM: GEN true false false
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: 
org.kde.akonadi.ETM: Fetch job took  39 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 0
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Fetch job took  42 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 2
org.kde.akonadi.ETM: first fetched collection: "Search"
org.kde.akonadi.ETM: Fetch job took  1 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 0
Pass a valid window to KWallet::Wallet::openWallet().
"Unable to fetch item from backend (collection -1) : Unable to retrieve item
from resource: Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy blocked the
reply, the reply timeout expired, or the network connection was broken."

To completely reindex akonadi may take a considerable time especially if you
have tens of thousands of emails. In my case it's still indexing after an hour.
However I can access my emails during this time.

looking at the process list with 'top' mysqld shows at 70-95% on my system
during this reindexing period.

If it all goes ok then remove the backup you made.
rm /home/jbloggs/.local/share/akonadi.orig

I don't use kontact or any Calendar so can't comment on what will happen to any
data you've entered in those apps however if like me you just use kmail then
this worked fine. In kmail it retained the various folders and filters I'd
created. And it now works without getting the annoying please wait retrieving
folder contents.

Because I made a backup of the original database I noticed that there were a
few mysql errors in the log, reproduced below. In particular the error that
stands out is this one (with lots of variations.. but basically native table
has the wrong structure.

[ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong
structure

more mysql.err
170915  0:46:57 [Note] InnoDB: innodb_empty_free_list_algorithm has been
changed to legacy because of small buffer pool size. In order to use backoff,
increase buffer pool at least up to 20MB.

170915  0:46:57 [Note] InnoDB: Using mutexes to ref count buffer pool pages
170915  0:46:57 [Note] InnoDB: The InnoDB memory heap is disabled
170915  0:46:57 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
170915  0:46:57 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for
memory barrier
170915  0:46:57 [Note] InnoDB: Compressed tables use zlib 1.2.8
170915  0:46:57 [Note] InnoDB: Using Linux native AIO
170915  0:46:57 [Note] InnoDB: Using CPU crc32 instructions
170915  0:46:57 [Note] InnoDB: Initializing buffer pool, size = 128.0M
170915  0:46:57 [Note] InnoDB: Completed initialization of buffer pool
170915  0:46:57 [Note] InnoDB: Highest supported file format is Barracuda.
170915  0:46:57 [Note] InnoDB: 128 rollback segment(s) are active.
170915  0:46:57 [Note] InnoDB: Waiting 

[kontact] [Bug 352701] Kontact forgets how to download messages

2017-09-15 Thread Nick
https://bugs.kde.org/show_bug.cgi?id=352701

Nick  changed:

   What|Removed |Added

 CC||nick.craig@gmail.com

--- Comment #3 from Nick  ---
And me, I get this same error. Retrieving folder contents please wait. This bug
has been around for years. Kmail/akonadi has been working for me ok for a
couple of months but now I just get this inability to read a email. Perhaps
it's related to quantity of emails stored that makes it more likely to trigger
this bug ? Who knows :-/ In the past I think I've deleted the akonadi database
file and configs and started again but it's such a pain to keep doing that.
Looking at the logs this seems to be the problem "Cannot connect to agent
instance with identifier 'akonadi_maildir_resource_0', error message: ''"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kaddressbook] [Bug 384736] New: Version 5.6.1 : contact modification not recorded

2017-09-15 Thread Alex6
https://bugs.kde.org/show_bug.cgi?id=384736

Bug ID: 384736
   Summary: Version 5.6.1 : contact modification not recorded
   Product: kaddressbook
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: alex.pre...@laposte.net
CC: to...@kde.org
  Target Milestone: ---

No modification recorded in "Location" tab (recorded in "Contact" and "Notes")

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 363531] TLS negotiation was unsuccessful

2017-09-15 Thread Terenyi Balazs
https://bugs.kde.org/show_bug.cgi?id=363531

Terenyi Balazs  changed:

   What|Removed |Added

 CC||tere...@freemail.hu

--- Comment #6 from Terenyi Balazs  ---
The same here with IMAP and a Letsencrypt cert on OpenSuSE Leap 42.2 with KMail
Version 5.3.0 KDE Frameworks 5.26.0 Qt 5.6.1.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 325224] CalDav doesn't read server items

2017-09-15 Thread Oliver Rettig
https://bugs.kde.org/show_bug.cgi?id=325224

Oliver Rettig  changed:

   What|Removed |Added

 CC||oliver.ret...@alumni.kit.ed
   ||u

--- Comment #72 from Oliver Rettig  ---
I have the same above described problem in combination with an Synlogy DS116
based webdav based calendar. The communication with the servers works fine for
two android smartphone but not the calendar app of the kde. All items created
by calendar are visible correctly for the other clients but if I create or
change items by the android app the changes are unvisible for the kde calendar
but visible for all android apps.

Does anybody know some more in details how is this bug comes from?

If I interpret the comments correct the problem does not occures in combination
with all webdav servers. Isnt it?

-- 
You are receiving this mail because:
You are the assignee for the bug.