QMessageBox.StandardButton = QMessageBox.NoButton): argument 4 has unexpected type 'str'

[themusicgod1]

mnemosyne: 2.4-0.1
ubuntu: 17.04 zesty

1) Click on "Add a new card" button,
2) select card type "Front-to-Back"
3) Type something into the "Front" field (example "adfksafd")
4) click on card type dropdown & change type to Vocabulary
5) "Convert Card type data" dialog comes up

expected result
6) Changeing "front" dropdown and "back" dropdown to the same thing
should either produce an error box telling you not to do that(most likely), or allow you to select both to be the same thing.

actual result:

Traceback (innermost last):
  File "/usr/lib/python3/dist-packages/mnemosyne/pyqt_ui/convert_card_type_keys_dlg.py", line 62, in combobox_updated
    _("&OK"), "", "", 0, -1)
 TypeError: critical(QWidget, str, str, buttons: Union[QMessageBox.StandardButtons, QMessageBox.StandardButton] = QMessageBox.Ok, defaultButton: QMessageBox.StandardButton = QMessageBox.NoButton): argument 4 has unexpected type 'str'

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: mnemosyne 2.4-0.1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun May 21 10:31:06 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-07-09 (1046 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708)
PackageArchitecture: all
SourcePackage: mnemosyne
UpgradeStatus: Upgraded to zesty on 2017-04-13 (37 days ago)

[Peter Bienstman (peter-bienstman)]

This has been fixed in 2.4.1.

Please only report bugs in Mnemosyne itself against the latest Mnemosyne version, and using Mnemosyne's own bug tracker. "Mnemosyne (Ubuntu)" is better suited for packaging specific issues.

[themusicgod1 (themusicgod1)]

This is broken *in the build produced in zesty*. This is a bug specific to the version produced and packaged and delivered to ubuntu users by default as part of zesty 17.04, and this is not an invalid bug if a fix was made to it.

[Peter Bienstman (peter-bienstman)]

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 :-)