[01:26] Just out of curiosity, why do we have th camera module in ubiquity/oem-config? lightdm doesn't appear to use it. [01:26] Ubuntu doesn't support face recognition as an auth method? :) [01:28] Not that I know of (cool as it may be). [01:31] GrueMaster: can you think of any other difficult questions? [01:31] :) [01:31] Always. [01:32] But most of them can't be repeated in public. :P [01:32] dmesg [01:33] oops [01:33] heh [01:51] ubiquity: cjwatson * r5153 trunk/ (4 files in 3 dirs): [01:51] ubiquity: Behave a little more usefully when running over ssh with X forwarding [01:51] ubiquity: such that ubiquity is unable to talk to NetworkManager. This [01:51] ubiquity: configuration isn't actually supported, but is occasionally useful for [01:51] ubiquity: debugging so it helps to be able to start ubiquity at the very least. [12:09] partman-auto: cjwatson * r620 ubuntu/ (3 files in 3 dirs): [12:09] partman-auto: Close mount's fds 6 and 7 when running within an [12:09] partman-auto: open_dialog/close_dialog pair, so that if ntfs-3g is in use it doesn't [12:09] partman-auto: keep those fds open in the background and cause havoc (LP: #912031). [14:44] ubiquity: cjwatson * r5154 trunk/ (debian/changelog scripts/plugininstall.py): [14:44] ubiquity: Configure the target system to disable installation of Recommends if [14:44] ubiquity: base-installer/install-recommends is preseeded to false (LP: #918401). [14:48] partman-auto: cjwatson * r621 ubuntu/debian/changelog: releasing version 93ubuntu19 [14:52] ubiquity: cjwatson * r5155 trunk/ (d-i/manifest debian/changelog): [14:52] ubiquity: Automatic update of included source packages: flash-kernel 2.28ubuntu39, [14:52] ubiquity: partman-auto 93ubuntu19. [14:57] ubiquity: cjwatson * r5156 trunk/debian/changelog: releasing version 2.9.16 [17:04] stgraber: you'd mentioned that "EXT2-fs (loop1): error: ext2_lookup: deleted inode referenced: 255209" were likely hardware errors for people using wubi correct? [17:05] bdmurray: indeed, the key part here being the (loop1) where loop0 is the squashfs from the install media and loop1 is the disk image on the ntfs partition [17:06] bdmurray: and the error could be from either: hardware => ntfs => ext2 [17:06] I'd think most likely ntfs, could be hardware and unlikely to be ext2 (though definitely not impossible) [17:07] okay, thanks [17:42] Has anybody looked at unetbootin and how it setups up the installer? [18:06] I ask because there might be a relationship between unetbootin and ext2_lookup errors