[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Mark Fraser]

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

Mark Fraser  changed:

   What|Removed |Added

 CC||mfraz74+...@gmail.com

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[bugzilla_noreply]

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

--- Comment #48 from stefanfr...@gmx.net ---
Hi!
>and misses debug symbols, doesn't manjaro package debug stuff ?

sorry Manjaro base on Arch and unfortunately do not support debug-symbols.
I hope somebody else has the same problem and can upload the debug-log-file.
Best regards

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Christophe Giboudeaux]

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

--- Comment #47 from Christophe Giboudeaux  ---
the last backtrace looks unrelated (and misses debug symbols, doesn't manjaro
package debug stuff ?)

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[bugzilla_noreply]

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

--- Comment #46 from stefanfr...@gmx.net ---
Created attachment 105260
  --> https://bugs.kde.org/attachment.cgi?id=105260&action=edit
New crash Apps 17.04

New crash Apps 17.04.
I have pop3 und mailfilter active.
When I want to open an filtered mail in html format kmail/acodadi crashes.
The mail-text window do not show the text.
Please fix that issue, that makes kmail unuseable!
Best regards

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[bugzilla_noreply]

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

--- Comment #45 from stefanfr...@gmx.net ---
still not working Apps 17.04, Manjaro updated at April 27. 

At the moment ne crach report just:
Application: Kontact (kontact), signal: Segmentation fault

I will report when available!

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #44 from Daniel Vrátil  ---
The crash should be fixed in 17.04 release.

http://cgit.kde.org/akonadi.git/commit/?id=da7070a7facb3c2f91c03b28c36ba5b929b89a42

Please test against the new version and reopen if you can still reproduce the
crash.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[bugzilla_noreply]

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

--- Comment #43 from stefanfr...@gmx.net ---
Created attachment 104840
  --> https://bugs.kde.org/attachment.cgi?id=104840&action=edit
Another crash

a second crash this morning.
That could be more useful.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[bugzilla_noreply]

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

--- Comment #42 from stefanfr...@gmx.net ---
Hi!
yes I know. But the only text that is displayed is:


--Application: Kontact (kontact), signal: Segmentation fault--


not very useful I think.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[bugzilla_noreply]

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

--- Comment #41 from stefanfr...@gmx.net ---
Created attachment 104839
  --> https://bugs.kde.org/attachment.cgi?id=104839&action=edit
Crash

crash

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Christoph Feck]

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

--- Comment #40 from Christoph Feck  ---
Please attach it using the "Add an attachment" link on this page; mail
attachments are not displayed here.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[bugzilla_noreply]

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

--- Comment #39 from stefanfr...@gmx.net ---
Maybe my problem is exactly the filtering bug. I am using Pop3 and filters in
Kmail. What is the link to that Bugreport?
To complete your request I attached the crashreport:

Application: Kontact (kontact), signal: Segmentation fault

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Daniel Vrátil]

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

--- Comment #38 from Daniel Vrátil  ---
(In reply to stefanfrank from comment #34)
> Hi,
> unfortunately the new update to Version 5.4.3 do not solve the problem. I
> still have crashes!
> Best regards

Please provide a new backtrace of the crash.


Regarding the filtering issue, there are another bug reports regarding this,
please report your issue there.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Denis Kurz]

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

Denis Kurz  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---
Version|5.4.0   |5.4.3

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Robby Engelmann]

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

--- Comment #37 from Robby Engelmann  ---
Hi,
I also updated to 16.12.3 and it still has some issues with the filter agents
as described in the previous post.
I figured out now, that filtering spams with bogofilter or spamassassin does
work now, not sure whether that is new. However, adding additional filters,
e.g. move all incoming mails which contain a specific string to another
subfolder still leads to the problems described: doubling of mails, not able to
delete mails.

I also use pop. Not sure whether that also applies to imap.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Olivier BELLEUX]

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

--- Comment #36 from Olivier BELLEUX  ---
I confirm that the update does not completely solve the bugs.

