[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-08-28 Thread Sandro Knauß
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #25 from Sandro Knauß --- Git commit ca67354dcc5b4640f26de0b3e46c79cf1e50bc32 by Sandro Knauß, on behalf of David Faure. Committed on 28/08/2019 at 16:36. Pushed by knauss into branch 'Applications/18.08'. Akonadi: fix dangling transaction

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-08-16 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #24 from David Faure --- Git commit 15c91a0ac93051465b37807efceb6e9fd36cb73b by David Faure. Committed on 16/08/2019 at 09:27. Pushed by dfaure into branch 'Applications/18.12'. Akonadi: fix dangling transaction after itemsync failure

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-04-07 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #23 from David Faure --- Oh, and about part-less items, I just noticed that I had a bunch in a spam folder, and after syncing that folder, the same query returns nothing. So it seems to me that a successful sync clears that up. In other

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-04-07 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #22 from David Faure --- Additional fix pushed in https://cgit.kde.org/akonadi.git/commit/?id=257598195d09b1022ebf08cd58245cd3493f5a2e for 19.04 Note: all this is about akonadi not getting stuck when the "multiple merge candidates" problem

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-04-04 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #21 from David Faure --- Found one more problem https://phabricator.kde.org/D20243 -- You are receiving this mail because: You are watching all bug changes.

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-03-21 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=399167 David Faure changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-03-21 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #19 from David Faure --- Git commit 8ff596c4fe15199b66262c624d8b7c8d8ec7368f by David Faure. Committed on 21/03/2019 at 15:50. Pushed by dfaure into branch 'Applications/19.04'. Akonadi: fix dangling transaction after itemsync failure

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-03-21 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #18 from David Faure --- Git commit f1281cf18f40fd69acd61c31b48f5ce43e138eea by David Faure. Committed on 21/03/2019 at 15:49. Pushed by dfaure into branch 'master'. Akonadi: fix dangling transaction after itemsync failure Summary:

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-03-14 Thread Michal Hlavac
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #17 from Michal Hlavac --- Can confirm that temporary fix works. Didn't try to cancel fetch process. Patched packages form openSUSE Tumbleweed: https://build.opensuse.org/package/show/home:hlavki/akonadi-server -- You are receiving this

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-03-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=399167 m...@bearsh.org changed: What|Removed |Added CC||m...@bearsh.org -- You are receiving this

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-03-11 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #16 from David Faure --- I debugged this and came up with https://phabricator.kde.org/D19487 It breaks canceling (as a user, clicking on the progress item to cancel), but if you stay away from canceling, you can try that patch to make

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-03-11 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=399167 Kevin Funk changed: What|Removed |Added CC||devuran...@gmx.net --- Comment #15 from Kevin

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-03-08 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=399167 Christoph Feck changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-02-27 Thread Michal Hlavac
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #13 from Michal Hlavac --- Created attachment 118398 --> https://bugs.kde.org/attachment.cgi?id=118398=edit mariadb status I run `SHOW ENGINE INNODB STATUS` query in akonadiconsole. It looks like 2 transactions with same update query

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-02-11 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #12 from Milian Wolff --- ok, that cleanup didn't help for long... First I got spammed by hundreds of lines of: 1281.968 critical:

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-02-11 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #11 from Milian Wolff --- I had 1007 part-less items, removing them seems to have helped for now. Could we add that cleanup routine to `akonadictl fsck`? Also, any idea how could prevent this from happening again - I am willing to apply

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-02-07 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=399167 Volker Krause changed: What|Removed |Added CC||vkra...@kde.org --- Comment #10 from Volker

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-01-08 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=399167 David Faure changed: What|Removed |Added CC||fa...@kde.org -- You are receiving this mail

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2019-01-08 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=399167 Kevin Funk changed: What|Removed |Added CC||kf...@kde.org --- Comment #9 from Kevin Funk ---

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2018-12-01 Thread Vinzenz Vietzke
https://bugs.kde.org/show_bug.cgi?id=399167 Vinzenz Vietzke changed: What|Removed |Added CC||v...@vinzv.de --- Comment #8 from Vinzenz

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2018-11-27 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #7 from Andreas Schneider --- I press 'Del' the message is remove from the message list. The message reappears because of the imap sync in the message list. Now if you 'Del' the reappeared message again, you create a 'Multiple merge

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2018-11-27 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #6 from Andreas Schneider --- I can more or less reproduce the multiple merge canditates. I'm connected to an imap server over a slow VPN connection. I have "Download all messages for offline use" selected. When I read the Inbox and

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2018-11-27 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=399167 Daniel Vrátil changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2018-11-19 Thread Michal Hlavac
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #4 from Michal Hlavac --- It didn't help. After few days errors are back. I think it may have some connection with suspend to RAM. -- You are receiving this mail because: You are watching all bug changes.

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2018-11-16 Thread Michal Hlavac
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #3 from Michal Hlavac --- I fixed this by completely reinitialization of akonadi. somethink like: akonadictl stop remove directories ~/.local/share/akonadi* remove files and directories ~/.config/akonadi* akonadictl start and setup all

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2018-10-19 Thread Christian Boltz
https://bugs.kde.org/show_bug.cgi?id=399167 Christian Boltz changed: What|Removed |Added CC||kde-b...@cboltz.de -- You are receiving

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2018-10-11 Thread Michal Hlavac
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #2 from Michal Hlavac --- Created attachment 115560 --> https://bugs.kde.org/attachment.cgi?id=115560=edit Akonadi error log Same issue here. I get this on daily basis. It's realy unusable. Full akonadi log in attachment. -- You are

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2018-10-11 Thread Michal Hlavac
https://bugs.kde.org/show_bug.cgi?id=399167 Michal Hlavac changed: What|Removed |Added CC||hla...@hlavki.eu -- You are receiving this

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2018-10-02 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #1 from Andreas Schneider --- Please print the "folder name" in the error/debug message: org.kde.pim.akonadicore: Creating/updating items from the akonadi database failed: "Multiple merge candidates, aborting" and/or

[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable

2018-09-28 Thread Andreas Schneider
https://bugs.kde.org/show_bug.cgi?id=399167 Andreas Schneider changed: What|Removed |Added CC||dvra...@kde.org -- You are receiving this