Hi, $buffer =~ s/\e//g;
.. this was all that was needed to fix my mess. Though, kpcli for obvious reasons shouldn't be able to write broken data it can't read again, so I keep seeing this as a severe bug in the code which can lead to data loss for people who aren't familiar enough with perl or who don't have friends who support them to dig down the issue. The above line was a quick fix for my case, I'm uncertain if it might appear to others in other ways, but this clearly goes against the principle of robustness. Upstream is at 3.6 in the meantime, I'm willing to update it now that I digged a bit further into it. If I don't hear back in the next few days I propose an NMU for it, as thanks for having it around in the first place. :) Enjoy, Rhonda [happy again] * Rhonda D'Vine <rho...@deb.at> [2022-03-08 16:19:46 CET]: > Hi, > > I managed to find the culprit With A Little Help From My Friends[tm]. I > used Data::Dumper before the content got passed to XML::Parser, and it > turned out that there is an Escape character (0x1b, ^[) in a comment > field. > > kpcli seems to have accepted this when the comment was pasted and > stored it happily, but was unable to re-read the file written with that > in it. > > I'm currently fiddling around to delete that escape character on load > time and have kpcli start, allowing me to save it without the escape > character, hopefully allowing to re-read it afterwards. > > I'll keep you posted, > Rhonda -- Fühlst du dich mutlos, fass endlich Mut, los | Fühlst du dich hilflos, geh raus und hilf, los | Wir sind Helden Fühlst du dich machtlos, geh raus und mach, los | 23.55: Alles auf Anfang Fühlst du dich haltlos, such Halt und lass los |
