Bug 168602

Summary:	task and event attach names are corrupted after reopen (non ascii characters)
Product:	[Applications] korganizer	Reporter:	Anton N. Grachov <fragster>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	smartins
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	task with 2 attaches

Description Anton N. Grachov 2008-08-07 15:01:07 UTC

Version:           4.1 (using KDE 4.1.0)
Installed from:    SuSE RPMs
OS:                Linux

When we create task, or event, then attach file with non ascii character in name - after closing and reopening program - filename would be corrupted.
If we only reopen task or event - without closing whole program - all ok.
May be this bug information will be useful: https://bugs.kde.org/show_bug.cgi?id=14954

some more info in attached screenshot (russian localisation)

Comment 1 Anton N. Grachov 2008-08-07 15:03:23 UTC

Created attachment 26714 [details]
task with 2 attaches

task with one attach, that was added before kontact reopen, and one (same file)
- added instantly before screenshot

Comment 2 Anton N. Grachov 2008-09-15 10:09:38 UTC

when korganizer save .ics with such attaches, name if attach (field X-LABEL in ics) - every non ascii character - doubles... after some time - name of attaches grow up to many megabytes - and korganizer (and korgac) eats huge amount of memory (100-400 mb per item) to handle it... if there is no enough memory to handle it - it crashes...

Comment 3 Sergio Martins 2009-03-03 04:39:52 UTC

Confirmed in trunk 934413.

Comment 4 Denis Kurz 2016-09-24 18:46:15 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 5 Denis Kurz 2017-01-07 21:25:21 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.