Comment 3 for bug 1421884

I received a similar error a few days ago.
It's a very strange error, because the file that was mentioned actually exists in my computer.
Unless that file was momentarily missing due to a repository update, and exactly when oneconf decided to sync. If that's how this works, of course.

The best and easiest way to fix this bug would probably be to just add a try...except block around one of the lines in the traceback.