https://bugs.kde.org/show_bug.cgi?id=335776
Luis Silva changed:
What|Removed |Added
CC||lacsi...@gmail.com
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=335776
Daniel Eklöf changed:
What|Removed |Added
CC||dan...@ekloef.se
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=335776
Rafael Jesús Alcántara Pérez changed:
What|Removed |Added
CC||rafaelalcantaraperez@gmail.
https://bugs.kde.org/show_bug.cgi?id=335776
--- Comment #6 from Christian Mollekopf ---
(In reply to Daniel Vrátil from comment #5)
> I discovered one of the possible causes of the crash:
>
> In ItemSync, when the ItemCreateJob fails, the TransactionSequence is rolled
> back and ItemSync emits f
https://bugs.kde.org/show_bug.cgi?id=335776
Daniel Vrátil changed:
What|Removed |Added
CC||dvra...@redhat.com
--- Comment #5 from Daniel V
https://bugs.kde.org/show_bug.cgi?id=335776
Sergio Martins changed:
What|Removed |Added
CC||iamser...@gmail.com
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=335776
--- Comment #3 from Christian Mollekopf ---
Created attachment 88644
--> https://bugs.kde.org/attachment.cgi?id=88644&action=edit
debug info by dfaure
I suppose this version of the crash could be explained if for some reason the
the task was killed (
https://bugs.kde.org/show_bug.cgi?id=335776
David Faure changed:
What|Removed |Added
CC||fa...@kde.org
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=335776
--- Comment #2 from Christian Mollekopf ---
dfaure reported a disconnect just before a similar crash, so let's assume
that's the cause.
This happens due to the CollectionFetchJob that is not aborted on disconnect,
so we need to fix that.
--
You are re
https://bugs.kde.org/show_bug.cgi?id=335776
Christian Mollekopf changed:
What|Removed |Added
CC||mollek...@kolabsys.com
--- Comment #1 fro
10 matches
Mail list logo
