[08:09] veebers: not really, as desktop installer doesn't do "package installation" for most of the installation (it simply copies the whole cd contents). You can chroot into /target and add ppa & upgrade after the install is finished. [09:21] xnox, bug 1066256 has been there for a while, but might be something to fix in next respin ? [09:21] Launchpad bug 1066256 in ubiquity "/usr/lib/ubiquity/user-setup/user-setup-apply: ligne 165 : [: 5 : unary operator expected" [Undecided,New] https://launchpad.net/bugs/1066256 [09:23] jibel: I'm not sure. I'd ask cjwatson for second opinion. I haven't look what $ROOT is expected to be (with/without trailing slash) and also maybe a better fix is to test for empty value in that script. [09:24] jibel: is it easy to reproduce? e.g. do oem-install and that's it?! [09:24] xnox: cool, thanks for the info :) [09:25] veebers: your welcome =) [09:25] * xnox is happy with his irc bouncer to get the scrollback =) [09:25] xnox, right, oem install and that's it. I just do not read the logs very often. I was searching something else :) [09:26] =)))) [09:29] I kinda like to fix syntax errors personally [09:30] Hm. Crappy quoting. [09:31] Ah yes, and jibel has a point as well. Trailing slash will be fine there. [09:31] yeah, there is more than one way to fix it =) [09:33] Some of which are correct ;-) [15:48] xnox, about bug 1065502, I could only reproduce it on vbox, not hw or kvm. So maybe there is something special in the way vbox handles virtual disks. [15:48] Launchpad bug 1065502 in ubiquity "Ubiquity failed to proceed to partman, fails at replace recipe now..." [High,Confirmed] https://launchpad.net/bugs/1065502 [15:48] Perhaps you get /dev/vd* in vbox? [15:48] kvm has virtio options [15:48] hmm... good suggestion, I can try that. [15:51] it's sd* in vbox [15:53] jibel: and what's on disk? simple full disk quantal? or like free space available (or old quantal) or multiple OS? [15:53] no luck with virtio nor sata nor ide. [15:53] in kvm [15:54] xnox, it is a 16GB, default desktop installation in English. By default, I mean blindly press continue and enter some text in the mandatory fields until it reboots [15:54] 16GB disk [15:55] so maybe it's limited to vbox [15:57] I did do this with 16GB disk =/ and no luck in kvms. ok, will bring my vbox at one point to sort it out. putting it to rest for now. [17:11] I was reproducing bug 1066173 and now on first boot after installation I'm dropped to grub rescue mode with the message: [17:11] Launchpad bug 1066173 in ubiquity "whole disk install puts grub in wrong place" [High,Confirmed] https://launchpad.net/bugs/1066173 [17:11] error: file '/boot/grub/i386-pc/normal.mod' not found [17:11] what does it mean ? [17:12] Just an extension of the same "wrong place" thing [17:12] The GRUB core has a prefix that doesn't correspond to where GRUB modules are actually to be found [17:13] but the external drive is plugged. I only removed the usb stick [17:13] jibel: can you mount the hard-drive and retrieve the logs? /var/log/syslog & /var/log/installer/* from the hard drives? [17:13] sure [17:14] if I find a usb port on a working machine with enough power :) [17:14] ah... /me does everything in VMs so it would be just a few CLI commands to mount it ;-) [17:20] https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1066173/+attachment/3399107/+files/_var_log_installer_2.12.11_LP1066173_01.tgz [17:20] Launchpad bug 1066173 in ubiquity "whole disk install puts grub in wrong place" [High,Confirmed]