Comment 7 for bug 837261

This looks like a caught Python exception, not an error message from C/Vala. I suppose oem-config has something like a catch-all "except:" somewhere which causes the error message to be displayed in a dialog box? Perhaps it should rather crash normally and have apport pick up the traceback, so that we get a sensible stack trace?