https://bugs.kde.org/show_bug.cgi?id=378189
Marc Cousin changed:
What|Removed |Added
CC||cousinm...@gmail.com
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=378189
Brallan Aguilar changed:
What|Removed |Added
CC||apcomp...@gmail.com
--- Comment #15 from Bral
https://bugs.kde.org/show_bug.cgi?id=378189
--- Comment #14 from Matt Whitlock ---
(In reply to Matt Whitlock from comment #13)
> I have the Akonadi Console open with the Job Tracker enabled now, to try to
> see if any jobs hang in Akonadi.
Nope. KMail has gone out to lunch again, but Akonadi Co
https://bugs.kde.org/show_bug.cgi?id=378189
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #13 from Mat
https://bugs.kde.org/show_bug.cgi?id=378189
--- Comment #12 from Martin Koller ---
>Can there not be a "no caching" mode? "Mail" is already on the machine
>(maildir >resource), and just copying the mail to some other location on the
>FS seems >rather pointless...
There is no copying done. Mail
https://bugs.kde.org/show_bug.cgi?id=378189
--- Comment #11 from emili...@gmail.com ---
Did that countless times, problem comes back.
Can there not be a "no caching" mode? "Mail" is already on the machine (maildir
resource), and just copying the mail to some other location on the FS seems
rather
https://bugs.kde.org/show_bug.cgi?id=378189
--- Comment #10 from Martin Koller ---
What you see is a different problem.
This bug report was about not getting an answer from akonadi at all and
therefore
kmail showing only a "please wait..." display
At least you GET an answer - although there is s
https://bugs.kde.org/show_bug.cgi?id=378189
emili...@gmail.com changed:
What|Removed |Added
CC||emili...@gmail.com
--- Comment #9 from emil
https://bugs.kde.org/show_bug.cgi?id=378189
--- Comment #8 from Martin Koller ---
This patch does not fix your current database nor does it solve the issue
that akonadi creates multiple ids in the first place.
It just avoid the "endless waiting".
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=378189
--- Comment #7 from Laurent Montel ---
Yep I still can able to see "Multiple merge candidates"
I use pop3 + imap too.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=378189
--- Comment #6 from Martin Koller ---
> Are you sure that it's enough ?
> I still have this problem.
Well ... how sure can I be, given that I know not much about the Akonadi
internals ...
This is what I found during my analysis, and here it solves the
https://bugs.kde.org/show_bug.cgi?id=378189
Laurent Montel changed:
What|Removed |Added
CC||mon...@kde.org
--- Comment #5 from Laurent Mon
https://bugs.kde.org/show_bug.cgi?id=378189
Martin Koller changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=378189
--- Comment #3 from Paul Colquhoun ---
I have followed the directions at
https://docs.kde.org/trunk5/en/pim/kmail2/clean-start-after-a-failed-migration.html
to rebuild the akonadi databases from scratch, but the problem has persisted.
--
You are recei
https://bugs.kde.org/show_bug.cgi?id=378189
--- Comment #2 from Paul Colquhoun ---
I forgot to include this:
$ kmail --version
kmail2 5.4.3
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=378189
Paul Colquhoun changed:
What|Removed |Added
CC||kdeb...@andor.dropbear.id.a
16 matches
Mail list logo
