Not sure if this is the right place to report bugs, but I couldn't see links to a bug-tracker, so here goes..
Got an exception thrown while in the edit deck mode. Had altered the list of viewed cards to show only cards from one category, opened a card to look at / edit it (though I didn't change it), then closed it in order to make a new one. Hit Ctrl-A next, somewhat automatically, as that seemed like the old short-cut to add a card. Not sure if that was what triggered it, as when nothing happened, I clicked on the card to open it again, and then noticed it wasn't responding. A few seconds later, the exception dialog pops up. Trying again now shows that Ctrl-A should select all; that didn't happen last time.
Uncaught exception!
Traceback (innermost last):
File "mnemosyne\pyqt_ui\browse_cards_dlg.pyo", line 221, in paint
File "mnemosyne\pyqt_ui\browse_cards_dlg.pyo", line 184, in card
File "mnemosyne\lib_mnemosyne\component.pyo", line 111, in card_type_with_id
KeyError: u"
Clicking OK on the dialog makes it go away, and I get a few more seconds of responsiveness, but then it happens again. My guess is that I've put something in an inconsistent state that's causing it to throw an error whenever it re-paints the UI.
I'm running Win7 64, with the Mnemosyne 2.0 version that was posted to the thread about Windows hangs as an attempt at fixing things.
Unfortunately, I can't reproduce the error following my notes above, so I'm not sure how helpful this will be. Mnemosyne seems to be functioning OK after ending the process and re-starting.
Trond.