It's perfectly safe to delete the defective log file if you bump into this--they're just log files.
I'm not sure why the RotatingFileHandler doesn't just create a new log file when it encounters the IOError. I'm also not sure why it's encountering an IOError--that's bizarre. I'll fix it upstream for Miro 3.1 and backport the fix to Miro 3.0.1 and toss a link to the revision in here. I'm not supporting the Miro 2.5 series anymore, but it should be pretty easy to take the revision and build a patch for Miro 2.5.3 for whoever wants to do that. ** Bug watch added: Participatory Culture Bugzilla #13338 http://bugzilla.pculture.org/show_bug.cgi?id=13338 ** Also affects: democracy via http://bugzilla.pculture.org/show_bug.cgi?id=13338 Importance: Unknown Status: Unknown -- IOError: [Errno 5] Input/output error: '~/.miro/miro-log' https://bugs.launchpad.net/bugs/500623 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
