[14:19] <charlie-tca> Good morning
[14:28] <jibel> Good day charlie-tca
[14:30] <charlie-tca> I filed a bug to get the partitioning explanations in a darker text. bug 743238
[14:30] <ubot4`> Launchpad bug 743238 in ubiquity (Ubuntu) "Ubiquity installer is difficult to read on "Allocate Drive Space" (affects: 1) (heat: 6)" [Medium,New] https://launchpad.net/bugs/743238
[14:30] <charlie-tca> one of those, "sure would be nice to see this" bugs
[14:36] <jibel> charlie-tca, was it the accessibility testcase ? http://testcases.qa.ubuntu.com/Install/DesktopAccessibility ? Which flavour do I add it to, ubuntu and xubuntu ? other ?
[14:37] <charlie-tca> that's the testcase, Ubuntu Desktop only, probably optional?
[14:38] <jibel> charlie-tca, ack. doing it right now
[14:38] <charlie-tca> Thank you
[14:38] <charlie-tca> I forgot the email :-(
[14:41] <jibel> charlie-tca, done. No problem, I forgot to add the testcase :-)
[14:42] <charlie-tca> Thanks for doing that!
[14:45] <jibel> charlie-tca, did you tried the installer with a high-contrast theme enabled ? Some steps are totally unreadable. white on white
[14:45] <charlie-tca> No, I haven't been through that one yet.
[14:46] <charlie-tca> alternate or desktop?
[14:49] <jibel> charlie-tca, desktop. Boot to a live session, change to theme to high contrast then run ubiquity, steps "Preaparing to install" and "Erase disk" are unusable.
[14:50] <charlie-tca> Thanks, I will go try it
[14:51] <charlie-tca> oops
[14:51] <charlie-tca> I forgot to sync today's images
[14:58] <jibel> charlie-tca, I filed bug 744283, I'll link it to the tracker once the builds are out.
[14:58] <ubot4`> Launchpad bug 744283 in ubiquity (Ubuntu) "Steps "Preparing to install" and "Erase disk" are unreadable with high-contrast theme enabled (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/744283
[14:58] <charlie-tca> Thank you
[14:58] <charlie-tca> Soon as I get today's image, I will confirm it
[15:04] <jibel> charlie-tca, Do you have hw which doesn't support Unity to confirm something ? It looks like the fallback to the classic desktop doesn't work on the livecd, nautilus and metacity are running, but there's no panel. I don't know if it's an issue with the fallback or vbox.
[15:04] <charlie-tca> I can throw an nvidia card in a system
[15:05] <charlie-tca> what about log out/log in again?
[15:10] <jibel> ubuntu classic works correctly, but not the Unity fallback, that's why I'd like to confirm on real hw. opengl support in vbox sometime generates strange results. btw there's no logout button :-)
[15:12] <charlie-tca> okay, running it up now
[15:28] <charlie-tca> um, starting the live desktop is taking over 3 minutes after clicking on "Try Ubuntu"?
[15:32] <jibel> charlie-tca, I've seen a report about the slowness of the livecd but can't find the bug number.
[15:33] <charlie-tca> That's not slow, it's impossible. How many users will really wait that long?
[15:35]  * jibel trying on a netbook and a stopwatch 
[15:35] <jibel> charlie-tca, cd or usb ?
[15:35] <charlie-tca> dvd
[15:36] <charlie-tca> oversize image
[15:36] <jibel> :-)
[15:36] <jibel> I've no dvd I'll go for a usb.
[15:36] <charlie-tca> starting again, just clicked Try
[15:37] <charlie-tca> Went throught this time
[15:37] <charlie-tca> and fallback worked, I have both top and bottom panels
[15:38] <charlie-tca> VBox does have problems, Xubuntu will only give one workspace on VBox installs, but two on hardware installs
[15:39] <jibel> Yeah, start the stopwatch killed Unity
[15:40] <charlie-tca> At least fallback is working on the hardware
[15:40] <jibel> charlie-tca, the invisible panel is a known rendering issue with Compiz and the fallback, it was fixed last week but obviously it is not.
[15:40] <jibel> thanks for testing
[15:41] <charlie-tca> next is the high-contrast install
[15:42] <charlie-tca> I have both 386 and 64bit hardware to test on now. the 64bit is a laptop, so no changing the intel video card, but at least it is 64bit hardware.
[15:44] <jibel> nice
[16:18] <jibel> charlie-tca, confirm starting live session from usb is slow. 3 minutes to the Welcome screen then 4 minutes to the desktop after clicking on Try. That's a total of 7 minutes.
[16:19] <charlie-tca> sure is. Most users gave up during that
[16:19] <jibel> charlie-tca, I can't find the report I mentioned above, I'll file a new one.
[16:20] <jibel> and try with another memory stick, to eliminate the crappy hw bug.
[16:21] <davmor2> jibel: on my laptop I have an atheros wifi card that still isn't working :(  I've written a bug for it that jfo has marked as triaged but I think it has gone no further
[16:21] <davmor2> jibel: wifi card is ateros AR5001
[16:22] <jibel> davmor2, what's the bug number ?
[16:22] <davmor2> jibel: one second
[16:22] <jibel> ohoh, the boot from livefs starts with a fsck for more than 1 minute, non sense
[16:23] <charlie-tca> jibel: I did something wrong and never saw the "Preparing to install  screen
[16:23] <charlie-tca> jibel: I did something wrong and never saw the "Preparing to install " screen
[16:23] <charlie-tca> or is that the all white page that never stopped?
[16:24] <davmor2> jibel: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/710738
[16:24] <ubot4`> Launchpad bug 710738 in linux (Ubuntu) "Regression latest kernel breaks my Atheros AR5001 wifi (affects: 1) (heat: 74)" [Undecided,Triaged]
[16:25] <charlie-tca> hm, slideshow does not fit on my 19" LCD display with high-contrash install
[16:25] <charlie-tca> lol
[16:26] <charlie-tca> Propably okay, though, because it appears stuck on the Welcome page
[16:28] <jibel> davmor2, okay, I'll give it a higher priority and bring it to the attention of the release team.
[16:29] <davmor2> jibel: thanks you
[16:30] <jibel> davmor2, also, once the first images are out tomorrow, please link it to a testcase on the tracker Desktop install or Live Session will be fine.
[16:31] <davmor2> jibel: will do if I have time we currently have 5 releases of our own in the pipeworks :)
[16:35] <davmor2> jibel: it wouldn't bother me so much but pre alpha2 it worked a dream :)
[16:55] <charlie-tca> jibel: screens are readable in hardware with ati card
[16:55] <charlie-tca> will try it with the intel card and see if it makes a difference
[16:55] <jibel> charlie-tca, that's maybe the color depth.
[16:56] <charlie-tca> I will keep working on verifying it, even if it takes me into VBox to do it
[16:57] <jibel> charlie-tca, I filed bug 744362 for the boot slowness
[16:57] <ubot4`> Launchpad bug 744362 in casper (Ubuntu) "Booting to a live session is really slow (7 minutes) (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/744362
[16:58] <charlie-tca> I will confirm that one now
[16:58] <jibel> I'm trying with another stick but it looks the same
[16:59] <jibel> I mean, as bad
[16:59] <charlie-tca> Yeah, I don't think it is the stick, it really is a slow boot
[17:01] <jibel> yeah, I've found nothing obvious from the log excepted the fsck but which doesn't take that long
[17:03] <skaet> jibel, all - cjwatson's building fresh set of images now,  they should start to appear on the iso tracker for smoke testing shortly.   ARM images will be coming later.
[17:04] <skaet> cregan,  suggest you wait until jibel's had a chance to do some smoke tests to make sure that these are likely images (and we won't respin),  before you kick off your efforts.
[17:04] <skaet> cgregan, ^^  (sorry, bout typo)
[17:05] <jibel> skaet, ack.
[17:05] <jibel> thanks
[17:05]  * jibel having a break
[17:05] <charlie-tca> thanks
[17:22] <cjwatson> skaet: I'm pretty sure we'll need to respin tomorrow; there are a bunch of RC bugs as yet unresolved
[17:23] <skaet> cjwatson, ack
[17:24] <skaet> cjwatson,  smoke test of some of the images though have value?
[17:24] <cjwatson> certainly, I was just responding to your "and we won't respin" comment
[17:24] <skaet> cjwatson, fair 'nuf.
[17:50] <cgregan> noted skaet
[18:56] <cjwatson> quite a few images are up for smoke-testing, BTW
[18:56] <cjwatson> I've posted everything that's built so far
[18:58] <skaet> jibel, charlie-tca, Riddell ^^^
[18:58] <charlie-tca> thanks
[18:59] <Riddell> Kubuntu images were good when I tested this morning
[19:15] <charlie-tca> syncing again
[19:41] <Gulfstream> my Belkin F5D8053 (V3000) wireless card seems to be working better, but it randomly disconnects. Is there a spot where I can post my test results?
[20:04] <marjo> skaet: according to jibel, the smoke tests for alternate images passed
[20:04] <marjo> skaet: other images are syncing now
[20:06] <jibel> skaet, desktop is running on both amd64 and i386
[20:09] <skaet> jibel,  :)  baseline established.  We have our fallback then.
[20:15] <meganerd> is this an appropriate place for asking questions about 11.04 and my hardware?
[20:21] <Gulfstream> meganerd, I think jibel knows... I am not sure though.
[20:28] <jibel> skaet, can I open the upgrades on the tracker ?
[20:28] <skaet> jibel,  yes, please go ahead
[21:58] <jibel> skaet, bug 739632
[21:58] <ubot4`> Launchpad bug 739632 in ubiquity (Ubuntu Natty) (and 1 other project) "ubiquity crashed during install with: plugininstall.py: DebconfError: (10, "oem-config/enable doesn't exist") (affects: 7) (dups: 4) (heat: 156)" [High,Confirmed] https://launchpad.net/bugs/739632
[21:59]  * skaet looking
[21:59] <jibel> seems to affects many users but passed below the radar during last milestone
[21:59] <jibel> the retracer is fighting against us here
[22:00] <jibel> a large part of the duplicates are in bug 652916
[22:00] <ubot4`> Launchpad bug 652916 in ubiquity (Ubuntu) "ubiquity-dm crashed with ValueError in command(): invalid literal for int() with base 10: '' (affects: 65) (dups: 32) (heat: 442)" [Medium,Triaged] https://launchpad.net/bugs/652916
[22:04] <skaet> thanks for flagging jibel.   yeah this one needs to be looked at,  esp. since it looked like the other oem config bug was resolved.
[22:07] <jibel> urgh, the retracer is aggregating all kind of bugs to 652916
[22:31] <cjwatson> skaet: it doesn't actually have anything to do with oem-config, FWIW, despite the backtrace
[22:31] <cjwatson> what's happening is that the debconf protocol has got out of sync due to one of the packages being installed
[22:32] <cjwatson> and the next thing ubiquity does using debconf falls over
[22:32] <cjwatson> it's sort of the equivalent of malloc corruption - the effect is distant from the cause
[22:32] <skaet> yuck
[22:34] <skaet> cjwatson, is it obvious which of the package being installed is causing this?  or is it going to take some significant detective work?
[22:34] <cjwatson> the debug log I've asked for should make it clear to an installer developer
[22:34] <cjwatson> unless we're particularly unlucky
[22:34] <cjwatson> it's not obvious from the existing logs, no
[22:35] <skaet> ack
[22:36] <cjwatson> hm, I don't normally turn on restricted guff in my installs, let's try that
[23:10] <chadadavis> Hi. I'm testing the amd64+mac ISOs. I see tracker entries for i386 and amd64. Will there be a separate category for amd64+mac, or shall I mix my results in with amd64 ?
[23:24] <skaet> chadadavis, there should be a separate entry for the amd64+mac ISO
[23:25] <skaet> jibel,  ^^
[23:26] <skaet> chadadavis, jibel is in europe so we'll need to catch him in the morning.
[23:27] <chadadavis> I'm also in Europe and will rejoin this in the morning as well, then. Thanks. I'll track the results externally in the meantime and fill them in later.
[23:29] <skaet> chadadavis, thanks!   also,  we'll be spinning some new images overnight to pick up the fix to the issue that jibel pointed out earlier.
[23:30] <skaet> if you've got any "hot" bugs, that are a result of the smoke testing,  feel free to post them here.
[23:31] <chadadavis> skaet, great, I'll wait for those then and zsync them. Will that be 20110329 then?
[23:32] <skaet> chadadavis, I'd be assuming so, but verify with jibel directly if in doubt.  (I'll be zzz ing then ;) )
[23:32] <chadadavis> skaet, will do. Thanks.
[23:35] <cjwatson> 20110329 or 20110329.something