[10:36] <stgraber> ubiquity doesn't work in alpha-3 candidate :(
[10:36] <davmor2> help please intrepid A3 testing in progress and ubquity fails at 87% but exits with no bug I've run ubiquity --debug where does it store it's debug files?
[10:38] <stgraber> davmor2: /var/log/installer/debug ?
[10:41] <davmor2> http://paste.ubuntu.com/29560/
[10:43] <stgraber> nope, that's /var/log/debug, the interesting one is /var/log/installer/debug
[10:44] <davmor2> bugger
[10:47] <stgraber> yeah, I have a nice crash :)
[10:51] <davmor2> stgraber: try http://www.davmor2.co.uk/ubiq-debug.txt
[10:52] <stgraber> I have the same, I'm opening a bug on LP
[10:52] <davmor2> cool
[10:52] <davmor2> are you going to add your copy of the file?
[10:53] <stgraber> yes
[10:55] <stgraber> davmor2: bug 251089
[10:55] <stgraber> davmor2: please confirm
[12:26] <CIA-12> ubiquity: cjwatson * r2724 ubiquity/ (3 files in 2 dirs):
[12:26] <CIA-12> ubiquity: Preseed netcfg/dhcp_ntp_servers from install component rather than
[12:26] <CIA-12> ubiquity: clock-setup, since the latter doesn't have debconf database access at
[12:26] <CIA-12> ubiquity: the right time (LP: #251089).
[12:32] <mons88> Please help , am i able to pose a question re. successful net install but keyboard issue as described here, http://ubuntuforums.org/showthread.php?t=818390
[12:32] <mons88> ?
[12:35] <cjwatson> console-setup/layoutcode should be en not en_US
[12:36] <cjwatson> I've no idea whether that's actually your problem - I'm off sick today, but would be happy to help tomorrow if I'm better then
[12:36] <cjwatson> console-common is completely wrong in modern Ubuntu
[12:36] <cjwatson> we don't support it any more
[12:37] <cjwatson> oh, er, console-setup/layoutcode should be us, not en or en_US :-)
[12:37] <cjwatson> en_US isn't a defined keyboard name so goodness only knows what you'll get
[12:40] <mons88> okay thanks alot for the response, I'll try 'us' again tomorrow, this post mentions it worked for hardy, actually I'm sure I tried us originally
[12:41] <cjwatson> if you got 'd-i console-setup/layoutcode string en_US' from some documentation, I'd like to know where that documentation is so that it can be hit over the head^W^W^W^Wfixed
[12:42] <CIA-12> ubiquity: jriddell * r2725 trunk/ (debian/changelog ubiquity/components/language.py):
[12:42] <CIA-12> ubiquity: * language.py: Change string to unicode, fixes crash when using KDE
[12:42] <CIA-12> ubiquity:  frontend, closes LP: #251097
[12:43] <mons88> actually as per that post, I'm using 'd-i console-setup/layoutcode string us'
[12:44] <cjwatson> are you kai4785?
[12:45] <cjwatson> anyway, sorry, I'm going back to bed, check back tomorrow and I can try to help you
[12:45] <mons88> No, he successfully got around this using kickseed, I tried using a ks.cfg
[12:45] <mons88> no worries , thanks
[13:33] <CIA-12> ubiquity: jriddell * r2726 trunk/ (debian/changelog ubiquity/frontend/kde_ui.py): kde_ui.py: comment out dcop code
[15:32] <CIA-12> ubiquity: evand * r2727 ubiquity/ (18 files in 8 dirs): Bump to 1.9.5
[17:27] <CIA-12> ubiquity: jriddell * r2728 trunk/ (debian/changelog ubiquity/frontend/kde_ui.py): add set_hostname method
[17:33] <CIA-12> ubiquity: jriddell * r2729 trunk/ (bin/ubiquity-wrapper debian/changelog): temporarily force sudo until we work out why kdesudo stops it passin partitioning stage, bug 251203
[17:48] <CIA-12> ubiquity: evand * r2730 ubiquity/ (d-i/manifest debian/changelog):
[17:48] <CIA-12> ubiquity: Automatic update of included source packages: user-setup
[17:48] <CIA-12> ubiquity: 1.20ubuntu3.
[17:48] <CIA-12> oem-config: cjwatson * r489 oem-config/ (44 files in 10 dirs): Upgrade to current autotools in Intrepid, including libtool 2.2.
[17:51] <CIA-12> oem-config: cjwatson * r490 oem-config/ (configure configure.ac): bump to 1.43
[17:52] <CIA-12> oem-config: cjwatson * r491 oem-config/lib/components/language.py: port Jonathan's language component fix from ubiquity r2725
[18:01] <CIA-12> ubiquity: evand * r2731 ubiquity/debian/changelog: releasing version 1.9.5
[18:04] <mdz> evand: did you happen to read my install test report on -devel@?
[18:04] <evand> mdz: reading now
[18:05] <mdz> evand: there's a ubiquity bug in there which was fatal but doesn't look too complex
[18:05] <mdz> evand: but at the moment I'm working on the kernel issue.  I'm able to reproduce it
[18:05] <mdz> 2 out of 2 attempts, the system hangs during the final stages of ubiquity
[18:06] <mdz> I'm trying to narrow it down to a more useful test case
[18:06] <mdz> and am wondering if you have any guesses about what might be triggering it
[18:06] <mdz> it looks vaguely aufs related so far
[18:06] <mdz> I'm trying to get a trace now, but it takes forever to use the install process as a test case, which is why I want to narrow it down
[18:07] <evand> hrm
[18:08] <mdz> can you think of anything interesting that ubiquity does with the aufs filesystem toward the end (after the copy is finished)?
[18:08] <mdz> it might be when it's copying the installation logs
[18:08] <mdz> but they don't make it across to the target, so I don't have much to go on
[18:09] <evand> it hard locks?
[18:09] <evand> I don't suppose you have a serial cable or vmware (not sure how to create that setup in kvm)?
[18:11] <mdz> evand: it's a laptop, so no serial
[18:11] <mdz> I can't even get intrepid's kvm to boot the iso at the moment
[18:11] <mdz> evand: I'm trying it with a klogd running in /target to try to capture the crash
[18:12] <mdz> but this takes forever with such a long test case
[18:13] <mdz> evand: can you give me a log from a successful installation with current ubiquity, so I can see which steps come after the point where it hangs for me?
[18:14] <evand> mdz: Sure, but bare with me for a few moments as I'll have to set up vmware to do it (kvm is failing for me with the intrepid kernel).
[18:15] <mdz> evand: even a hardy one would do if you have one handy
[18:15] <mdz> s/do/help/
[18:15] <evand> ah, will do
[18:24] <mdz> evand: also, I noticed (as noted in the report) that apport didn't trigger when ubiquity crashed.  do you know why that is?
[18:25] <evand> offhand no, but I've made a note to look into it
[18:32] <mdz> evand: the crash is happening when dpkg is running, removing packages
[18:32] <mdz> I've got a digital photo of the call trace now
[18:33] <evand> ok
[19:08] <evand> http://evalicious.com/tmp/syslog-8.04-20080723.txt curiously enough, the debug log didn't get copied over.  That or I mistyped 'debug-ubiquity'.
[19:09] <CIA-12> ubiquity: evand * r2732 ubiquity/ (configure configure.ac): Bump to 1.9.6
[19:09] <CIA-12> ubiquity: evand * r2733 ubiquity/debian/ (changelog control): Add a dependency on intltool to fix a build failure.
[19:13] <evand> hrm, that was a mistake.
[20:09] <CIA-12> ubiquity: evand * r2734 ubiquity/debian/changelog: releasing version 1.9.6
[20:09] <evand> I'll fix that up after the alpha is out the door.  I didn't want to hold it up any longer.
[20:36] <CIA-12> ubiquity: evand * r2735 ubiquity/ (configure configure.ac): Bump to 1.9.7
[20:48] <CIA-12> ubiquity: evand * r2736 ubiquity/ (5 files in 3 dirs):
[20:48] <CIA-12> ubiquity: Properly fix intltool dependency. Remove old copies of intltool
[20:48] <CIA-12> ubiquity: scripts.