I received two mail (html newsletters) that were filtered to the right folder
but then read them caused a crash; Unable to delete them from kmail; I had to
do it by hand since my maildir (my accounts are all in pop3: safer) then:
Akonadi fsck
Akonadi vacuum
Akonadi restart
Kontact

Tired of this akonadi.

Akonadi is an interface between the client and the server ... but when akonadi
bugs it becomes a wall between the applications of the kontact suite and
servers ...

The idea was good but the implementation is far from conclusive: perhaps it is
time to replace the too complex and fragile akonadi with a simpler solution
such as a module kcm to centralize the management of accounts (kde -pim and
telepathy) and stored these configurations in such a way that all software can
access these resources directly. In addition kpart k-d-bus technologies would
allow a client to access resources through another client.

Of course this implies more code and work for each client but in the end it
would probably be more KISS and therefore more robust.

This does not prevent the use of databases to optimize clients, but several
sqlite db may be more robust than a very large mysql db, may not ?

Sorry for my comment a bit long but these multiple and recurring Akonadi
dysfunction starts to disgust me from Kontact which is the killer apps for
which I chose kde instead of gnome 7 years ago.

If the situation does not evolve in the right direction then I should resolve
to leave kde for gnome: it will be painful to me but if the stubbornness of the
kde-pim team to keep alive akonadi persists then it will be bye bye. ..

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Dennis Schridde]

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

--- Comment #35 from Dennis Schridde  ---
I am using akonadi-server/xenial,now 4:16.12.3-0neon+16.04+build7 and am also
still experiencing this issue. (How do I figure out the actual version number?)

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[bugzilla_noreply]

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

--- Comment #34 from stefanfr...@gmx.net ---
Hi,
unfortunately the new update to Version 5.4.3 do not solve the problem. I still
have crashes!
Best regards

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||sgr...@redhat.com

--- Comment #33 from Christoph Feck  ---
*** Bug 377393 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Jure Repinc]

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

Jure Repinc  changed:

   What|Removed |Added

 CC||j...@holodeck1.com

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Christoph Feck]

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

--- Comment #32 from Christoph Feck  ---
*** Bug 377273 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||dennis.schridde@uni-heidelb
   ||erg.de

--- Comment #31 from Christoph Feck  ---
*** Bug 376976 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||s.pa...@spiekerbros.com

--- Comment #30 from Christoph Feck  ---
*** Bug 376923 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit|https://commits.kde.org/ako |https://commits.kde.org/ako
   |nadi/5219f770b998aad16a3d51 |nadi/1593c17da9cbdc1483541e
   |bbd4f4c7ceb8b143c9  |1e7d7630f3c91f8208

--- Comment #29 from Daniel Vrátil  ---
Git commit 1593c17da9cbdc1483541e1e7d7630f3c91f8208 by Daniel Vrátil.
Committed on 24/02/2017 at 16:22.
Pushed by dvratil into branch 'Applications/16.12'.

Fix crash when Connection is closed while ItemRetriever is running

ItemRetriever::exec() runs a nested QEventLoop. If the parent
Connection is terminated while the event loop is running, the
delayed AkThread::quit() invocation is executed and the thread
is destroyed, while technically there is still execution going
on. To workaround that issue we don't destroy the thread in
Connection::quit() if we detect a nested QEventLoop but instead
we just notify the event loop to quit and destroy the thread
later when execution returns back to ItemRetriever::slotNewData().

This fixes a crash in QPSQLQuery, which was dereferencing a
QPSQLDriver after the driver has been deleted as the thread was
destroyed and avoids more of random crashes due to the Connection
being virtually deleted from its own nested event loop.
FIXED-IN: 5.4.3

M  +24   -1src/server/connection.cpp
M  +3-0src/server/connection.h
M  +1-0src/server/storage/datastore.cpp
M  +2-0src/server/storage/itemretriever.cpp

https://commits.kde.org/akonadi/1593c17da9cbdc1483541e1e7d7630f3c91f8208

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||kde...@posteo.de

--- Comment #28 from Daniel Vrátil  ---
*** Bug 375104 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||robby.engelm...@igfs-ev.de

