[03:09] <CIA-3> ubiquity: superm1 * r3896 ubiquity/ (4 files in 2 dirs):
[03:09] <CIA-3> ubiquity: Remove has_separator property from gtk dialogs to prevent a warning
[03:09] <CIA-3> ubiquity: from gtk.Builder when they are loaded.
[03:46] <shtylman> how man one human deal with all the launchpad email
[04:36] <superm1> filters :)
[06:10] <Ou42> hello, anybody home?
[15:53] <cr3> I'm getting an apt-setup/cdrom/failed error window when installing the desktop image today. is there a convenient way to get log files from the system being installed over the network? on the alternate, I'm used to calling httpd which is a simple script calling nc to open /var/log through http
[17:37] <cjwatson> cr3: you could install openssh-server and scp them - just remember to set PermitEmptyPasswords yes, since the 'ubuntu' user has an empty password
[17:47] <cr3> cjwatson: I was hoping for a consistent way to retrieve information across alternate and desktop images, so perhaps I could simply run the same nc command as in the httpd script for the desktop install
[19:30] <cjwatson> cr3: up to you, I guess that would work modulo slightly different list of files to fetch
[19:31] <cr3> cjwatson: good point, /var/log/syslog (alternate) != /var/log/installer/debug (desktop)
[22:40] <shtylman> https://code.launchpad.net/~shtylman/ubiquity/kubuntu
[22:40] <shtylman> contains the language bugfix and greeter functionality ^
[23:06] <shtylman> a code review would be appreciated if there is time
[23:08] <ev> I'm not convinced we need the "please choose the language to use for the install process" message.  It's a pretty straightforward interface.
[23:10] <shtylman> ev: think so? I dunno... cause the old message used to talk about selecting the language to continue... but the new one doesn't... and feel that it is a bit unclear (at least to me) what I am supposed to think about this random box with languages in it
[23:10] <ev> shtylman: also, do you have any objection to using ubiquity/text/install_ubuntu instead of ubiquity/text/begin_install_button?  I think it's more consistent.
[23:11] <shtylman> yea... by objection is that I feel the text "install ubuntu" is unclear... and feels like as soon as you hit it, it will perform the install
[23:11] <ev> oem-config doesn't have any description text
[23:11] <ev> it simply puts the languages in front of you
[23:12] <ev> with the theory being that if the text is in a language you don't understand, you'll find your language in the list and click on it
[23:12] <shtylman> ev: ubiquity/text/welcome_text_oem_user_label
[23:12] <shtylman> look at that template
[23:12] <shtylman> I think thats what it uses... no?
[23:12] <ev> only because I missed that when updating the interface
[23:13] <ev> I'm keen to strip the last line off that string
[23:13] <ev> I don't want to overcrowd the interface with text to the point that people cease to read it
[23:13] <shtylman> ev: I think it is a very helpful line
[23:13] <shtylman> right.. but in this case the text is actually telling you about an option
[23:13] <shtylman> leaves all guessing aside
[23:14] <shtylman> installing is important.. the user should never feel like they arn't aware of what is happening
[23:14] <shtylman> just my thoughts on it
[23:14] <shtylman> I won't cry if it is taken out...
[23:14] <shtylman> but I did have a reason for adding it
[23:14] <shtylman> likewise for the "continue installation" text :)
[23:16] <shtylman> a valid concern is more text to translate... ill give you that
[23:16] <ev> sure, which is why I asked if you had an objection.  I have no intention of trying to strong-arm you.  If you want to leave it in, by all means. :)
[23:17] <ev> I still disagree, but I don't think anyone is going to complain of massive UI differences between the GTK and KDE frontends on account of a single line of text.
[23:17] <shtylman> ev: :) I would prefer to leave it just on the grounds that it makes things clearer (at least to me) ... but then again.. I wrote it... so I am biased
[23:18] <ev> heh
[23:18] <shtylman> ev: noted
[23:19] <shtylman> something I do want to look at tho... unrelated to these changes is the slowness in startup
[23:20] <shtylman> somewhere there is a bottleneck... cause in my vm... when I launch the installer I can see the unreplaced text before it replaces it
[23:20] <shtylman> like its still thinking about something
[23:20] <shtylman> I will need to investigate that
[23:23]  * shtylman just finished yelling at my monitor... I think my neighbors think im crazy
[23:25] <ev> shtylman: see my change to the GTK+ frontend on that
[23:25]  * ev digs for the revspec
[23:25] <ev> we hide the text and language selector until they're ready
[23:25] <shtylman> ev: ahh.. I see.. interesting..
[23:26] <ev> 3871
[23:26] <shtylman> ev: a nice fix... but I do wanna know why it takes a while for it to start up... is this internal behavior? or frontend specific?
[23:27] <ev> the page is shown as soon as it can be, not as soon as the text that's going to be displayed is known
[23:27] <ev> between those two states is the running of localechooser
[23:27] <ev> which can take a noticeable amount of time
[23:28] <shtylman> I see
[23:33] <ev> so roughly, start up ubiquity and its ui frontend -> run the d-i component for the language page (localechooser) -> wait for a the localechooser/languagelist debconf question to be asked -> build a translation map, figure out the default language, etc -> populate the UI with the language list from debconf -> select the default language -> translate and substitute (RELEASE, MEDIUM, etc) the instructional text, and now we're ready for the user :)
[23:34] <shtylman> and this can't happen quickly? :p
[23:34] <shtylman> I would think 2 cores of an i7 and 2 GB of ram.. it should be a _bit_ quicker than it is...
[23:35] <ev> it's a lot quicker than it used to be
[23:35] <shtylman> but maybe I have unrealistic expectations... sigh
[23:35] <ev> no, but it's a hard nut to crack
[23:36] <superm1> i think that is causing problems if you run ubiquity in non maybe mode where quit keeps focus
[23:36] <ev> I've noticed the quit keeps focus thing as well
[23:36] <ev> I suspect it's that we try to set the next button as the default but it's disabled at the time
[23:36] <ev> a race of sorts
[23:37] <superm1> so maybe need to special case it that after the text gets substituted in and shown, reset next as the focused item
[23:38] <ev> or perhaps we should always wait until next can be selected to make it the default?
[23:39] <superm1> that probably is the smarter way