Comment 4 for bug 1040353

The backtrace shows it failing when writing the report file on line 84. This is because write in problem_report.py checks that it was opened in binary mode, with a comment that it is required. Changing line 82 in apportcheckresume so it opens report_file in binary mode with 'wb' instead of just 'w' seems to fix it.

Running it manually triggers bug #1046092 because the script assumes /var/lib/pm-utils/status exists. Not sure if that was the case all along, or if either the change to python3 or changes to attach_file_if_exists changed the behavior.