--- Comment #27 from Daniel Vrátil  ---
*** Bug 375450 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Daniel Vrátil]

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

--- Comment #26 from Daniel Vrátil  ---
*** Bug 375558 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||kosse...@kde.org

--- Comment #25 from Daniel Vrátil  ---
*** Bug 375714 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 CC||a...@cryptomilk.org

--- Comment #24 from Daniel Vrátil  ---
*** Bug 376852 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

   Severity|critical|normal
 CC||dvra...@kde.org
   Version Fixed In||5.4.3
  Latest Commit||https://commits.kde.org/ako
   ||nadi/5219f770b998aad16a3d51
   ||bbd4f4c7ceb8b143c9

--- Comment #23 from Daniel Vrátil  ---
The crash itself has been fixed by commit
https://commits.kde.org/akonadi/5219f770b998aad16a3d51bbd4f4c7ceb8b143c9 which
will be in Akonadi 5.4.3 (KDE Applications 16.12.3) in March.

The patch fixes the crash itself, but does not address the underlying problem.
I'll keep this opened until the underlying problem is resolved.

--- Notes for future me:
The root cause is the nested QEventLoop in ItemRetriever::exec(). When
Connection is terminated (by server shutdown or connection loss on socket)
while the nested QEventLoop in ItemRetriever is running, Connection::quit()
will be invoked from the nested loop, destroying certain resources (socket,
datastore). This then leads to various crashes once the nested event loop ends
and execution within ItemRetriever::exec() continues.

I don't think it's possible to prevent nested event loop from executing
metacalls on Connection, after all the main reason for using QEventLoop in
ItemRetriever was to make it more interactive and interruptable.
Connection::quit() cannot directly terminate the nested QEventLoop, because it
has been invoked from it. It could however use delay invocation to quit the
loop and return early without actually quiting and destroying the thread. The
thread would quit once the excecution would return from the Handler back to
Connection::slotNewData(). Connection::quit() could probably set a flag or
something. However it's not clear how Connection::quit() should detect where
it's invoked from and whether it's a nested QEL or not, and how it should
interact with it.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Knut Hildebrandt]

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

--- Comment #22 from Knut Hildebrandt  ---
(In reply to Alexander from comment #21)
> The trouble comes from filtering emails in a POP3 account.

That might explain why I do not experience the crashes while deleting mails. I
only use IMAP. But there are still the problems mentioned in Comment 9 and
Comment 18. Maybe these should be moved to separate bugreports.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Alexander]

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

--- Comment #21 from Alexander  ---
(In reply to Christoph Feck from comment #20)
> From looking at the stack trace in comment #13, it looks like
> Akonadi::Server::Connection still runs in thread 11, while thread 1 already
> deleted it.
> 
> Deleting a connection should wait until all threads that run from it are
> terminated.

Christoph, here:
https://lists.opensuse.org/opensuse-factory/2017-02/msg00048.html is a good
description, what happens. The trouble comes from filtering emails in a POP3
account.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Christoph Feck]

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

--- Comment #20 from Christoph Feck  ---
>From looking at the stack trace in comment #13, it looks like
Akonadi::Server::Connection still runs in thread 11, while thread 1 already
deleted it.

Deleting a connection should wait until all threads that run from it are
terminated.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[bugzilla_noreply]

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

--- Comment #19 from stefanfr...@gmx.net ---
I hope its gonna fixed very soon. Kmail is not useable!

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Knut Hildebrandt]

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

--- Comment #18 from Knut Hildebrandt  ---
(In reply to C. Brouerius van Nidek from comment #17)
> Found in all email folders that are regularly used that read messages where
> still in the new subdirectory.

Because of Bug374925 I regularly check the directories where I move or copy
mails and thus can partially confirm this behaviour. All mails - read or unread
- end up in the   new subdirectory and stay there. Always move them by hand.
Maybe that is why I do not experience the crashes when deleting mails?

But mails that directly arrive to the inbox are moved from new to cur after
being read. Once in cur no mail ever gets moved back to new, even if I mark
them unread again.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[C . Brouerius van Nidek]

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

--- Comment #17 from C. Brouerius van Nidek  ---
Found in all email folders that are regularly used that read messages where
still in the new subdirectory. Since 24 hours I have removed these messages
manualy (Midnight Commander) from new to cur and did not have any crash of
kmail. Will report in a week :) if this is this is a temporary solution. The
problem of too many duplicates receiving does not seem to be of importance for
crashing. Just a nuisance.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Knut Hildebrandt]

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

