=== NCommander_ is now known as NCommander === NCommander is now known as Guest88162 === Guest88162 is now known as NCommmander [09:03] persia: thanks for the heads up, I'll keep an eye on that thread [09:05] michaelforrest: do you have a few minutes today to clarify exactly what you need in terms of the size of the installer window in Lucid? I'm in the office, for what it's worth. [09:05] I've managed to shrink the window down quite a bit, but there are a few caveats [09:06] ev: absolutely [09:06] come and find me whenever [09:07] good deal [09:09] ev: You might just want to catch Anzenketh in #ubuntu-bugs to plan the best strategy, depending. Threads have a way of solidifying :) [09:30] persia: good call :) [09:31] persia: while I have you here, what's the smallest resolution that you guys need ubiquity to work on? [09:32] Um, hrm. [09:32] I don't have a good answer. [09:32] I'd personally like 640x480, but that's not realistic. [09:33] There are still some 800x480 devices being manufactured, and I'd say that's a more reasonable absolute smallest. [09:34] But there's 4.8" 1024x600 screens available, so I'd like to hope that smaller stuff becomes less common, or more specialised. [09:35] To sum up: [09:35] If you'd like to enable running ubiquity on the N900 (or similar devices), we need 800x480. [09:35] okay, big thanks for clearing that up [09:36] If you want to run on the new generation of handhelds, 1024x600 is probably sufficiently low res. [09:36] (unless manufacturers go for "cheap" over "useful" again) [09:40] michaelforrest: is now a good time to swing by? [09:57] ev sure [10:00] ncdjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjkkkjkjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk jjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj [10:00] whhops [10:00] whoops* [10:30] cjwatson: given that we're going with the "boot straight into ubiquity and let it deal with creating a try/install page" for lucid+1, is the greeter stuff (specifically the design and artwork for it) still a priority for you? [10:30] no [10:30] it came up in discussion with michaelforrest [10:30] okay cool [10:30] I actually want to do this for lucid if possible [10:30] and am still tracking it in the release meetings and such [10:30] if nothing else because Mark announced it for lucid :P [10:31] cjwatson: oh god. what ? [10:31] I have been enormously clear about this in e-mail [10:31] I cannot believe that it is a surprise [10:32] I also don't think it matters to you guys since we have the bits we need to do it now :) [10:32] I didn't know Mark had announced something [10:33] I thought it was still a 'nice-to-have' [10:33] at the platform briefing at UDS [10:33] it was practically the very first thing in his presentation [10:33] there's a reason this spec is Essential ... [10:34] and why I've been desperately trying to get styling information from people for months [11:23] ubiquity: evand * r3853 ubiquity/ (5 files in 4 dirs): (log message trimmed) [11:23] ubiquity: * The timezone is perfectly usable at half its width and height, so [11:23] ubiquity: only request that. This also means we're not trying to guess how [11:23] ubiquity: much space we can reasonably take up with the map, but rather [11:23] ubiquity: letting the rest of the interface determine the width and height of [11:23] ubiquity: the installer window. [11:23] ubiquity: * If the screen resolution is particularly low (< 600px height), allow [11:28] \o/ [11:31] still more work to do there on the partitioner so it works reasonably well at 640x480 [11:32] Is it a horizontal issue, or a vertical issue? [11:32] cjwatson: http://people.canonical.com/~evand/tmp/try_or_install2.png <- about to implement that for lucid, per michaelforrest's request, and with the workflow we've discussed. Any massive objections? :) [11:32] persia: vertical [11:32] * ev shakes his fist at the segmentedbars [11:33] fixable though [11:35] ev: gosh, you beat me to it, I thought I was going to end up doing that :) [11:36] ev: slight UI glitch in the "release notes" link, but overall looks fine to me - can we make sure that this workflow only appears when you're booting with maybe-ubiquity (or some similar switch) though? [11:37] it would be weird for it to appear if (for example) you use the icon on the live CD desktop [11:38] cjwatson: indeed, that's the plan :) [11:40] just awaiting sign off from boss^3 [11:40] hugo ? :) [12:40] hmm, oem-config still doesnt remove itself on my rootstock install [12:42] seems it exits with: [12:42] debconf (developer): <-- PROGRESS INFO ubiquity/install/hardware [12:42] Can't call method "info" on an undefined value at /usr/share/perl5/Debconf/FrontEnd.pm line 142, line 315. [12:43] Does ubiquity/install/hardware appear in your debconf db? [12:50] persia, i dont touch the debconf db at all [12:50] mainly what i do is run debootstrap and install oem-config in that [12:50] Understood. And it ought be there if ubiquity is installed. I'm just curious if it's present in your local environment when you encounter the issue. [12:50] touch /var/lib/oem-config/run and that it [12:50] *thats [12:56] ubiquity: cjwatson * r3854 ubiquity/ (debian/changelog ubiquity/components/ubi-partman.py): [12:56] ubiquity: Fix choose_partition thawing to handle free space at the end of [12:56] ubiquity: update_partitions (LP: #527848). [12:58] well, i see it in the ubiquity template file [12:59] so i would assume its there [13:01] * persia grabs trunk ubiquity thinking that this may solve the partman-uboot bug that has been confusing for the past few days [13:01] root@osiris:/# echo get ubiquity/install/hardware | debconf-communicate [13:01] 0 [13:01] Can you call INFO on it? [13:02] root@osiris:/# echo info ubiquity/install/hardware | debconf-communicate [13:02] 0 [13:03] Hrm. Nothing else comes to mind offhand. Logs might help (or maybe someone who knows more has an idea). [13:04] well, the above is all thet is in the logs [13:04] *that [13:04] the rest looks normal [13:06] i wonder if its caused by hw-detect [13:07] err - INFO != PROGRESS INFO [13:07] (and you won't be able to call PROGRESS INFO on its own via d-c anyway ...) [13:08] persia: what's up with partman-uboot? [13:08] hmm, i see in syslog that it tries to install usbutils [13:08] which it cant because there is no network setup [13:08] this all sounds pretty unrelated [13:09] ogra: can I see the debug log? [13:09] yeah, i just noticed it has the same timestamp ... [13:09] yup, one sec [13:09] http://people.canonical.com/~ogra/oem-config.log [13:09] cjwatson: It keeps selecting "dummy__________dummy" as the preferred partition, causing error 141 with choose_partition//do_option [13:09] ev - we are go on the installer first screen - mark just wants to make the "If you have internet access…" bit only show if there's network. Reworded as "You may wish to…". [13:10] persia: could I see the full logs, please? [13:10] cjwatson: So I'm guessing that it was a space (which may be why I had trouble tracking), and want to test your most recent fix. [13:10] and http://people.canonical.com/~ogra/syslog [13:10] persia: it's certainly in the category that *might* have been fixed, but I could tell you for sure given a debug log [13:11] ogra: ok, so the problem is that nested progress bars don't work outside debconffilter [13:12] cjwatson: I'd have to construct one (rebooted over the weekend, and scrapped the virtual machine). Do you especially want it, or do you see a reason I shouldn't pull trunk to keep debugging? [13:12] wow [13:12] it has nothing to do with that particular template name [13:12] what does indicate that ? [13:12] persia: if you don't have it conveniently to hand, you might as well use trunk, sure [13:12] * persia would otherwise merge patches to ubiquity, and start installs again tomorrow. [13:12] ogra: PROGRESS STOP followed by PROGRESS failing [13:12] ah [13:13] ogra: this is complicated to fix - could you file a bug, please? [13:13] yep, do you want both logs ? [13:13] sure [13:13] ok [13:18] bug 530027 [13:18] Launchpad bug 530027 in ubiquity "nested progress bars don't work outside debconffilter" [Undecided,New] https://launchpad.net/bugs/530027 [13:20] michaelforrest: AWESOME [13:20] working on it now [13:36] michaelforrest: http://people.canonical.com/~evand/tmp/thinner-partition-bars.png - does that look okay? [14:10] 14:06 didrocks: the point of casper's ubiquity-hooks is specifically to reproduce things that are done by casper at live CD boot time, and need to be repeated after installation [14:10] 14:08 didrocks: accessibility is there because casper does accessibility stuff at boot time [14:10] 14:07 it isn't meant to be a grab-bag of post-install scripts [14:10] 14:08 cjwatson: there is already some hooks like that like accessibility, etc. ev told me to put the first version there (which works in live mode) [14:10] 14:08 didrocks: I don't think things should go in casper's ubiquity-hooks unless they're also done at boot time in casper [14:10] 14:09 otherwise the result is that we end up with code spread around between casper and ubiquity when it doesn't need to be [14:10] 14:09 you could install a ubiquity-hooks file in gnome-desktop if you want, but it might be better to just have it in ubiquity [14:10] (from #ubuntu-devel) [14:25] ugh, I didn't tell him to put it in casper [14:25] I told him to look at the hooks in casper as examples [14:33] heh, ok [14:34] I said I was OK with either ubiquity or a hook in gnome-desktop [14:34] if you have a strong preference for the latter, you should join #u-d and say :) [15:01] nope, I just agree that casper is the wrong place [16:29] ev, michaelforrest re http://people.canonical.com/~evand/tmp/try_or_install2.png, should you really still be referring to it as from CD as a lot of people install from USB media these days instead? [16:31] I was hoping you'd make that dynamic actually ev [16:31] not that I said that! [16:37] will do [17:20] michaelforrest: just to clarify, you want the labels beneath the bars in the partitioner left-aligned rather than their present center-alignment, correct? [17:27] hm [17:28] can you show me? [17:28] ev^ [17:29] yup, heading over [17:30] netcfg: cjwatson * r640 ubuntu/debian/changelog: Rebuild against libiw30. [17:40] ubiquity: evand * r3855 ubiquity/ (debian/changelog ubiquity/segmented_bar.py): [17:40] ubiquity: * Left-align the labels on the segmented_bars. [17:40] ubiquity: * Make the segmented_bars narrower. === dpm is now known as dpm-afk [20:10] is it just me or does the casper.log generated on lucid no longer seem to contain: Found label '...' containing the disk image information? [20:11] I'm quite sure I recall that information existing before [20:12] there's now /var/log/installer/media-info though === dpm-afk is now known as dpm [21:41] netcfg: cjwatson * r641 ubuntu/debian/changelog: releasing version 1.51ubuntu2 [21:48] hrm, are "USB" and "CD" universally accepted acronyms, or should they be translated to something? Google is entirely unhelpful for such a query. [21:57] ev: they get transliterated in at least (random sample) Chinese [21:57] ev: see the cdrom-detect translations, for example [22:24] ah, damn, okay [22:24] thanks [23:23] so far: http://people.canonical.com/~evand/tmp/ubiquity-greeter.png - just need to fix one glaring bug. [23:24] are you parsing the OS from .disk/info to populate that, so Kubuntu, Xubuntu etc will automatically have their text set properly? [23:24] cool [23:25] does that dialog expand if you have a reasonable amount of screen space available? [23:27] as in the space between the try section and the install section? [23:27] or in some other way? [23:28] the whole window, it's smaller than it was, presumably due to your timezone changes [23:28] I'm just making sure that it uses more screen space if you have it, otherwise it'll feel cramped [23:29] while being smaller when there isn't so much space available [23:37] cjwatson: ah, a mistake in my previous commit. Fixing now. [23:42] ubiquity: evand * r3856 ubiquity/ (gui/gtk/stepUserInfo.ui ubiquity/components/ubi-usersetup.py): Fix r3853. Only use scrollbars on the user setup page when needed. [23:42] ^ fixed, thanks === robbiew is now known as robbiew_