=== tjaalton_ is now known as tjaalton === ara_ is now known as ara [15:58] cjwatson: How long do I have to test lp:1180880? I will be building new systems for shipping later this week, and will be able to test it then, but I am busy with other tasks for the next few days. [15:58] Oh, I expect it would be weeks before anyone started prodding you [15:59] It was pushed to proposed on Friday. [16:00] In my former job, I would have tested it within hours of hitting proposed, but the new job has different priorities. :P [16:00] If you want to not end up blocking anyone, then "this week" [16:00] (Assuming the other bugs fixed by the same upload get tested) [16:01] Excellent. I do have some systems to build later this week (Wed or Thu), so planned on testing it then. [16:01] Thanks === ogra_ is now known as ogra [17:25] xnox: could you have a look at bug 1186735? [17:25] Launchpad bug 1186735 in ubiquity (Ubuntu) "disappointing installation crash" [Undecided,New] https://launchpad.net/bugs/1186735 [17:26] From what I can tell it looks like the installer fails to get some information from the archive but carries on with the install and then crashes [17:28] I found some similar ones too like bug 1186651 and bug 1186637 [17:28] Launchpad bug 1186651 in ubiquity (Ubuntu) "13.04 install" [Undecided,New] https://launchpad.net/bugs/1186651 [17:28] Launchpad bug 1186637 in ubiquity (Ubuntu) "eu nao consegui instalr deu erro " [Undecided,Incomplete] https://launchpad.net/bugs/1186637 [17:31] bdmurray: your analysis looks correct. It did download sources/packages/translations, but they were all invalid (I am guessing captive WiFi portal?! or proxy redirect/login page), which resulted in invalid apt-cache status on disk, which blows up later. [17:32] xnox: I see some unable to connects - Unable to connect to gb.archive.ubuntu.com:http: [IP: 198.18.1.32 80] [17:33] well, if the cache is invalid (regardless how we got there), we should just copy the valid one from the cdimage (i hope we have one there). [17:35] xnox: is there already a bug tracking that? [19:24] can you do a test once they input the wifi network to see if they're in a captive portal/proxy and spawn out a gtk webkit or FF in that scenario? [21:22] superm1: we already do of the sorts test. We check the md5sum of the http://start.ubuntu.com/connectivity-check.html [21:22] and if that doesn't match, we assume we do not have internet connectvity. [21:22] ah [21:23] superm1: mpt did create a design of how the captive portals should work & auto-popup for sign-in, but that was not implement yet on any of the platforms (installer, desktop, touch...) [21:24] superm1: but one can launch a browser to login and that should make "internet" available. but it's not easily discoverable. === kentb is now known as kentb-out