Let me jump in as the upstream author: this is with absolute certainly not in any way related to "libstdc++6 upgrade" nor to any outdated libraries.
Just read the backtrace that Thomas helpfully provided: it shows that the LucenePlusPlus library asserts on reading what is probably corrupted data. This should be filed as a bug with LucenePlusPlus, as it should never assert on inputs and should throw an exception instead. The other grave bug is of course that apparently Poedit/LucenePlusPlus corrupted the data in the first place when saving. I have some spurious reports of this corruption happening on other platforms, but this is the first confirmation I have that it was caused by Poedit itself while editing. Apparently, LucenePlusPlus's supposed ACID properties don't exist in real life in the C++ port (not the first problem). Pity there isn't a backtrace from the time of crash, that could be useful. To "fix" this to get Poedit working again, I'm afraid the only solution is to delete the local TM in ~/.local/share/poedit/TranslationMemory (or try to recover it with Lucene tools). Vaclav -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
