[00:50] <CIA-45> ubiquity: stgraber * r5041 ubiquity/bin/ubiquity-dm: Make the clear call in ubiquity-dm clear the right tty
[00:51] <CIA-45> ubiquity: stgraber * r5042 ubiquity/bin/ubiquity-dm: Wait until clear in ubiquity-dm returned
[01:01] <CIA-45> ubiquity: stgraber * r5043 ubiquity/bin/ubiquity-dm: Don't fail if we can't open the tty
[01:01] <CIA-45> ubiquity: stgraber * r5044 ubiquity/debian/changelog: releasing version 2.8.3
[08:59] <CIA-45> ubiquity: evand * r5045 trunk/ (debian/changelog ubiquity/plugins/ubi-console-setup.py):
[08:59] <CIA-45> ubiquity: Handle the keyboard query window closed callback being fired twice
[08:59] <CIA-45> ubiquity: (LP: #865493).
[09:23] <ev> ugh, this is why I need the Ubuntu geonames server set up in a Vagrant configuration: https://bugs.launchpad.net/ubuntu-geonames/+bug/837054
[09:23] <ubot2> Launchpad bug 837054 in ubuntu-geonames "Time Zone selection shows about 20 different "New York"s and doesn't autoselect my location" [Medium,Confirmed]
[11:34] <CIA-45> ubiquity: evand * r5046 trunk/ (debian/changelog ubiquity/frontend/gtk_ui.py):
[11:34] <CIA-45> ubiquity: Allow focusing of labels when we're in the screen reader
[11:34] <CIA-45> ubiquity: acessibility profile, so that Orca can read them
[11:34] <CIA-45> ubiquity: (LP: #856782, LP: #856773).
[11:35] <ev> tried to get the resize widget usable from the keyboard
[11:35] <ev> but I can't seem to navigate it, even in a simple test application
[11:35] <ev> using a keyboard that is
[11:35] <ev> f6 and f8 do nothing
[13:00] <cjwatson> grr, why is localechooser-apply installed in two places
[13:00] <cjwatson> wasted an hour of testing time due to that :(
[13:05] <CIA-45> ubiquity: cjwatson * r5047 trunk/ (4 files in 2 dirs):
[13:05] <CIA-45> ubiquity: Don't install duplicate copies of console-setup-apply,
[13:05] <CIA-45> ubiquity: localechooser-apply, and netcfg-wrapper.
[13:09] <ev> eep
[13:09] <ev> I'm currently losing time to virtualbox yet again losing the location of my windows 7 disk
[13:09] <ev> despite it being *right there*
[13:20] <cjwatson> I'm sure everything would be easier if Simplified and Traditional Chinese had two different language codes
[13:20] <cjwatson> sigh
[13:49] <ev> ugh, this definitely appears to be trashed
[14:16] <cjwatson> argh, why am I getting I/O errors inside kvm
[14:17]  * cjwatson tries giving it a bit more memory
[14:18] <ev> :)
[14:18] <ev> I'm getting "Windows failed to start" using the Windows setup CD
[14:18] <ev> I don't think today is turning out to be a stellar one for compuing
[14:18] <ev> computing even
[14:23] <cjwatson> this is my third try; if this fails I'll have to resort to (shock) real hardware
[14:25] <ev> hahaha
[14:48] <Peanut> I am upgrading an install-server, re-using the preseed.cfg for a lucid LTS (previously karmic). As expected, I get a few questions popping up - how can I figure out which d-i entries correspond to the questins that pop up?
[15:10] <stgraber> argh, just noticed I get "shutdown" and "log out" in the session indicator when installing using ubiquity-dm
[15:10] <stgraber> I guess I'll have to fix that, seems like I missed it in my tests yesterday
[15:11] <stgraber> btw, any reason why we even have indicator-session when in install-only mode?
[15:14] <superm1> is that the same indicator applet that shows you your name?
[15:14] <superm1> if so, i noticed that during an oem-config run it briefly pops up the "OEM" name too
[15:16] <ev> stgraber: so they can reboot if they really didn't mean to boot the Ubuntu CD
[15:16] <stgraber> ev: ah, ok
[15:56] <CIA-45> ubiquity: evand * r5048 trunk/ (debian/changelog ubiquity/plugins/ubi-partman.py):
[15:56] <CIA-45> ubiquity: Make sure we account for the size of the installation and swap
[15:56] <CIA-45> ubiquity: partition when calculating the bounds for the partition resizer
[15:56] <CIA-45> ubiquity: (LP: #769350).
[16:03] <stgraber> fun, starting a live session, killing lightdm and starting ubiquity-dm makes gsettings work just fine, doesn't help to reproduce the bug though :)
[16:08] <stgraber> ok, I "think" I found the bug. for some reason we don't have $USER set in the environment when using ubiquity-dm
[16:08] <stgraber> so ubiquity tries to change the gsettings options for root instead of for the ubuntu user
[16:18] <CIA-45> ubiquity: stgraber * r5049 ubiquity/ (bin/ubiquity-dm debian/changelog): Update ubiquity-dm to export self.username as SUDO_USER.
[16:19] <stgraber> ev: that one line should be all that's needed to fix my gsettings bug, release when you want :)
[16:19] <ev> yay
[16:20] <ev> just waiting for the publisher
[16:21] <ev> and while I do, I'll fire up pbuilder
[16:23] <CIA-45> ubiquity: evand * r5050 trunk/.bzrignore: Update bzrignore.
[17:04] <ev> just trying to get a working pbuilder build
[17:04] <ev> the last one curiously segfaulted somewhere in the depths of gettext
[19:05] <stgraber> ev: found out what made it segfault?
[20:28] <stgraber> superm1: for bug 868668, is the firewall/router on your network rejecting the connections on tcp/80 or just ignoring them?
[20:28] <ubot2> Launchpad bug 868668 in ubiquity "Installer hangs when progressing to timezone page for 45 sec" [Undecided,New] https://launchpad.net/bugs/868668
[20:29] <stgraber> superm1: I'd expect wget to give up quite quickly if it gets reject but the timeout value can be pretty high if it just doesn't get any response
[20:29] <superm1> stgraber, ignores them
[20:30] <superm1> it's annoying that DNS resolves though
[20:30] <stgraber> ok, so would probably be worth tweaking the timeouts in the code a bit so it doesn't take that long
[20:30] <stgraber> I'll have a quick look at that once I'm done testing Edubuntu
[21:02] <stgraber> superm1: is it only tcp/80 that's being dropped or everything except 8080 to whatever your proxy server is?
[21:02] <cjwatson> dropping packets really is rubbish, you should get that fixed
[21:02] <cjwatson> I consider that hostile firewall design ...
[21:03] <stgraber> cjwatson: it's unfortunately common :( I've seen that one quite a few company and university networks, though in some cases it's not so much dropping everything as just not having a route to the outside (with the same result)
[21:03] <superm1> stgraber, everything except local network servers and what the proxy server is
[21:03] <cjwatson> it's common, but I don't think it should be tolerated when it can be changed
[21:04] <superm1> and it's the latter where there is no route to the outside really
[21:04] <cjwatson> BTW I knew the timezone page was slow in this case but did not consider it RC, as most people can still easily complete the questions before ubiquity finishes copying files
[21:05] <cjwatson> I'm not sure why it's been escalated through oem-priority given that
[21:05] <superm1> it's more the oem-config scenario that it matters
[21:05] <cjwatson> ah, I guess that does have a similar problem, yes
[21:05] <superm1> because testers get to the page and it's hung and bugs get filed
[21:07] <cjwatson> the fix is probably pretty invasive though
[21:07] <cjwatson> for oneiric
[21:08] <superm1> if it's not fixed for oneiric, it might just need to be SOP for oneiric to unplug the cable before going through oem-config or something i guess then
[21:09] <cjwatson> I'm just trying to think of what a fix would look like
[21:09] <stgraber> I'm surprised it takes 45s, the code indicates it should take 15s + loading time of the ubiquity page, so let's say 20s maximum
[21:09] <stgraber> and testing here seems to match that
[21:09] <cjwatson> 30s for rdate maybe?
[21:10] <cjwatson> rdate is already wrapped in progresscancel; there's no progress bar on that page, but that means ubiquity at least has a way to cancel it
[21:10] <cjwatson> the wget is trickier
[21:11] <cjwatson> we have the connectivity check in the ubiquity frontend, so maybe we could stub out that wget
[21:12] <stgraber> yeah, that was my plan too, except that I just noticed that the connectivity check is buggy :)
[21:12] <cjwatson> oh?
[21:12] <stgraber> it uses --timeout=15 but it's been running for 6 minutes here :)
[21:12] <cjwatson> !
[21:12] <cjwatson> it's not just repeatedly running?
[21:12] <stgraber> same pid
[21:12] <cjwatson> stubbing out the wget would require either a change in ubiquity, or a compat script
[21:13] <cjwatson> er, a change in *tzseteup
[21:13] <cjwatson> can't type, YKWIM
[21:13] <stgraber> ok, found the problem
[21:13] <stgraber> we start wget with -T 15 but not with -t 1 for the connectivity check
[21:13] <stgraber> so it waits 15s per try, with a possibly infinite number of retries
[21:14] <cjwatson> ah, yes
[21:14] <cjwatson> default is 20
[21:14] <stgraber> -t 1 -T 15 is what's being used by tzsetup and probably a good idea of the connectivity test too
[21:14] <cjwatson> well, allegedly, that would give five minutes though
[21:14] <cjwatson> agreed
[21:15] <cjwatson> I think the easiest would be to give ubi-timezone a plugin_set_online_state method so that it gets told about state, and then before it starts the d-i callout it can preseed tzsetup/geoip_server to empty if it doesn't have connectivity
[21:16] <cjwatson> that will get rid of the wgwet
[21:16] <cjwatson> and probably simplest to preseed clock-setup/ntp to false as well, which will get rid of the rdate
[21:17] <cjwatson> slightly brutal but that seems like the least invasive fix
[21:17] <cjwatson> stgraber: are you OK with doing that?
[21:18] <CIA-45> ubiquity: stgraber * r5051 ubiquity/ubiquity/ (frontend/base.py plugins/ubi-language.py): Whenever we call wget with a timeout, also set the number of tries to 1 instead of default of 20
[21:19] <stgraber> cjwatson: yep
[21:19] <CIA-45> ubiquity: stgraber * r5052 ubiquity/debian/changelog: Update changelog
[21:20]  * cjwatson fails to understand why ubi-language has its own implementation of check_returncode *and* a plugin_set_online_state method
[21:20] <cjwatson> oh, it's talking to a different URL
[21:21] <cjwatson> try:
[21:21] <cjwatson>     import lsb_release
[21:21] <cjwatson>     _ver = lsb_release.get_distro_information()['RELEASE']
[21:21] <cjwatson> except:
[21:21] <cjwatson>     _ver = '10.10'
[21:21] <cjwatson> classy
[21:21] <stgraber> :)
[21:21]  * cjwatson fixes
[21:22] <CIA-45> ubiquity: cjwatson * r5053 trunk/ (debian/changelog ubiquity/plugins/ubi-language.py): Bump fallback Ubuntu version number in ubi-language to 11.10.
[21:54] <stgraber> cjwatson: http://paste.ubuntu.com/703017/
[21:56] <cjwatson> stgraber: s/thing/think/ in the changelog :)
[21:56] <cjwatson> stgraber: what happens if we get to the timezone page before the 15 seconds for the initial check have elapsed?
[21:56] <cjwatson> stgraber: I wonder if maybe we'd be better off initialising self.online = False
[21:57] <cjwatson> with a TODO comment saying that we can flip this once we have the ability to abort the wget / rdate in progress
[21:57] <stgraber> well, the way ubiquity seems to work is that it first runs plugin_set_online_state as True if Network Manager says we're online. Then starts the wget in background and sends a False if it timeouts or doesn't match the expected content.
[21:58] <stgraber> so whatever default we set in ubi-timezone, it'll always be True until wget times out
[21:58] <cjwatson> hm
[21:58] <cjwatson> that's awkward then; many users won't take as long as 15 seconds to get past the first page
[21:59] <stgraber> indeed
[21:59] <stgraber> we could change the logic to be offline until we get the right content from wget
[22:00] <stgraber> I personaly think it'd make sense though we need to make sure that server will scale on release day :)
[22:00] <cjwatson> actually, are you sure?  the network_change stuff only calls set_online_state if False
[22:01] <cjwatson> I don't see code setting it to True unless it gets a response from wget
[22:01] <stgraber> I only assumed it was as ubi-prepare always shows I'm connected until wget times out
[22:01] <stgraber> but maybe it's just the default on ubi-prepare that's wrong too
[22:02] <cjwatson> yeah, that's just ubi-prepare
[22:02] <cjwatson> the actual underlying code looks OK
[22:02] <stgraber> ok, setting self.online to False by default then
[22:03] <cjwatson> the rest looks fine
[22:03] <cjwatson> I wish my Chinese handling tests weren't taking forever and a day
[22:04] <CIA-45> ubiquity: stgraber * r5053 ubiquity/ (debian/changelog ubiquity/plugins/ubi-timezone.py): Don't contact geoip or run rdate if we don't have internet connectivity
[22:05] <stgraber> cjwatson: should I try to make ubi-prepare consistent with ubi-timezone (as in, not showing you're online when wget is still running)?
[22:05] <stgraber> argh, forgot to pull again... time to bzr bind that branch :)
[22:06] <CIA-45> ubiquity: stgraber * r5054 ubiquity/ (debian/changelog ubiquity/plugins/ubi-timezone.py): Don't contact geoip or run rdate if we don't have internet connectivity
[22:08] <cjwatson> I think leave ubi-prepare alone at this point
[22:08] <cjwatson> and maybe file a bug
[22:08] <cjwatson> anyone want to comment on http://paste.ubuntu.com/703026/ and http://paste.ubuntu.com/703027/, for bug 590108?
[22:08] <ubot2> Launchpad bug 590108 in ubiquity "User get wrong system language after executing oem-config, if he is a foreigner in the country he selected in timezone select stage" [Medium,In progress] https://launchpad.net/bugs/590108
[22:12] <cjwatson> I've yet to test this all the way through, working on that
[22:16] <stgraber> the comments make sense, it indeed won't affect anything that's not pt or zh, as for the rest, can't comment much without testing (and I already did my chinese install of the day ;))
[22:18] <cjwatson> I'm on about my fifth :-/
[22:18] <cjwatson> I probably could have made it more general but decided it was safest to constraint it
[22:18] <cjwatson> constrain*
[22:18] <cjwatson> gah.  coffee.
[22:26] <cjwatson> I'll go ahead with localechooser - I've tested that at least in d-i
[22:27] <CIA-45> localechooser: cjwatson * r165 ubuntu/ (debian/changelog post-base-installer.d/05localechooser):
[22:27] <CIA-45> localechooser: For cases where selecting a different location may imply a different
[22:27] <CIA-45> localechooser: dialect of the language, i.e. Portuguese and Chinese, take care to set
[22:27] <CIA-45> localechooser: LANG to something reflecting the location and
[22:27] <CIA-45> localechooser: LANGUAGE/LC_MESSAGES/LC_CTYPE/LC_COLLATE to something reflecting the
[22:27] <CIA-45> localechooser: language (LP: #590108). This roughly matches the behaviour of
[22:27] <CIA-45> localechooser: language-selector.
[22:27] <cjwatson> and that needs to go ASAP
[22:28] <CIA-45> localechooser: cjwatson * r166 ubuntu/debian/changelog: releasing version 2.37ubuntu2
[22:32] <cjwatson> stgraber: so did pbuilder work OK for you or was it just ev?  (or have you tried?)
[22:33] <stgraber> cjwatson: didn't try. I usually push to a PPA for testing
[22:33] <cjwatson> I can try it locally now if that would be helpful
[22:33] <cjwatson> waiting for an install anyway
[22:37] <cjwatson> running it through now
[22:53] <stgraber> currently building in a PPA: https://launchpad.net/~stgraber/+archive/experimental/+build/2825494
[22:55]  * cjwatson requests a ubiquity translations export
[23:14] <cjwatson> built cleanly here
[23:16] <cjwatson> ooh, and that looks suspiciously like a correct /etc/default/locale
[23:16] <cjwatson> now I just have to test oem-config
[23:27] <stgraber> ubiquity also built fine for both i386 and amd64 on the PPA builders
[23:32] <CIA-45> ubiquity: cjwatson * r5055 trunk/ (9 files in 3 dirs): Update translations from Launchpad.