[12:47] <rvba> roaksoax: hello there.
[14:37] <rvba> roaksoax: ping
[14:49] <roaksoax> rvba arghhh i tested this manually in a lab and in my machones and worked as expected
[14:50] <roaksoax> rvba:  were you able tobtrst this manually?
[14:51] <rvba> roaksoax: no, the tests fail.  I suspect MAAS cannot power the nodes anymore.
[14:53] <rvba> roaksoax: when I issue ipmipower commands with --driver-type=LAN_2_0, they fail.
[14:53] <roaksoax> ipmipower  --driver-type=LAN_2_0  -h ip -u pw -p user --stat
[14:53] <roaksoax> I get: "ip: BMC error"
[14:54] <roaksoax> ip should be replaced with a real ip
[14:54] <rvba> Yes, I know :)
[14:54] <roaksoax> ah ok
[14:54] <roaksoax> so 2.0 ahould also include 1.o authentication
[14:54] <roaksoax> which is what its strange to me
[14:55] <roaksoax> abd again i trsted this in 2 dofferent set of machines with no error wjatsoever
[14:55] <roaksoax> rvba: since the tests are broken... lets roll this change back and re-address it after thebhollidays
[14:55] <rvba> roaksoax: sounds good to me.
[14:56] <rvba> roaksoax: the fix could look like this: http://paste.ubuntu.com/1454885/
[14:57] <roaksoax> rvba: cool i like it and we should default tobsomething for enlistment unless the c tells us that info
[14:59] <rvba> roaksoax: let's do that after the holiday. I'm going to do a test run in the lab (with the --driver-type=... manually removed) just to be 100% sure it's the problem, and if it's the case I'll roll-back the changes and re-open the bugs.
[14:59] <roaksoax> agreed
[15:27] <rvba> roaksoax: confirmed, I'm rolling back the changes.
[15:28] <roaksoax> rvba:  cool thanks
[22:43] <HelpMeMAAS> Anyone here..
[22:43] <HelpMeMAAS> I'm having problem with MAAS on 12.04
[22:43] <HelpMeMAAS> says that mass-cli can't be found..
[22:43] <HelpMeMAAS> and PXE boot ends in a kernel panic
[22:43] <HelpMeMAAS> Would I just be best off going to 12.10?


[03:46] <dajhorn> Where can I get the current source code for the mountall package in precise-updates at Launchpad?  `bzr branch lp:ubuntu/precise/mountall` returns an old version.  (Got 2.36 expected 2.36.3)
[03:50] <wgrant> dajhorn: It looks like the bzr import of the mountall package has been suspended due to bug #714622 (someone overwrite the branch). But you can always download the latest source package by expanding the relevant row on https://launchpad.net/ubuntu/+source/mountall
[03:53] <micahg> dajhorn: pull-lp-source mountall precise-updates (needs ubuntu-dev-tools installed)
[03:59] <dajhorn> wgrant, is this repository corruption? Should I put a meetoo on that ticket?
[03:59] <dajhorn> micahg, that got the expected version.
[04:01] <wgrant> dajhorn: Not corruption as such, just someone doing something wrong
[04:21] <dajhorn> Thanks for the help. I opened a new ticket for mountall and blurbed it at 714622.
[05:15] <dajhorn> wgrant, my bug report was invalidated by Steve Langasek. (Bug 1103319)
[05:15] <dajhorn> Any other ideas on where to get this Ubuntu source code repository?
[05:17] <wgrant> dajhorn: micahg and I each gave you an another way to get it.
[05:17] <wgrant> Just not in bzr form (because a bzr branch of the latest version does not exist)
[05:17] <dajhorn> wgrant, I actually need the repo history, not the raw source code.
[05:17] <dajhorn> ie: To maintain a separate branch.
[05:17] <wgrant> There is no repo to have history.
[05:18] <wgrant> So that's a bit difficult.
[05:18] <wgrant> What you request simply does not exist.
[05:18] <wgrant> Why do you need it?
[05:18] <dajhorn> wgrant, I'm maintaining a branch of mountall that has ZFS support.
[05:20] <wgrant> dajhorn: Well, you might have to merge in the 2.36.3 changes yourself
[05:20] <dajhorn> wgrant, okay, thanks.  I never suspected that Ubuntu doesn't keep everything in source control.
[05:20] <wgrant> The mountall branches on Launchpad are not imported, and haven't obviously been updated with the 2.36.3 changes.
[05:21] <wgrant> dajhorn: The uploaded source packages are themselves a form of source control
[05:21] <wgrant> But not everything is in bzr
[08:42] <tsdgeos> Hi guys, trying to do a branch "Resubmit proposal to merge" and getting timeouts all the time
[08:42] <tsdgeos> known issue?
[09:51] <xnox> dajhorn: hmm... why don't you submit a patch for zfs support in mountall?
[09:52] <xnox> dajhorn: it's interesting to upstream because debian has zfs support =)
[10:10] <ricotz> hello :), it seems only one armhf ppa builder is actually accepting builds, is this intended?
[10:17] <czajkowski> wgrant: builders ok?
[10:18] <wgrant> Various qemu bugs keep taking out the ARM virtual builders.
[10:18] <wgrant> I'll get them restarted
[10:19] <lifeless> wgrant: cron it ? :)
[10:20] <wgrant> That would make the long-running builds somewhat unhappy
[10:20] <lifeless> wgrant: Twas a joke.
[10:20] <wgrant> Yes, but it's scarily close to relaity :)
[10:21] <czajkowski> it's funny cause it's true
[10:21] <czajkowski> it's gonna be one of them weeks :(
[10:21] <ricotz> oh, i see :\, thanks for taking care
[11:39] <ricotz> wgrant, hi, do you mind taking a look at those rogue builds https://launchpad.net/~elementary-os/+archive/daily/+build/4240273  https://launchpad.net/~elementary-os/+archive/daily/+build/3742041
[11:39] <czajkowski> do you want them restarted ?
[11:49] <ricotz> czajkowski, they are not accessible, just an OOPS
[11:50] <czajkowski> ah  not seen one of them before. LocationError: (None, 'builder')
[11:51] <czajkowski> perhaps after they kicked those machines
[11:57] <ricotz> could be, would be nice to clear those
[11:58] <czajkowski> ok give me a few in the middle of stuff now
[11:58] <czajkowski> also wasnt this the first project to get arm builds, still staying below the 10 builds a week ?
[11:58] <czajkowski> seems to be alot of issues usually with this builds
[12:12] <czajkowski> ricotz: so would you like them restarted?
[12:13] <ricotz> czajkowski, please restart https://launchpad.net/~elementary-os/+archive/daily/+build/4240273
[12:13] <ricotz> and just remove https://launchpad.net/~elementary-os/+archive/daily/+build/3742041
[12:13] <ricotz> czajkowski, yes, you said it was the first probject
[12:14] <ricotz> czajkowski, hmm, restriction of 10 builds a weeks, this seems to be quite more
[12:14] <ricotz> czajkowski, you mean 10 builds for the whole ppa?
[12:15] <czajkowski> ricotz: yes in order to have the arm builds we did set some limits.
[12:15] <ricotz> or per package?
[12:16] <czajkowski> https://dev.launchpad.net/CommunityARMBuilds
[12:18] <ricotz> i see, the builds are way less then 4 hours, but i assume there are like 120 builds per week
[12:18] <czajkowski> we did advertise these guildelines
[12:19] <czajkowski> as for those builds, they are currently oopsing
[12:19] <czajkowski> and I'll need to wait till wgrant or StevenK come online later today
[12:20] <ricotz> czajkowski, sorry, the guidelnes were set after it was enabled and it is a daily ppa :\
[12:20] <czajkowski> guidelines were set before we annouced the availability
[12:21] <ricotz> i know, but you enabled them even before that, anyhow so we need to reduce the amount significantly?
[12:22] <czajkowski> no I enabled them on the day :)
[12:22] <ricotz> ok, ok :)
[15:05] <oly> hi, wonder if anyone may be able to tell me the cause of this, i am trying to create a package for a C program how ever the resulting deb does not contain any files its liek it never actually build / configures the code
[15:05] <oly> the packaging files are located here, http://bazaar.launchpad.net/~oly/+junk/geanypy-packaging/files
[15:06] <oly> and the source is here, i am using a recipe but also tried locally http://bazaar.launchpad.net/~oly/geanypy/geanypy/files
[15:06] <oly> i normally package files that dont need compiling so its partially new territory and this is the result of following a tutorial.
[15:19] <Laney> oly: I suggest you try #ubuntu-packaging; this isn't really the right place for questions about that
[15:31] <oly> cheers Laney, was not aware of that room :)
[16:56] <exarkun> Can I remove a project from a project group?
[16:57] <czajkowski> not done that before
[16:57] <czajkowski> let me know
[16:57] <czajkowski> what i the project group and project
[16:57] <mgz> exarkun: yes, if you're an admin of the project
[16:58] <exarkun> mgz: Maybe I'm not?  I can't see any UI for doing so.  Where do I look?
[16:58] <mgz> go to "Change details" (+edit) and remove the "Part of..." text
[16:58] <exarkun> I would like to remove https://launchpad.net/pyflakes from its group.
[16:58] <exarkun> Oh :(  I think I did things in the wrong order.
[16:59] <exarkun> I already changed the maintainer for a group I am part of to a different person.  So I can't "Change details" any more, I think?
[16:59] <mgz> right :)
[16:59] <mgz> czajkowski has super-powers though, so can probably do it for you
[16:59] <exarkun> s/for/from/
[17:00] <mgz> or you can ask the newly assigned maintainer to do it.
[17:01] <czajkowski> aye as I currently can';t :/
[17:01] <exarkun> Okay, thanks.
[17:39] <sarnold> is this a reasonable place to report spam in launchpad bugs?
[17:41] <czajkowski> yeah
[17:41] <czajkowski> it is
[17:41] <czajkowski> which bug ?
[17:41] <czajkowski> if ther are many
[17:41] <czajkowski> please file a question however.
[17:41] <czajkowski> https://answers.launchpad.net/launchpad
[17:42] <sarnold> czajkowski: heh, I noticed the funny chanserv notice after asking :) thanks
[17:43] <sarnold> czajkowski: https://answers.launchpad.net/launchpad/+question/219950  thanks :)
[17:47] <czajkowski> done
[17:47] <sarnold> woot
[17:58] <czajkowski> sarnold: please always create a new question
[18:00] <sarnold> czajkowski: will do, thanks :)
[19:16] <kdub> if i upload a package to launchpad, does launchpad go and  build that package, or should it appear immediately
[19:55] <joey> dzin: oh you know what, I bet the LP guys are sprinting this week
[19:55] <czajkowski> joey: what's up
[19:55] <czajkowski> can I help
[19:55] <czajkowski> or else wait for mainteance to come online from AU
[19:55] <joey> czajkowski: ah good I was just going to poke you :-)
[19:55] <dzin> czajkowski: actually I have an issue
[19:56] <joey> czajkowski: dzin is here from Linaro and has an issue I can't explain
[19:56] <czajkowski> well try adn explain to me and if not we can wait till StevenK or wgrant come online in a few hours
[19:56] <dzin> czajkowski:  no bugs displayed here (trunk series) https://bugs.launchpad.net/linaro-big-little-system/trunk
[19:57] <dzin> czajkowski:  yet bugs displayed here: https://launchpad.net/linaro-big-little-system/+milestone/13.01
[19:57] <joey> czajkowski: if you check the default search parms it should show those. They aren't private, they are new/confirmed
[19:57] <czajkowski> why are you doing it to /trunk
[19:58] <dzin> czajkowski: joey: actually one is private
[19:58] <czajkowski> daft question but seeing as I'm not sure it's a good place to ask as a ny
[19:58] <czajkowski> https://bugs.launchpad.net/linaro-big-little-system/  I can see them there
[19:58] <czajkowski> so wondering why /trunk
[19:58] <joey> dzin: oh I see 2 public and no private (but I don't have Linaro powers any longer so that might be why)
[19:58] <dzin> czajkowski: I click on the trunk series then on bugs
[19:59] <czajkowski> not seen people do it that way before
[19:59] <czajkowski> :/
[19:59] <dzin> joey: quite right, there are 3 bugs total
[19:59] <joey> yeah the series is trunk apparently as seen in https://launchpad.net/linaro-big-little-system/+milestone/13.01
[19:59] <dzin> czajkowski: I've always been a bit different
[19:59] <czajkowski> I clicked on https://bugs.launchpad.net/linaro-big-little-system/  then on the milestones on the page
[19:59] <joey> right but the bug section below is blank
[19:59] <czajkowski> Milestone-targeted bugs
[20:00] <joey> and all bugs takes you to https://bugs.launchpad.net/linaro-big-little-system/trunk
[20:00] <joey> which is also blank
[20:00] <czajkowski> I've not seen this before at all
[20:00] <czajkowski> um...
[20:01] <czajkowski> we're going to have to wait till AU comealone as they will probably know straight off
[20:01] <joey> that was my reaction :-)
[20:01] <czajkowski> sorry
[20:01] <dzin> czajkowski: I've just recently changed some details on the project
[20:01] <czajkowski> dzin: for future though filing a question on LP gets our attention
[20:01] <czajkowski> dzin: ahhhhhhhhhh
[20:02] <czajkowski> dzin: what have you done in /+sharing
[20:02] <czajkowski> re bugs
[20:02] <dzin> czajkowski: right
[20:04] <joey> dzin: make sure it's shared with the right teams (hat tip czajkowski)
[20:04] <Munchor> Hey there guys, I'm using launchpadlib, is it ok to ask a question here, or is there another channel more launchpadlib-specific?
[20:05] <dzin> joey: czajkowski: I've changed bugs to public
[20:05] <czajkowski> Munchor: if it's dev inclined you will be better off mailing launchpad-dev at this hour of the day tbh
[20:09] <dzin> joey: czajkowski: sorry, not sure I get where to share. The sharing policies are: branches: Forbidden, bugs: Public, blueprints: Public.
[20:10] <joey> dzin: I *think* you need to ensure that your teams have project grants
[20:10] <dzin> joey: if I'm the admin here, why can't I see the bugs?
[20:11] <Munchor> alright czajkowski
[20:11] <joey> dzin: darn good question. I would think you should be able to do so
[20:13] <joey> dzin: if you can hang on until wgrant wakes up, he might know the answer to this boggle
[20:14] <dzin> joey: sure thing, thanks
[20:15] <dajhorn> xnox, we might have a Debian sponsor, and the plan is to get it integrated there first, and ensure that it fits with the existing kFreeBSD support.  PPAs are better for vibrant packages than the universe section.
[20:15] <czajkowski> joey: dzin have you read http://blog.launchpad.net/general/information-sharing-is-now-in-beta-for-everyone
[20:20] <dzin> czajkowski: yes, I've seen that, thanks
[20:22] <dobey> what's the problem?
[20:25] <dobey> dzin: bugs.lp.net/project/series only shows bugs filed in that project, and which are targeted to that series. if a branch hasn't been specifically targeted to trunk, it won't show up on the list for /trunk.
[20:25] <dobey> dzin: you're not seeing any bugs there, because no bugs have trunk as a target :)
[20:30] <dzin> dobey: how do I target a bug to a series?
[20:32] <dobey> dzin: make sure the project you want to target for is in the URL of the bug you're viewing, and click the "Target to series" underneath the bug info box
[20:33] <dobey> dzin: it can be confusing if a bug has tasks for multiple projects on it
[20:33] <dzin> dobey: ah, I see it.
[20:33] <dobey> but the project will be in the URL and the project name at the top of the page
[20:35] <dzin> dobey: perfect, I see the logic of it now. Thanks.
[20:36] <dobey> sure
[20:38] <exarkun> Um, https://launchpadlibrarian.net/129061557/HookError_source_ubuntuone_client.txt (linked from https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/1102685 )
[20:38] <exarkun> Oh sorry, nothing interesting there at all, please ignore me, sorry for the noise.
[20:44] <xnox> dajhorn: i can sponsor into debian... and ubuntu... and upstream... ;-)
[20:44]  * xnox is DD and Core Dev
[20:45] <dajhorn> xnox, right, thanks.  I just realized that you are CC'd on the ITP ticket.


