[00:29] <dmandell> So I figured out that if I want to spawn multiple windows from the launcher I have to open the trash window and then switch.  It's annoying.  Especially because there's no other way through the GUI to launch Nautilus.
[15:57]  * skaet waves
[15:59] <zul> hi
[15:59]  * joshuahoover waves
[15:59]  * Riddell photons
[15:59] <Riddell> (it made the physicists laugh)
[15:59] <cjwatson> *groan*
[15:59] <leoquant> lo
[15:59]  * cjwatson runs Riddell through a double-slit experiment
[16:00] <skaet> lol
[16:00] <skaet> #startmeeting
[16:00] <MootBot> Meeting started at 10:00. The chair is skaet.
[16:00]  * pitti waves
[16:00] <skaet> hi all
[16:00] <skaet> Reminder:   please use ".." on separate line when you've finished typing.   If someone wants to comment during the updates, please "o/", so we know to wait.
[16:00] <skaet> .
[16:00] <skaet> Agenda is at:
[16:00] <skaet> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2011-04-08
[16:00] <skaet> .
[16:00] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2011-04-08
[16:00] <skaet> Milestoned bugs for beta 2 can be found:
[16:00] <skaet> [LINK]https://bugs.launchpad.net/ubuntu/+bugs?field.milestone=38691
[16:01] <MootBot> LINK received: https://bugs.launchpad.net/ubuntu/+bugs?field.milestone=38691
[16:01] <skaet> .
[16:01] <skaet> Milestoned bugs for 11.04 release can be found:
[16:01] <skaet>  https://bugs.launchpad.net/ubuntu/+bugs?field.milestone=33569
[16:01] <skaet> .
[16:01] <skaet> Bugs targetted for this release can be found:
[16:01] <skaet> [LINK] https://bugs.launchpad.net/ubuntu/natty/+bugs
[16:01] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/natty/+bugs
[16:01] <skaet> .
[16:01] <skaet> Upcoming Significant Dates:
[16:01] <skaet> 11.04 Beta Freeze: April 11, 2011 (0900 UTC)
[16:01] <skaet> 11.04 Beta 2: April 14, 2011
[16:01] <skaet> 11.04 Release Date: April 28, 2011
[16:02] <skaet> Lots of bugs and interesting things to discuss, so unless there are questions about the release dates,  will move directly on to round table.
[16:02] <Riddell> skaet: week days would be useful on Upcoming Significant Dates, saves me having to look them up
[16:02] <skaet> Riddell,  good suggestion.
[16:02] <skaet> will add next time.
[16:03] <skaet> Freeze is monday, btw.  ;)
[16:03] <skaet> ..
[16:03] <ogasawara> skaet: is there a specific time on monday?
[16:03] <skaet> ogaswara,  ^^ (0900 UTC)
[16:04]  * skaet looks around, and figures time to move on.... ;)
[16:05] <skaet> [Topic] QA team update -  jibel
[16:05] <MootBot> New Topic:  QA team update -  jibel
[16:05] <jibel> hi all
[16:05] <skaet> :)
[16:05] <jibel> Natty Beta-2 Work Items
[16:05] <jibel> https://launchpad.net/ubuntu/+spec/cloud-server-n-uec-qa
[16:05] <jibel> hggdh still blocked due to lack of working UEC since after Alpha 2. Blocked on Critical bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/746751
[16:05] <jibel> Daviey, Hallyn, and hggdh are working on it
[16:06] <jibel>  * QA Dashboard
[16:06] <jibel>  http://reports.qa.ubuntu.com/reports/qadashboard/qadashboard.html
[16:06] <jibel>  As last week linux, unity, compiz are in both last day and last 7 days top 5
[16:06] <jibel>  * Testing status:
[16:06] <jibel>  Desktop Automated Testing results
[16:06] <jibel> http://reports.qa.ubuntu.com/reports/desktop-testing/natty/
[16:06] <jibel>    2D: 83% pass / Unity: 76% pass
[16:06] <MootBot> LINK received:  http://reports.qa.ubuntu.com/reports/desktop-testing/natty/
[16:06] <jibel> List of bugs found is at the bottom of page. Still cleaning the list of tests that generates false positives
[16:07] <jibel>  Server Automated Testing results
[16:07] <jibel>  http://<IP_ADDRESS>/view/ISO-server-Natty/?
[16:07] <jibel>  1 failure because of a bug with the testing system (LP: #751297)
[16:07] <jibel>  http://<IP_ADDRESS>:8080/view/natty-desktop/?
[16:08] <jibel> no failure with alternate. desktop test disabled, a fix is committed and being tested with yesterday and today's iso.
[16:08] <jibel>  Automatic Upgrade Testing
[16:08] <jibel> http://people.canonical.com/~mvo/automatic-upgrade-testing/current/
[16:08] <jibel>  * python-all has some python import failures, but they look like false positives mostly, mvo will dig into that
[16:08] <jibel>  * bug 744831: main-all has a file overwrite problem with the langpacks that is fix-commited. According to comment 3 "The next -base langpack build will have this fixed (for beta-2)."
[16:08] <MootBot> LINK received:  http://people.canonical.com/~mvo/automatic-upgrade-testing/current/
[16:08] <jibel> Overlay Scrollbar testing:
[16:08] <jibel>  * 50 results received / 3 bugs reported
[16:08] <jibel>  * Report available at https://wiki.ubuntu.com/QATeam/TestingReport/OverlayScrollbar_NattyBeta1
[16:10] <jibel> Boot performance: We stopped the boot performance bug filing to the focus on Unity.
[16:10] <jibel> ..
[16:10] <skaet> Thanks jibel!   Lots of good data there,  agree priority is fixing natty bugs over boot performance (unfortunately).   Couple of questions:
[16:10] <skaet> Do we have the incoming bug numbers trending down on the bugs coming in?   (is worst of beta surge over?)
[16:10] <skaet> How many of the desktop bugs not passing (2D-17%, unity-24%) are estimated to be test failures, vs. actual failures?
[16:12] <skaet> if you want to answer later, we can circle back later?
[16:12] <jibel> 21 tests failures are false positives in 2d and approximately the same test in unity.
[16:12] <jibel> it's around 30% of the failures.
[16:12] <jibel> I don't have the answer to question 1 on the top of my mind.
[16:13] <skaet> ok,  lets come back to that at the end.
[16:13] <skaet> thatn's for the data on the false positives.
[16:13] <skaet> any other questions?
[16:13] <skaet> [Topic] Hardware Certification team update - victorp
[16:13] <MootBot> New Topic:  Hardware Certification team update - victorp
[16:13] <ara> o/
[16:14] <skaet> hiya ara
[16:14] <ara> I will be representing the hw cert team this week :)
[16:14] <ara> This week (and next one), the hardware certification team, is running the full certification testing suite against the systems that are scheduled to be certified for 11.04. This is a great team effort that it is already paying off.
[16:14] <ara> [LINK] https://bugs.launchpad.net/ubuntu/+bugs?field.tag=blocks-hwcert
[16:14] <ara> We are tagging the bugs as "blocks-hwcert" and we hope these will get the needed attention in order to get as many fixed as possible before release (or in an early SRU).
[16:14] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/+bugs?field.tag=blocks-hwcert
[16:14] <ara> This is how the coverage looks so far:
[16:14] <ara> [LINK] http://people.canonical.com/~hwcert/natty-testing/natty_beta1.html
[16:14] <ara> We will keep testing the Beta1 image with the remaining systems.
[16:14] <MootBot> LINK received:  http://people.canonical.com/~hwcert/natty-testing/natty_beta1.html
[16:14] <ara> ..
[16:15] <skaet> Thanks ara!
[16:15] <skaet> I'll go look at the actual data after meeting - is the overall picture positive or do we have some blockers starting to show?
[16:16] <ara> skaet, there are some systems that won't pass certification in 11.04 if the bugs are not addressed :(
[16:17] <ara> skaet, and the list of bugs will probably grow as we continue testing
[16:17] <skaet> understand.
[16:17] <skaet> what % of the tested systems won't pass certification at this point?
[16:17]  * skaet is seeing a fair bit of red on that chart....
[16:18] <ara> skaet, not that bad, I don't have the exact numbers though
[16:19] <skaet> ara,  ok,  thanks.  we'll move on then now.
[16:19] <ara> skaet, I will generate them if you're interested when the run is finished
[16:19] <skaet> thanks.  understanding impact of problem helps.
[16:20] <skaet> any other questions?
[16:20] <skaet> [Topic] Security team update - jdstrand
[16:20] <MootBot> New Topic:  Security team update - jdstrand
[16:20] <jdstrand> hi!
[16:20] <skaet> :)
[16:20] <jdstrand> Sorry for missing last week, I was on holiday.
[16:20] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Natty
[16:20] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Natty
[16:20] <jdstrand> [LINK] http://people.canonical.com/~platform/workitems/natty/canonical-security.html
[16:20] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-security.html
[16:20] <jdstrand> Since I brought it up last time I was here, I thought I'd mention that wrt the FTBFS in natty, I see that main is looking quite good, but universe and multiverse are still fairly scary (based on http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110329-natty.html).
[16:21] <jdstrand> aiui, http://people.canonical.com/~vorlon/broken-srcs-universe.txt shows which universe FTBFS packages are the result of the multiarch changes.
[16:21] <jdstrand> that list is less scary
[16:21] <jdstrand> All work items tied to the release process are completed. We are pleased to see that upstream thinks they know what the problem is wrt bug #663294. We fixed a couple of milestoned bugs (see the above report), but as usual, team has been focusing primarily on stable release updates.
[16:21] <jdstrand> I also had a question on the hardy desktop EOL, but not sure I should ask it now, in this meeting or somewhere else.
[16:21] <jdstrand> ..
[16:22] <skaet> thanks jdstrand!  hardy desktop EOL announce email is to be sent out.
[16:22] <skaet> its on my todo.
[16:23] <jdstrand> skaet: ok-- and that is also for the end of april, no?
[16:23] <pitti> jdstrand: doko just handed us a test binutils for that, Chris is testing it right now
[16:23] <chrisccoulson> yep :)
[16:23] <jdstrand> pitti: awesome :)
[16:24] <chrisccoulson> i'm going to drink beer tonight if it works
[16:24] <skaet> jdstrand,  yes, but natty release + hardy EOL + karmic EOL on same week isn't feasible workload,  so I'm staggering out the EOLs until after.
[16:24] <jdstrand> chrisccoulson: and especially awesome to you for all the analysis and reduced test case :)
[16:24] <chrisccoulson> :)
[16:24] <skaet> +1
[16:25] <jdstrand> skaet: ok. there are support costs wrt security updates when delaying EOL announcements though...
[16:25] <skaet> jdstrand, understand.  will discuss with you offline.
[16:25] <jdstrand> ok. that's it from me
[16:26] <skaet> [Topic] Kernel team update - ogasawara
[16:26] <MootBot> New Topic:  Kernel team update - ogasawara
[16:26] <ogasawara> Overall status is reported at the first link below.  Burn down for the release milestone is at the second link below.  Burndown for the cycle is at the third link:
[16:26] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty
[16:26] <ogasawara> [LINK] http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team-ubuntu-11.04-beta-2.html
[16:26] <ogasawara> [LINK] http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team.svg
[16:26] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty
[16:26] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team-ubuntu-11.04-beta-2.html
[16:26] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team.svg
[16:26] <ogasawara> All remaining work items are not release critical and should start moving to completion.  We recently uploaded the linux-2.6.38-8.41 kernel which most notably contains patches to allow powerpc to boot once again.  With Kernel Freeze next week, we plan to do our final kernel upload on Monday to allow enough time for builds to complete by Thursday.  Announcements regarding kernel freeze have been posted to the Ubuntu kerne
[16:26] <ogasawara> l-team mailing list as well as in the weekly kernel-team IRC meeting.  Any bug fixes which have not landed by Monday will be subject to SRU.
[16:26] <ogasawara> An update on the bugs noted in the agenda is as follows:
[16:26] <ogasawara> #508516 This is a BIOS bug, workaround exists by setting nohz=off and highres=off.  See comment #94 for release notes blurb. Set linux task to Won't Fix.
[16:26] <ogasawara> #539467 SATA alpm is now disabled in userspace, possible fix for Nvidia mcp65 controllers when in minimal power mode has been tested with positive feedback; Those still experiencing issues but with a different controller have been instructed to file new bugs.
[16:26] <ogasawara> #542660 Testing with v2.6.38 final still problematic.  Unfortunately, the tester appears to have sold the hw.
[16:26] <ogasawara> #608312 Patches pushed upstream but no response.  Kernel dev to re-test and confirm against Natty and submit patches to Ubuntu kernel-team mailing list if still needed.
[16:27] <ogasawara> #625364 Some comments indicate this has been resolved with a recent kernel update.  Still waiting confirmation from the original bug reporter.  Other subscribers/reporters may have a slightly different issue and confirmed that switching to vt1 and back on suspend mitigates the issue.
[16:27] <ogasawara> #634487 Kernel dev able to reproduce, currently under further investigation.
[16:27] <ogasawara> #674984 Awaiting confirmation this exists against Natty.
[16:27] <ogasawara> #686388 Test kernel built.  However, there are known issues with the proposed patches when on a macbook.  Call for testing with non-macbook hw.
[16:27] <ogasawara> #710738 Asked for testing to confirm the issue remains with the latest 2.6.38-8.41 kernel.
[16:27] <ogasawara> #712075 Partial fix in place, testing requested with 2.6.38 final kernel;  Remaining issue not release critical.
[16:27] <ogasawara> #719620 Investigation pointed to this being a BIOS bug.  Reporter going to try to upgrade the BIOS to see if this helps.
[16:27] <ogasawara> #720949 Assigned to kernel dev, currently under investigation.
[16:27] <ogasawara> #746751 Upon further investigation this does not appear to be kernel related but rather an issue with eucalyptus.
[16:27] <ogasawara> #747090 Currently under investigation.
[16:27] <ogasawara> #750649 Working on getting this assigned and under investigation.
[16:27] <ogasawara> #753071 Pull request Nack'd on the mailing list.  With the majority of the code not being upstream, this presents a maintenance burden as well as the fact that it brings in a large amount of change on the eve of kernel freeze.  Won't Fix at the moment.
[16:27] <ogasawara> #731878 We've isolated the bad commit and are currently tracking the upstream discussion regarding the issue.  We plan to revert the commit if no solution is found prior to kernel freeze.
[16:27] <ogasawara> Phew, any questions?
[16:27] <ogasawara> ..
[16:27] <cjwatson> if you can give me an idea of what time Monday, that would be useful.  I'll have to refresh installer images, and beta-2 CD builds will be gated on that (at least).
[16:28] <doko> please expect a (non-code changing) gcc-4.5 upload over the weekend
[16:28] <ogasawara> cjwatson: now that I hear we'll freeze the archive at 0900UTC, I'm inclined to upload on sunday instead.
[16:28] <cjwatson> that's easier from my end, as long as it works for you
[16:28] <cjwatson> however it sounds like it'll need to go after the gcc-4.5 build
[16:28] <ogasawara> cjwatson: works better for me actually, I don't like to cut it close
[16:29] <ogasawara> doko: gcc takes at least a day to build, can you upload today or saturday?
[16:29]  * skaet likes ogasawara attitude ;)
[16:29] <pitti> oh, 0900 UTC on Monday? seems I missed that
[16:29] <skaet> pitti, was on release mail list discussion, and agenda. ;)
[16:30] <doko> ogasawara: I'll upload as soon as possible, but not before the new binutils is in the archive
[16:30] <ogasawara> doko: is there an ETA for that?
[16:30] <doko> scroll back, waiting for feedback
[16:31] <ogasawara> doko: ack, can you ping me so I have a heads up when you've uploaded.
[16:31] <doko> and as I did say, it's a *non-code changing* upload
[16:31] <skaet> Thanks ogasawara!   Will go through the detailed status and get with you offline if specific questions.
[16:32]  * skaet looks around for o/ ...
[16:32] <skaet> moving on then.
[16:32] <skaet> [Topic] Foundations team update - cjwatson
[16:32] <MootBot> New Topic:  Foundations team update - cjwatson
[16:33] <cjwatson> Status: Drowning in bugs as far as the meeting agenda is concerned.  On the other hand, most of them aren't actually that important.  The important ones in my opinion are:
[16:33] <cjwatson> bug 663294 - upstreamed by Matthias, looks as though upstream knows what the problem is so we should have a fix soon
[16:33] <cjwatson> bug 683355 - plan here is to use grub-mount (from an upstream branch) to do true read-only mounts without needing to replay journals - Colin has this sort of working and is debugging it into existence
[16:33] <cjwatson> bug 711926 - only speculation on this so far
[16:33] <cjwatson> bug 728088 - this showed up in ISO testing, but Colin can't reproduce it.  Help wanted!
[16:33] <cjwatson> bug 728531 - new headline feature in upstart that needs to be fixed up.  James has a fix in testing, which is looking good so far
[16:33] <cjwatson> bug 732149 - reproduced, debugging in (slow) progress
[16:33] <cjwatson> bug 741304 - another ISO testing bug; partially fixed, but apparently this wasn't sufficient
[16:33] <cjwatson> bug 743136 - fix previously attempted, but we need to try again
[16:33] <cjwatson> bug 746758 - Evan has been swearing at this for most of the week, but I believe is still working on it
[16:33] <cjwatson> The good news is that Wubi's fixed, we finally have an EOL landing web page, and in general the resolution rate continues to be high.  We just have a lot coming in as well.
[16:33] <cjwatson> Finally, a worthwhile thing to know for the next release: http://twitter.com/#!/WeAreFact/status/56348015618834433
[16:34] <cjwatson> ..
[16:35] <skaet> Thanks cjwatson!
[16:35] <skaet> sorry about letting some cruft in on the agenda.
[16:35] <doko> test rebuilds still running, will expect to file the remaining bug reports this weekend
[16:35] <skaet> and *\o/* on wubi working!
[16:36] <cjwatson> doko: thanks - are you planning to milestone any/all?
[16:36] <cjwatson> (IIRC you said "yes, once they're done")
[16:36] <doko> cjwatson: the script doesn't yet support milestoning :-/
[16:37] <cjwatson> if you give me a batch of bug numbers then I can script it
[16:37] <cjwatson> if that's what you want to have happen
[16:37] <doko> anyway, if somebody has a script template ...
[16:37] <cjwatson> and give you the resulting interactive session for future reference :-)
[16:37] <cjwatson> (I tend to make stuff up on the fly in lp-shell(1))
[16:38] <doko> we'll sort it out later
[16:38] <skaet> any other questions?
[16:38] <skaet> [Topic] Server team update - zul
[16:38] <MootBot> New Topic:  Server team update - zul
[16:39] <zul> hi
[16:39] <zul> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus/
[16:39] <zul> The burn down chart looks really good. We are currently bug squashing mode. The new gamma release for Opentack will be uploaded today. The only new outstanding bug is 747498, which is pending on the landscape team testing the patch but will uploaded to the archive today. Other than that things are looking pretty good.
[16:39] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus/
[16:39] <zul> Bugs still in progress
[16:39] <zul> * 728088 - debian-installer - iscsi root (amd64) with or without auth fails to boot
[16:39] <zul>     Someone needs to retest.
[16:39] <zul> * 717166 - Eucalyptus - Broken with v4 isc-dhcp-server in Natty
[16:39] <zul>     Marked as invalid its a bug in dhcp.
[16:39] <zul> * 580319 - dhcp3-server launches before upstart brings all interface, thus failing to start
[16:39] <zul>     Assigned to JamesHunt
[16:39] <zul> * 727200 [MIR] lxcguest in main
[16:39] <zul>     Pending MIR review
[16:39] <zul> ...
[16:40] <zul> I think we are in pretty good shape
[16:40] <cjwatson> iscsi: it's not so much retesting, as either "help cjwatson to reproduce it" or "fix it" :-)
[16:40] <zul> cjwatson: ah ill see if i can try to reproduce it
[16:40] <cjwatson> somebody's reproduced with a hardy ietd, but I don't propose to set that up - in any case I rather suspect it isn't server-version-specific
[16:42] <skaet> thanks zul.   what about the other bugs on agenda?
[16:42] <zul> skaet: err...i need to have a look
[16:42] <skaet> can you go through them asynch,  and make sure they're all valid and prioritieze correctly?
[16:43] <skaet> prioritized even..
[16:43] <zul> skaet: yeah the powernap one was just fixed i think as well
[16:43] <skaet> cool.
[16:44] <skaet> I'll move on then...
[16:44] <skaet> [Topic] Desktop team update - pitti
[16:44] <MootBot> New Topic:  Desktop team update - pitti
[16:44] <pitti> General status:
[16:44] <pitti>  * Nothing noteworthy since last week; bug fixing going on with full steam.
[16:45] <pitti>  * Unity team asked for uploading a final flush of bug fixes on Monday, can we fit that in?
[16:45] <pitti> Blueprint implementation:
[16:45] <pitti>  * On track for entire cycle
[16:45] <pitti>  * Remaining work for Natty:
[16:45] <pitti>   * [packageselection-desktop-n-firefox-4] Some remaining porting to xulrunner-2.0/webkit: At this point this will probably mean to drop most of the remaining stuff from the archive
[16:45] <pitti>   * Today we did the final decisions about the remaining xulrunner rdepends, looks like we can actually get rid of both 1.9.2 and 2.0 by final (which is pretty much a must for our own sanity)
[16:45] <pitti>   * Various "test that this works", discuss user testing
[16:45] <pitti> RC bugs:
[16:45] <pitti>  * Slew of new bug reports from beta-1, as expected
[16:45] <pitti>  * details: https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus#rcbugs
[16:45] <pitti>  * biggest blocker here is bug 663294, but we just got a test binutils from doko which will hopefully resolve that without having to resort to workarounds like using gcc-4.4
[16:45] <pitti>  * The others are not blocked and are just a time/manpower issue
[16:45] <pitti> njpatel | I will buy many beers, can we push freeze time to 11:00 UTC or something?
[16:45] <pitti> ..
[16:45] <skaet> Thanks pitti!
[16:45] <skaet> in terms of unity drop on monday
[16:46] <skaet> probably a question of how late you're willing to work (or slangasek)
[16:46] <skaet> and how much else is still landing
[16:46] <dbarth> note that the offer for beer stands and can be doubled
[16:46] <pitti> I had assumed starting to test the Tuesday images would be enough, or do you think it's too late?
[16:47] <pitti> we didn't get structural changes in the last week, after all
[16:47] <pitti> or building them at 1300 UTC then
[16:47] <pitti> (on Monday)
[16:47] <skaet> pitti,  given the wubi testinging not working up til now,  would like the QA team to have images to start sniff testing as soon as possible.
[16:47] <pitti> skaet: that should be fine
[16:47] <pitti> first round of images Monday morning, next ones Tuesday morning?
[16:48] <pitti> so we can accept OMG, really safe, and unity during Monday?
[16:48] <skaet> jibel,  will that work for you?
[16:48] <pitti> (totally +1 for freezing during that time, and only doing manual review, of course)
[16:49] <jibel> skaet, yes, that's fine.
[16:49] <skaet> ok,  everthing else is 0900,   unity is 1300.
[16:49] <skaet> that will give us a set of images to start the sniff testing on, and find the OMG's
[16:49] <njpatel> We'll be available for any criticals you guys need fixing too, didrocks and seb128 have been alerting them to us as usual but even after release, we only have Unity to focus on right now
[16:49] <pitti> skaet: sounds good
[16:50] <njpatel> skaet, pitti , thank you :)
[16:50] <skaet> and then hopefully have the tuesday images AM for the final validation.
[16:50] <seb128> skaet, thanks
[16:50] <seb128> didrocks, ^
[16:50] <didrocks> yeah, got it, thanks :)
[16:50]  * skaet notes that AM is pitti and jibel AM for the images,  not skaet am ;)
[16:50] <dbarth> right, thanks guys
[16:50] <pitti> oh, another thing
[16:51] <pitti> bug 725434 is the other "interesting" one on our list
[16:51] <pitti> we have thrown around splitting the package etc., but it's all opening a can of worms
[16:51] <skaet> :(
[16:51] <pitti> summary is that at this point we have to screw wayland to unscrew Nvidia users
[16:51] <pitti> as wayland at this point is a developer only thing, but there are millions of nvidia users out there
[16:51] <pitti> so we'll have to rever the EGL support from cairo
[16:52] <pitti> as we can't fix the nvidia driver
[16:52] <pitti> and instead provide it in a PPA
[16:52] <pitti> this will also mean to break wayland in ubuntu without the PPA, though
[16:52] <skaet> thanks for raising,  yes, that makes sense (unfortunately).
[16:52] <skaet> nvidia drivers working is priority.
[16:53] <skaet> any other questions?
[16:53] <skaet> [Topic] Ubuntu One Team - joshuahoover
[16:53] <MootBot> New Topic:  Ubuntu One Team - joshuahoover
[16:53] <joshuahoover> [LINK] https://wiki.ubuntu.com/UbuntuOne/NattyReleaseStatus
[16:53] <MootBot> LINK received:  https://wiki.ubuntu.com/UbuntuOne/NattyReleaseStatus
[16:53] <joshuahoover> details on where we're at with our natty work and releases are in the link above
[16:53] <joshuahoover> UI FFE #733327 was released just a bit ago
[16:53] <joshuahoover> we'll be doing more package releases early next week that will take care of the rest of the bugs linked to in the list above
[16:54] <joshuahoover> and that's it for this week for u1 - questions?
[16:54] <joshuahoover> --
[16:54] <seb128> when is early next week known that freeze is monday at 9?
[16:54] <skaet> thanks joshuahoover
[16:54] <seb128> (I noticed a few ubuntuone-client-gnome crash fixes pending upload that I want to see in natty)
[16:54] <joshuahoover> seb128: i meant monday at the latest...most should be done yet today
[16:54] <skaet> joshuahoover, 0900 freeze on monday...  ?
[16:55] <skaet> heh
[16:55] <joshuahoover> skaet: yes :)
[16:55] <skaet> :)
[16:55] <skaet> thanks!
[16:55] <skaet> any questions?
[16:55] <skaet> [Topic] Kubuntu Team update - Riddell
[16:55] <MootBot> New Topic:  Kubuntu Team update - Riddell
[16:55] <Riddell>  * KDE SC 4.6.2 is in, still compiling away on ARM
[16:55] <Riddell>  * plasma-desktop crashes on today's live CD, it's due to a patch we added, I'm taking a look at it but we can take it out if I don't figure it out
[16:55] <Riddell>  * plasma-mobile also crashes, new package on revu due to go in shortly
[16:55] <Riddell>  * http://goo.gl/HbXHe 6 bugs milestoned for beta 2
[16:55] <Riddell>  * bug 744812 is high importance, waiting on sladen to confirm upload with workaround
[16:55] <Riddell> ..
[16:56] <Riddell> oh and docs didn't make the freeze :( due this weekend I'm told
[16:56] <skaet> Thanks RIddell
[16:57] <skaet> there were some bugs showing up from the iso testing, that are on the agenda.   Have you had a chance to look, at them?
[16:58] <skaet> please feel free to remove if they aren't significant.
[16:58] <Riddell> skaet: I'll take a look after the meeting
[16:58] <skaet> Thanks!
[16:58] <skaet> any other questions?
[16:59] <skaet> [Topic] Desktop Experience Team Update - dbarth
[16:59] <MootBot> New Topic:  Desktop Experience Team Update - dbarth
[16:59] <dbarth> hi
[16:59] <skaet> :)
[16:59] <dbarth> Report at https://wiki.ubuntu.com/DesktopExperienceTeam/NattyReleaseStatus
[16:59] <dbarth> the gist of it being that
[16:59] <TheBIGone> There a way to play game on ubuntu... the newest game like Starcraft II
[16:59] <TheBIGone> ?
[16:59] <dbarth> we released unity 3.8.4 with almost 80 bugs fixed
[16:59] <dbarth> new release of compiz as well with test logs @ https://wiki.ubuntu.com/Unity/QA/TestLog
[17:00] <dbarth> a11y regressions (again) but we're on top of the cpu problem here
[17:00] <dbarth> https://bugs.launchpad.net/bugs/754377
[17:00] <dbarth> the FFE front is hopefully stabilizing
[17:00] <dbarth> https://bugs.launchpad.net/ayatana-design/+bug/754583 is the last one
[17:01] <dbarth> the code is ready and i hear thta it is considered positively- it's mostly based on user feedback that we want to address before the hard freeze
[17:01] <cjwatson> TheBIGone: this is a meeting channel, and there is a meeting in progress - please try #ubuntu instead
[17:01] <pitti> dbarth: I think that just pretty much got turned down, even by sabdfl himself now
[17:01] <dbarth> nothing major on the u-foundations side, except the CJK problem
[17:02] <dbarth> ah, that happened during my call then; will update you in a bit
[17:02] <dbarth> the CJK problem https://bugs.launchpad.net/bugs/745243 requires changes in different packages outside of the strict unity scope
[17:03] <dbarth> we've proposed a ppa or an oem port so far; ie there's not much we think we can do that late in the cycle
[17:03] <dbarth> ..
[17:03] <pitti> dbarth: I suppose that's all internal logic, so at worst we could SRU it?
[17:03] <dbarth> yes
[17:03] <dbarth> with a lot of testing though
[17:04] <TheBIGone> cjohnston okay
[17:04] <dbarth> there are 2 options to fix the issue
[17:04] <pitti> or do you think it's bad enough that we should default to gnome for CJK locales?
[17:04] <TheBIGone> but I have never used UBUNTU
[17:04] <TheBIGone> so why Ubuntu is better than windows
[17:04] <pitti> TheBIGone: please, #ubuntu-users
[17:04] <dbarth> it's not a locale problem afaict, it's turning cjk support in libxapian
[17:04] <skaet> dbarth,  will add 745243 to the list.   Have you had a chance to look at the bugs on the agenda?
[17:05] <dbarth> but that would have to be tested with all of the apps that link with it
[17:05] <dbarth> skaet: not in details, sorry
[17:05] <skaet> dbarth,  ok,  just want to make sure the importances are correct.
[17:05] <dbarth> the high/crtiical ones should be on our the list for our last upload
[17:05] <skaet> so if you cold take a pass after the meeting, that would be appreciated.
[17:05] <dbarth> i can double check that
[17:06] <dbarth> right
[17:06] <skaet> thanks dbarth!
[17:06] <skaet> any other questions?
[17:06] <skaet> [Topic] ARM team update - ogra
[17:06] <MootBot> New Topic:  ARM team update - ogra
[17:06]  * ogra_ waves
[17:06] <skaet> :)
[17:07] <ogra_> Status is at:
[17:07] <ogra_> [LINK] https://wiki.ubuntu.com/ARMTeam/ReleaseStatus/Natty
[17:07] <ogra_> --
[17:07] <ogra_> Summary:
[17:07] <ogra_>  * OMAP4 work on sound implementation is ongoing pulseaudio and alsa patches are being adjusted for bug 746023
[17:07] <MootBot> LINK received:  https://wiki.ubuntu.com/ARMTeam/ReleaseStatus/Natty
[17:07] <ogra_>  * TI PPA icon should be back on the desktop (needs verification, no image builds possible atm)
[17:07] <ogra_>  * unity-2d was updated to the final release
[17:07] <ogra_>  * banshee is the default music player on arm too now (thanks to NCommander)
[17:07] <ogra_>  * ARM specific FTBFS list for main has grown a bit again, but all under control.
[17:07] <ogra_> --
[17:07] <ogra_> Image status:
[17:07] <ogra_>  * Netbook images are currently broken, waiting for the archive to settle
[17:07] <ogra_>  * Headless/serial image works fine
[17:07] <ogra_> --
[17:07] <ogra_> Specs:
[17:07] <ogra_> Entire status: http://people.canonical.com/~platform/workitems/natty/ubuntu-armel.html
[17:07] <ogra_> Milestone: http://people.canonical.com/~platform/workitems/natty/ubuntu-armel-ubuntu-11.04-beta-2.html
[17:07] <ogra_> --
[17:07] <ogra_> Bugs being worked on for beta-2:
[17:07] <ogra_>  * 747247
[17:07] <ogra_>  * 746023
[17:07] <ogra_>  * 744862
[17:07] <ogra_>  * 746137
[17:07] <ogra_>  * 651302
[17:07] <ogra_> ..
[17:08]  * skaet likes new separator character. ;)
[17:08] <ogra_> this bug might need a freeze exception, diwic and TheMuso are working with TI on patch adjustment, i'm not sure when they will be ready
[17:08] <skaet> ogra_, understood.
[17:08] <ogra_> i hope it will be fine over the weekend, both audio devs of TI sit in mexico, so it might be that we get the final patchset only later on monday
[17:09] <ogra_> thats all :)
[17:09] <ogra_> ..
[17:09] <skaet> re: bug 67544 - is it really high,  its been lingering for a while?
[17:09] <ogra_> lamon is working on that one, no ?
[17:09] <ogra_> at least he has it assigned
[17:10] <skaet> ogra_, no progress of entire release, so wondering if we should be carrying it.
[17:10] <ogra_> not sure, i'll ask him
[17:10] <skaet> thanks
[17:10] <skaet> are all the bugs on the agenda at the right priority?
[17:10] <skaet> (and appropriate for the arm team).
[17:11] <cjwatson> it's been assigned to lamont since 2010-01-26; however, due to the constraints on this kind of bootstrapping, it does need his involvement
[17:11] <doko> well, I think somebody else from is could retry this
[17:11] <ogra_> i think so, i'll double check after the meeting
[17:11] <ogra_> (sorry, big lag here)
[17:11] <skaet> would appreciate it if you could take a pass at them after the meeting, and double check they should be on the list.   I'll add the ones you've got to the list.
[17:12] <ogra_> Yep
[17:12] <skaet> thanks ogra_ :)
[17:12] <cjwatson> doko: lamont is the Ubuntu OSA, they'll likely assign it straight back to him :)
[17:12] <cjwatson> I'll ask him though
[17:13] <skaet> any other questions for ogra_ ?
[17:13] <skaet> [Topic] MOTU team update - ScottK
[17:13] <MootBot> New Topic:  MOTU team update - ScottK
[17:13] <TheBIGone> skaet what`s that chan .. for what you use it ?
[17:13] <lamont> g'morning
[17:14]  * lamont will wear his developer with uOSA powers this weekend and throw that against the wall and see if maybe it sticks this time
[17:14] <skaet> TheBIGone, please wait until you see after the endmeeting, for general questions.
[17:14] <cjwatson> TheBIGone: please, this is a meeting room.  I'm sure you wouldn't walk into a professional meeting room and ask questions outside the agenda
[17:14] <TheBIGone> okay .. no problem I`ll just read :)
[17:15]  * skaet looks around for ScottK?
[17:15] <Riddell> he hasn't been around today that I've noticed
[17:15] <skaet> thanks Riddell
[17:16] <skaet> [Topic] Linaro update - JamieBennett
[17:16] <MootBot> New Topic:  Linaro update - JamieBennett
[17:17] <skaet> hmm,  no JamieBennett, it appears...
[17:17] <skaet> [TOPIC] any catch up comments from prior questions?
[17:17] <MootBot> New Topic:  any catch up comments from prior questions?
[17:18] <skaet> ok
[17:18] <skaet> doesn't seem like we'll get updates
[17:18] <skaet> [TOPIC] any other release concerns/comments/questions?
[17:18] <MootBot> New Topic:  any other release concerns/comments/questions?
[17:19] <skaet> going once
[17:19] <skaet> twice
[17:19] <skaet> #endmeeting
[17:19] <MootBot> Meeting finished at 11:19.
[17:19] <ogra_> thanks skaet
[17:19] <pitti> thanks everyone
[17:19] <skaet> Thanks jibel, ara, jdstrand, cjwatson, ogasawara,  pitti, zul, joshuahoover, Riddell, dbarth, ogra
[17:20] <joshuahoover> thanks skaet
[17:20] <jdstrand> thanks skaet
[17:21] <skaet> TheBIGone,  #ubuntu is for general questions,   #ubuntu-meeting is for team meetings (which we just had,  others meet here too).  :)
[17:21] <maco> an also #ubuntu-offtopic for chatter
[17:22] <jibel> thanks for chairing skaet
[17:23] <lamont> skaet: ogra_: I'll see what I can do with fpc/armel this weekend - maybe on a current beaglexm it will actually build from source... that would be a wonderful change from the last 2 or 3 attempts
[17:23] <ogra_> i bet it will :)
[17:23] <skaet> thanks lamont.  :)
[17:25] <lamont> ogra_: if it doesn't, I'll reject the bug as invalid. :-p
[17:25] <ogra_> heh
[17:25] <lamont> or maybe not....
[17:25] <ogra_> no, better wait for the pandas
[17:25] <ogra_> :)
[17:26] <lamont> ogra_: if it fails on beaglexm, I'll try it on a random panda I'm aware of
[17:26] <ogra_> they will fix the world and make us all rich and happy
[17:27] <ogra_> ... and beautiful :)
[17:27] <skaet> :)


[02:09] <imgbot> [03:29] <imgbot> [03:29] <imgbot> [06:08] <davmor2> popey: confirmed ota for all devices has wifi disabled
[07:17] <popey> davmor2: intentional?
[07:17] <didrocks> hey popey! how was your travel?
[07:17] <popey> great!
[07:18] <didrocks> the 1h jetlag isn't terrible, right? :p
[07:18] <didrocks> do you confirm they really have the wrong type of plug btw? :)
[07:18] <popey> ☻
[07:20] <popey> ['/90
[07:32] <davmor2> popey: I assume not
[07:32] <didrocks> hey davmor2!  (I guess you have QA folks there)
[07:53] <bzoltan> didrocks: OK, thanks. I will look around. I have attached all the autopilot logs to the Silo15 sheet.. that should help a bit.
[07:54] <didrocks> great :)
[08:02] <Mirv> didrocks: they also drive on the wrong side of the road
[08:04] <didrocks> Mirv: wrong plug, wrong side of the road but good timezone
[08:04] <didrocks> I give them 33% then
[08:10] <asac> didrocks: do they have UK plug?
[08:11] <didrocks> asac: yeah…
[08:11] <asac> didrocks: can you ping me in 20 seconds? wanbt to check something :)
[08:12] <didrocks> asac: ping!
[08:12] <asac> didrocks: ack. thanks!
[08:12] <didrocks> yw :)
[08:12] <sil2100> ;p
[08:13] <asac> didrocks: wanted to check what the time offset ist hat bip displays here... seems it displays UTC time
[08:13] <didrocks> your bip service is in an UTC machine?
[08:13] <asac> yeah
[08:13] <asac> seems so :)
[08:16] <Laney> wait, do they drive on the right (left) side there?
[08:16] <Laney> I like the sound of this place!
[08:17] <didrocks> Laney: right is right, left can't be right. It's in the name! :)
[08:18] <Laney> rong!
[08:21] <ogra_> oh ! 37 looks really nice on the dashboard
[08:22] <asac> :)
[08:23] <ogra_> that was surely worth all the hassle on thu and fri :)
[08:23] <seb128> Laney, it was a British colony until 1974
[08:23] <seb128> Laney, so it's pretty much on u.k standards
[08:23] <Laney> yeah
[08:23] <sil2100> ;)
[08:23] <Laney> I knew about the plugs, but not about the road side
[08:23] <Laney> but it does make sense
[08:24] <sil2100> ogra_: we even had 8 tests ran on manta!
[08:24] <ogra_> lol
[08:24] <sil2100> All of them were a big success as well
[08:24] <asac> when did manta fall over?
[08:24] <asac> 26 is the last image that gave more than 0 results?
[08:24] <asac> guess 27 is when it fell apart
[08:25] <ogra_> asac, it never worked right ... the devices started failing around 27 though
[08:25] <sil2100> asac: there were networking issues there, from what I remember someone mentioned driver failures
[08:26] <ogra_> (but until someone makes Mir/oxide behave it is pretty unusable anyway)
[08:26] <ogra_> right, cyphermox is looking actively into it
[08:26] <veebers> Saviq: hey how's it going. Can you you let me know when you're done with the gatekeeper? :-)
[08:26] <sil2100> You can always use it as a digital picture though
[08:26] <Saviq> veebers, oops, if you need it cancel my job
[08:26] <ogra_> heh, yeah
[08:27] <ogra_> as long as you dont want to display pics from a html site
[08:27] <ogra_> :)
[08:27] <Saviq> veebers, didn't think you guys would still be around
[08:27] <veebers> Saviq: well, if you need the run I can wait a little bit
[08:27] <veebers> Saviq: we're currently in Malta for a sprint
[08:27] <Saviq> veebers, aah that explains things ;)
[08:28] <Saviq> veebers, you could just queue the job now
[08:28] <veebers> Saviq: aye, good point I'll do that :D
[08:28] <ogra_> Wellark, so we have two lindicator-network-service crashers during dualer-app and messaging-app tests on mako (this is with ofono-phonesim-autostart installed FWIW) see http://ci.ubuntu.com/smokeng/utopic/touch/mako/37:20140519:20140513.2/8093/ (click on the test name and scroll down to find the .crash files)
[08:29] <ogra_> *dialer-app ...
[08:29] <ogra_> thought you would be interested :)
[08:31] <sil2100> ogra_: do you know if psivaa is on the sprint this week or the next?
[08:31] <ogra_> is he QA ir CI ?
[08:32] <psivaa> sil2100: on the way
[08:32] <ogra_> QA is there this week i think
[08:32] <ogra_> ha
[08:32] <psivaa> not to the sprint but to the meeting. hangout is failing me
[08:46] <sil2100> Too many things happening right now, geh!
[08:47]  * sil2100 wonders if anything landed inbetween 37 and now
[08:47] <ogra_> i was asking if you want the summary :P
[08:49] <xnox> didrocks: wouldn't the right currency push it to 50%? =)
[08:49] <ogra_> 34 fixed a firewall test issue (py2->3 switch) ... and had a unity8 landing, as well as the final indicator-network fix
[08:49] <didrocks> xnox: well, did you here about what happened between Malta and euro? :p
[08:49] <ogra_> 35 had another unioty8 and addressbook-app landing
[08:50] <didrocks> xnox: so not sure I'm going to vote for it ;)
[08:50] <ogra_> in 36 Laney has gone wild and uploaded our seed !! (for desktop session changes)
[08:50] <ogra_> and 37 had nothing interesting
[08:50] <ogra_> sil2100, ^^^
[08:51] <xnox> didrocks: not sure what happened between Malta and euro, but i do know what happened between Lats and Euro =) which was only this year.
[08:53] <popey> Laney: I only noticed the road side half way to the hotel from the airport
[08:54] <Laney> "wait, everything is normal"
[08:54] <popey> very.
[08:54] <ogra_> lol ... normal
[08:54] <popey> its nice not being the guy hogging the mains strip
[09:05] <popey> davmor2: video lens, put videos on device, check out thumbnails - they're broken
[09:05] <popey> saw this on #36 last night and #37 today
[09:06] <popey> imgur.com/p0oiNEo
[09:06] <popey> like that
[09:09] <sil2100> ogra_: I meant like, if anything landed after 37 ;)
[09:10] <sil2100> ogra_: since I'm thinking about publishing UITK, and prefered to have an image 'before' that
[09:10] <sil2100> brb, vet
[09:25] <mhr3> Saviq, ^^ see the imgur link
[09:26] <Saviq> mhr3, :|
[09:30] <Wellark> ogra_: ok. thanks! isn't the smoketester doing retraces automatically? :(
[09:36] <ogra_> i dont think so
[09:37] <ogra_> Wellark, oh, and it seems we still come up with wifi off after a flash .... which might be fine on first boot but is surely wrong after an OTA upgrade ... popey opened a bug for  that
[09:37] <ogra_> (works fine after enabling wlan again)
[09:42] <Wellark> ogra_: I would still think the wifi off thingy relates to lower level
[09:42] <t1mp> sil2100: do we still need QA signoff for the landing in silo15? I think that's the only thing we are still waiting for
[09:44] <Wellark> ogra_: so, how do I retrace that thing manually?
[09:45] <ogra_> dunno, there is a wikipage for that ... apport-retrace or so
[09:51] <mhr3> Mirv, can i have silo for #36?
[09:52] <mhr3> 35
[09:52] <Mirv> mhr3: sure
[10:16] <sil2100> Damn
[10:16]  * sil2100 is back
[10:16] <sil2100> t1mp: no, no sign-off needed right now
[10:17] <t1mp> ok, thanks
[10:20] <sil2100> t1mp: I'll try publishing it in some nearest minutes
[10:21] <t1mp> sil2100: great
[10:30] <Mirv> ogra_: ui-toolkit needs packaging ack, they depend on one more module from qtdeclarative-opensource-src: https://ci-train.ubuntu.com/job/landing-015-2-publish/21/artifact/packaging_changes_ubuntu-ui-toolkit_0.1.46+14.10.20140516-0ubuntu1.diff
[10:30] <Mirv> t1mp: sil2100: I think you are talking about the same landing ^ :)
[10:30] <ogra_> Mirv, oooh i see my name imn there ACK ACK ACK !!!
[10:30] <ogra_> :)
[10:31] <Mirv> that was easy :)
[10:31] <sil2100> :)
[10:31] <ogra_> no more crazy vibrating when touching buttons :)
[10:31] <Mirv> +1 to that
[10:31] <sil2100> +1
[10:32] <sil2100> I was still looking at a possible image before publishing that one, but well, it's not that important - we have all we need in 37
[10:32] <ogra_> hmm, all these bug references ... is the janitor evn reacting to such entries ?
[10:33] <ogra_> should be (LP: #nnnnnn)
[10:33] <Mirv> sil2100: oh, I figured there weren't much landed after 37 that'd need a separate image
[10:34] <sil2100> Mirv: yes, as I said, all we need is in #37, so it's cool
[10:34] <sil2100> Just wanted to make sure, that's why I wasn't publishing instantly :)
[10:49] <Wellark> ok,  errors.u.c does not have stack traces
[10:50] <Wellark> and pete-woods told me that it seems that retracing seems to be totally broken and has been for some time now
[10:50] <Wellark> is this a known problem and is someone working on it?
[10:51] <pete-woods> Wellark: it doesn't quite look like retracing itself that is broken, the original stacktraces appear not to be being saved
[10:51] <pete-woods> Wellark: e.g. if you look into a specific crash here (https://errors.ubuntu.com/oops/90362158-dd16-11e3-bb6e-fa163e707a72)
[10:51] <pete-woods> there's just no stacktrace field at all
[10:51] <Wellark> or these ones https://errors.ubuntu.com/problem/f761f1b6abedfe3a66f40e2108453a087f22523c
[10:52] <Wellark> obviously a retrace has been made to be able to generate the "function"
[10:52] <Wellark> (title)
[10:52] <Wellark> but then it's lost.
[10:53] <Wellark> which makes it pretty much quite impossible to reliably figure out what's going on.
[10:54] <ogra_> well, you could pull the .crash file to your own devices and retrace yourself
[10:55] <Wellark> ogra_: errors.u.c does not offer the .crash files
[10:55] <ogra_> they are linked at the test results i gave you above
[10:56] <Wellark> ogra_: this is not about those tests. this is about why errors.u.c is not providing the stacktraces anymore
[10:57] <Wellark> + there is no way of making a connection between a random .crash file you get from somewhere and a report in errors.u.c.
[10:57] <ogra_> i think there was a race that the upload gets corrupted or so ...
[10:57] <Wellark> well, that's quite critical
[10:57] <ogra_> there is ... there is a device ID involved
[10:58] <ogra_> but someone from CI would have to determine it for you i guess
[10:59] <Wellark> is anyone working on getting the stactraces on errors.u.c fixed?'
[11:00] <Wellark> is there a bug filed for it?
[11:00]  * ogra_ has no idea, ...
[11:00] <ogra_> probably ev knows
[11:01] <sil2100> davmor2: just give me a sign once you have some dogfooding results
[11:01] <ogra_> ++
[11:01] <sil2100> davmor2: I personally wouldn't block promotion on the wifi-not-enabled-by-default thingy, but it's you as the QA-master to decide ;)
[11:02] <ogra_> yeah, not enabled after installl isnt a biggie ... switched off after OTA is something that needs to be mentioned in your mail though
[11:02] <ogra_> (but i agree it is no blocker)
[11:03] <sil2100> Right, +1 on mentioning that
[11:03] <Wellark> sil2100: we need more info on that "wifi off"
[11:03] <Wellark> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1320780
[11:09] <sil2100> Wellark: valid points
[11:09] <sil2100> davmor2: ^^
[11:29] <ev> pete-woods, Wellark, ogra_: completed stacktraces will never appear next to an instance of an error (an OOPS). This is because we group instances of crashes together by their stacktrace (well, a signature formed from it). So the problem page (a collection of crashes) should show the stacktrace
[11:30] <ev> obviously it's not for that particular one
[11:30] <ev> and it's not immediately clear why
[11:30] <ev> I'll ask bdmurray to have a look at it tomorrow
[11:30] <Wellark> ev: do you need more examples?
[11:30] <ev> any you have would help
[11:30] <Wellark> there is now one for hud and one for indicator-network
[11:30] <Wellark> pete-woods: do you have more examples?
[11:33] <pete-woods> Wellark: it actually looks like the HUD examples "fixed themselves" since I looked last https://errors.ubuntu.com/problem/b649801824262e51a5430cdf72a85fc3fe951765
[11:34] <pete-woods> it claims both a failure to retrace, but now has actually retraced
[11:35] <ev> Wellark, pete-woods: I've created this task to track it: https://app.asana.com/0/11345516654327/12422265621458 (you should have invites to Asana)
[11:36] <Wellark> ev: thanks!
[11:48] <mhr3> sil2100, /me off for today, if someone asks you to set one of my silos as tested, pls do ;)
[11:52] <sil2100> mhr3: aye! ;)
[11:56] <davmor2> sil2100: no worries it sounds like design are saying it's not them but I need to chase it down so more
[11:58] <Mirv> argh, why oh why I've problems running ap locally on #37 for address-book-app/calendar/clock. always failures.
[12:00] <davmor2> Mirv: I got no issues here, are you running autopilot tests?
[12:00] <sil2100> Mirv: how is it failing?
[12:20] <Mirv> davmor2: yes, AP
[12:20] <Mirv> davmor2: you got no issues, great! #37? there's a really nice PPA called ppa:ci-train-ppa-service/landing-005 that just begs you to upgrade to!
[12:21] <Mirv> sil2100: the tests just fail. on the other hand, now my phone is crashing on bootup so I guess it's maybe a sign to do a --bootstrap --wipe...
[12:21] <sil2100> uh
[12:22] <Mirv> I repeat that I'd like to understand what's happening a bit more often..
[12:28] <davmor2> Mirv: no there isn't :P
[12:39] <cgoldberg> thomi:
[12:39] <cgoldberg> $ python3 -m autopilot.run run autopilot.tests.functional.test_autopilot_functional.AutopilotVerboseFunctionalTests.test_local_module_loaded_and_not_system_module
[12:40] <ogra_> sil2100, davmor2, any news on promotion ?
[12:41] <didrocks> are you really considering promotion for an image with wifi off by default?
[12:41] <ogra_> didrocks, its a single switch you need to flick after flashing
[12:42] <ogra_> (and only then)
[12:42] <didrocks> seems like we are getting down on our quality expectations though
[12:42] <sil2100> didrocks: it's for davmor2 to decide - but since you can 'enable' it easily, I wouldn't personally block on that
[12:42] <sil2100> QA makes the final decision though
[12:42] <didrocks> yeah, let's see
[12:43] <ogra_> i wouldnt see it as a drastic blocker of you have to enable it once after the flash ...
[12:44] <davmor2> sil2100: no I'm temped to say not to block on it as you only need to flick it on and then it works
[12:46] <sil2100> davmor2: any more news on design about this? :) Since you mention they say they most probably didn't intend this
[12:46]  * sil2100 still waits for UITK to move out of proposed
[12:47] <davmor2> sil2100: yeah it appears that there is a lot of discussion around it Wellark though didn't actually set it up so it sounds like a race condition
[12:47] <sil2100> davmor2: did you see his comment on the bug btw.?
[12:47] <ogra_> already passed all tests ... next publisher run should promote it
[12:47] <sil2100> davmor2: (I know you have a lot going on there thought ;) )
[12:48] <davmor2> sil2100: #phablet
[12:48] <sil2100> ogra_: would like to have an image kicked after UITK lands ;) What do you say?
[12:48] <ogra_> ++
[12:48] <ogra_> definitely
[12:51] <davmor2> sil2100: so other than the wifi issue I don't really see anything more broken on this image
[12:51] <ogra_> davmor2, 3G is fine =
[12:51] <ogra_> ?
[12:53] <davmor2> ogra_: I can't test it, I have no data connection.  Please feel free to add comments on it
[12:53]  * didrocks always fears when he heard "it's a race" and we don't have great understanding of it
[12:53] <ogra_> davmor2, that would require me to have a device to test -proposed
[12:53] <davmor2> ogra_: as far as I can tell it is only wifi here that is effected
[12:54] <ogra_> i thought you guys had test SIMs over there for exactly this
[12:54] <davmor2> ogra_: no I have my sim
[12:55] <ogra_> davmor2, i mean there were management discussions to bring a handfull of SIMs for the dogfooders
[12:55] <ogra_> ask pmcgowan ...
[12:55] <davmor2> will do
[12:55] <davmor2> brb
[12:56] <ogra_> i know popey checked 3G on 36 ...
[12:56] <ogra_> (but thats indeed not 37)
[12:56] <sil2100> Let's test the image that's the candidate
[12:56] <didrocks> ogra_: do you understand exactly what changed to not have wifi on first startup?
[12:56] <ogra_> didrocks, nope
[12:57] <didrocks> that's… concerning
[12:57] <ogra_> didrocks, but we know the symptoms and their impact
[12:57] <sil2100> didrocks: no worries, I don't intend to promote it like now before there is more clarification
[12:57] <sil2100> I saw some discussion on #phablet
[12:57] <didrocks> ogra_: exact impact? do you have enough reboot to ensure it's not a race and can happen randomly, even on configured upgraded setup?
[12:57] <ogra_> didrocks, it definitely needs research, but as long as it works and only has that little annoyance i dont think we need to block on it
[12:58]  * didrocks feels it's a potential issue that can strike back in a worse state and side-effects
[12:58] <ogra_> didrocks, it happens after any flash action ... but works fine after reboots
[12:58]  * ogra_ doesnt think it is that bad
[12:58] <ogra_> its an annoyance
[12:59] <didrocks> but we don't really know the consequences because we don't know the why
[12:59] <ogra_> and as long as we know people look at it i'm confident we'll get a fix soon
[13:01] <ogra_> didrocks, the problem is you cant just bisect it ... the whole set of images of the last week had massive network issues due to various new issues every day ... getting the image out to users is the best way to get more data on the issue ...
[13:01] <didrocks> ogra_: and potentially to put people using their phone as daily driver on trouble
[13:02] <ogra_> well
[13:02] <ogra_> making them flick a switch once, after OTA or fresh flash
[13:02] <ogra_> surely not such a big trouble
[13:02] <didrocks> without knowing the cause, you are not clearly not sure about the consequence and trouble :)
[13:02] <ogra_> we know it is a problem related to booting ... and obviously only happens after flashing
[13:03] <didrocks> but I guess I gave my opinion, then, you are the one in charge :)
[13:03] <ogra_> nope, i'm not :)
[13:03] <ogra_> i also only give my opinion here :)
[13:03] <ogra_> last word is on sil2100 and davmor2
[13:04] <ogra_> i know that Wellark looks into indicator reaalted issues and cyphermox into NM urfkill and driver related ones
[13:04] <ogra_> so the problem is in god hands
[13:04] <ogra_> *good
[13:05]  * didrocks notices ogra_ retrogaded some people from "god hands" to "good hands"
[13:05] <ogra_> heh
[13:06] <Mirv> ogra_: rmadison tells me ui-toolkit is in release pocket now
[13:06] <ogra_> build triggered
[13:07] <sil2100> o/
[13:10] <davmor2> sil2100: ogra_: there is a guy here with a local sim 3g works
[13:10] <ogra_> awesome !
[13:14] <imgbot> [13:15] <jdstrand> I'm looking at http://ci.ubuntu.com/smokeng/utopic/touch/mako/36:20140518:20140513.2/8078/security/1137284/, which passed, but the 'Console Log' and 'Artifacts' seems to be wrong
[13:16] <jdstrand> as in, it seems to come from another test run
[13:16] <sil2100> jdstrand: so, we had some issues with 36, some tests didn't run and had to be ran later, maybe that's the reason
[13:16] <sil2100> Let me take a look
[13:16] <sil2100> psivaa: ^
[13:17] <psivaa> sil2100: jdstrand: let me take a look
[13:17] <jdstrand> well, like I said, the 'Test case data' looks ok. it is just that the attached logs all seem to be for a different set of tests. eg, I see nothing about ufw in either
[13:18] <jdstrand> https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/126/console and https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/126/artifact/clientlogs/security/
[13:30] <psivaa> jdstrand: http://pastebin.ubuntu.com/7488517/ is the segment of copying the logs for the security test. are the ufw logs stored somewhere else in the device?
[13:30] <psivaa> i.e. other than /home/phablet/.cache/upstart/
[13:32] <ogra_> most likely in a system path like /var/log
[13:36] <psivaa> ogra_: ok, i can only see /var/log/apt/history.log and /var/log/dpkg.log that has any reference to 'ufw' on a device that ran the security tests.
[13:37] <ogra_> well, there should surely be an upstart log of the upstart job
[13:37] <ogra_> not sure what else ufw logs ... or where
[13:38] <ogra_> jhodapp, we are still seeing a media-hub crash during automated testing, is that still on your plate ?
[13:38] <jdstrand> psivaa: ufw won't log somewhere else. mostly I was confused that console log didn't have stdout/stderr in it
[13:38] <jdstrand> s/ufw/the ufw tests/
[13:39] <ogra_> jdstrand, http://ci.ubuntu.com/smokeng/utopic/touch/mako/37:20140519:20140513.2/8093/security/1139053/
[13:39] <jdstrand> I know
[13:39] <ogra_> that should show stdout on the website at least
[13:40] <jdstrand> what I was saying was that 'Console' did not have it. I'm not blocked, I'm just reporting that the link for 'Console' doesn't have stdout/stderr from the test run
[13:41] <jdstrand> https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/128/console
[13:41]  * ogra_ thinks these console logs are weird anyway ... they have the whole log for all runs usually
[13:41] <jdstrand> ^ (no mention of ufw)
[13:41] <ogra_> you want https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/128/consoleFull
[13:41] <psivaa> jdstrand: ogra_: yea, console log caching is coming in the way i think
[13:41] <ogra_> else the first 1M is cut off
[13:42] <jdstrand> ah, well, we should link 'Console Log' to consoleFull, no? I had never heard of consoleFull
[13:42] <ogra_> i see a lot of ufw mentionings in the "Full" log
[13:43] <ogra_> jdstrand, go to console log, check the top of the log
[13:43] <ogra_> there is a small link
[13:43] <jdstrand> yes, me too. I wouldn't have said anything if the 'Console Log' link in http://ci.ubuntu.com/smokeng/utopic/touch/mako/37:20140519:20140513.2/8093/security/1139053/ went to consoleFull
[13:44] <ogra_> it is well hidden in front of your face ;)
[13:44] <jdstrand> I see the 'Full Log' link now. I missed it
[13:44] <jdstrand> it is pretty small
[13:44] <ogra_> yeah, should be <h2> and <blink> ;)
[13:44] <jdstrand> but I don't see why one wouldn't want to see all the logs. call it user error if you choose, but I think the usability could be improved
[13:45] <ogra_> i guess jenkins is just being clever here
[13:45] <ogra_> (it is properly translated to german, so i suspect its from jenkis itself)
[13:51] <psivaa> jdstrand: doing an MP to try and improve that to direct to consoleFull, hope it'd improve that bit.
[13:51] <jdstrand> thanks! :)
[14:07] <rsalveti> sil2100: can I get a silo for 32?
[14:07] <sil2100> rsalveti: looking
[14:07] <rsalveti> sil2100: platform-api is blocked by landing 01, but that's just a pre-flight silo
[14:07] <rsalveti> aka, in development
[14:08] <rsalveti> nothing should be blocked by it
[14:08] <sil2100> rsalveti: right! Let me get one for you straight away
[14:17] <Mirv> oh right 001 was preplanning only
[14:19] <sil2100> Mirv: indeed ;) I missed that as well somehow
[14:22] <Mirv> if we would live for Train longer it'd be good to simply have separate testing silos
[14:22] <Mirv> s/for/with/
[14:24] <rsalveti> sil2100: thanks!
[14:26] <sil2100> rsalveti: yw!
[14:26] <sil2100> Mirv: we might think about that, such as SRU-silos - but I think just increasing the number of silos would be sufficient
[14:34] <imgbot> [14:34] <imgbot> [14:45] <Mirv> not upgrading, trying these crappy test runs
[14:45] <Mirv> so --wipe --bootstrap helped, but one problem has been flaky network that might bring the wlan AP password dialog to front, and for example clock app at least requires network etc etc.. so I guess I have explanations for the problems I had
[14:46] <ogra_> Mirv, hmm, interesting ... the UITK dep you added seems to be on the image already
[14:46]  * ogra_ sses no added packages
[14:47] <Mirv> ogra_: I didn't add it, but ok
[14:48] <Mirv> there are probably other users of it, but UITK itself started using it only now
[14:48] <ogra_> yeah
[15:25] <Mirv> so another thing I have fairly frequent when running AP tests is that indicator-datetime and evolution-calendar-factory are consuming 100% CPU (well, 50%, or 100% of two CPU:s), which negatively affects tests
[15:38] <popey> sil2100: YO! updated bug 1320780
[15:40] <sil2100> Wellark: ^
[15:40] <sil2100> popey: thanks! :)
[15:44] <Mirv> quite a testing spree that was
[15:50] <sil2100> cyphermox: hi! Are you around already?
[15:50] <sil2100> cyphermox: did you have a look at bug #1320780 ?
[16:01] <sil2100> davmor2: poke, meeting, are you busy?
[16:01] <sil2100> popey: same ^ :)
[16:02] <popey> lemme join
[16:15] <sil2100> popey: beer it is! You deserve it!
[16:16] <cjwatson> Damnit I keep having to restart my livefs tests 'cos you guys have published silos :-)
[16:16] <popey> \o/
[16:18] <ogra_> cjwatson, let it run over night ... canada is off today we dont have an US TZ shift today
[16:18] <ogra_> so landings wont happen i gues
[16:18] <ogra_> s
[16:20] <cjwatson> I need to iterate during the day
[16:20] <cjwatson> It's not a problem, just amusing
[16:20] <ogra_> :)
[16:22] <sil2100> cjwatson: sorry! Just give us a sign when not to land and we'll wait ;)
[16:22] <asac> ogra_: no robert?
[16:22] <ogra_> asac, maple celebration day or some such in .ca today
[16:23] <sil2100> asac: holiday in Canada, but he was on the meeting and will be on the meeting with you :)
[16:23] <asac> inded
[16:23] <asac> sil2100: oh :)
[16:23] <asac> thats cool
[16:23] <sil2100> Maple celebration, sounds nice!
[16:23] <ogra_> asac, he was around in the landing meeting because he said he had a meeting with you later
[16:23] <asac> robru: we can also talk tomorrow!
[16:23] <asac> :)
[16:23] <asac> robru: no need to stick around for me during your public holiday
[16:23] <asac> robru: that was not my intend :/
[16:23] <robru> asac, ah, if it's ok with you.
[16:23] <robru> asac, I scheduled this before I realized it was a holiday
[16:23] <asac> robru: yes of course. if you would have told me, i wouldnt have it schedueld there
[16:24] <asac> robru: go off!!
[16:24] <asac> talk to you tomorrow
[16:24] <robru> asac, ok, see you tomorrow, thanks!
[16:24] <ogra_> and happy maple !
[16:24] <asac> see you and sorry!
[16:24] <ogra_> :)
[16:24] <robru> ;-)
[16:24] <asac> jummy :)
[16:24] <asac> ok tomorrow will be a fun long day
[16:24] <asac> nice
[16:28] <cjwatson> sil2100: no need, but thanks :)
[16:30]  * ogra_ goes to mow the lawn
[16:31] <cjwatson> woo, I now have a local setup that can do ubuntu-touch builds against a silo using a local Launchpad instance
[16:34] <didrocks> cjwatson: nice work! \o/
[16:36] <sil2100> Oh my! This smells CI Airlines :)!
[17:51] <ogra_> plars, in case you feel bored, shorts, filemanager and gallery on flo could need some love too
[18:01] <plars> I'll take a look
[18:05] <sil2100> o/
[18:20] <Wellark> popey: thanks!
[18:20] <Wellark> I've EOD'ed, but let's hope cyphermox has time to look into those
[18:21] <Wellark> at least the "unavailable" state for the wifi device looks suspicious
[19:08] <ogra_> Wellark, do you knwo if anything in the stack ever made use of pm-utils ? we recently dropped it ... (and i still cant find out why)
[19:14] <josharenson> ping fginther
[19:46] <barry> mandel: i think we have at least two regressions in udm that cause failures in s-i.  we really need to add some integration tests to gate landings in udm.
[19:46] <barry> mandel: LP: #1320987 and LP: #1320306


[00:41] <pgquiles> Riddell: ping
[00:44] <Riddell> hi pgquiles
[00:46] <pgquiles> Riddell: hi. Is it already too late to sync witty ( http://packages.debian.org/unstable/witty ) with Debian? (an updated version just got in)
[00:47] <Riddell> nope
[00:48] <Riddell> ah, it's the Wt stuff
[00:48] <pgquiles> yes
[00:48] <Riddell> pgquiles: have you checked it compiles and runs on ubuntu?
[00:48] <pgquiles> Riddell: yes. In fact, it's always available for Ubuntu from my PPA before being available for Debian :-)
[00:49] <Riddell> pgquiles: what's your launchpad username?
[00:49] <pgquiles> Riddell: pgquiles :-)
[00:49] <pgquiles> Riddell: http://launchpad.net/~pgquiles/+archive
[00:50]  * Riddell guesses pgquiles
[00:52] <Riddell> pgquiles: synced
[00:52] <pgquiles> Riddell: thanks!
[00:55] <Riddell> welcome back splitters :)
[00:55] <Riddell> pgquiles: synced incase you missed that
[00:57] <pgquiles> Riddell: I got it, thanks. IRC splits are funny to watch :-)
[02:09] <Riddell> who's still awake?
[02:09] <Riddell> testers needed for http://www.kubuntu.org/~jriddell/tmp/install-package_0.1_all.deb
[02:17] <echidnaman> wow
[02:17]  * echidnaman sees he was pinging out all the time he was away
[02:17] <Riddell> JontheEchidna!
[02:17] <JontheEchidna> it crashes?
[02:17] <Riddell> JontheEchidna: fancy testing http://www.kubuntu.org/~jriddell/tmp/install-package_0.1_all.deb ?
[02:18]  * JontheEchidna didn't notice that jockey crashed when he tested
[02:19] <JontheEchidna> but ya I can test that too
[02:21] <JontheEchidna> Riddell: we might want to steal the launch-kdesudo code from gdebi for software-properties and install-package
[02:21] <Riddell> well, it's a command line only app
[02:22] <JontheEchidna> Riddell: well it currently says to launch with kdesudo if you don't use sudo or kdesudo :P
[02:22] <Riddell> JontheEchidna: right, so jockey or whatever should use kdesudo
[02:23] <JontheEchidna> yeah I've been meaning to give jockey and software-properties gdebi's code...
[02:23] <Riddell> JontheEchidna: code for what?
[02:23] <JontheEchidna> for re-launching with kdesudo if not run with sudo in the first place
[02:24] <Riddell> right
[02:24] <Riddell> JontheEchidna: anyway, how's install-package working for you?
[02:24] <JontheEchidna> It's downloading file 0 of 1
[02:24] <JontheEchidna> (amarok-kde4)
[02:25] <Riddell> good package choice :)
[02:25] <JontheEchidna> and the details list is empty
[02:25] <Riddell> it only shows stuff during install
[02:26] <JontheEchidna> oh, any idea how to make it stop saying my computer needs a reboot? :P
[02:26] <Riddell> reboot?
[02:26] <JontheEchidna> earlier when I was testing update-manager
[02:26] <JontheEchidna> you gave me a command to test the need-reboot functionality
[02:27] <Riddell> rm /var/run/reboot-required
[02:27] <JontheEchidna> oh, duh
[02:29] <JontheEchidna> amarok-kde4 successfully installed
[02:29] <JontheEchidna> everything looked great aside from the "downloading package 0 out of 1" bug
[02:30] <Riddell> hmm, that comes from python-apt
[02:30] <Riddell> so not my fault, uploading :)
[02:30] <JontheEchidna> ;-)
[02:31] <JontheEchidna> so should that be a drop-in replacement for adept-batch?
[02:31] <Riddell> not quite, the command syntax is a bit different
[02:31] <Riddell> ports of jockey and language-selector welcome
[02:31]  * JontheEchidna needs to investigate the jockey crash
[02:32] <JontheEchidna> So is the week before feature freeze always like this? :P
[02:34] <JontheEchidna> dear jesus...
[02:34] <JontheEchidna> oookay... jockey-backed is ****-ed up
[02:34]  * JontheEchidna didn't touch it
[02:35] <JontheEchidna> seems to be throwing a hissy fit with dbus
[02:35]  * Riddell still needs to implement dist upgrade wizard into adept
[02:36] <JontheEchidna> Riddell: did you get anything like this when testing jockey? http://paste.ubuntu.com/39814/
[02:39] <Riddell> nope
[02:39] <Riddell> looks like a whole new crash
[02:40]  * JontheEchidna purges his jockey install and reinstalls the most recent official release
[02:41] <JontheEchidna> crap, happens with jockey from the repos
[02:41] <JontheEchidna> meaning it's a problem with my setup :(
[02:45] <JontheEchidna> this sucks
[02:48] <seele> whoa.. Riddell is still up?
[02:49] <Riddell> nobody to tell me to go to bed tonight :)
[02:49] <seele> hehe
[02:50] <seele> who wants to sleep alone when they can spend time with their IRC friends!
[02:50] <Riddell> exactly
[02:52] <seele> i'm finding some interesting stuff in the data you gave me
[02:53] <seele> i havent scrubbed the data for outliers yet or anything, but i did run some basic numbers on x and y resolutions
[02:53] <seele> 54% of the respondents reported runnign 1024 as their X res
[02:53] <seele> oh wait wait, wrong number
[02:54] <seele> 54% are running between 1024-1280
[02:54] <seele> BUT
[02:54] <seele> 60% are running y res between 768 and 1024
[02:54] <seele> 54% are running at 768
[02:55] <seele> so it's possible the values you pulled for laptop/desktop are valid afterall.. even though they seemed a bit high for laptop when you pasted the preview data
[02:55] <Riddell> 1024x768 is pretty well the norm for low to medium end computers
[02:55] <seele> right.. but there is a lot of 1280x768 going on too
[02:56] <seele> which is more common in laptops than monitors
[02:56] <seele> dell sells widescreen monitors, but i think most of them are larger than 1280x1024
[02:57] <seele> the interesting part (for me at least) is that this tells use we have very limited vertical real estate to work with
[02:57] <seele> screens are getting wider, not taller
[02:58] <Riddell> widescreen gets sales, resultion less so
[02:59] <seele> it looked like there were probably a few tablets submitted too because the resolutions reported were x < y
[03:00]  * claydoh is doing the kde4 fanboi thing on kubuntuforums
[03:00] <claydoh> is the msttcorefonts *not* part of kubuntu-restricted-extras?
[03:00] <Riddell> claydoh: doesn't seem to be
[03:00] <Hobbsee> claydoh: it's not so far.
[03:00] <claydoh> was there a reason maybe?
[03:01] <Hobbsee> hm, i didn't thikn it was in any of them.  obviously not
[03:01] <claydoh> I saw a discussion in the ml archives
[03:02] <claydoh> u-r-s does depend on msttcorefonts
[03:02] <claydoh> afaik
[03:02] <Riddell> patches welcome then :)
[03:03] <Riddell> although liberty fonts might mean there's no need any more
[03:03] <Hobbsee> fixed.
[03:03] <Hobbsee> there was already a patch
[03:03] <claydoh> heh someone already has
[03:03] <claydoh> https://bugs.edge.launchpad.net/ubuntu/+source/ubuntu-restricted-extras/+bug/231094
[03:04]  * Hobbsee doesn't see why ttf-liberation does not suffice, though.
[03:06] <Hobbsee> claydoh: the general reason as to why it wasn't (although i'm not sure how they got in for the other bits) was because i didn't see the point of having a package that effectively depends on everything in multiverse, with it's varying degrees of usefulness.
[03:06] <Hobbsee> and, y'know, fonts aren't generally extra functionality, per se.
[03:08] <JontheEchidna> holy crap, jockey works now
[03:08]  * JontheEchidna has no clue what he did wrong
[03:08] <claydoh> Hobbsee: I do agree with that
[03:08]  * Riddell snoozes
[03:09] <JontheEchidna> Riddell: so from my branch jockey crashes?
[03:09] <JontheEchidna> it doesn't here
[03:10] <JontheEchidna> https://code.edge.launchpad.net/~echidnaman/jockey/jockey-pykde4 , to be sure ;)
[03:13] <seele> 'night Riddell
[03:14] <Riddell> JontheEchidna: how do you run it?
[03:15] <JontheEchidna> Riddell: jonathan@jonathan-desktop:~/Documents/python/jockey-kde4/jockey-pykde4/kde$ sudo python jockey-kde
[03:16] <Riddell> http://paste.ubuntu.com/39816/
[03:17]  * Riddell snoozes
[03:17] <JontheEchidna> that rings a bell, actually
[03:17]  * JontheEchidna remembers something similar
[03:18] <JontheEchidna> but I thought I fixed that in bzr
[03:19] <JontheEchidna> Yeah, I did fix it in bzr, but that was after I made debs
[03:19]  * JontheEchidna remembers he screwed up the .ui file something awful
[03:27] <Hobbsee> claydoh: i see why it would suck to be the head of artwork, after doing u-r-e for a while...
[03:37] <vorian> JontheEchidna: kio-bookmarks uploaded
[03:37] <vorian> thanks again for your contributions :)
[03:49] <JontheEchidna> vorian: cooliosis
[03:49] <JontheEchidna> Did you try it? It's quite neat
[03:50] <JontheEchidna> I found it because commit-digest did a mini-article about it
[03:50] <JontheEchidna> oh lol, I forgot to push up my last to jockey commits to bzr
[03:52] <JontheEchidna> Riddell: When you wake up, update jockey and try it again. ;-)
[04:25]  * JontheEchidna goes to bed
[04:25] <Jucato> night JontheEchidna
[04:29] <vorian> nn
[09:27] <Czessi-m> morning
[09:28] <Czessi-m> Riddell: we found the kubuntu poll-up post in the kde booth box :-)
[15:29] <devfil> Riddell: there?
[15:49] <Riddell> hi devfil
[15:50] <devfil> Riddell: in kdebindings there are two files not installed usr/lib/kde3/libjsconsoleplugin.{la,so}, where should I put them? libkde3-java package?
[15:50] <Riddell> devfil: leave them out
[15:50] <Riddell> we took that out ages ago because it was broken
[15:51] <devfil> Riddell: ok, just to know ;)
[17:16] <taupter> Riddell: ping
[17:34] <Riddell> hi taupter
[17:35] <taupter> Riddell: Hi. :)
[17:35] <taupter> Riddell: Did you see thiago's rant?
[17:35] <Riddell> nope
[17:36] <Riddell> about nvidia?
[17:36] <taupter> Riddell: About the glib-in-Qt event stack making kwin spend 20% of processor time while idle?
[17:36] <Riddell> nope
[17:37] <taupter> Riddell: http://labs.trolltech.com/blogs/2008/08/22/rant-desktop-effects-never-more/
[17:38] <taupter> Riddell: I believe it's the same rant about nvidia. My machines suffer the same problem,
[17:39] <Riddell> and does it help to run kwin with QT_NO_GLIB=1?
[17:39] <taupter> Riddell: and I'm not aware of any Qt program using Glib's event stack anyway,
[17:39] <taupter> Riddell: Yes, QT_NO_GLIB=1 helps greatly.
[17:41] <taupter> Riddell: I'd like to suggest disabling glib support in Kubuntu's Qt packages, or at least disabling it with QT_NO_GLIB=1.
[17:41] <Riddell> taupter: does QT_NO_GLIB=1 for kwin only help?
[17:42] <taupter> Riddell: I'm not sure.
[17:42] <Riddell> JontheEchidna: jockey seems to work now
[17:42] <Riddell> taupter: if it's only a problem for kwin then we can easily enough turn it off for that
[17:44] <taupter> Riddell: I restarted kwin from a konsole here after export QT_NO_GLIB=1
[17:45] <Riddell> taupter: and your problem goes away?
[17:46] <taupter> Riddell: It seems quieter, but plasma and kwin still throw processor spikes regularly. :)
[17:47] <Riddell> would be easy enough to turn off, I'll talk to thiago first though and see what he recommends
[17:48] <taupter> Riddell: Just for the record, here I'm using an Nvidia 7500LE with 1920x1440, and when I disable glib it flies.
[17:49] <taupter> Riddell: Sorry. Nvidia 5700le
[18:26] <devfil> Riddell: dh_shlibdeps -pkommander  -l :debian/kommander/usr/lib
[18:26] <devfil> dh_shlibdeps: command returned error code 11
[18:26] <devfil> make: *** [binary-predeb-IMPL/kommander] Error 1
[18:27] <Riddell> wibble
[18:28] <devfil> Riddell: do you know why I get this error?
[18:29] <Riddell> never seen it before
[18:32] <nixternal> howdy all
[18:36] <JontheEchidna> Riddell: cool
[18:37] <taupter> Riddell: ping
[18:37] <JontheEchidna> Riddell: Once I get it working with the new package-installer it should be good to go
[18:38] <Riddell> hi taupter
[18:38] <taupter> Riddell: Heh. :) Disabling the Glib thing just to kwin does the trick, I confirm here, and
[18:39] <taupter> Riddell: thiago sent me a patch: http://pastebin.ca/1182538
[18:40] <taupter> Riddell: It will disable Glib just to kwin, but he doesn't want to commit it to kde's repos,
[18:40] <nixternal> hrmm, nobody can say hi....jeesh, see if I ever say hi again!
[18:40] <taupter> Riddell: as if he does so nobody will ever try to fix Glib in Qt. :D
[18:41] <taupter> Riddell: And he's right. :D. afaict the patch can be appliet to both 4.1 branch and trunk.
[18:42] <Riddell> taupter: great
[18:42] <Riddell> hi nixternal!
[18:42] <nixternal> hi Riddell :)
[18:42] <nixternal> now I feel some love again
[18:43] <taupter> Riddell: Can I bug you again? :) kmldonkey-kde4 doesn't install, as it depends on libplasma1 but only libplasma2 is installed.
[18:44] <taupter> Riddell: I made a .deb for my own comsumption, and maybe I could help to package some bits of kde4 for kubuntu.
[18:45] <yuriy> ok I've really gotta get designer running to get working on userconfig..
[18:49] <JontheEchidna> yuriy: so it's segfaulting trying to load pykde plugins?
[18:51] <JontheEchidna> oh hey, I don't have python-kde4-dev installed
[18:51] <JontheEchidna> maybe that's why it works
[18:52] <JontheEchidna> still works
[18:53]  * yuriy checks
[18:54] <yuriy> I don't have python-kde4-dev either
[18:54] <JontheEchidna> It worked before and after installing that for me
[18:54] <yuriy> JontheEchidna: where did you get that that's what it was segfaulting on?
[18:54] <JontheEchidna> running it in konsole
[18:55] <JontheEchidna> oh
[18:55] <JontheEchidna> actually I just deleted stuff from /usr/lib/qt4/plugins/designer until it worked
[18:55] <yuriy> this is what I get: http://pastebin.ubuntu.com/39957/
[18:55] <yuriy> yeah you told me that, but it didn't work for me
[18:56] <JontheEchidna> :(
[18:56] <yuriy> and this is last thing from valgrind: http://pastebin.ubuntu.com/39702/
[18:56] <JontheEchidna> would you happen to have the bespin qt4 widget theme installed?
[18:57] <yuriy> no
[18:57] <JontheEchidna> cuz that causes designer to segfault too
[18:58] <yuriy> JontheEchidna: probably should report that if you know specific things
[18:59] <JontheEchidna> bespin is unmaintained
[18:59] <JontheEchidna> it was the original oxygen theme iirc
[18:59] <yuriy> but designer shouldn't segfault on random things
[19:00] <JontheEchidna> ok so taking a random stab here, maybe pyqt3 is conflicting with pyqt4?
[19:02] <yuriy> removed python-qt3 and python-kde3, no luck
[19:02] <JontheEchidna> python-kde3-dev would probably be the offender if pyqt3 was conflicting
[19:03] <yuriy> nope :(
[19:04] <JontheEchidna> damn, this sucks
[19:04] <JontheEchidna> any way I could create the ui file for you?
[19:04] <yuriy> I think I'll need several
[19:05] <JontheEchidna> using userconfig from kde-guidance as a reference?
[19:05] <yuriy> yeah
[19:05] <yuriy> I guess that's doable
[19:05] <yuriy> and bzr branch for the ported one is available
[19:06] <JontheEchidna> what's your LP id?
[19:07] <yuriy> yuriy-kozlov
[19:08] <JontheEchidna> so how have you been doing work without ui files?
[19:08] <yuriy> the original didn't use them
[19:09] <yuriy> I actually prefer to write out GUIs
[19:09] <yuriy> but I don't want to debug what's there, and I figured I'd be nice to the next person who touches it
[19:12] <yuriy> all I've done so far is get it to run and all the dialogs to show up
[19:15]  * smarter <3 amarok2
[19:15] <yuriy> broken for me last I checked
[19:16] <smarter> yuriy: I had to remove my ~/.kde/share/apps/amarok and ~/.kde/share/config/amarok* to make it work
[19:16] <smarter> the only thing I miss is a working lyric applet
[19:18] <JontheEchidna> yuriy: so you want to change the current GUI into .ui files?
[19:19] <yuriy> JontheEchidna: rather than fix it, yeah
[19:19] <JontheEchidna> okie
[19:19] <yuriy> need:
[19:19] <yuriy> 1. details grid for user
[19:20] <yuriy> 2. details page for modify user
[19:20] <nixternal> apachelogger: you aren't telling people to replace KHC with a Wiki are you? or you aren't behind that movement?
[19:20] <yuriy> 3. password page for modify user
[19:21] <yuriy> 4. page for modify/new group
[19:21] <yuriy> I think that's it
[20:23] <Riddell> taupter: do fix up the package, that would be great
[20:23] <Riddell> it can probably drop hte -kde4 name
[20:52] <Tonio_> hi there
[20:52] <Tonio_> is knetworkmanager still working for you ?
[20:52] <Tonio_> I can seem to connect to any wireless network.... I can configure a connection, but nothing happens when I'm trying to connect...
[20:52] <Tonio_> works with wired connections btw
[20:58] <JontheEchidna> yuriy: http://i31.photobucket.com/albums/c355/Woremar/maindialogui.png
[20:58] <JontheEchidna> http://i31.photobucket.com/albums/c355/Woremar/maindialogui2.png
[20:58] <yuriy> Tonio_: wasn't working for me last I tried.. installed gnome-network-manager and forgot about it
[20:58] <yuriy> JontheEchidna: thanks!! I'll look at it later, working on my roof
[20:58] <JontheEchidna> hehe
[20:58] <JontheEchidna> have fun
[21:11] <Tonio_> yuriy: oki
[21:18] <yuriy> JontheEchidna: not quite what I was asking for, but cool!
[21:23] <JontheEchidna> would you like to use it?
[21:24] <yuriy> JontheEchidna: at least -- can you make the top level a widget and not a dialog, so it can be embedded in a kcm easily?
[21:24] <yuriy> other than that, great, I'll use it
[21:24] <JontheEchidna> yeah
[21:24] <JontheEchidna> I was having trouble making it a dialog anyway
[21:28] <JontheEchidna> I still need to make .ui files for the modify, new, and delete dialogs
[21:29] <seele> JontheEchidna: right align your labels!
[21:29] <seele> JontheEchidna: and is that going to be a kcm module as well?
[21:30] <JontheEchidna> seele: That's the dream
[21:30] <seele> oh, i missed yuriy's comment, hehe
[21:30]  * JontheEchidna just threw all the things in the details box in a grid layout
[21:30] <JontheEchidna> after I took the screenshot
[21:32]  * JontheEchidna needs web hosting space where he can throw up junk
[21:34] <yuriy> JontheEchidna: you can push the .ui files to the bzr branch
[21:34] <JontheEchidna> yuriy: isn't the branch owned by you?
[21:35] <Riddell> yuriy: you can embed it in a kcm?
[21:35] <yuriy> haven't tried yet, actually
[21:36] <yuriy> but I mean, how guidance utils pick a base class based on if it's run standalone
[21:36] <yuriy> so an ui based on a dialog or main window wouldn't work
[21:37] <yuriy> Riddell: do you know if libpythonize works for kde4?
[21:37] <Riddell> it doesn't
[21:38]  * yuriy -> back to the roof
[21:38] <yuriy> oh :-\
[21:39] <Riddell> it's on sime's todo I think but he's a busy chap
[21:42] <JontheEchidna> http://i31.photobucket.com/albums/c355/Woremar/mainwindowui3.png
[21:43] <JontheEchidna> ^That's with all the layouting, etc
[21:43] <JontheEchidna> and no dialog buttons
[21:43]  * JontheEchidna copied the tabwidget onto a pure qwidget
[22:31] <apachelogger> nixternal: I am telling people to replace most docbooks with a wiki and make KHC arrive in 2008 by making it access online content
[22:31] <JontheEchidna> QWebview ftw
[22:32] <apachelogger> KHTML ftw
[22:32] <JontheEchidna> Gecko ftw
[22:32] <apachelogger> or for that matter
[22:32] <apachelogger> KParts ftw!
[22:32] <apachelogger> JontheEchidna: ok, now that was seriously out of place
[22:32] <apachelogger> that is like IE ftw
[22:32] <yuriy> JontheEchidna: awesome!
[22:33] <yuriy> JontheEchidna: does it let you push to my branch?
[22:33] <JontheEchidna> yuriy: haven't tried
[22:33] <JontheEchidna> but the LP page says only you can
[22:33] <JontheEchidna> https://code.edge.launchpad.net/~yuriy-kozlov/guidance/userconfig-kde4
[22:33] <apachelogger> yuriy: he can push to his and you can merge
[22:33] <apachelogger> or you move the branch to kde-members
[22:35] <yuriy> moved to kubuntu-members
[22:35] <JontheEchidna> cool beans
[22:35] <yuriy> apachelogger: now now, Gecko is still FOSS
[22:35] <apachelogger> that doesn't mean it's good software though
[22:35] <JontheEchidna> has less rendering errors than KHTML too
[22:35] <yuriy> JontheEchidna: can you add focus buddies?
[22:36] <JontheEchidna> yuriy: focus buddies?
[22:36] <yuriy> so when you click on a label, it focuses its corresponding line edit
[22:36]  * apachelogger is wondering what to work on
[22:36] <yuriy> iirc this is denoted by a blue arrow in designer
[22:36]  * JontheEchidna didn't know you could do that
[22:36] <apachelogger> hm
[22:37] <apachelogger> JontheEchidna: you should get yourself a Qt book
[22:37] <apachelogger> focus buddies is one of the essential features ;-)
[22:37] <JontheEchidna> that was easy
[22:38] <JontheEchidna> ok, so I made a ui/ folder
[22:40] <JontheEchidna> which has all of 1 ui file in it right now :P
[22:41] <JontheEchidna> anyway, just pushed it up
[22:41] <JontheEchidna> you can edit the widget names with kate or whatever
[22:41] <JontheEchidna> I guess
[22:45] <JontheEchidna> Ok, for the delete user dialog we should just hard code in a KMessageBox
[22:45] <JontheEchidna> no need to make a ui file for that
[22:46] <JontheEchidna> Hmm, well actually I have no clue how you'd get checkboxes in there
[22:46] <JontheEchidna> so maybe not
[22:52] <yuriy> i'll code it if need be
[22:52] <yuriy> i had a list of stuff earliery^
[23:12] <JontheEchidna> yuriy: so do the modify and new dialogs use the same dialog and just populate it differently?
[23:33] <apachelogger> now I have more karma from bzr commits than bug triage
[23:33] <apachelogger> that algo is completely pointless
[23:33] <apachelogger> the most time consuming work creates the least karma
[23:33] <apachelogger> :S
[23:36] <JontheEchidna> just go and close a couple hundred bugs that are set to expire 10 years ago
[23:39] <JontheEchidna> Is it wrong if I laugh inside when I see window management bugs in compiz at launchpad?
[23:50] <apachelogger> JontheEchidna: it just seems wrong that closing expired bugs gives karma at all, how does that move anything forward? ... and the compiz thing is just normal
[23:50] <JontheEchidna> btw, this page is quite handy: http://people.ubuntu.com/~brian/reports/since-yesterday/
[23:52] <apachelogger> yeah, it shows how broken gnome is compared to KDE :P
[23:52] <JontheEchidna> :P
[23:53] <JontheEchidna> that's why I've been laughing at compiz so much lately
[23:56] <tyfon> the desktop effects in kde4 is working pretty nice here.. but i sort of miss an exposé effect :)
[23:57] <JontheEchidna> throw the mouse to the top left corner
[23:57] <yuriy> JontheEchidna: yes
[23:57] <yuriy> they do use the same dialog
[23:58] <JontheEchidna> thought so
[23:58] <tyfon> hmm
[23:59] <yuriy> apachelogger: I think it shows more the popularity of Ubuntu compared to Kubuntu, but we can keep thinking that :P
[23:59] <tyfon> i didnt see it in the settings list so i asumed it was not there ;)
[23:59] <tyfon> thats nice
[23:59] <JontheEchidna> tyfon: it's called something else
[23:59] <tyfon> yeah it works hehe
[23:59] <JontheEchidna> I think crtl + F10 also does it


[10:47] <tarzeau> Tribaal: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1696663
[10:47] <tarzeau> stuff like that is annoying
[10:47] <tarzeau> as well as: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1726798
[10:47] <tarzeau> https://bugs.launchpad.net/unity/+bug/1314587 (i'm hit by this every time a NEW USER starts here)
[10:47] <tarzeau> some stop minimizing the last open window, some curse unity/ubuntu forever, and just use mate (or something else)
[10:48] <Tribaal> Ah, I can help with the grub stuff
[10:49] <Tribaal> The desktop one but so much unfortunately
[10:49] <Tribaal> (well, I *could* just like any other programmer in the world, if given enough time ;))
[10:50] <tarzeau> haha
[10:51] <tarzeau> i've got a workaround for the grub being raped by canonical/ubuntu
[10:51] <tarzeau> but the bug keeps reappearing :(
[10:51] <Tribaal> I'll check with cyphermox if there's a reason for that timeout
[10:51] <tarzeau> +++
[10:52] <Tribaal> Huh, he's also the maintainer for Debian's grub, it's surprising we would do things differently
[10:53] <tarzeau> https://people.phys.ethz.ch/~myczko/dphys-config-xenial-fix-grub
[10:54] <Tribaal> Did you consider sending that patch? I mean, I'm not sure me being the middle man is very useful :)
[10:54] <tarzeau> to whom?
[10:54] <tarzeau> it's not really a patch. it's some script fixing what others break
[10:54] <tarzeau> and it's reported to console, however still things work, normally just fine, except it's UGLY!
[10:55] <Tribaal> Well, it's not like it's a works breaking change indeed, but if it annoys you, might as well fix it for good.. no?
[10:56] <Tribaal> Anyway, this will likely persist for xenial
[10:57] <Tribaal> But at least let's get this fixed in Bb (whatever it ends up being called)
[10:58] <Tribaal> The fix is therefore : change the grub package to have a 0 timeout
[10:59] <Tribaal> (going running now, see you later)
[11:41] <tarzeau> it also happened to me on 17.10, haha
[11:41] <tarzeau> Bb?
[12:04] <Tribaal> The next Ubuntu release?
[13:39] <Tribaal> lol
[13:39] <Tribaal> "Bionic Beaver"
[13:40] <Tribaal> "bionic" it is :)


[18:50] <Atamira> morning
[18:50] <Atamira> and im ultra early this morning, i havent been to bed yet
[18:51] <ajmitch> morning
[18:52] <ajmitch> (just, it's almost 12 here)
[18:56] <Atamira> nearly 7am here
[18:57] <Atamira> should have been in bed 2 hrs ago
[19:01]  * ajmitch adjusted fairly well after staying awake all through the boring 12 hour flight
[19:28] <chilts> morning
[19:40] <snail> morning
[19:49] <ibeardslee> morning
[21:22] <mwhudson> morning
[21:44] <kcj> Morning.
[23:03] <Guest17222> morning
[23:03] <ojwb> morning