[00:01]  * shtylman needs to get onto the kubuntu slideshow...really want that to happen :)
[00:44] <shtylman> cjwatson: I have been requested to pull out the stylesheet stuff I did for the installer into another package (kubuntu has another app that wants to use it for firefox installer)... can I just add a new .install file and package to trunk? and make ubiquity kde depend on it? or is there another process because this will create a new package?
[00:44] <shtylman> the package name will be something like kubuntu-installer-style
[00:46] <shtylman> ... or anyone else that might know ^
[00:52] <cjwatson> should be possible to just add a new binary package to ubiquity with relatively little trouble, but after alpha 5 please
[00:52] <shtylman> cjwatson: noted :)
[03:05] <shtylman> cjwatson: see the patch for dmraid grub-installer? in the debbugs comments?
[09:17] <CIA-33> debian-installer: cjwatson * r1147 ubuntu/debian/changelog: releasing version 20081029ubuntu57
[10:56] <evand> cjwatson: you scared me with re-enabling encrypted home.  I thought that happened by accident via another change and that we'd have to respin the CDs :)
[10:56] <CIA-33> ubiquity: cjwatson * r3419 ubiquity/ (4 files in 3 dirs):
[10:56] <CIA-33> ubiquity: Go back to using /var/log/oem-config.log for oem-config logging; it's
[10:56] <CIA-33> ubiquity: convenient and less confusing to have that in a separate file, rather
[10:56] <CIA-33> ubiquity: than /var/log/installer/debug.
[10:56] <cjwatson> evand: kees asked for it explicitly
[10:57] <evand> awesome!
[10:59] <CIA-33> ubiquity: cjwatson * r3420 ubiquity/ (bin/ubiquity debian/changelog): Be more explicit in logs when ubiquity is being run as oem-config.
[11:00] <davmor2> evand: morning :)
[11:00] <evand> good morning
[11:01] <davmor2> evand: on the firefox slide there is no image just the default icon (black terminal looking thing)
[11:01] <evand> indeed, it's a known issue
[11:01] <CIA-33> ubiquity: cjwatson * r3421 ubiquity/ (debian/changelog ubiquity/casper.py):
[11:01] <CIA-33> ubiquity: Don't warn about missing (as opposed to present-but-unreadable)
[11:01] <CIA-33> ubiquity: /etc/casper.conf.
[11:01] <davmor2> wubi is broken still :(
[11:02] <evand> indeed, I need to evaluate re-enabling wubi for the DVDs today, which will fix the "wubi doesn't work on big usb disks" issue.
[11:02] <davmor2> evand: needs max_iso_size upping so it shows up on unr and kne but xivulon might of done this.  It was however his anniversary so he might not of :)
[11:03] <evand> that won't actually fit it, if I understand the problem correctly
[11:04] <evand> fix*
[11:04] <davmor2> evand: I did a local build here and changed the the 9 at the front for a 20 and it showed up fine
[11:04] <evand> right, but that will make the DVDs show Wubi
[11:05] <davmor2> ah right :)
[11:05] <CIA-33> ubiquity: cjwatson * r3422 ubiquity/ (debian/changelog scripts/install.py): Don't try to copy installation logs when running as oem-config.
[11:06] <davmor2> evand: also on oem end user setup on screen 2 local it is already setup for england but screen 3 keyboard recommends usa keyboard any ideas?
[11:08] <CIA-33> ubiquity: cjwatson * r3423 ubiquity/ (bin/ubiquity debian/changelog): Fix setting of TARGET when ubiquity is running as oem-config.
[11:10] <cjwatson> davmor2: did oem-config print anything in particular to the *screen* after it finished?
[11:11] <davmor2> cjwatson: nothing this time I just get the ubuntu backdrop and nothing else
[11:12] <cjwatson> I was hoping not to have to actually run this through myself, but maybe I have no choice
[11:14] <evand> davmor2: I just tried with the latest daily-live CD and it doesn't happen for me.  Are you sure you didn't proceed to the keyboard selection screen with New York selected first?
[11:15] <davmor2> evand: london, england was tagged by the marker.  That's not to say the text wasn't.  Next time I'll try clicking on the marker again
[11:16] <evand> If you've already proceeded to the language page once, it's going to remember your selection
[11:16] <evand> so I'd suggest trying from a fresh boot
[11:16] <davmor2> evand: I meant next time I install :)
[11:18] <evand> ah, sure
[11:33] <AnAnt> cjwatson: Hello
[11:34] <cjwatson> AnAnt: nagging me every twelve hours is not going to make me look at this bug any faster. :)
[11:35] <AnAnt> cjwatson: actually, most ppl ask to be pinged. sorry if that bothered you
[11:35] <davmor2> cjwatson: would it help if I ran the ubiquity-debug line on reboot from oemuser?
[11:36] <cjwatson> davmor2: debug-ubiquity not ubiquity-debug; but probably not, I don't think the problem is susceptible to debconf debugging
[11:37] <davmor2> cjwatson: I was close :)  just a thought to help you not have to run it :)
[11:39] <davmor2> cjwatson: actually I've just noticed that there is a new cd for this morning so I'll try it out with that cd and see if I can get the apport bug to fire off then
[12:03] <evand> cjwatson: regarding bug 315644, are you suggesting that we use remove_extras to remove all the language packs save the one for the system language?  My thought is that would work, but I want to be sure I'm not heading down a different path from what you had in mind.
[12:07] <cjwatson> yeah
[12:07] <cjwatson> just the obvious bit of code to use at first glance; if it doesn't work then do something else :-)
[12:07] <evand> sure thing :)
[12:20] <davmor2> evand: right new install I'm back at the time zone map.  It currently reads region uk zone uk time and the time is correct.  would you like me to tell you what keyboard it gives me by default or would you like me to click on the map and see if it gives me the right one?
[12:25] <evand> if it is set to UK time zone and you haven't yet gone through the installer, then the next page should show a UK keyboard
[12:25] <davmor2> evand: USA
[12:26] <evand> very odd
[12:26] <davmor2> my oem was setup to uk
[12:27] <evand> ohh, I'm an idiot.  Sorry, my brain isn't fully re-engaged.  I was trying with ubiquity, which isn't going to reproduce your issue.
[12:28] <evand> davmor2: please file a bug.
[12:28] <davmor2> evand: will do
[12:28] <evand> thanks
[12:35] <davmor2> cjwatson_: I used today's iso and now I get a whole new crash :)  bug 423123
[12:40] <davmor2> publicified the bug
[12:46] <cjwatson_> err, meep. I want to know why gdm is involved at all! oem-config is supposed to implement its own display manager
[12:47] <davmor2> cjwatson_: this is after I have run through the end user steps
[12:48] <cjwatson> oh
[12:48] <cjwatson> err, dunno, didn't think we did anything special to gdm
[12:50] <davmor2> cjwatson: I'll just double check that oem user has been removed and I'll try a reboot and see if it behaves properly then
[12:52] <davmor2> cjwatson: right this time oem user has been removed.  I'll try a reboot and let you know if gdm displays properly then
[12:54] <davmor2> cjwatson: Okay so on today's iso it is working after a reboot, so something got fixed :)
[12:55] <davmor2> cjwatson: gdm lists automatic as a user though not sure if it is that, that caused the hiccup
[12:57] <cjwatson> maybe our gdm configuration is buggered somehow
[12:57] <cjwatson> crashing with SIGTRAP is a bit much though
[12:58] <cjwatson> ah, I just worked out why we keep getting branches that remove po/ubiquity.pot
[12:59] <CIA-33> ubiquity: cjwatson * r3424 ubiquity/ (autogen.sh debian/changelog po/Makefile.in.in):
[12:59] <CIA-33> ubiquity: Stop the po directory's mostlyclean target from removing ubiquity.pot.
[12:59] <CIA-33> ubiquity: We want to keep this file in the source package.
[13:43] <evand> nice catch
[13:56] <CIA-33> grub-installer: cjwatson * r804 ubuntu/ (debian/changelog grub-installer):
[13:56] <CIA-33> grub-installer: Preseed grub-pc/install_devices based on grub-installer/bootdev (LP:
[13:56] <CIA-33> grub-installer: #420604).
[13:57] <CIA-33> grub-installer: cjwatson * r805 ubuntu/debian/changelog: releasing version 1.42ubuntu2
[14:01] <CIA-33> ubiquity: cjwatson * r3425 ubiquity/ (bin/ubiquity debian/changelog): Import tempfile, to stop start_debconf crashing.
[14:32] <CIA-33> ubiquity: cjwatson * r3426 ubiquity/ (d-i/manifest debian/changelog):
[14:32] <CIA-33> ubiquity: Automatic update of included source packages: grub-installer
[14:32] <CIA-33> ubiquity: 1.42ubuntu2.
[14:35] <CIA-33> usb-creator: evand * r149 usb-creator/ (7 files in 6 dirs): Show partition table block devices.
[14:37] <CIA-33> ubiquity: cjwatson * r3427 ubiquity/debian/changelog: releasing version 1.99.16
[14:42] <CIA-33> ubiquity: mterry * r3363 plugins/ (16 files in 12 dirs): sync with trunk
[14:59] <evand> cjwatson: ^ do you think you're likely to have a chance to look at that? (FFe bug #419989)
[15:11] <cjwatson> evand: I did
[15:11] <cjwatson> there's a review in the merge proposal
[15:12] <cjwatson> it's fine with me once mterry has finished addressing the comments I made there, but post-a5 of course
[15:12] <mterry> cjwatson, I did address them.  but yeah, post-a5
[15:15] <evand> ah, sorry about that
[15:15] <evand> good deal
[15:35] <davmor2> cjwatson: the fsck thing seems to be down to the time on a superblock.  It reads Superblock last mount time (Wed Sep  2 16:18:53 2009, now = Wed Sep  2 15:31:31 2009) is in the future. I'm assuming this is maybe a utc issue triggering this or something?
[15:36] <davmor2> only on first boot after install, you manually run fsck then ctrl-D and everything is alright again then
[15:37] <davmor2> kirkland: ^ is that the same for you?
[15:38] <cjwatson> probably a recurrence of an old issue
[15:49] <davmor2> cjwatson: cr3 is having the same thing on the automated installs too :(
[15:50] <cjwatson> I think doing anything about it is probably pretty scary at the moment
[15:50] <cjwatson> all that code is hairy as all get-out
[15:50] <cr3> cjwatson: I thought it was related to my preseed of d-i clock-setup/ntp boolean true, but I disabled that and still getting the same problem
[15:51] <cr3> cjwatson: might there be a workaround? perhaps calling hwclock --systohc in the late command or somesuch
[15:52] <cjwatson> can you not simply disregard the failure for now? I'm extremely reluctant to recommend a workaround *before* analysis
[15:55] <cr3> cjwatson: sure, I could disregard for now. if you need information for analysis from particular hardware, let me know
[16:03] <cjwatson> sconklin: what exactly were you looking to find out about grub?
[16:03] <sconklin> I need advice - the installer didn't behave as I expected.
[16:03] <sconklin> I plugged in a USB hard drive, booted the jaunty CD, and installed to the USB drive.
[16:03] <sconklin> what I wanted was a bootable USB drive that I could move to another test system
[16:03] <sconklin> what it appears that I got is an MBR on the internal HD that points to the USB drive,
[16:03] <sconklin> and no MBR on the USB drive - so my system now only boots if the USB drive is attached.
[16:03] <sconklin> I need them isolated from each other
[16:04] <cjwatson> do you want to find out how to get it fixed so that it works automatically in future (I'm not sure; this is a difficult area to get right), or just how to fix it now?
[16:04] <sconklin> I want to fix my system now - if you think it's worth filing a bug, I can do that too.
[16:05] <sconklin> and thanks btw
[16:07] <cjwatson> I suspect there are already a number of bugs about this, sadly
[16:07] <cjwatson> the immediate fix is, assuming your USB drive is /dev/sdb (otherwise substitute appropriately): sudo grub-install /dev/sdb
[16:07] <cjwatson> wewll
[16:07] <sconklin> oh possibly complicating things - The system already had karmic daily installed, the USB drive was installed with Jaunty
[16:08] <cjwatson> you probably actually want to either boot from the USB drive first, or chroot into it and bind-mount /dev /proc /sys
[16:08] <cjwatson> and make sure /boot/grub/device.map is right - hd0 should be the drive you're booting from
[16:09] <cjwatson> then, from your karmic installation, remove the USB drive (just to make sure) and run grub-install /dev/sda
[16:10] <sconklin> ok, thanks - I'll go offline and give that  a try
[16:11] <cjwatson> /boot/grub/device.map is less relevant in karmic
[16:11] <cjwatson> assuming you have grub2, anyway
[16:11] <xivulon> ahaha been reading on the "store" story
[16:11] <xivulon> my vote: "store" -> "world"
[16:26] <kirkland> davmor2: yes, same thing i'm seeing
[16:26] <davmor2> kirkland: okay cool I'm just getting the info that keybuk needs
[16:27] <CIA-33> usb-creator: evand * r150 usb-creator/ (5 files in 5 dirs): Fix persistence once more.
[16:27] <kirkland> davmor2: is there a bug number yet?
[16:29] <rgreening> evand: ping
[16:30] <davmor2> kirkland: I found bug 422869 I'm just checking with keybuk as to whether he wants us to us that or a new one
[16:34] <evand> rgreening: pong
[16:34] <davmor2> kirkland: new bug I'll start it off :)
[16:34] <kirkland> davmor2: great, i'll subscribe and add any info, if necessary
[16:39] <rgreening> heya evand. I see you fixed persistence :)
[16:39] <evand> hopefully
[16:39] <rgreening> ty. I was pulling my hair out trying to fiugre out why it wasn't working :)
[16:40] <evand> testing it is a bit difficult at the moment as kde is not playing nice with my nvidia drivers
[16:40] <evand> or rather, the other way around
[16:40] <rgreening> evand: Im about to test now
[16:40] <evand> cool
[16:40] <rgreening> evand: another thing. Format option doesn't work either. It never creates the vfat FS
[16:41] <rgreening> evand: and using an ISO image doesn't work. It only seems to accect burned CD/DVD.
[16:42] <evand> rgreening: format button> indeed, there's a bug in devicekit (https://bugs.freedesktop.org/show_bug.cgi?id=23541)
[16:42] <rgreening> oh
[16:42] <rgreening> heh
[16:43] <evand> iso> I fixed image writing when using the devicekit backend, I'm about to fix iso writing.
[16:44] <rgreening> awesome. then i can look at re-enabling the "Other" button again :)
[16:44] <rgreening> haha
[16:44] <evand> indeed :)
[16:44] <rgreening> yesterday was my test and break day
[16:44] <rgreening> :)
[16:46] <davmor2> kirkland bug 423247
[16:52] <cjwatson> can we have this on just one channel perhaps - Scott is on #ubuntu-devel
[16:53] <xivulon> evand what do you want to do with DVD support in wubi?
[16:56] <davmor2> kirkland: your issues is that on a server install?
[16:58] <evand> xivulon: I haven't had a chance to look at it today
[16:58] <cjwatson> kirkland is on #ubuntu-devel too, can we move this all there?
[16:59] <evand> xivulon: I hope to tomorrow
[16:59] <kirkland> cjwatson: sure
[16:59] <cjwatson> cross-channel conversations are very confusing
[16:59] <davmor2> cjwatson: missed that :)
[17:12] <rgreening> evand: persistence works now with latest bzr
[17:22] <xivulon> evand, was mostly interested in your opinion
[17:41] <rgreening> evand: CD-ROM entry in source doesn't update on insert/eject in usb-creator-kde/gtk.. thoughts?
[18:18] <superm1> ISO format isn't implemented in usb creator with device kit?
[19:24] <Scott_____> hello
[19:25] <Scott_____> Having some issues with ubuntu, I just installed it, and it seems my drivers must be out of date
[19:26] <Scott_____> how do I update them
[19:54] <joshk> hey, I tried a karmic nightly with my unattended install setup, and it seems to install in the background yet it doesn't display the installer GUI
[19:54] <joshk> this is a change from 9.04
[19:56] <joshk> oh, haha. I got a crash report from ubiquity. would that do it?
[19:57] <joshk> heh, it even reboots itself.. it works properly, it just doesn't LOOK it ;)
[20:14] <davmor2> evand:  you about still?  Why does the partitioner in wubi (on the linux side) get to 128%
[20:23] <davmor2> evand, cjwatson:  Wubi got through the linux install and died at grub on reboot syntax error Incorrect command syntax error Could not find a bootloader configuration syntax error incorrect command syntax error sh: grub>
[21:14] <joshk> aha! alpha4 fixes the bug.
[21:56] <cjwatson> davmor2: that seems like a slightly garbled error message - could you take a photo of the screen or something so I can be sure I have it exactly?
[21:57] <davmor2> cjwatson: It is correct in the bug 2 secs
[21:57] <davmor2> https://bugs.launchpad.net/wubi/+bug/423381
[21:58] <davmor2> the layout there is how it appeared on screen
[22:03] <davmor2> cjwatson: I would of got the logs for you off the ubuntu install but I had no idea how to get it to boot so I could :)
[22:11] <cjwatson> hmm, the string 'syntax error' appears nowhere relevant in current grub2
[22:14] <cjwatson> I'm baffled