https://bugs.kde.org/show_bug.cgi?id=410596
David Jarvie changed:
What|Removed |Added
Version Fixed In||19.08.1
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=410596
--- Comment #13 from Jiri Palecek ---
(In reply to David Jarvie from comment #12)
> Can you please commit your Phabricator patch so that this bug report can be
> closed? Thanks.
Hardly, I have no access.
--
You are receiving this mail because:
You ar
https://bugs.kde.org/show_bug.cgi?id=410596
--- Comment #12 from David Jarvie ---
Can you please commit your Phabricator patch so that this bug report can be
closed? Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410596
--- Comment #11 from David Jarvie ---
Ok, that makes sense. Thanks for your Phabricator patch, which I have accepted.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410596
--- Comment #10 from Jiri Palecek ---
(In reply to David Jarvie from comment #9)
> Yes, there is a bug in removeKAEvents, and your patch looks good. I'll wait
> for you to submit it in Phabricator.
I've posted it.
> The valgrind trace shows that a cal
https://bugs.kde.org/show_bug.cgi?id=410596
David Jarvie changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=410596
--- Comment #8 from Jiri Palecek ---
Created attachment 122029
--> https://bugs.kde.org/attachment.cgi?id=122029&action=edit
This patch looks better
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410596
Jiri Palecek changed:
What|Removed |Added
Attachment #122027|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=410596
--- Comment #6 from Jiri Palecek ---
Created attachment 122027
--> https://bugs.kde.org/attachment.cgi?id=122027&action=edit
proposed patch
Will send it through Phabricator in a few days, just sending so you can comment
on it now.
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=410596
--- Comment #5 from Jiri Palecek ---
Hello,
thanks for your effort. Yes, there are duplicate items:
$ grep ^UID ~/.kde/share/apps/kalarm/*.ics | sort -k 3 -t:
/home/jirka/.kde/share/apps/kalarm/calendar.ics:UID:b355410c-07af-4ded-abf3-d88743a1
/ho
https://bugs.kde.org/show_bug.cgi?id=410596
--- Comment #4 from David Jarvie ---
The valgrind crash is in fact different from the original crash. The valgrind
crash shows that multiple calendar status changes are being received in
AlarmCalendar, before the processing of the previous one has compl
https://bugs.kde.org/show_bug.cgi?id=410596
--- Comment #3 from David Jarvie ---
Oops, the command should be
grep ^UID: file1 file2 ... | sort | uniq -c | grep -v "^ *1 "
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410596
--- Comment #2 from David Jarvie ---
Thank you for the good quality bug report.
Even with the information you provided, it isn't clear what went wrong. It's
possible (but not certain) that if any events have UIDs which are duplicated
between different
https://bugs.kde.org/show_bug.cgi?id=410596
--- Comment #1 from Jiri Palecek ---
BTW valgrind says this about the problem:
==23380== Invalid read of size 4
==23380==at 0x4BF3134: KAlarmCal::KAEvent::category() const
(kaevent.cpp:1769)
==23380==by 0x1B0C31: AlarmCalendar::events(Akonadi::
14 matches
Mail list logo
