(reopened after a dupe bug #1027648 got filed) Triggering this bug is inherently racy. I have tried to trigger it back & forth myself with precise-daily image and did not manage so. Second time around, this bug was brought to our attention through crash database.
The statistics for this crash signature are here: https://errors.ubuntu.com/bucket/?id=%2Fusr%2Flib%2Fubiquity%2Fbin%2Fubiquity%3AValueError%3Awatch_debconf_fd_helper%3Aprocess_input%3Await%3Acleanup%3Apreseed%3A%3Clambda%3E%3Acommand There are no reports for versions 2.10.21, 2.10.22 and 2.10.23 which are currently in precise-proposed testing. Please consider this bug verified for precise SRU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/792652 Title: ubiquity crashed with ValueError in command(): I/O operation on closed file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/792652/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
