[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2023-05-22 Thread Gael L.
https://bugs.kde.org/show_bug.cgi?id=360834 Gael L. changed: What|Removed |Added CC||g...@openwebzone.fr -- You are receiving this mail

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2022-12-03 Thread Richard Bos
https://bugs.kde.org/show_bug.cgi?id=360834 --- Comment #14 from Richard Bos --- I use kmail more or less on weekly basis (every weekend), and the first I need to do is to clean up emails that I processed before (days or weeks). That are emails that then again retrieved and shown in kmail. It

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2022-12-01 Thread sourcemaker
https://bugs.kde.org/show_bug.cgi?id=360834 sourcemaker changed: What|Removed |Added CC||kde-bugzi...@aschoettler.co |

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2022-07-21 Thread Tobias Rautenkranz
https://bugs.kde.org/show_bug.cgi?id=360834 Tobias Rautenkranz changed: What|Removed |Added CC||tob...@rautenkranz.ch -- You are

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2022-06-27 Thread Aaron Williams
https://bugs.kde.org/show_bug.cgi?id=360834 Aaron Williams changed: What|Removed |Added CC||aar...@doofus.org --- Comment #12 from Aaron

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2021-12-07 Thread Llyw
https://bugs.kde.org/show_bug.cgi?id=360834 Llyw changed: What|Removed |Added CC||llyw.li...@coders-haven.net --- Comment #11 from Llyw

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2019-10-01 Thread Marc Mezzarobba
https://bugs.kde.org/show_bug.cgi?id=360834 Marc Mezzarobba changed: What|Removed |Added CC||marc+b...@mezzarobba.net -- You are

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2019-09-07 Thread Daniel Roschka
https://bugs.kde.org/show_bug.cgi?id=360834 Daniel Roschka changed: What|Removed |Added CC||danielroschka@phoenitydawn.

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2018-08-05 Thread Richard Bos
https://bugs.kde.org/show_bug.cgi?id=360834 Richard Bos changed: What|Removed |Added CC||richard@xs4all.nl --- Comment #10 from

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2018-01-29 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=360834 --- Comment #9 from Martin Steigerwald --- Also see: akonadictl fsck: What messages indicate real issues and what to do about them? https://marc.info/?l=kdepim-users=149426877926602=2 (I am about to reply to this thread with a

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2016-06-24 Thread Erik Quaeghebeur via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360834 Erik Quaeghebeur changed: What|Removed |Added CC|

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2016-04-03 Thread piedro via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360834 --- Comment #8 from piedro --- p.s.: Also this will probably be realted to many of the bugs regarding incomplete email indices created by the "akonadi-indexing-agent". p. -- You are receiving this mail because: You are

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2016-04-03 Thread piedro via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360834 --- Comment #7 from piedro --- Just to mention: This should have a very high priority in my opinion as most forums, threads and websites dealing with akonadi problems explicitly recommend deleting your akonadi folder to

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2016-03-23 Thread Martin Steigerwald via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360834 --- Comment #6 from Martin Steigerwald --- Knut, it is safe to remove them (but only the file_lost+found files not file_db_data!). That Akonadi leaks files in file_db_data which akonadictl fsck moves to lost+found is a known bug

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2016-03-23 Thread Knut Hildebrandt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360834 Knut Hildebrandt changed: What|Removed |Added CC|

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2016-03-22 Thread Martin Steigerwald via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360834 Martin Steigerwald changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2016-03-22 Thread Martin Steigerwald via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360834 Martin Steigerwald changed: What|Removed |Added CC|

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2016-03-22 Thread Martin Steigerwald via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360834 --- Comment #2 from Martin Steigerwald --- Oh and Dan later added that "server" actually means any resource, so "server" could also be a local maildir or calender file or what not. -- You are receiving this mail because: You are

[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource

2016-03-22 Thread Martin Steigerwald via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360834 --- Comment #1 from Martin Steigerwald --- Adding link to DanĀ“s mail in the thread "Akonadictl fsck" on kdepim-users where he explains this: https://mail.kde.org/pipermail/kdepim-users/2016-March/000113.html Also this report