Public bug reported:
Binary package hint: ubiquity
During an installation test here, I get a warning dialog saying
"MigrationAssistant failed with exit code 32". However, the log
indicates that ma-ask exited 0. Baffled, I added some further debugging
to investigate, and discovered that something in the middle of the
migration-assistant component's cleanup handler is forking! (I happened
to add a debug statement after the cleanup handler, and I get one line
of output from the pre-cleanup debug and two lines of output from the
post-cleanup debug.) In the process no doubt it's trashing the local
variable containing the return code, but more importantly I have
absolutely no idea where the control flow is going to go afterwards.
This is probably due to the stuff in MigrationAssistant.cleanup that
tries to stop ubiquity from going forward after m-a fails; this is
necessary but it probably needs to be done in a different way. Evan,
unless you're around and see this very soon, I'll try to think up a
minimal fix.
** Affects: ubiquity (Ubuntu)
Importance: High
Status: Confirmed
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
Status: Unconfirmed => Confirmed
Target: None => ubuntu-7.04
--
migration-assistant cleanup handler manages to fork somewhere
https://bugs.launchpad.net/bugs/105861
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
