I've tried various scenarios to reproduce in a VM since I don't have
physical hardware to test this on. I'm not able to reproduce it. In
bug 792652 Colin says:
"I believe that this is ultimately a regression caused by the fix for
bug 756920 (ubiquity r4693). In order to try to ensure that the boot
loader choice was recorded in debconf in every possible code path, this
was done in exit_ui_loops as a sort of "finally" handler. However,
exit_ui_loops is only supposed to do frontend interaction, and (as this
bug demonstrates) it isn't safe for it to attempt to talk to debconf. I
think a correct fix would move this out of exit_ui_loops again and try
to find a safer way to fix the original bug."
but I'm quite reluctant to change this code unless I can reproduce it
and/or provide a test case for the failure. Do you have any other
suggestions for triggering this bug while under, say a vm install?
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942111
Title:
ubiquity crashed in ubi-partman.py : ValueError: I/O operation on
closed file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/942111/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