Knut Hildebrandt  changed:

   What|Removed |Added

 CC||knut.hildebra...@gmx.de

--- Comment #16 from Knut Hildebrandt  ---
(In reply to Alexander from comment #9)
> The description, that akonadi crashes if you delete an email is true, but it
> crashes randomly, independently from what you do. Click an email, it may
> crash or not; go to another account, same. 

I'm not sure if it is the same as bug 375558, but what Alexander writes suggest
this assumption. The problem with deleting mails I did not notice yet. But I
usually do not delete more than one mail at a time.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[tomaggio]

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

--- Comment #15 from tomaggio  ---
Same here; Chakra Linux with KDE Applications 16.12.1

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Alexander]

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

--- Comment #14 from Alexander  ---
The bug »survived« the update to KDE Applications 16.12.1. Akonadi crashes,
when I'm changing to a mailing list folder, which contains lots of emails.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Andreas K . Huettel]

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

Andreas K. Huettel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||dilfri...@gentoo.org
 Ever confirmed|0   |1

--- Comment #13 from Andreas K. Huettel  ---
Same phenomenon here as described by original submitter, here with Gentoo. 
* randomly, kmail does not delete an e-mail
* when leaving kmail and then stopping akonadi, akonadi crashes. 

Backtrace:

Application: akonadiserver (akonadiserver), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
pthread_cond_timedwait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
[Current thread is 1 (Thread 0x7f8b76e62780 (LWP 32690))]

