https://bugs.kde.org/show_bug.cgi?id=358217
David Jarvie changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=358217
--- Comment #3 from David Jarvie ---
I don't understand what can have given rise to the bug, but there is now an
extra guard against using invalid data. Hence I can't be sure that it's fixed.
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=358217
--- Comment #4 from George R. Goffe ---
David,
I appreciate your help with this one!
I'll keep my eyes peeled and will open a new bug if I see the problem again.
Again, thanks,
George...
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=358217
--- Comment #5 from David Jarvie ---
Preferably reopen this bug rather than a new one if you see the problem again.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358217
David Jarvie changed:
What|Removed |Added
Latest Commit||4c8ecf34c1d9432b692d4ead41f
https://bugs.kde.org/show_bug.cgi?id=358217
--- Comment #2 from George R. Goffe ---
David,
This may be a timing of processes problem. I guess that kalarm got a bad
address and tried to use it? Who provided the address?
I'll keep my eyes open and re-open if I see it again.