[12:22] cjwatson, evand, ping. [12:22] https://bugs.launchpad.net/dell/+bug/135602 [12:22] marked as 'invalid', but I see this bug in today's daily. [12:24] hmm... Ok, I see that it is closed as a dup of: https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/23537 [12:24] which is 'fix released' [12:25] but question remains: when will this hit the daily builds? === cjwatson_ [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk] has joined #ubuntu-installer [12:25] cjwatson, --^ [12:26] cjwatson_,, did you see my last couple sentences? [12:27] nope [12:27] ok... [12:27] https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/23537 [12:27] which is 'fix released' [12:27] yep [12:27] I dont see it fixed in today's daily [12:28] and I tried your wget manifest| grep trick [12:28] and dont see oem-config listed... :( [12:28] I'll have to try it out [12:28] it's not in the live image, grep for it in .list [12:28] /pool/main/o/oem-config/oem-config_1.21_i386.deb [12:29] which looks to me like it should be fixed... [12:29] should be [12:29] as lp# shows closed in 1.20 [12:29] but... [12:29] when I tried it out. I installed all language packs on my list and chose 'spanish' as the language [12:29] and the rest of the screens were still in english [12:30] (I speak spanish pretty well, so it is easy for me to test...) [12:32] should I re-open the lp#? [12:32] let me try it [12:32] I have to go for tonight in a min [12:32] it's 23:30 here, if I don't respond or fix it or something, sure, reopen it [12:32] ok. [12:33] british time? [12:34] yes [12:34] ok. Well, have a great weekend. [12:35] send me an email if you need anything. [12:35] ok [12:35] I have this issue and iirc one other one that are important to me to get the Dell install going [12:35] https://bugs.launchpad.net/dell/+bug/149582 [12:35] is the other critical one. [12:35] for the installer [12:36] yeah, you mentioned that, I'll look at the same time [12:36] If you need anything from me, I'll be checking email this weekend. I know you are in the last few days worth of changes before the release. [12:36] I have a lingering suspicion it's because you're preseeding the username and full name when that's not necessary [12:36] (or shouldn't be anyway) [12:36] but I can't think of a reason why that would actually break this [12:36] ok. If it isnt needed, I can just as easily take it out. [12:36] just remove the value, or the entire line? [12:37] leave it there for now [12:37] maybe it's a generic bug, in which case I can squash it [12:37] ok. [12:38] Spanish is a good test case BTW, because its oem-config translation is complete [12:38] the translation team was nice and speedy [12:38] Well, I'm going now. Let me know if you need anything from my side. You have my preseed. [12:38] Yeah, [12:38] I'm considering changing my desktop to spanish by default [12:38] to get more practise [12:39] just noticed testing today that there werent very many untranslated strings around the desktop at all [12:39] (as compared to, say, chinese) [12:39] ttfn. === xivulon [n=ago@87-194-85-156.bethere.co.uk] has joined #ubuntu-installer [01:17] cjwatson,evand I am out of ideas with the mkfs bug [01:18] to make a long story short, if I pause at the end of autopartition-loop and run strace mkfs.ext3 /dev/loop2 it works [01:18] if run mkfs without strace it doesn't [01:18] any hint of what I may try? [02:12] xivulon: sorry, I have no bright ideas, sounds like a race but who knows [02:13] ubiquity: cjwatson * r2324 ubiquity/ (debian/changelog scripts/install.py): [02:13] ubiquity: * Remove excessive blank lines in GDM and KDM configuration files in OEM [02:13] ubiquity: mode. [02:29] cjwatson is the update of ntfs-3g going to happen? maybe that can address it (hmm might test that) === cjwatson_ [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk] has joined #ubuntu-installer === xivulon testing ntfs-3g 1.1913 === booxter [n=booxter@80.94.230.57] has joined #ubuntu-installer === booxter [n=booxter@80.94.230.57] has joined #ubuntu-installer === booxter [n=booxter@80.94.230.57] has joined #ubuntu-installer === booxter [n=booxter@80.94.230.57] has joined #ubuntu-installer === booxter [n=booxter@80.94.230.57] has joined #ubuntu-installer === xivulon [n=ago@87-194-85-156.bethere.co.uk] has left #ubuntu-installer [] === booxter_ [n=booxter@80.94.230.16] has joined #ubuntu-installer === booxter__ [n=booxter@80.94.230.121] has joined #ubuntu-installer === booxter [n=booxter@80.94.230.121] has joined #ubuntu-installer === booxter [n=booxter@80.94.230.44] has joined #ubuntu-installer === J-Georg_ [n=Frater@dsl59-103.uninet.ee] has joined #ubuntu-installer [01:36] Morning. [01:38] I have a grub-related problem installing Ubuntu, could anyone help me a little? [01:38] oem-config: cjwatson * r365 oem-config/ (debian/changelog lib/frontend/gtk_ui.py): [01:38] oem-config: * GTK frontend: [01:38] oem-config: - Make sure the next button remains the default widget despite being [01:38] oem-config: hidden and re-shown. [01:39] J-Georg_: it's a weekend and I was mostly planning to do other things; if you explain your problem and hang around for a bit, I or somebody may be able to [01:40] Ok, the installation just fails to grub-install (hd0). The root partition is an ext3 at /dev/sda5 and if I chroot to /target and try to do it by hand it fails with "/boot/grub/stage1 not read correctly." [01:41] I had to create menu.lst by myself as it didn't exist. [01:41] I was browsing the forums and checked fstab and mtab as suggested but they look fine to me. [01:41] just one disk? [01:42] Yes. [01:42] device.map looks ok as well... [01:44] normally that error is because fstab and menu.lst are out of sync (and beware that grub counts partition numbers from zero not from one) [01:45] but it's possible that it could also be because grub's internal low-level read-stuff-from-the-disk code is breaking [01:45] which is liable to be beyond me :-/ [01:45] Right... [01:45] I'll take another look at fstab and menu.lst [01:46] I'm sorry that may not be a very satisfying answer [01:46] in extremis, you could try installing lilo [01:46] ubiquity: cjwatson * r2325 ubiquity/ (debian/changelog ubiquity/frontend/gtk_ui.py): [01:46] ubiquity: * GTK frontend: [01:46] ubiquity: - Make sure the next button remains the default widget despite being [01:46] ubiquity: hidden and re-shown. [01:47] In fstab /dev/sda5 was identified by UUID. Changed it to /dev/sda5, it didn't help. [01:47] In menu.lst root is set to (hd0,4) [01:48] if you want to try to dig into exactly what's failing, there should be log and image files left over from grub-install's attempts to read back stage1 lying around in /tmp [01:49] it copies the files to /boot/grub/ and then tries to read them back using the 'dump' command in the grub shell, then does a binary compare to ensure they're the same [01:49] I trust you don't have a separate /boot? [01:49] No, it's on the same sda5 [01:49] the other problem you *could* be having is that maybe you have a sufficiently wacky BIOS that grub is having trouble reading from the logical partition [01:50] might be worth trying to put a small /boot on a primary partition if possible [01:50] also, put /boot near the start of the disk [01:50] depending on the vintage and bugginess of the BIOS, it may have trouble reading from later in the disk [01:51] Ok. Now I can see in the tmp file that: [01:51] Error 17: Cannot mount selected partition [01:51] As a result to dump command. [01:52] 17 : Cannot mount selected partition [01:52] This error is returned if the partition requested exists, but the [01:52] filesystem type cannot be recognized by GRUB. [01:52] interesting [01:52] Wait a little... [01:52] let me check fdisk output [01:53] /dev/sda5 xxxx xxxxx xxxxxxxx 7 HPFS/NTFS [01:53] Shouldn't it be Linux? [01:54] Or doesn't it matter if fstab says it's ext3? [01:55] that does matter [01:56] Well, changing id [01:56] or at least it certainly could matter, ext2fs_mount does check that [01:56] interesting how it got that way - I'd like to see your installation logs [01:57] (/var/log/syslog and /var/log/partman if you're still in the installer) [01:57] if you could try to copy those out before you finish the installation and reboot, I'd appreciate it [01:57] Already rebooted... [01:57] Sry. [01:57] damn [01:57] are they in /var/log/installer/ ? [01:58] I guess you've probably trashed them now so I won't be able to figure out why this happened :-/ [01:58] if you were using the alternate installer, there's a chance they might still be there [01:58] Well, the partitioning was done in Windows. [01:58] Hence the NTFS setting. [01:58] ah [01:59] Ubuntu installer didn't complain about it and created ext3 happily on it. [01:59] could you file a bug on partman-base? (that may not be the right package but it's a start) [01:59] But failed at the grub stage. [01:59] and explain the situation [01:59] Ok. [01:59] were you using the alternate install CD or the desktop CD? [01:59] feel free to just paste this whole IRC log into the bug [01:59] Desktop CD. [01:59] ok [02:00] Ok, trying to install again now with right ID. [02:00] It's AMD 64 install cd. [02:00] that shouldn't matter [02:00] Ok. [02:01] Thanks for guidance, anyway :) [02:02] The hint about tmp files was very helpful :) [02:06] should probably copy the grub log output to the syslog [02:06] this is weird, it definitely tries to set the partition id [02:08] J-Georg_: did you use automatic partitioning? [02:08] I guess not if you did the partitioning in Windows [02:08] J-Georg_: perhaps you could describe to the best of your memory exactly what you did in the partitioner [02:09] Used manual partitioning. [02:16] J-Georg_: any more detail? [02:16] oem-config: cjwatson * r366 oem-config/debian/ (59 files in 2 dirs): * Update translations from Rosetta. [02:17] oem-config: cjwatson * r367 oem-config/ (d-i/manifest debian/changelog): [02:17] oem-config: * Automatic update of included source packages: user-setup 1.14ubuntu4 [02:17] oem-config: (LP: #149582). [02:20] oem-config: cjwatson * r368 oem-config/debian/changelog: releasing version 1.22 [02:26] Right... [02:27] It still doesn't work... [02:27] Wait a little... [02:27] I changed the partition Id but it's again HPFS/NTFS... [02:27] Weird... [02:28] remember to save the logs this time, please [02:28] I'm off to do other things for a while (comment about weekend above :-)) [02:28] Ok, thanks anyway. [02:29] There's only version file in /var/log/installer [02:35] /var/log/syslog and /var/log/partman are the ones you want before reboot [02:35] they're only copied into /var/log/installer/ right at the end [02:42] Ok. === J-Georg_ [n=Frater@dsl59-103.uninet.ee] has left #ubuntu-installer [] === cjwatson_ [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk] has joined #ubuntu-installer === cjwatson [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk] has joined #ubuntu-installer === stgraber [n=stgraber@dakara.stgraber.org] has joined #ubuntu-installer === cr3 [n=cr3@bas5-montreal02-1167965450.dsl.bell.ca] has joined #ubuntu-installer === xivulon [n=ago@87-194-85-156.bethere.co.uk] has joined #ubuntu-installer [09:33] cjwatson, the only way to go around the mkfs issue is to run mkfs on the file and not on the loopdevice (no need to detach the loopdevice) [09:33] how difficult would that be to override the current partman behaviour? === cr3 [n=cr3@bas5-montreal02-1167965450.dsl.bell.ca] has joined #ubuntu-installer === cjwatson [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk] has joined #ubuntu-installer === arnekolja [i=Miranda@dslc-082-082-168-084.pools.arcor-ip.net] has joined #ubuntu-installer