Thread 19 (Thread 0x7f8b6cfc5700 (LWP 32691)):
#0  0x7f8b73242b79 in g_mutex_lock (mutex=mutex@entry=0x7f8b68000990) at
/var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gthread-posix.c:1336
#1  0x7f8b731fd6c2 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f8b680210c0, timeout=-1, context=0x7f8b68000990) at
/var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:4223
#2  g_main_context_iterate (context=context@entry=0x7f8b68000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3924
#3  0x7f8b731fd7ec in g_main_context_iteration (context=0x7f8b68000990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990
#4  0x7f8b766f369c in QEventDispatcherGlib::processEvents
(this=0x7f8b680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#5  0x7f8b766a6d9a in QEventLoop::exec (this=this@entry=0x7f8b6cfc4e10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f8b765001f4 in QThread::exec (this=this@entry=0x7f8b769a9b00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#7  0x7f8b7693b445 in QDBusConnectionManager::run (this=0x7f8b769a9b00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#8  0x7f8b7650478c in QThreadPrivate::start (arg=0x7f8b769a9b00 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#9  0x7f8b74c72454 in start_thread (arg=0x7f8b6cfc5700) at
pthread_create.c:333
#10 0x7f8b75c3a5dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7f8b6768d700 (LWP 32700)):
#0  0x7f8b75c314fd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f8b731fd6dc in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f8b60295560, timeout=3330855, context=0x7f8b6990) at
/var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x7f8b6990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3924
#3  0x7f8b731fd7ec in g_main_context_iteration (context=0x7f8b6990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990
#4  0x7f8b766f369c in QEventDispatcherGlib::processEvents
(this=0x7f8b68c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#5  0x7f8b766a6d9a in QEventLoop::exec (this=this@entry=0x7f8b6768ce40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f8b765001f4 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f8b7650478c in QThreadPrivate::start (arg=0x2010e80) at
thread/qthread_unix.cpp:368
#8  0x7f8b74c72454 in start_thread (arg=0x7f8b6768d700) at
pthread_create.c:333
#9  0x7f8b75c3a5dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7f8b66e8c700 (LWP 32713)):
#0  0x7f8b75c314fd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f8b731fd6dc in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f8b58003020, timeout=3330881, context=0x7f8b58000990) at
/var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x7f8b58000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3924
#3  0x7f8b731fd7ec in g_main_context_iteration (context=0x7f8b58000990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990
#4  0x7f8b766f369c in QEventDispatcherGlib::processEvents
(this=0x7f8b580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#5  0x7f8b766a6d9a in QEventLoop::exec (this=this@entry=0x7f8b66e8be40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f8b765001f4 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f8b7650478c in

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Gero Müller]

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

--- Comment #12 from Gero Müller  ---
Hello,

i have the same problem in Archlinux, akonadi 16.12.1-2, mariadb 10.1.21-1

I found the following line in ~/.local/share/akonadi/db_data/mysql.err:
  2017-01-24 14:10:07 139694250785536 [ERROR] mysqld: Deadlock found when
trying to get lock; try restarting transaction

Also, if i delete the messages one after another and wait between the deletion,
it does not hang. Looks like a synchronization problem.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Gero Müller]

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

Gero Müller  changed:

   What|Removed |Added

 CC||p...@geromueller.de

--- Comment #11 from Gero Müller  ---
Created attachment 103615
  --> https://bugs.kde.org/attachment.cgi?id=103615&action=edit
kcrash stacktraces after crash on akonadictl stop

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[C . Brouerius van Nidek]

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

C. Brouerius van Nidek  changed:

   What|Removed |Added

 CC||const...@indo.net.id

--- Comment #10 from C. Brouerius van Nidek  ---
Have the same problems and help myself with folloWING SOLUTION (which seems to
work quit often:
 rm -rf ~/.local/share/akonadi/socket*
 rm -rf /tmp/akonadi*
and a restart of kmail

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Alexander]

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

Alexander  changed:

   What|Removed |Added

 CC||cookie...@web.de

--- Comment #9 from Alexander  ---
The description, that akonadi crashes if you delete an email is true, but it
crashes randomly, independently from what you do. Click an email, it may crash
or not; go to another account, same. See this bug report: 

https://bugzilla.opensuse.org/show_bug.cgi?id=1017147

Akonadi stopped working with update to 16.12 and this is more than an month
ago.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[tomaggio]

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

tomaggio  changed:

   What|Removed |Added

 CC||tomomel...@gmx.de

--- Comment #8 from tomaggio  ---
same Problem here ChakraLinux after last upgrade to 16.12.0. Sometimes it's
enough try to open an mail. Retrieving mail wait. Something in the db blocks.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[bugzilla_noreply]

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

--- Comment #7 from stefanfr...@gmx.net ---
I hope that helps?

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[bugzilla_noreply]

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

--- Comment #6 from stefanfr...@gmx.net ---
Crash report of akonadi server:
Application: akonadiserver (akonadiserver), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcb47c55080 (LWP 1116))]

Thread 39 (Thread 0x7fcacbfff700 (LWP 1917)):
#0  0x7fcb42ba5c33 in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#1  0x7fcb42ba66ab in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fcb42ba689c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fcb468142db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fcb467bdd3a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fcb465e0063 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fcb4487d454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fcb45ce37df in clone () from /usr/lib/libc.so.6

Thread 38 (Thread 0x7fcae67fc700 (LWP 1907)):
#0  0x7fcb448834b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fcb465e5ae6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7fcb465e11e4 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fcb4487d454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fcb45ce37df in clone () from /usr/lib/libc.so.6

Thread 37 (Thread 0x7fcaa6ffd700 (LWP 1906)):
#0  0x7fcb448834b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fcb465e5ae6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7fcb465e11e4 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fcb4487d454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fcb45ce37df in clone () from /usr/lib/libc.so.6

Thread 36 (Thread 0x7fcae4ff9700 (LWP 1905)):
#0  0x7fcb448834b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fcb465e5ae6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7fcb465e11e4 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fcb4487d454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fcb45ce37df in clone () from /usr/lib/libc.so.6

