On 14.04 I re-ran ubiquity in --debug mode. The process stalled with 100% CPU use at around 02:55. I suspect the causeis the non-zero return code from partman-commit:
debconf (developer): --> 1 Installing system Sep 27 02:55:31 debconf (filter): --> 0 OK Sep 27 02:55:31 debconf (filter): <-- PROGRESS INFO ubiquity/install/apt_clone_save Sep 27 02:55:31 debconf (filter): widget found for ubiquity/install/title debconf (developer): <-- METAGET ubiquity/install/apt_clone_save description debconf (developer): --> 1 Saving installed packages... Sep 27 02:55:31 debconf (filter): --> 0 OK Sep 27 02:55:31 ubiquity: ['log-output', '-t', 'ubiquity', '--pass-stdout', '/bin/partman-commit'] exited with code 32 ** Attachment added: "14.04 ubiquity --debug" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1500110/+attachment/4476039/+files/debug.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500110 Title: mount point /tmp/tmp.${RANDOM}/var does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1500110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
