https://bugs.kde.org/show_bug.cgi?id=406718
--- Comment #5 from John Gehrig ---
Patrick, I took a look at your backtrace... It looks like the same crash to me.
Your crash should be fixed by this patch. Probably Duplicate.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=406718
--- Comment #4 from John Gehrig ---
Hi Nate,
Sure, I can submit a patch... I should have some free time this weekend.
Thanks for the link! I will ping you if I have any troubles.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=406718
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--- Comment #3 from Nate Graham
https://bugs.kde.org/show_bug.cgi?id=406718
Patrick Silva changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=406718
John Gehrig changed:
What|Removed |Added
Assignee|kdelibs-b...@kde.org|k...@davidedmundson.co.uk
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=406718
--- Comment #1 from John Gehrig ---
As per the documentation
(https://api.kde.org/frameworks/kcoreaddons/html/classKJob.html#a975a15193b17d06e182f8fd55c5f0d8b)
job->errorString() should only be called when job->error() != 0.
A quick fix for my issues
