Comment 4 for bug 1692326

I'm not sure what the Ubuntu policy is with respect to upstream bugs, but can I humbly suggest looking at the latest Mnemosyne version first, and if the bug has been fixed there, open an Ubuntu bug to upgrade to the latest version? If it's a new bug, please open a report in the Mnemosyne tracker.

There's plenty more bugs from 2.4 fixed in 2.4.1 which you haven't found yet, and it makes no sense to revisit them all :-)