Thread 35 (Thread 0x7fcae57fa700 (LWP 1904)):
#0  0x7fcb448834b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fcb465e5ae6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7fcb465e11e4 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fcb4487d454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fcb45ce37df in clone () from /usr/lib/libc.so.6

Thread 34 (Thread 0x7fcaa77fe700 (LWP 1903)):
#0  0x7fcb448834b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fcb465e5ae6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7fcb465e11e4 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fcb4487d454 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fcb45ce37df in clone () from /usr/lib/libc.so.6

Thread 33 (Thread 0x7fcaa5ffb700 (LWP 1875)):
#0  0x7fcb45cda48d in poll () from /usr/lib/libc.so.6
#1  0x7fcb42ba6786 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fcb42ba689c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fcb468142db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fcb467bdd3a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fcb465e0063 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fcb4487d454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fcb45ce37df in clone () from /usr/lib/libc.so.6

Thread 32 (Thread 0x7fcaa67fc700 (LWP 1776)):
#0  0x7fcb42bebdd4 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0
#1  0x7fcb42ba5d60 in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#2  0x7fcb42ba66ab in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7fcb42ba689c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7fcb468142db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7fcb467bdd3a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7fcb465e0063 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7fcb465e4cf8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fcb4487d454 in start_thread () from /usr/lib/libpthrea

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Christoph Feck]

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

--- Comment #5 from Christoph Feck  ---
Please ask in a forum of your distribution how to install debug symbol
packages.

See also
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Ian]

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

--- Comment #4 from Ian  ---
(In reply to Christoph Feck from comment #3)
> Could you please add a backtrace for the crash? It might be a duplicate that
> is already reported, or already fixed.

Not really sure how to do this - but googled. Apparently one needs to run an
application with gdb? 

So - I tried that. Stopped akonadictl. Then:

gdb akonadictl start

This is what I get:
GNU gdb (GDB; openSUSE Tumbleweed) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from akonadictl...(no debugging symbols found)...done.
/home/ian/start: No such file or directory.
Missing separate debuginfos, use: zypper install
akonadi-server-debuginfo-16.12.0-2.1.x86_64


But then 
zypper install akonadi-server-debuginfo-16.12.0-2.1.x86_64
Retrieving repository 'Packman Repository' metadata
..[done]
Building repository 'Packman Repository' cache
...[done]
Retrieving repository 'openSUSE-Tumbleweed-Non-Oss' metadata
.[done]
Building repository 'openSUSE-Tumbleweed-Non-Oss' cache
..[done]
Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata
.[done]
Building repository 'openSUSE-Tumbleweed-Oss' cache
..[done]
Loading repository data...
Reading installed packages...   
'akonadi-server-debuginfo-16.12.0-2.1.x86_64' not found in package names.
Trying capabilities.
No provider of 'akonadi-server-debuginfo-16.12.0-2.1.x86_64' found.
['--plus-content debug'?]   
Resolving package dependencies...   

The following application is going to be REMOVED:   
  "System Tray" 

No additional space will be used or freed after the operation.  
Nothing to do.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Christoph Feck]

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

--- Comment #3 from Christoph Feck  ---
Could you please add a backtrace for the crash? It might be a duplicate that is
already reported, or already fixed.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Ian]

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

--- Comment #2 from Ian  ---
(In reply to stefanfrank from comment #1)
> same problem here. Manjaro with KDE Apps 16.12.
> Please fix it.

Glad to know I am not the only one experiencing this. 

Kmail has basically become unusable for me. I've had to switch to Thunderbird
in order to retrieve, read and reply to emails. I have been  using Kmail for
many many years (since 2002) and it's unfortunate that I've had to change email
app just to be able to read, reply and send emails.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[bugzilla_noreply]

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

stefanfr...@gmx.net changed:

   What|Removed |Added

 CC||stefanfr...@gmx.net

--- Comment #1 from stefanfr...@gmx.net ---
same problem here. Manjaro with KDE Apps 16.12.
Please fix it.

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