[00:10] <half_mast> Can anyone tell me what channel should nexus 4 user should be using? I'm currently on utopic but I haven't had an update since October and I keep seeing images from the rtm channel.
[00:38] <Riku-san> Is it possible to have a normal desktop on Ubuntu Touch? Instead of the homescreen, like Ubuntu Desktop for Nexus 7 that was dropped.
[01:12] <Riku-san> why is ubuntu touch armel?
[01:13] <Riku-san> the boot image is armhf
[01:13] <Riku-san> but the preinstalled system says armel
[01:20] <Riku-san> I can't flash the boot image because it's too large
[01:20] <Riku-san> correct size is 8192 KB
[01:21] <Riku-san> but it's 8368 KB
[02:01] <Riku-san> I just installed Ubuntu Touch using ubuntu-device-flash, but now fastboot isn't working and the device won't boot to Ubuntu, only recovery works
[03:02] <Riku-san> scratch that
[03:02] <Riku-san> but it still fails to boot
[09:34] <JamesTait> Good morning all; happy World Architecture Day! :-D
[09:46] <oSoMoN> rpadovani, hey, I’ve just reviewed https://code.launchpad.net/~rpadovani/webbrowser-app/addressBarFullWidth/+merge/239039 , the change looks good but it breaks a number of autopilot tests (see my comment in the MR)
[09:47] <seb128> kenvandine, jgdxx, Laney, could one of you review/approve https://code.launchpad.net/~seb128/ubuntu-system-settings/build-translations-template/+merge/240696 ?
[09:48] <oSoMoN> daker, hey, I don’t know if you ever saw my comments on https://code.launchpad.net/~daker/webbrowser-app/fix.airbnb-smartbanner/+merge/230855 ?
[09:49] <rpadovani> oSoMoN, ok, thanks, I'll try to take a look and fix it
[09:50] <oSoMoN> rpadovani, cheers! don’t hesitate to ping me for help, fixing autopilot tests can be arduous sometimes :/
[09:51] <Laney> seb128: I didn't follow the reasoning, what good does that do?
[09:51] <rpadovani> oSoMoN, thanks!
[09:51] <seb128> Laney, it means the template is updated on package uploads and that we don't need to play catchup with manual updates commits in trunk
[09:52] <Laney> so we use ubuntu translations? what happens to the one in trunk?
[10:00] <seb128> Laney, we stop using it
[10:00] <seb128> yes we use ubuntu translations
[10:00] <seb128> easier
[10:00] <seb128> dpm asked to keep the pot in trunk for a bit because it's used for stats
[10:01] <seb128> if stats are bit wrong it's not a big issue, better than having the template used for translations behind
[10:01] <Laney> does it still commit the updates to trunk?
[10:01] <dpm> Laney, yes
[10:01] <Laney> s/it/lp/
[10:01] <Laney> okay!
[10:03] <dpm> Laney, regardless of where the translations are done (Ubuntu or upstream), they're committed to trunk. It's only that the Ubuntu template will be up-to-date with every upload, but the upstream one won't be up-to-date unless it's manually committed. This will make the stats to be a bit wrong, but until I can get the stats exported from Ubuntu, "a bit wrong" is still better than "no stats at all" :)
[10:08] <seb128> Laney, dpm, thanks
[10:12] <daker> oSoMoN: I'll fix it
[10:13] <oSoMoN> daker, thanks!
[10:23] <seb128> Laney, was bug #1384760 a whoopsie issue? did you say you were looking at it or talking to bdmurray about it?
[10:23] <Laney> seb128: never reproduced it, can you?
[10:25] <seb128> Laney, no, but I didn't try hard
[10:26] <Laney> well, let's mark it as Incomplete until we get better steps
[10:27] <marcustomlinson> mardy: ping
[10:27] <mardy> marcustomlinson: pong
[10:28] <marcustomlinson> mardy: looking at your slides. The slide on scopes OA, there is a rough "a" before ".application and .service files"
[10:28] <marcustomlinson> mardy: also the example then is only of a service file.
[10:29] <marcustomlinson> mardy: then "unity-shell-api" should be "unity-scopes-api"
[10:34] <mardy> marcustomlinson: I did some changes, does it look better now?
[10:39] <marcustomlinson> mardy: so the bold text in the stuff you copied from our API doc is the stuff to be highlighted.
[10:40] <marcustomlinson> mardy: you've highlighted odd stuff :p
[10:41] <mardy> marcustomlinson: which slide?
[10:42] <marcustomlinson> mardy: slide 13. Example: only "accounts" should be highlighted
[10:42] <marcustomlinson> mardy: in the apparmor file
[10:42] <marcustomlinson> mardy: the manifest file also has some bold text
[10:42] <mardy> marcustomlinson: right :-)
[10:43] <marcustomlinson> mardy: hightlight the bold stuff
[10:43] <mardy> marcustomlinson: those are the OA-specific hooks
[10:43] <marcustomlinson> mardy: right, which is what you want to draw attention too
[10:46] <marcustomlinson> mardy: and just for some readability, on slide 14, could you insert a blank line before "// Check if our service is authenticated..."
[12:43] <Chipaca> seb128: hi there! how busy are you today? i've got a not-at-all-urgent review for system settings that needs doing :)
[12:43] <Riku-san_> yes, a person
[12:44] <Riku-san_> I just installed Ubuntu Touch on my grouper, following the instructions exactly, but when it's done, it drops to a boot screen in which 'start' does nothing. Selecting 'reboot to bootloader' and then 'start' puts 'Booting failed' in the top left corner.
[12:45] <Riku-san_> To install I put it in fastboot and used 'ubuntu-device-flash --channel=ubuntu-touch/trusty --bootstrap'
[12:45] <ogra_> Riku-san_, groupper has not been supported in about 1 year ...
[12:47] <seb128> Chipaca, hey, reasonably busy but I can probably find a slot for a review, is that the push helper logging one?
[12:47] <Chipaca> seb128: yep
[12:47] <seb128> Chipaca, on my list ;-)
[12:47] <Chipaca> seb128: excellent, thanks
[12:47] <seb128> yw!
[12:52] <Riku-san_> ogra_, there's an image for it of 14.04
[12:53] <Riku-san_> therefore it should be supported, no?
[12:53] <ogra_> not really, no, that was just fo convenience
[12:53] <Riku-san_> I've had enough 'not supported' crap for one day
[12:54] <Riku-san_> just please help me fix my tablet
[12:54] <ogra_> install android ... the ubuntu image you would install there would be massively outdated anyway
[12:55] <ogra_> and most likelyonly work half way
[12:55] <Riku-san_> grah
[12:55] <Riku-san_> I'll just go back to the even less supported 13.04 desktop image
[12:56] <ogra_> grouper support was dropped before trusty release, not sure the driver would even work or anything
[12:56] <jgdxx> seb128, can you add [1] to the list? :) [1] https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/cellular-manual-carrier-persist-fix-1388044/+merge/241541
[12:56] <seb128> jgdxx, hey, looking
[12:57] <Riku-san_> oh of course, the tablet I just bought for $100 isn't supported
[12:57] <jgdxx> seb128, hi, thanks.
[12:57] <Riku-san_> I'll go back to the desktop image where xorg breaks alot
[12:57] <seb128> jgdx, oh, that's not a small one :/
[12:57] <seb128> not sure I'm going to have slots for that one
[12:58] <jgdx> seb128, no, not really. But if you'd like, a quick install + testing of the new functionality would help!
[12:58] <seb128> k
[12:58] <jgdx> I have only forbidden carriers, so it's pretty useless.
[12:59] <Riku-san_> gtg
[13:15] <jgdx> Laney, hi, how do I land [1]? I assume it's not automatically landed by jenkins, or else it probably would have landed by now.. [1] https://code.launchpad.net/~jonas-drange/gsettings-ubuntu-touch-schemas/other-vibrations/+merge/239734
[13:15] <Laney> ci train
[13:15] <Laney> I just commented on that too after I saw your mail. :-)
[13:15] <jgdx> ah :)
[13:16] <ogra_> jgdx, you ask the lander of your team :)
[13:16] <ogra_> he/she will then push it onto the train
[13:17] <jgdx> ogra_, got it
[13:21] <jgdx> Laney, pushed r51 which adds the comment.
[13:21] <Laney> ty
[13:21] <Laney> you can get it in the same silo as whatever uses it
[13:59] <akiva-thinkpad> the ubuntu online summit is starting; come join the foray http://summit.ubuntu.com/uos-1411/meeting/22327/intro-by-michael-hall-keynote-by-rick-spencer/
[14:01] <marcustomlinson> mardy: ping
[14:09] <mardy> marcustomlinson: pong
[14:09] <marcustomlinson> mardy: hey man, sorry to bug you about this again. its about the soundcloud scope I'm working on.
[14:10] <marcustomlinson> mardy: so (on the desktop) when I add the account from settings, the account is successfully and I get this log: http://pastebin.ubuntu.com/8964802/
[14:10] <marcustomlinson> mardy: but, when I do the log-in from a scope via OnlineAccountsClient::Setup, the account doesn't get added. I get this log: http://pastebin.ubuntu.com/8964817/
[14:13] <mardy> marcustomlinson: I can see that the account plugin is deleting the identity, for some reason
[14:13] <marcustomlinson> mardy: yeah, it seem like everything goes alright, then it just gets deleted :/
[14:14] <mardy> marcustomlinson: please set UOA_LOGGING_LEVEL=2 and UOA_DAEMON_TIMEOUT=9999 and restart online-accounts-service
[14:14] <marcustomlinson> mardy: k
[14:19] <marcustomlinson> mardy: ok, where do I get the online-accounts-service log?
[14:19] <mardy> marcustomlinson: on the terminal where you run the online-accounts-service command
[14:19] <marcustomlinson> mardy: ah
[14:19] <marcustomlinson> :p
[14:24] <marcustomlinson> mardy: http://pastebin.ubuntu.com/8965121/
[14:25] <mardy> marcustomlinson: that "error: " line, is it from your Main.qml?
[14:26] <marcustomlinson> mardy: "qml: error: 401"? no
[14:27] <mardy> marcustomlinson: not the whole string, just "error:". Maybe when getting the username
[14:28] <marcustomlinson> mardy: well I can't tell you that its not coming from unity8, but not from me
[14:29] <mardy> marcustomlinson: can I see the account plugin source code?
[14:30] <marcustomlinson> mardy: oh! right. now I get what you're asking
[14:30] <mardy> marcustomlinson: :-))
[14:30] <marcustomlinson> mardy: sorry, I inherited this project
[14:31] <marcustomlinson> mardy: http://pastebin.ubuntu.com/8965274/
[14:35] <Mirv> I've now updated all packages' bzr:s that I rebuilt for Qt 5.3.2, so your next landings should work as normal
[14:36] <Mirv> btw Qt 5.3.2 is in the newest vivid-proposed image now, just published
[14:38] <marcustomlinson> mardy: I may need to set the user agent in the http header
[14:39] <mardy> marcustomlinson: no, I think that the access token should not be passed like that
[14:40] <mardy> marcustomlinson: unfortunately the SoundCloud API doc only shows how to use their client libraries, but it's likely that you need to write the token in the Authorization header
[14:40] <marcustomlinson> mardy: k, let me try something
[14:46] <mardy> marcustomlinson: instead of "?access_token=", try "?oauth_token="
[14:46] <marcustomlinson> mardy: k
[14:46] <mardy> marcustomlinson: at least, this is what I can guess looking at https://github.com/soundcloud/soundcloud-python/blob/master/soundcloud/client.py#L115
[14:47] <mardy> marcustomlinson: ah, you also need "client_id"
[14:48] <mardy> marcustomlinson: or maybe not; try without it, first
[14:49] <kenvandine> dednick, i just finished thoroughly testing my cherry-pick of the check.sync branch in rtm and found some things that failed which work in vivid
[14:49] <dednick> kenvandine: which things?
[14:49] <kenvandine> orientation-lock, wifi switch under battery, and data roaming under cellular
[14:50] <kenvandine> the orientation-lock and wifi under battery both fail to stay in sync with the indicators
[14:50] <marcustomlinson> mardy: right, it didn't error 401 this time :)
[14:50] <marcustomlinson> mardy: but... It looks like Main.qml is trying to parse xml into JSON :p
[14:50] <kenvandine> the data roaming under cellular isn't really changing the ofono setting, no indicator for that
[14:51] <kenvandine> dednick, so are you sure there aren't indicator/shell changes needed to keep those in sync with the indicator?
[14:51] <dednick> kenvandine: is the orientation lock gsetting changing, or is that broken?
[14:51] <kenvandine> let me confirm
[14:51] <marcustomlinson> mardy: but that was the right fix THANKS!
[14:52] <kenvandine> dednick, ok, that one is working it's the indicator is broken
[14:52] <kenvandine> i forgot that didn't work in rtm yet
[14:52] <dednick> kenvandine: ya. thought so
[14:52] <dednick> kenvandine: what's up with the wifi?
[14:52] <mardy> marcustomlinson: yw :-)
[14:52] <kenvandine> the wifi switch under battery doesn't stay in sync with the network indicator
[14:53] <kenvandine> dednick, the wifi switch under wifi does stay in sync
[14:53] <kenvandine> dednick, that's weird though, because it works in vivid
[14:53] <kenvandine> and that code merged cleanly
[14:53] <kenvandine> dednick, it's in rtm silo 3
[14:54] <dednick> kenvandine: depends if the battery & wifi use same backend
[14:54] <dednick> kenvandine: i'm having trouble with my devices at the mo. they aren't co-operating :/ testing is a bit of a trial
[14:54] <kenvandine> dednick, yeah, but that plugin hasn't diverged in vivid
[14:54] <kenvandine> so odd... let me compare the code
[14:56] <dednick> kenvandine: right, the wifi uses the indicator, and the battery uses libnm.
[14:56] <cwayne> mardy: ping, is it possible for a service to pull from 2 providers?
[14:56] <kenvandine> dednick, oh... that's annoying!
[14:56] <dednick> kenvandine: slightly!
[14:56] <kenvandine> dednick, but... why is that regressing?
[14:56] <jgdx> Wellark, hi, where is bug 1374082 in the pipeline? :)
[14:56] <dednick> kenvandine: no idea there
[14:56] <kenvandine> or... maybe it's already broken in rtm
[14:57] <kenvandine> jgdx, do you have an rtm device handy?
[14:57] <kenvandine> jgdx, can you test to see if the wifi switch under battery works?
[14:57] <dednick> kenvandine: i would think that the indicator uses libnm anyway
[14:57] <jgdx> kenvandine, sorry no
[14:58] <kenvandine> dednick, the wifi switch there does stay in sync with the indicator on vivid
[14:58] <kenvandine> but not on rtm
[14:58] <dpm> pitti, renatu, so https://translations.launchpad.net/ubuntu-rtm/14.09/+source/mediaplayer-app/+pots/mediaplayer-app/es/+translate?batch=10&show=all&search=player shows no .desktop file string to translate
[14:58] <kenvandine> pmcgowan, can you test something on rtm quickly?
[14:58] <dednick> kenvandine: i'll try rtm one of mine.
[14:58] <kenvandine> dednick, thanks
[14:58] <kenvandine> -            SettingsItemTitle {
[14:58] <kenvandine> +            ListItem.Standard {
[14:58] <dpm> pitti, renatu,looks like for RTM the template was not updated on build, or that the package was not uploaded recently?
[14:59] <mardy> cwayne: I don't think so... what's your use case?
[14:59] <kenvandine> that's the diff between vivid and this branch for rtm
[14:59] <pitti> dpm: right, I just found that out with renatu; https://code.launchpad.net/~renatofilho/mediaplayer-app/fix-1382317/+merge/240875 needs to land to fix that
[15:02] <pmcgowan> kenvandine, what do you need
[15:02] <mzanetti> cyphermox: please let me know if you need some logs or anything regarding this: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1391912
[15:02] <kenvandine> pmcgowan, can you see if the wifi switch in the battery panel works for you?
[15:02] <kgunn> oSoMoN|afk: i updated the bug, but yes, child processes do get stopped as well
[15:02] <kenvandine> pmcgowan, specifically does it seem to stay in sync with the network indicator?
[15:03] <pmcgowan> kenvandine, seems to yes
[15:03] <kenvandine> wtf!
[15:03] <pmcgowan> kenvandine, I have monday build
[15:03] <kenvandine> pmcgowan, i'm testing the backport of the fix for keeping the indicators in sync
[15:03] <pmcgowan> kenvandine, turned off wifi in the panel, ok, then turned it on in the indicator, and ok
[15:03] <kenvandine> and that doesn't work on rtm
[15:04] <kenvandine> but does on vivid
[15:04] <seb128> kenvandine, want me to test on rtm157?
[15:04] <kenvandine> seb128, please do
[15:04] <kenvandine> the diff between vivid and rtm is one line... and shouldn't affect it
[15:04] <kenvandine> but it doesn't work for me with silo 3
[15:05] <seb128> kenvandine, doesn't work on rtm 157
[15:05] <kenvandine> pmcgowan, and why did bug 1336715 drop off the topblocker list?
[15:05] <seb128> I toggled it off in battery's panel
[15:05] <kenvandine> seb128, interesting... ok
[15:05] <seb128> and the indicator didn't change
[15:05] <seb128> well the icon did
[15:05] <marcustomlinson> mardy: sorted out. Thanks again!
[15:05] <seb128> but not the item in the indicator menu
[15:05] <seb128> wifi panel still shows it on as well
[15:06] <kenvandine> seb128, so that isn't a regression caused by this branch then
[15:06] <kenvandine> still odd
[15:06] <seb128> but it doesn't list any aps
[15:06] <kenvandine> seb128, can you test silo 3?
[15:06] <seb128> kenvandine, yes, but after that UOS session
[15:07] <kenvandine> http://pastebin.ubuntu.com/8965818/
[15:07] <kenvandine> seb128, that's the list of stuff to test
[15:08] <kenvandine> 2 failures for me, one expected
[15:08] <kenvandine> the rotation lock indicator fix hasn't landed yet
[15:08] <seb128> kenvandine, ok
[15:08] <kenvandine> oh, data roaming also failed for me
[15:09] <kenvandine> pmcgowan, i think that bug fell off the list because the unity8 task was marked fixed
[15:09] <kenvandine> but the settings fix didn't land in rtm yet
[15:09] <pmcgowan> kenvandine, it should be showing up, let me check on t
[15:10] <tedg> seb128, kenvandine, so for a u-s-s fix that I expect to land on rtm, which branch should it be targeted for?
[15:10] <kenvandine> we land in trunk(vivid) and cherry-pick for rtm
[15:11] <kenvandine> to speed up you can also propose a branch for our rtm branch
[15:11] <tedg> kenvandine, Is the rtm branch getting seb128's header fix? I merged that already, but it doesn't seem to be in rtm.
[15:11] <kenvandine> nope
[15:11] <tedg> Uhg, okay.
[15:11] <kenvandine> sorry... i wish :)
[15:12] <kenvandine> convince pmcgowan it's important :)
[15:12]  * kenvandine passes the buck
[15:12] <tedg> pmcgowan, kenvandine says this is important ^
[15:12] <kenvandine> haha
[15:12] <kenvandine> it's nice for sure..
[15:12] <pmcgowan> which fix?
[15:12] <kenvandine> the header/labels stuff
[15:12] <jgdx> kenvandine, my mako is soon at latest rtm. Will test.
[15:12] <kenvandine> cosmetic
[15:13] <pmcgowan> sounds like ota? got a bug #
[15:14] <kenvandine> i'll find it
[15:14] <tedg> Probably makes sense when we sync all of vivid.
[15:16] <kenvandine> tedg, do you have the bug number handy?
[15:16] <kgunn> oSoMoN|afk: oh, but you should have like 3 seconds before life cycle kicks in, so you should have time to pull back the keepDisplayOn
[15:17] <kenvandine> seb128, was there a bug filed for that?
[15:17] <kenvandine> seb128, the section headers/titles branch
[15:17] <tedg> kenvandine,Doesn't seem like one was attached: https://code.launchpad.net/~seb128/ubuntu-system-settings/titles-uis-tweaks
[15:17] <kenvandine> yeah
[15:18] <seb128> kenvandine, tedg, you can use bug #1389767
[15:18] <seb128> it was opened after the fix landed but that's good enough
[15:18] <kenvandine> pmcgowan, ^^
[15:21] <pmcgowan> kenvandine, I can propose it we'll see, as you said nice to have
[15:21] <kenvandine> yeah
[15:22] <jgdx> don't forget the great sequel: ~jonas-drange/ubuntu-system-settings/titles-uis-tweaks-2
[15:23] <pmcgowan> jgdx, can you add that to the bug
[15:23] <jgdx> pmcgowan, done
[15:33] <dednick> kenvandine: looks like the wifi setting in batter doesnt work in rtm either.
[15:33] <dednick> *battery
[15:33] <kenvandine> dednick, yeah seb128 saw that too
[15:34] <kenvandine> pmcgowan, what image version did you test that in ?
[15:34] <kenvandine> i'm trying to see what's changed
[15:34] <seb128> dednick, kenvandine: the battery toggle seems to work to me
[15:34] <seb128> the icon in the panel change to a not connected one
[15:34] <seb128> it's the indicator switch which is buggy it seems
[15:35] <kenvandine> oh, maybe i didn't look close enough :)
[15:35] <jgdx> kenvandine, r7 keeps indicator and uss wifi toggle in sync
[15:35] <dednick> kenvandine, seb128: works indicator->battery wifi, but when changing battery indicator does not update
[15:35] <kenvandine> seb128, oh... you're right
[15:35] <dednick> seb128: in rtm?
[15:35] <seb128> dednick, rtm 157
[15:36] <seb128> on krillin
[15:36] <kenvandine> same here
[15:36] <kenvandine> with silo 3
[15:36] <kenvandine> it is working, just the switch in the indicator isn't changing
[15:36] <kenvandine> but it is disconnecting from wifi
[15:36] <kenvandine> and going to edge
[15:36] <dednick> kenvandine: ah. ok
[15:36] <kenvandine> whew
[15:36] <kenvandine> so an indicator bug :)
[15:36] <kenvandine> that works in vivid though
[15:36] <dednick> kenvandine: how do you tell that? just ifconfig?
[15:37] <kenvandine> dednick, the icon in the indicator
[15:37] <kenvandine> changes to wifi disconnected, then to edge
[15:37] <kenvandine> but the wifi switch in the network indicator stays checked
[15:38] <kenvandine> dednick, however in vivid the switch in the indicator toggles properly
[15:39] <dednick> kenvandine: hm. my icon isnt changing :/
[15:39] <kenvandine> so looks like bug 1336715 is still valid for indicator-network in rtm
[15:39] <seb128> kenvandine, https://launchpad.net/ubuntu/+source/indicator-network/0.5.1+14.10.20141007.2-0ubuntu1 ?
[15:39] <kenvandine> dednick, weird... mine is
[15:39] <seb128> is that in rtm?
[15:39] <kenvandine> 0.5.1+14.10.20141031.3~rtm-0ubuntu1
[15:39] <kenvandine> that's the version i have
[15:40] <seb128> dunno then
[15:40] <seb128> check with Wellark
[15:40] <kenvandine> yeah, dunno
[15:40] <kenvandine> Wellark, ^^
[15:40] <dednick> hm. ok, it seems to be changing when i turn it off, but not back on again
[15:41] <dednick> or just sometimes
[15:41] <pmcgowan> kenvandine, does your silo address this as well https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1388804
[15:41] <kenvandine> pmcgowan, i think so
[15:42] <kenvandine> seb128, according to the changes mail, that did land in rtm
[15:42] <seb128> kenvandine, k
[15:42] <kenvandine> pmcgowan, confirmed, that bug is fixed in silo 3
[15:43] <dednick> kenvandine, seb128: ok, it's actually an indicator-network issue. the backend switch value isn't updating. it's not a UI sync issue at least.
[15:43] <kenvandine> dednick, yeah
[15:43] <pmcgowan> kenvandine, great
[15:43] <kenvandine> tedg, you proposed a branch for that
[15:44] <pmcgowan> kenvandine, titles fix is approved to land, seems everyone likes that
[15:44] <tedg> kenvandine, Yeah, updating it now.
[15:44] <kenvandine> tedg, thanks
[15:44] <tedg> kenvandine, (quite literally, it was pushing as I was typing) :-)
[15:44] <kenvandine> that should already be fixed in vivid and now in this branch for rtm
[15:44] <kenvandine> pmcgowan, woot
[15:45] <kenvandine> seb128, would you mind preparing a backport of that for rtm?
[15:45] <seb128> kenvandine, I can do
[15:45] <kenvandine> seb128, thanks!
[15:45] <seb128> yw!
[15:45] <kenvandine> maybe we can included jgdx's too
[15:45] <kenvandine> which i haven't looked at yet :)
[15:46] <jgdx> it's fine *waves hand*
[15:46] <kenvandine> dednick, so now i'm down to figuring out why data roaming isn't working
[15:46] <kenvandine> dednick, can you file a bug about the indicator-network issue?
[15:46] <seb128> kenvandine, did that land in trunk yet?
[15:46] <kenvandine> seb128, did what?
[15:47] <seb128> kenvandine, <kenvandine> maybe we can included jgdx's too
[15:47] <kenvandine> that hasn't
[15:47] <seb128> so we should do that first
[15:47] <kenvandine> i don't think it's been reviewed yet
[15:47] <seb128> before backporting
[15:47] <kenvandine> yeah
[15:47] <seb128> it has
[15:47] <seb128> it's approved
[15:47] <jgdx> seb128, just looked at it
[15:47] <kenvandine> cool
[15:48] <kenvandine> pmcgowan, did the titles fixed get approved for rtm like for landing today?
[15:48] <kenvandine> or for ota?
[15:48] <seb128> we should probably ota that one
[15:49] <pmcgowan> kenvandine, we can land it now if you want
[15:49] <seb128> it's non trivial and cosmetic
[15:49] <kenvandine> if for today, we should just take what's already in vivid
[15:49] <kenvandine> i'd like too
[15:49] <pmcgowan> if you think its too risky we can defer
[15:49] <kenvandine> it's been in vivid for a while now
[15:49] <kenvandine> seb128, what do you think?
[15:49] <kenvandine> i think it's awesome :)
[15:49] <seb128> kenvandine, wfm
[15:50] <kenvandine> seb128, ok, can you prepare just the backport then?
[15:50] <seb128> it's a bit of suboptimal to have it incomplete, but better that nothing
[15:50] <seb128> k
[15:50] <kenvandine> we'll handle jgdx's later
[15:50] <seb128> k
[15:52] <tedg> kenvandine, So I'm not sure how to update this silent mode autopilot test. Is there an example of someone using an action in the autopilot tests?
[15:52] <dednick> kenvandine: ok
[15:53] <pmcgowan> kenvandine, btw I tested in 127 mako
[15:53] <kenvandine> tedg, there is an existing test for that
[15:54] <kenvandine> dednick, ah... found the cellular data roaming problem
[15:54] <kenvandine> in merging that the Binding got dropped
[15:54] <kenvandine> but i think we still need that
[15:55] <tedg> kenvandine, Do you know which one? :-)
[15:55] <kenvandine> the silent mode test :)
[15:55] <kenvandine> tedg, i really don't remember though... i just know there was  a test
[15:56] <kenvandine> and that uses an action
[15:56] <kenvandine> dednick, so in the Binding, i want the property to be serverChecked right?
[15:56] <kenvandine> not checked
[15:57] <dednick> kenvandine: line?
[16:08] <seb128> kenvandine, https://code.launchpad.net/~seb128/ubuntu-system-settings/titles-uis-tweaks-rtm/+merge/241578
[16:09] <kenvandine> dednick, sorry... http://bazaar.launchpad.net/~ken-vandine/ubuntu-system-settings/rtm-lp1336715.check.sync/revision/937
[16:09] <kenvandine> dednick, what do you think?
[16:12] <dednick> kenvandine: eh? whats the binding for?
[16:12] <Chipaca> seb128: have you ever had the duplicated indicator messages in the wild again?
[16:13] <seb128> Chipaca, no
[16:13] <Chipaca> seb128: ok
[16:14] <tedg> kenvandine, So, I really can't find it :-/ Any ideas of what to look for?
[16:16] <kenvandine> dednick, oh... i  was wrong
[16:16] <kenvandine> doesn't need the Binding, just fix for poweredSim
[16:17] <dednick> kenvandine: hm. might also need a check for a change in what "getOnlineSim()" returns.
[16:17] <kenvandine> dednick, ok, dropped the Binding and pushed again
[16:18] <Chipaca> larsu: did you do anything about the weird delete index error in the messaging indicator?
[16:18] <dednick> if there isn't already
[16:24] <kenvandine> dednick, got a bug number for the indicator bug?  i want to reference it in the test plan for the silo for QA
[16:24] <oSoMoN> pitti, pmcgowan mentioned that dpm and you discussed reviewing the set of font and lang packs in the touch seed, is bug #https://launchpad.net/bugs/1378184 on your radar?
[16:28] <kenvandine> tedg, sorry, let me look now
[16:28] <Chipaca> mpt: when can i have 10 minutes of an mpt to go over system update notification pitfalls with you?
[16:28] <mpt> Chipaca, ask Magdalena or Benjamin
[16:29] <larsu> Chipaca: weird index error?
[16:29] <kenvandine> tedg, ok... i was wrong we don't directly mess with the actions, we mock accountsservice
[16:29] <Chipaca> mpt: ok
[16:29] <Chipaca> larsu: the one on delete
[16:29] <Chipaca> or remove?
[16:29] <kenvandine> tedg, now i remember what jgdx was complaining about... the actions being hard to mock/test :/
[16:30] <Chipaca> larsu: let me dig up the pastebin for you again
[16:30] <tedg> kenvandine, Hmm, okay. They're not hard as much as it's easier when someone's done the foundation for you :-)
[16:31] <Chipaca> larsu: “g_menu_remove: assertion '0 <= position && position < menu->items->len' failed”
[16:31] <pitti> oSoMoN: (in meeting -- but no, not on my radar)
[16:31] <kenvandine> tedg, or that :)
[16:31] <kenvandine> tedg, so do the foundation for jgdx :)
[16:31] <larsu> Chipaca: ah that one. I think the issue was that I couldn't reproduce it
[16:32] <larsu> Chipaca: do you see this all the time?
[16:32] <Chipaca> larsu: no, only seen it once as far as i can tell
[16:34] <larsu> Chipaca: hm, okay. I can review the code, but can't promise anything without a way to reproduce
[16:37] <mhall119> kenvandine: BTW, Content Hub's .move is still failing for me on RTM #7
[16:37] <mhall119> is there still a known issue?
[16:37] <kenvandine> mhall119, no... that should have been fixed
[16:38] <kenvandine> it was confirmed fixed in the music-app
[16:38] <mhall119> kenvandine: memebook is still failing :(
[16:38] <kenvandine> mhall119, any errors?
[16:38] <kenvandine> initctl set-env --global CONTENT_HUB_LOGGING_LEVEL=2
[16:38] <Chipaca> larsu: i understand; thank you. I guess I can review the code too -- I'll see if I can't take a look later this week
[16:38] <kenvandine> mhall119, do that then try
[16:38] <kenvandine> and look at the logs
[16:38] <mhall119> kenvandine: I'll try that after UOS and pastebin the logs
[16:39] <kenvandine> thx
[16:39] <mhall119> np
[16:41] <oSoMoN> pitti, on whose radar should it be? or how do I bribe you to get it on your radar? ;)
[16:41] <dednick> kenvandine: https://bugs.launchpad.net/ubuntu-rtm/+source/indicator-network/+bug/1391940
[16:41] <kenvandine> dednick, thanks
[16:42] <pitti> oSoMoN: well, the hard bit is choosing an adequate font package (can't help with that), and after that it's a trivial seed addition?
[16:42] <pitti> oSoMoN: I can help with rebuilding/uploading ubuntu-touch-meta or something like that
[16:44] <Riku-san> hmm so trusty wsn't working, I tried saucy and I think it may be working judging by how long it's taking
[16:44] <oSoMoN> pitti, I can’t really tell whether that’s the best choice, but fonts-lohit-deva was suggested, and from my very shallow tests it seems to do the job
[16:44] <Riku-san> on the flashing screen
[16:44] <Riku-san> annnd nope
[16:44] <Riku-san> 'Booting failed'
[16:45] <Riku-san> when it booted to recovery at first it did mention that it failed to load /cache/ubuntu something
[16:46] <Riku-san> and it couldn't find autodeploy.zip
[16:47] <Riku-san> any ideas?
[16:47] <Riku-san> my device is grouper
[16:48] <oSoMoN> kenvandine, hey, I could use a core-dev ack on the packaging changes in https://code.launchpad.net/~osomon/webbrowser-app/sanity-unit-tests/+merge/241543 , when you have a moment
[16:48] <kenvandine> oSoMoN, sure
[16:48] <Riku-san> the error was 'E:Can't open /cache/recovery/ubuntu_command'
[16:48] <Riku-san> then 'Checkinf for autodeploy.zip'
[16:48] <oSoMoN> kenvandine, all it does is adding a build dep, and re-ordering existing one alphabetically
[16:48] <Riku-san> *Checking
[16:48] <Riku-san> 'autodeploy.zip not found.'
[16:49] <oSoMoN> s/one/ones/
[16:50] <kenvandine> oSoMoN, does that add python3-flake8 as a build depends?
[16:50] <oSoMoN> kenvandine, it does, yes
[16:50] <kenvandine> that's in universe
[16:50] <kenvandine> the browser is in main
[16:50] <kenvandine> so that'll need a MIR first
[16:51] <oSoMoN> argh, dammit, not the first time I’m being bitten by this
[16:51] <kenvandine> :/
[16:51] <oSoMoN> nevermind then, I’ll withdraw this MR for now
[16:51] <kenvandine> oSoMoN, that's why you get the core-dev ack :)
[16:51] <oSoMoN> kenvandine, thanks for the review! :)
[16:51] <kenvandine> np
[16:52] <kenvandine> i'm surprised nothing in main needs that yet
[16:52] <kenvandine> oh, it's a wrapper
[16:56] <oSoMoN> kenvandine, it looks like python-flake8 is in main, I can probably update the dep to use that instead, I don’t think that will make any difference in the actual checks being run
[16:56] <kenvandine> ok
[16:58] <oSoMoN> kenvandine, done
[16:59] <Riku-san> I think I may have fixed it
[16:59] <Riku-san> previously I had erase userdata and system (and it warned me that I should have formatted them)
[16:59] <Riku-san> so I did and it hasn't thrown any errors yet
[17:00] <Riku-san> s/erase/erased
[17:02] <Riku-san> I hope this works
[17:04] <Riku-san> I think it's doing something because last time it was on the flashing screen for less than a minute
[17:05] <kenvandine> oSoMoN, great, done
[17:05] <Riku-san> I like how I don't exist here
[17:05] <Riku-san> but meh
[17:06] <Riku-san> the moment of truth...
[17:07] <Riku-san> YESYESYES
[17:08] <Riku-san> it booted
[17:08] <Riku-san> and then hung :(
[17:09] <oSoMoN> kenvandine, thanks!
[17:09] <kenvandine> oSoMoN, np
[17:09] <Riku-san> rebooting...
[17:10] <Riku-san> YES
[17:10] <Riku-san> it works
[17:10] <Riku-san> take that 'oh grouper isn't supported' guy who didn't even remotely help me solve my problem by telling me it wasn't supported
[17:11] <Riku-san> well this is stable...
[17:11] <ogra_> Riku-san, well, it isnt supported and the image is so old that the majority of apps from teh store wont run
[17:11] <Riku-san> 14.04 is old?
[17:11] <ogra_> touch ?
[17:11] <Riku-san> yes
[17:12] <ogra_> what image number is that ? we definitely didnt build a final 14.04 for grouper
[17:12] <Riku-san> 294 iirc
[17:13] <Riku-san> it's about as stable as windows 95 underwater
[17:13] <ogra_> yeah
[17:13] <ogra_> the released image was 303
[17:13] <Riku-san> as in it hangs at random times so my average uptime is 20 seconds
[17:13] <ogra_> you are actually not *that* far behind :)
[17:14] <Riku-san> any idea why it hangs so much?
[17:15] <ogra_> i doubt anyone even looked at grouper since jan/feb ... when it became clear we will switch to flo, might well be the graphics driver
[17:16] <Riku-san> I have a working graphics driver
[17:16] <Riku-san> how can I push it into the .tar.xz ?
[17:20] <Riku-san> hello?
[17:20] <Riku-san> I pulled the drivers from the linux for tegra package
[17:23] <Riku-san> what is a tar.xz anyway? how do I make one
[17:24] <Riku-san> I managed to extract it but how would I recompress it?
[17:28] <ogra_> Riku-san, touch uses android drivers
[17:28] <Riku-san> and I have the nvidia armhf gpu drivers
[17:35] <kenvandine> seb128, build complete in silo 3
[17:35] <kenvandine> seb128, how would we word the testing verification for the header/title change?
[17:38] <Tassadar> rsalveti: hi, I'm working on some project where I need multiple instances of android emulator running, and adb often fails to connect to the emulator - it just shows the device as "offline" or not at all. Did you encounter that issue when working on the UT emulator? Or are you using ssh for everything?
[17:39] <seb128> kenvandine, not sure "check that the title items look closer from the design"
[17:39] <kenvandine> seb128, that's pretty vague.. but that's the best i came up with :)
[17:40] <seb128> kenvandine, yeah...
[17:41] <kenvandine> brendand, ^^ i just marked silo 3 as testing and needs QA verification... give seb128 or myself a shout if you guys need more clarification on the title item verification
[17:42] <kenvandine> s/testing/tested/
[17:45] <rsalveti> Tassadar: hm, I tried with a few instances and was working fine, but you need to specify the port you want to connect
[17:45] <rsalveti> each emulator will have 2 adb ports
[17:46] <rsalveti> and only one can really receive new connections
[17:46] <Tassadar> one is qemu console and one is adb connection from what I've understood
[17:46] <Tassadar> hmm, I'll try to make it "offline" in adb devices again and then specify where I wanna connect to
[17:47] <rsalveti> right
[17:47] <lool> ogra_: hey, so I've poked brendand who pointed at jibel who pointed at you about promotion of vivid-proposed to vivid :-)
[17:47] <rsalveti> I can give it a try as well in a few minutes to see
[17:47] <lool> ogra_: what are your expectations/blockes?
[17:47] <ogra_> lool, LOOL
[17:48] <ogra_> lool, well, "it boots" is my criteria for such an early devel image ... but it should at least be boot tested once on all arches we support
[17:48] <ogra_> mako, krillin, both emulators, flo and manta
[17:49] <lool> ogra_: OGRA
[17:49] <ogra_> haha
[17:50] <rsalveti> OMG
[17:51] <ogra_> :)
[17:51] <Tassadar> rsalveti: what exactly do you mean by "specify the port you want to connect to"?
[17:51] <rsalveti> I think each port will have a serial
[17:51] <rsalveti> adb devices should show them
[17:51] <ogra_> yeah
[17:52] <ogra_> and you can specify then with -s
[17:52] <ogra_> when connecting to one
[17:52] <ogra_> adb should also complain on the host that there are multiple devices
[17:52] <Tassadar> heh, so I take it you didn't have the issue at all
[17:52] <Tassadar> for me the problem is the emulator shows as "offline"
[17:52] <Tassadar> so I can't connect to it
[17:53] <ogra_> Tassadar, offline means that the gadget is configured biut that the adbd daemon isnt up on the device
[17:53] <ogra_> i assume thats not ubuntu ?
[17:53] <Tassadar> no
[17:53] <Tassadar> hmmm, it works now :D dammit
[17:53] <ogra_> you might need to have developer builds or some such when doing that with android
[17:54] <lool> ogra_: did you say manta?
[17:54] <Tassadar> now it looks like adb just sometimes takes longer to launch
[17:54] <Tassadar> yeah
[17:54] <Tassadar> hm
[17:54] <Tassadar> okay, problem solved I guess
[17:55] <ogra_> lool, yep, i did
[17:55] <ogra_> manta is the only device we have the sidestage enabled on
[17:55] <lool> ack
[17:56] <lool> jibel / brendand: would you have the LP id for the clock app issue?
[18:00] <Wellark> kenvandine: having a sick leave today
[18:00] <Wellark> kenvandine: but you should ping the guys who have worked on the fix
[18:00] <dobey> does anyone know if there is a way to determine if something is being cross-compiled or not, in cmake?
[18:00] <Wellark> AFAIK it was done on unity8 side
[18:02] <Wellark> dobey: check this: https://wiki.debian.org/CrossBuildPackagingGuidelines
[18:02] <Wellark> ifeq ($(DEB_BUILD_GNU_TYPE),$(DEB_HOST_GNU_TYPE))
[18:03] <dobey> Wellark: keyword *cmake* :)
[18:03] <dobey> not in debian packaging
[18:04] <Wellark> dobey: well, I assumed you need to change something in your cmake configuration when building debs :)
[18:04] <Wellark> you could always pass whatever -D in debian/rules
[18:04] <Wellark> jussi might know how to do that in plain cmake alone, but he is on vacation
[18:05] <dobey> Wellark: no, i'm building a click
[18:06] <kenvandine> Wellark, we confirmed that fix is in rtm, so i guess a new bug
[18:20] <dobey> ah well
[18:21] <Wellark> kenvandine, dednick: did you confirm the gaction state?
[18:25] <Wellark> kenvandine, dednick: https://bugs.launchpad.net/ubuntu-rtm/+source/indicator-network/+bug/1391940
[18:27] <Wellark> kenvandine, dednick: it's actually system-settings ;(
[18:27] <Wellark> http://pastebin.ubuntu.com/8969057/
[18:28] <kenvandine> Wellark, i pasted it to the bug
[18:28] <kenvandine> Wellark, yes, in the battery plugin it uses libnm
[18:28] <kenvandine> Wellark, bug... in vivid it works properly
[18:28] <kenvandine> s/bug/but/
[18:28] <ogra_> whats vivid ?
[18:28] <dednick> Wellark: i confirmed that the gaction state was not changing, but the wifi was turned on/off.
[18:28] <ogra_> :P
[18:29] <kenvandine> Wellark, and in rtm it does disable wifi and the indicator icon does change from wifi to edge
[18:29] <kenvandine> just the switch doesn't change
[18:30] <dednick> Wellark: it seems that the indicator is not sensitive to the dynamic changes is libnm in rtm.
[18:31] <dednick> (or wherever it gets the network state from)
[18:31] <dednick> s/indicator/indicator switch
[18:31] <dednick> since the icon does change
[18:32] <Wellark> dednick, kenvandine: please see my latest comment in the bug report.
[18:32] <Wellark> kenvandine: nobody should touch the wifi enabled property of NM on Touch
[18:32] <Wellark> I just was not aware that the battery did it
[18:33] <dednick> Wellark: why not?
[18:33] <kenvandine> Wellark, sure, we could do that
[18:33] <dednick> i mean "what is the reasoning behind that"
[18:33] <kenvandine> but this does work in vivid... so seems this should work in rtm
[18:34] <Wellark> dednick: long story short: it was agreed in Malta that nobody should touch the WifiEnabled property of NM as it's problematic
[18:34] <Wellark> it has some fundamental problems in terms of interaction
[18:34] <dednick> i c.
[18:34] <Wellark> so we agreed that instead of using it
[18:34] <Wellark> we go to the radios directly through URfkill
[18:34] <Wellark> and let NM just react to the wifi device being disabled
[18:35] <Wellark> and this is easy to fix. just copy paste the few lines of QML from the wifi panel to battery panel and you are all fine
[18:35] <Wellark> kenvandine: --^
[18:35] <kenvandine> pmcgowan, we need to prioritize bug 1391940
[18:35] <kenvandine> pmcgowan, it only affects rtm
[18:35] <Wellark> updating the titel.
[18:35] <Wellark> *title
[18:36] <Wellark> well, it working on vivid is just pure luck
[18:36] <kenvandine> but should be fixed in vivid too of course
[18:36] <Wellark> :)
[18:36] <pmcgowan> kenvandine, is that not the same sync issue from earlier?
[18:36] <kenvandine> no
[18:36] <kenvandine> it's the battery plugin using libnm to control wifi instead of the action in the indicator
[18:36] <kenvandine> like the wifi plugin does
[18:37] <kenvandine> pmcgowan, for some reason it works properly in vivid, but not rtm
[18:37] <kenvandine> so we just need to make it use the action just like the wifi plugin does
[18:37] <Wellark> just like 10 lines of QML
[18:37] <kenvandine> but it's a regression in rtm, somewhere in the past few images
[18:37] <pmcgowan> kenvandine, sounds good, attach an MR and we can approve landing
[18:37] <kenvandine> Wellark, agreed... and we can drop some cpp
[18:38] <Wellark> and indeed. there is a grave risk that hitting the switch item in the battery page does not actually power down the chipset
[18:38] <Wellark> but I think we already have enough validation to land to RTM
[18:38] <dednick> yeah, i saw some cases where it wasn't powering up/down
[18:38] <dednick> bit random
[18:39] <Wellark> yes. it is :)
[18:39] <Wellark> I totally forgot the battery page has a wifi switch
[18:39] <Wellark> would have checked that earlier if I knew
[18:44] <Wellark> kenvandine: just send me an email if you need any help
[18:48] <kenvandine> Wellark, i think i have it
[18:48] <kenvandine> just building it now
[19:10] <kenvandine> Wellark, i pushed branches with that fix for both trunk and rtm
[19:27] <kenvandine> seb128, can you please review https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/lp1391940/+merge/241607
[19:28] <kenvandine> seb128, i needed to rebuild vivid silo 5 because one of jgdx's branch had been superseded, so i added that branch to the silo too
[19:29] <kenvandine> with hopes it gets approved without issue :)
[19:29] <seb128> kenvandine, can do that later but I'm about to go for tennis
[19:29] <kenvandine> ok
[19:29] <kenvandine> seb128, enjoy!
[19:30] <kenvandine> Wellark, or if you have time, maybe you can give me a review
[19:43] <DLmass> Hey. Is it possible to install Ubuntu on xperia arc s?
[19:44] <dobey> !devices | DLmass
[19:46] <DLmass> ah. Not supported..
[19:58] <Riku-san> how do I make ubuntu-device-flash bypass image verification?
[19:58] <Riku-san> I modified the image, but when I try to flash it starts downloading a new one
[19:59] <Riku-san> I feel like I need to sideload it
[20:05] <mterry> cwayne, has there been any use yet of the wizard customization support?
[20:06] <cwayne> mterry: nothing other than the nokia here stuff (which im not even sure that counts)
[20:06] <mterry> cwayne, naw, not in the sense I'm talking.  I'm considering changing the path you would use when dropping files in place.  Just wanted to confirm I wouldn't break anything
[20:06] <Riku-san> no answer?
[20:07] <cwayne> mterry: yeah, shouldn't break anything
[20:08] <kenvandine> Riku-san,  you won't be able to change the image used in flashing that way
[20:08] <kenvandine> you'll need a channel to use, not sure the details on how
[20:08] <kenvandine> but there is steps in place to verify the images in the channel
[20:09] <kenvandine> Riku-san: i'd imagine there is a way to use your image, just not with ubuntu-device-flash
[20:10] <kenvandine> and your updates will get broken
[20:11] <taiebot> Looks like vivid got qt5.3.2 has anyone upgraded to vivid #18? i am interested to see if apps are starting up faster?
[20:15] <kenvandine> renatu, what's the word on updating syncevolution in vivid?
[20:15] <kenvandine> is that package good?
[20:15] <renatu> kenvandine, is working nice for me. hey bfiller what do you think?
[20:36] <bfiller> renatu, kenvandine: i haven't tested it enough. only tried it once for contacts and it worked.
[20:37] <bfiller> renatu, kenvandine : I tried it once for calendar but just an initial sync
[20:37] <bfiller> didn't test making mods, etc
[20:46] <pierrec> hi all
[20:46] <kenvandine> renatu, bfiller: so is that a no for now?
[20:47] <pierrec> I've got a question concerning installing unbuntu touch on a nexus4...
[20:47] <bfiller> kenvandine: I think so, unless renatu has run through the full test plan
[20:47] <kenvandine> renatu, ok, it's up to you then :)
[20:47] <renatu> renatu, is too much for me, lets wait more :D
[20:48] <pierrec> I'm trying to do it, using ubuntu-device-flash, but I get stuck in recovery mode after a few lines of CLI ouput...
[20:48] <kenvandine> renatu, haha, if you are telling yourself that, i guess i'll hold off too :)
[20:49] <renatu> :D
[20:49] <pierrec> (I'm using the --bootstrap flag, and I start in teh bootloader on my nexus 4
[20:49] <kenvandine> pierrec, not sure, did you bootstrap in fastboot mode?
[20:49] <pierrec> anyone has seen this behaviour before?
[20:49] <pierrec> yes
[20:49] <pierrec> (I guess)
[20:50] <kenvandine> pierrec, sorry, i haven't seen that
[20:50] <bfiller> renatu: run through the test plan for calendar and contacts and if it works I'm +1
[20:50] <pierrec> I did: "adb reboot bootloader"
[20:50] <bfiller> I only spend a few minutes on it
[20:50] <kenvandine> unless maybe you weren't in fastboot
[20:50] <pierrec> ok. how do I get in fastboot?
[20:50] <pierrec> (I probably messed that up)
[20:50] <renatu> I am using it on my daily phone but I did not go through the tests plan yet
[20:51] <renatu> I will do that
[20:51] <kenvandine> pierrec, after rebooting into the bootloader
[20:51] <kenvandine> fastboot devices
[20:51] <kenvandine> does that show your device?
[20:52] <kenvandine> and did you run "sudo fastboot oem unlock" ?
[20:52] <pierrec> kevandine: I did the second thing (got the bootloader to say: unlocked)
[20:52] <kenvandine> ok
[20:52] <kenvandine> and you rebooted into fastboot right?
[20:53] <kenvandine> before running ubuntu-device-flash with --bootstrap?
[20:53] <sarnold> hello, is it expected that my nexus 4 never actually updates any of the applications on the device? I haven't seen any upgrades ever work and I'm wondering if this is known or if everyone just flashes entirely new images often enough to not see this
[20:53] <pierrec> I'm gonna give it another go... (boot in android, and then use fastboot to reboot?
[20:53] <pierrec> )
[20:53] <kenvandine> pierrec, no, don't boot into android
[20:54] <pierrec> uhm
[20:54] <pierrec> so from the bootloader?
[20:54] <kenvandine> Reboot into the bootloader by pressing the correct physical button combination for your device type as shown here: https://source.android.com/source/building-devices.html#booting-into-fastboot-mode
[20:54] <pierrec> done
[20:54] <kenvandine> sarnold, what channel?
[20:54] <taiebot> sarnold: you need to re-enter your ubuntu one acount
[20:54] <sarnold> taiebot: ooooooo
[20:54] <kenvandine> pierrec,  now you should be able to flash with --bootstrap
[20:54] <pierrec> sudo fastboot devices does show my device
[20:55] <sarnold> taiebot: would you know off-hand how to file a bug against the "Updates" part of the system settings?
[20:56] <pierrec> kenvadine: thanks for the help, but I get the exact same problem
[20:56] <kenvandine> sarnold, just file it against the ubuntu-system-settings package
[20:56] <sarnold> kenvandine: I've got "ubuntu 14.10 (r7) in the system information screen
[20:56] <kenvandine> sarnold, is it about this issue?  because that's a bug that has already been fixed
[20:56] <taiebot> sarnold: there was a change which required people to re-enter there ubuntu one account  https://lists.launchpad.net/ubuntu-phone/ this has been discussed plenty of time in the mailing list
[20:56] <sarnold> kenvandine: thanks
[20:57] <kenvandine> pierrec, sorry... dunno then :/
[20:58] <taiebot> sarnold: Do not bother it will be rejected has it was fixed already. You just did not know :-D.
[20:58] <jgdx> kenvandine, superseeded due to failing tests, so nothing major
[20:58] <jgdx> upower failure, that is
[20:58] <kenvandine> yeah, i've already rebuilt it in the silo with the new branch
[20:58] <kenvandine> jgdx, can you review my branch?
[20:58] <jgdx> kenvandine, sure
[20:58] <kenvandine> it's blocking the silo :)
[20:59] <kenvandine> https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/lp1391940/+merge/241607
[20:59] <kenvandine> jgdx, and if you want to test it, you can grab vivid silo 5
[20:59] <sarnold> taiebot: I disagree that it has been fixed :) a huge pile of "0%" progress bars is not wonderful :)
[21:00] <sarnold> taiebot: but now that i've re-signed-in it's downloading as I expected. Thanks! It feels a lot less broken now...
[21:00] <kenvandine> sarnold, yeah... problem is you needed to get an update to get the fix :/
[21:00] <jgdx> kenvandine, like a normal silo?
[21:00] <sarnold> kenvandine: r7 is known broken?
[21:00] <kenvandine> jgdx, yeah, ubuntu 5
[21:00] <kenvandine> sarnold, i'm sure that's from before the u1 token change
[21:01] <kenvandine> dobey, ^^ you would know for sure
[21:01] <kenvandine> 14.10 r7 sounds pretty old :)
[21:01] <taiebot> sarnold: i know but we are still all beta-tester  :-D at the moment there is still some bugs that needs to be solved by the user. Sometime it is useful to get your hands dirty.
[21:02] <sarnold> kenvandine: heh, it just downloaded 14.10 r7 last night
[21:02] <kenvandine> sarnold, what channel?
[21:02] <kenvandine> i have 15.10 (r18)
[21:02] <kenvandine> whoops
[21:02] <kenvandine> 15.04
[21:03] <sarnold> kenvandine: About This Phone says "14.10 (r7)", no idea what channel that is..
[21:03] <taiebot> I have 14.10 rtm 130
[21:03] <taiebot> You are on the stable release of the rtm
[21:03] <kenvandine> sarnold, what channel did you install from last night?
[21:03] <kenvandine> you can also click on "OS" in the about panel of system-settings
[21:04] <kenvandine> although that doesn't clearly show the channel
[21:04] <kenvandine> annoying
[21:04] <sarnold> kenvandine: I haven't used the phablet-flashy thing in weeks, I've been using the OTA updates
[21:04] <sarnold> ... are we not supposed to use the OTA updates?
[21:04] <kenvandine> sarnold, yes... you should
[21:04] <taiebot> sarnol: yes but there are too may channels.......
[21:05] <taiebot> many sorry
[21:05] <kenvandine> so your might have gotten the latest from an older channel
[21:05] <sarnold> kenvandine: ah there it is, ubuntu utopic unicorn (development branch) 20141107-153000
[21:05] <sarnold> argh
[21:05] <sarnold> sigh
[21:05] <sarnold> so I've been fiddlinmg with a zombie? sure it gets updates but no one else cares about it?
[21:06] <ogra_> all focus is on 14.09 RTM
[21:06] <kenvandine> so you must be using the utopic channel not the devel alias to the channel
[21:06] <taiebot> sarnold: be careful this ones might get very edgy, i would advise you to be on the channel you are on
[21:06] <kenvandine> so it didn't get switched automatically
[21:06] <ogra_> (for QA and fixes)
[21:06] <kenvandine> sarnold, ubuntu-device-flash --channel=devel
[21:06] <kenvandine> or devel-proposed
[21:06] <sarnold> hehe, 14.09 "sounds" even older than 14.10 :)
[21:06] <kenvandine> to switch
[21:07] <ogra_> kenvandine, no, the devel alias still points to utopic until there is the first promoted vivid image
[21:07] <kenvandine> ah!
[21:07] <kenvandine> that's why
[21:07] <ogra_> which means we need to pull resources out of stabilizing RTM 14.09 ... to verify the images
[21:07] <kenvandine> sarnold, so listen to ogra_, not me :)
[21:07] <ogra_> but we dont have these atm
[21:08] <kenvandine> sarnold, i run devel-proposed (vivid) on my mako
[21:08] <sarnold> "Seth Should Install ____ on his nexus 4 to be most helpful"  :)
[21:08] <sarnold> off to lunch, I'll see results whe nI return :)
[21:08] <sarnold> thanks guys
[21:08] <taiebot> kenvandine: Any performance improvement with qt5.3.2? on vivid r18? are apps starting faster. this would make me switch
[21:08] <kenvandine> taiebot, i haven't profiled
[21:08] <kenvandine> but it works :)
[21:09] <kenvandine> my mako isn't my daily driver though, my daily driver is krillin with 14.09-proposed
[21:12] <taiebot> Was there a battery improvement on r131 i am getting a flat line at 100%
[21:13] <jgdx> kenvandine, had a misfire (duplicate silos), reloading
[21:15] <kenvandine> jgdx, thx
[21:17] <jgdx> kenvandine, hm, no. Can't seem to get silo 5 installed. $ citrain device-upgrade 5 nnnn ubuntu  ?
[21:17] <kenvandine> what happens?
[21:17] <jgdx> it finishes seemingly OK but I'm not seeing the "wifi multiple fixes"
[21:17] <kenvandine> phablet-shell and check
[21:17] <kenvandine> see what's installed
[21:18] <kenvandine> apt-cache policy ubuntu-system-settings
[21:20] <jgdx> kenvandine, can you give me 10 mins?
[21:20] <kenvandine> sure
[21:20] <jgdx> I broke it
[21:22] <dobey> kenvandine: misssed the conversation. what would i know?
[21:22] <kenvandine> dobey, never mind :)
[21:22] <dobey> ok
[21:26] <jgdx> kenvandine, should not the dialog be scrollable by now? I'm not quite sure where that fix is.
[21:26] <jgdx> kenvandine, I thought it maybe came before the resize fix?
[21:27] <kenvandine> jgdx, that should be
[21:27] <kenvandine> and it worked for me
[21:27] <jgdx> kenvandine, you could flick the dialog
[21:27] <kenvandine> yes
[21:27] <kenvandine> in wifi add other network
[21:28] <kenvandine> is your vivid image current?
[21:28] <jgdx> kenvandine, ish
[21:28] <kenvandine> that uitk just landed in vivid like monday
[21:28] <kenvandine> i think
[21:28] <jgdx> oh
[21:28] <kenvandine> jgdx, for now if you can just test my branch :)
[21:28] <kenvandine> i want a +1 on that
[21:28] <kenvandine> toggling wifi under battery
[21:29] <jgdx> kenvandine, just did. It werked
[21:29] <kenvandine> and checking the wifi toggle in the network indicator
[21:29] <kenvandine> great
[21:29] <kenvandine> jgdx, awesome, thanks
[21:29] <kenvandine> check what version of uitk you have
[21:29] <jgdx> kenvandine, it seems old
[21:29] <jgdx> (-er than Monday)
[21:30] <jgdx> upgrading as we speak
[21:30] <kenvandine> qtdeclarative5-ubuntu-ui-toolkit-plugin
[21:30] <jgdx> kenvandine, many thank yous for landing this!
[21:31] <kenvandine> :-)
[21:39] <jgdx> kenvandine, +1 on silo5
[21:39] <kenvandine> jgdx, thx
[21:50] <Riku-san> kenvandine: it's just a normal trusty image from the ubuntu-touch/trusty channel, but I added tegra drivers to it from linux for tegra because it kept hanging