https://bugs.kde.org/show_bug.cgi?id=415614
Jack <ostrof...@users.sourceforge.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO |RESOLVED
--- Comment #4 from Jack <ostrof...@users.sourceforge.net> ---
I'm closing as WORKSFORME, since it would have been a bug if KMM itself put
that null char in the data, even if during an import, and you got the error
with other apps, not KMM itself. As to how that character got there, you are
correct - it shouldn't have happened, but we certainly won't figure it out now.
I'm guessing an import, but I'm not sure, and the import code has probably
changed enough.
--
You are receiving this mail because:
You are the assignee for the bug.
