[01:12] <persia> cjwatson: Reading your updates to bug #538536 : is this in a state where I should proceed with install, or do you want me to keep the system uninstalled for a couple more weeks?
[01:12] <cjwatson> persia: I think it's worth you going ahead with a test
[01:15] <persia> OK :)  If it succeeds, I'd like to leave the system installed : do you feel confident enough with your simulation that this is a safe path?
[01:15] <persia> (otherwise I'll do a test and leave it uninstalled)
[01:18] <cjwatson> I think that should be safe, assuming it works at all
[01:19] <cjwatson> partitioning doesn't usually tend to leave subtle hidden traps around for later
[01:19] <cjwatson> if there are traps, they're big and pointy
[01:21] <persia> heh.  Yeah.  I was more concerned about subtle stuff in the simulation.  I'll run a test as soon as my cdimage mirror has 2.2-1ubuntu3 in the server image.
[01:22] <cjwatson> what I'm not certain about, and can't easily be, is whether the result will boot
[01:22] <cjwatson> we're using grub-pc rather than any of the -efi variants - and if you use one of the -efi variants, AFAIK you need to do somewhat different partitioning
[01:23] <cjwatson> so I suspect that the installer would need to be explicitly prepared for that somehow
[01:23] <persia> Is the use of an -efi variant expected to be required for this sort of hardware?
[01:23] <cjwatson> grub-pc should work, but you might need something EFI-ish to chain to it, like refit
[01:23] <cjwatson> or you might just be able to hold down Option at boot and have it work
[01:24] <cjwatson> the exact details have probably changed a bit since I was last deeply involved with Apple kit
[01:24] <persia> Hrm.  I was planning to leave this system entirely headless.  I guess I'll plan on keeping it not installed, unless it just works flawlessly.
[01:24] <cjwatson> anyway, I've been meaning to go to bed for about 40 minutes, so I shall go :)
[01:25] <cjwatson> night
[01:25] <persia> Night :)
[10:07] <CIA-3> usb-creator: evand * r277 usb-creator/ (bin/usb-creator-helper debian/changelog): Don't write usb-creator-helper's log to /root (LP: #461064).
[11:28] <CIA-3> partman-base: cjwatson * r192 ubuntu/parted_server.c: abstract partition creation constraints
[11:59] <persia> cjwatson: The 20100315 Server image was unable to handle manual LVM, but successfully completed with guided LVM.  As you predicted, the result didn't boot.  Shall I add the logs to a new bug, or to the old one?
[12:01] <cjwatson> your old one is fine
[12:02] <cjwatson> I probably won't get further for beta-1 at this point
[12:03] <persia> No worries.  I'm fairly sure I can get the system to be a basic sbuild host with what I have an grub-efi.  Due to other circumstances, I'm not going to be able to set it up properly until right around Beta 2 release anyway, so I should be able to do another end-to-end run for that.
[12:04] <persia> And because of this, running more installs next week (but not this coming weekend) shouldn't interrupt much.
[13:16] <CIA-3> ubiquity: cjwatson * r3931 ubiquity/ (debian/changelog ubiquity/components/ubi-language.py):
[13:16] <CIA-3> ubiquity: * KDE frontend:
[13:16] <CIA-3> ubiquity:  - Honour ubiquity/show_alpha_warning.
[13:43] <CIA-3> ubiquity: cjwatson * r3932 ubiquity/ (debian/changelog ubiquity/components/ubi-partman.py):
[13:43] <CIA-3> ubiquity: * Noninteractive frontend:
[13:43] <CIA-3> ubiquity:  - Fix up plugin problems in the partman component (LP: #539493).
[13:44] <cjwatson> ev: I'm worried about the fact that we're seeing tracebacks from the noninteractive frontend from people who never asked for it.  How would you feel about http://paste.ubuntu.com/396177/ ?
[13:47] <ev> cjwatson: I think that's fine, but maybe check with Mario as I believe he added the original code
[13:47] <cjwatson> hmm, not sure we have time to wait for Mario to get up
[13:47] <ev> if memory serves it was to work the problem now solved by your failsafe X work
[13:47] <ev> I'd just upload it then, given the above
[13:48] <cjwatson> superm1: ^- can you review the above post-hoc?  I think that noninteractive should only be provided if you explicitly ask for it
[13:48] <CIA-3> ubiquity: cjwatson * r3933 ubiquity/debian/ (changelog ubiquity.ubiquity.upstart):
[13:48] <CIA-3> ubiquity: Never start the noninteractive frontend unless it was explicitly
[13:48] <CIA-3> ubiquity: requested.
[13:49] <superm1> cjwatson, the worry was that if a monitor isn't plugged in in the factory, X doesn't start, so automatic doesn't work
[13:50] <cjwatson> superm1: the fact that noninteractive is being started on innocent users' machines TERRIFIES ME
[13:50] <cjwatson> yes, I know it generally doesn't do much because it isn't preseeded, but even so
[13:51] <superm1> cjwatson, understood, perhaps only if automatic-ubiquity was passed do the noninteractive fallback then, if it's just only or maybe-ubiquity mode don't have a fallback?
[13:51] <cjwatson> and we get all sorts of weird crash reports as a result of this.  We need something better
[13:51] <cjwatson> it would be OK in automatic mode
[13:52] <ev> wubi runs in automatic mode
[13:52] <ev> but I suppose that's still okay
[13:52] <cjwatson> yeah, I think so, it's preseeded what it wants to do
[13:54] <cjwatson> ok, thanks, done
[13:54] <CIA-3> ubiquity: cjwatson * r3934 ubiquity/debian/ (changelog ubiquity.ubiquity.upstart): Only fall through to the noninteractive frontend in automatic mode.
[13:58] <CIA-3> ubiquity: cjwatson * r3935 ubiquity/debian/changelog: better bug number
[14:01] <cjwatson> *blink* bug 539353 has an RTF file attached
[14:01] <cjwatson> that's a blast from the past
[14:02] <soren> I wonder what possesses people to do something like that.
[14:11] <persia> copy&paste into a word processor?
[14:11] <CIA-3> ubiquity: cjwatson * r3936 ubiquity/debian/changelog: releasing version 2.2.1
[14:13] <soren> persia: Yes.
[14:14] <persia> soren: In many environments in the past, real text editors are hidden from the users.  I believe this is still true in recent versions of Mac OS X.
[14:15] <persia> So users develop habits that continue into other environments.
[14:22]  * soren admits to have had a brief period where he exclusively jotted down notes in LaTeX
[14:46] <highvoltage> Hi!
[14:46] <highvoltage> I have a zenity dialog I'd like to be displayed close to the end of the installation that will perform some additional configuration in the target system
[14:47] <highvoltage> I put it in /usr/lib/ubiquity/target-config, it's number is the last in the bunch that's there and it's excecutable, I'm not sure if that's the best place to put it but it seems so
[14:48] <highvoltage> ubiquity doesn't pop up the dialog though, it just seems to hang while doing the "Configuring target system..." stage, the script runs fine if executed seperately
[14:49] <highvoltage> any advice on how to get it working properly would be greatly appreciated!
[15:57] <CIA-3> usb-creator: evand * r278 usb-creator/ (5 files in 5 dirs):
[15:57] <CIA-3> usb-creator: * Provide a format confirmation dialog (LP: #443330).
[15:57] <CIA-3> usb-creator: * Error out of formatting if we're unable to unmount all of the
[15:57] <CIA-3> usb-creator:  partitions (LP: #507420).
[15:57] <CIA-3> usb-creator: * Provide feedback via a spinning cursor and disabled format button
[15:57] <CIA-3> usb-creator:  while formatting (LP: #457737).
[15:57] <CIA-3> usb-creator: * Only call gtk.main_quit if we're in a mainloop.
[16:10] <CIA-3> ubiquity: cjwatson * r3937 ubiquity/ (bin/ubiquity-dm debian/changelog):
[16:10] <CIA-3> ubiquity: Quit plymouth if it doesn't have an active VT, rather than trying to
[16:10] <CIA-3> ubiquity: reuse the VT it doesn't have, which results in X running on VT1.
[16:12] <ev> ah, I was wondering why that was happening
[16:13] <ev> interesting
[16:14] <ev> the kde frontend is using nearly 100% cpu
[16:30] <CIA-3> ubiquity: cjwatson * r3938 ubiquity/debian/changelog: releasing version 2.2.2
[18:36] <exlt> I have dug thru the last week's irc logs and ref'ed partitioning bugs - there is something wildly broken with partman recently..  been using a very simple partman-auto/expert_recipe for months almost identical to the example on https://help.ubuntu.com/9.10/installation-guide/i386/preseed-contents.html
[18:37] <exlt> errors out with cannot write partitions outside of device (or very similar)
[18:38] <exlt> removed all partitioning preseeding and picked default "guided - use entire disk"
[18:38] <cjwatson> can you please file a new bug with your logs (syslog and partman) attached?
[18:38] <exlt> partitions suggested are...interesting
[18:38] <exlt> logs are not exactly available since it cannot install
[18:38] <cjwatson> sure they are
[18:39] <cjwatson> go back to the main menu and select "Save debug logs"
[18:39] <exlt> ah, that's right - sorry forgot
[18:39] <cjwatson> or, switch to alt-f2 and run 'anna-install openssh-client-udeb' to get yourself scp
[18:40] <cjwatson> there are known problems, but I'll need to analyse your logs in order to determine whether what you're seeing is related to anything else
[18:40] <exlt> but even the suggested defaults of (completely blank 500G drive) http://12.am/tmp/lucid_partman-hmmm.png - that's quite unexpected
[18:40] <cjwatson> yes
[18:40] <cjwatson> but I would prefer to debug logs rather than screenshots. :-)
[18:41] <exlt> ok - could you suggest a package to file under?  partman-(something)  ;)
[18:41] <cjwatson> partman-base
[18:41] <exlt> perfect
[18:41] <exlt> thanks, cjwatson - hate to keep bugging you  :)
[18:42] <cjwatson> that's ok, I'd rather know about problems
[18:54] <sbeattie> cjwatson: bug 539774 is probably the same thing.
[18:55] <sbeattie> (bug report has partman logs attached)
[18:56] <cjwatson> possibly.
[18:56] <cjwatson> elmo reported something similar-sounding too.
[18:56] <exlt> start of first partition at 2049 was what I saw yesterday, too
[19:01] <cjwatson> exlt: as in LBA 2049?
[19:01] <cjwatson> that's intentional
[19:01] <cjwatson> starting at 16GB+ is a somewhat different matter, and is not intentional
[19:02] <cjwatson> starting at 1MiB improves compatibility with various hardware and OSes
[19:02] <exlt> no - same as that bug has - cyl 2049 and 16.8G free before first part
[19:04] <cjwatson> oh, *cylinder* 2049
[19:04] <cjwatson> helps to specify your units ;-)
[19:05] <cjwatson> even if they are crazy obsolete ones like cylinders ;-)
[19:05]  * cjwatson wonders if it's possible to query blkid's idea of topology from the command line
[19:07] <exlt> I could be wrong on cyl - whatever the "Start" value is in fdisk -l - cyl, sector..
[19:08] <exlt> it is cylinders
[19:09] <exlt> perhaps that intentional start after the first 2048 cylinders is the bug
[19:14] <cjwatson> no, you have misstated what I said
[19:14] <cjwatson> I never said that there was an intentional start after 2048 cylinders
[19:32] <cjwatson> I've reproduced the weird partitioning alignment in kvm, so should be able to fix it
[19:33] <cjwatson> the size of the disk matters - my usual test size of 3GB exhibited 1MiB alignment, but 200GB exhibited 16GiB alignment
[19:37] <sbeattie> cjwatson: hrm, but why did it not align everything; e.g. why was 2GB I specified for swap created as gap *after* the 16GB swap space it created?
[19:39] <cjwatson> who knows, it's clearly screwed
[19:45] <exlt> cjwatson: #539822 has my logs attached
[19:50] <cjwatson> sbeattie: it could easily be a difference between primary and logical partitions or something - at this point I'm strongly suspecting a bug inside libparted
[19:50] <cjwatson> exlt: thanks, since I've reproduced it I should be OK from here
[19:51] <exlt> :)