This bug was fixed in the package ubiquity - 1.11.7
---
ubiquity (1.11.7) jaunty; urgency=low
[ Mario Limonciello ]
* bin/ubiquity-dm, debian/init: Fallback to noninteractive if automatic fails
- If the X server fails to startup (due to issues with vesa, or automatic
pro
Thanks for following up with this information; I believe I've fixed this
for the next upload to Jaunty. The workaround for Ubuntu 8.10
installations is probably to simply avoid clicking the Cancel button,
annoying though I realise that is; I don't *think* this bug can arise
without doing so.
** Ch
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Confirmed
--
crash: InstallStepError: ClockSetup failed with code 30
https://bugs.launchpad.net/bugs/313259
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
I have no hope of investigating this without the things you edited out,
I'm afraid. They shouldn't contain any personal information apart from
(possibly) the things you filled into the "Who are you?" box. Could you
please reproduce this and attach the crash file again?
** Changed in: ubiquity (Ubu
