[07:44] <epyx> hey guys, what's your take on user privacy using Ubuntu Touch?
[07:44] <epyx> will everything be leaked to Canonical as with Android to Google or iOS to Apple? :P
[08:03] <iamnoob> hi guys i want to install ubuntu touch on my device but my device is not in the list of supported devices so would it be good if i install ubuntu touch over it?
[08:05] <dholbach> good morning
[10:03] <JamesTait> Good morning all; happy Wright Brothers Day! :-D
[10:08] <ogra_> asac, ?
[10:13] <Mirv> sil2100: jibel: so, gallery-app is totally no-go. 1) it has invalid framework so can't be uploaded (ubuntu-sdk-14.10-dev2), 2) dholbach found for me that the current version in the store is 2.9.1.1101 which means they have already uploaded from the vivid trunk branch to the store (mine from rtm branch is 2.9.1.1049)
[10:13] <Mirv> bfiller: ^
[10:14] <Mirv> apparently 1101 at least was not yet using anything not available in rtm, so the current version isn't broken
[10:15] <Mirv> I guess we would need another rtm branch branching from 1101, adding fixes on top of that and making sure no lp:gallery-app versions are uploaded to the store as long as we have only one store
[10:18] <Mirv> it looks like lp:gallery-app/rtm-14.09 would have a merge from trunk at when lp:gallery-app was at the rev 1111. so the new rtm package, if somehow for example version mangled and published, would bring revisions 1102-1111 + the new fixes.
[10:24] <sil2100> ....
[10:25] <sil2100> I explicitly talked with bfiller yesterday, and he said he's aware that we have only one store
[10:26] <sil2100> Love those complications
[10:26] <Mirv> bfiller: that has happened a month or two ago though
[10:26] <Mirv> sil2100: that is
[10:26] <sil2100> Mirv, dholbach: thanks!
[10:26] <sil2100> Let's wait for bfiller for that then, but I'm afraid this batch of fixes just won't make it then
[10:26] <sil2100> ;/
[10:27] <Mirv> sil2100: bfiller: jibel: I've pushed https://code.launchpad.net/~phablet-team/gallery-app/rtm-14.09-new that is bit-for-bit identical with the rtm-14.09 branch, but with better revision numbering wrt to store (and more clear history). the only change is 1113 update of the framework, and I'll start a build of that branch but this starts to be a bit complicated for me to "just" upload the new thing to the store?
[10:28] <Mirv> technically there should be anything wrong with this, but I'd absolutely need some ack:s from you first to feel certain ;)
[10:28] <sil2100> Mirv: ok, so if you're sure that the contents (besides the framework change) are the same, I would give it a try
[10:29] <sil2100> Especially that gallery had so many critical fixes
[10:29] <sil2100> But I want jibel to comment as well...
[10:29] <Mirv> sil2100: could you double-check for me: bzr branch lp:~phablet-team/gallery-app/rtm-14.09-new , bzr branch lp:~phablet-team/gallery-app/rtm-14.09 , rm -rf rtm-14.09/.bzr rtm-14.09-new/.bzr , diff -urN rtm-14.09 rtm-14.09-new ?
[10:29] <sil2100> Mirv: sure ;)
[10:30]  * sil2100 trusts Mirv's checks always anyways
[10:31] <jibel> Mirv, I've no idea what the impact of the update of the framework is :) If you and sil2100 say it is fine, we can test the new build again.
[10:32] <sil2100> Mirv: all looks cool here as well \o/
[10:32] <Mirv> sil2100: thanks!
[10:33] <Mirv> jibel: I'm not really familiar with the frameworks either, but my understanding is that in this case the change doesn't change anything. lool just announced 6 days ago that everyone needs to switch from the older framework names to the non-dev one. https://lists.launchpad.net/ubuntu-phone/msg10750.html
[10:34] <Mirv> those were used during utopic development
[10:41] <sil2100> I also think this implies no change to the current application's operation
[10:45] <Mirv> sil2100: jibel:: new .click at http://s-jenkins.ubuntu-ci:8080/job/gallery-app-click-from-branch/lastSuccessfulBuild/artifact/out/com.ubuntu.gallery_2.9.1.1113_armhf.click - does it need retesting or shall I just upload it?
[10:46] <sil2100> jibel: ^ ? Do you think it needs re-testing? Only the framework changed and I'm pretty sure this should change anything in the application, but I'm not an expert on this topic
[10:46] <sil2100> *shouldn't
[10:46] <jibel> sil2100, I'll do a quick test to make sure it's alright.
[10:46] <jibel> Mirv, ^
[10:47] <sil2100> Ok, thanks :)
[10:48] <Mirv> jibel: thanks!
[10:52] <jibel> Mirv, the gallery hangs when I open from the scope
[10:52] <jibel> s/hangs/crash
[10:53] <sil2100> uh?
[10:53] <sil2100> :O
[10:54] <sil2100> Due to a different framework?
[10:55] <iamnoob> hi guys i want to install ubuntu touch on my device but my device is not in the list of supported devices so would it be good if i install ubuntu touch over it?
[10:55] <iamnoob> hi guys i want to install ubuntu touch on my device but my device is not in the list of supported devices so would it be good if i install ubuntu touch over it?
[10:56] <Mirv> jibel: uh oh :( and you don't have any duplicate gallery-app .deb installed, just the .click updated?
[10:56] <jibel> Mirv, yes, just the click from jenkins, but it happened only once.
[10:57] <jibel> I'm trying to figure out what happened
[11:02] <jibel> Mirv, hm, crashed again but this time while switching photos
[11:22] <Mirv> jibel: code wise it is identical to what was previously tested. we'd need someone in the know with the frameworks if it's truly so that with the ubuntu-sdk-14.10 framework instead of -dev3 there are some problems (for example, coming from additional app containment restrictions or such)
[11:24] <jibel> Mirv, crashes are rather random. I'll try with 1101 again.
[11:46] <jibel> Mirv, it could be a QML cache issue
[11:46] <jibel> it is certainly it
[11:47] <jibel> Mirv, there are several apparmor denials for files in the cache
[11:49] <jibel> Mirv, confirmed, if I clear the QML cache, the app crashes
[11:49] <jibel> Trying with 1101 now
[11:49] <jibel> sil2100, ^^
[11:50] <sil2100> \o/
[11:50] <jibel> sil2100, it'd rather be /o\
[11:55] <jibel> Mirv, sil2100 cannot reproduce with 1101. So it's a no-go for 1139
[11:55] <sil2100> Ouch...
[11:56] <sil2100> I wonder what's up with that?
[11:56] <sil2100> Anyway, yeah, let's not risk it
[11:56] <jibel> Mirv, sil2100 test case is, remove the QML cache of the gallery app, take a photo, go to the photo scope, open the photo.
[11:56] <jibel> with 1139 gallery-app crashes
[11:58] <jibel> sil2100, with 1139 there are messages like: Dec 17 12:12:30 ubuntu-phablet kernel: [  387.562605]type=1400 audit(1418814750.945:114): apparmor="DENIED" operation="open" profile="com.ubuntu.gallery_gallery_2.9.1.1113" name="/home/phablet/.cache/QML/Apps/" pid=7581 comm="gallery-app" requested_mask="r" denied_mask="r" fsuid=32011 ouid=32011
[11:58] <jibel> I didn't see any with 1101
[11:59] <sil2100> jibel: did you see the same thing in the original version from the silo?
[11:59] <Mirv> jibel: ok :( no idea, but we can't risk it indeed.
[12:00] <jibel> sil2100, no, I'm trying it now
[12:00] <jibel> I could have missed it, but it didn't crash
[12:05] <jibel> sil2100, Mirv works fine with 1049 from the silo
[12:06] <jibel> it's a regression introduced by the update of the framework
[12:06] <sil2100> Oh my
[12:07] <sil2100> Good thing you tested this before we uploaded it, phew
[12:07] <jibel> yeah, always expect the unexpected
[12:07] <Mirv> that's why he's called the QA and we are not :)
[12:07] <jibel> sil2100, no denial and no crash
[12:08] <Mirv> sil2100: where could we find out more about the framework differences between -dev3 and 14.10 final?
[12:08] <Mirv> also, the ban to upload -dev3 packages came only last Thursday like mentioned
[13:09] <nerochiaro> ondra: you around ?
[13:10] <nerochiaro> ondra: i am trying to buidl the android side of hybris based on your notes, but i got stuck. not sure where to download the sources
[13:42] <ondra> nerochiaro no android side you need to build on your host
[13:42] <ondra> nerochiaro for which device?
[13:42] <nerochiaro> ondra: krillin
[13:43] <ondra> nerochiaro you need to fetch krilling tree then
[13:43] <nerochiaro> ondra: how ?
[13:44] <ondra> nerochiaro git pull :P
[13:45] <ondra> nerochiaro do you have access to barajas gerrit?
[13:45] <nerochiaro> ondra: no
[13:45] <nerochiaro> ondra: i never touched anything in android, so pardon my ignorance
[13:45] <ondra> nerochiaro then you need to talk to john-mcaleely
[13:45] <ondra> nerochiaro he will have to grant you access first
[13:46] <john-mcaleely> nerochiaro, what's your launchpad id?
[13:46] <nerochiaro> john-mcaleely: uriboni
[13:50] <john-mcaleely> nerochiaro, thanks!
[14:48] <kenvandine> mandel, did you figure anything out with the fix-pause branch?
[15:18] <mandel> kenvandine, I'm trying to see what is the diff between vivd and rtm, vivid seems to be working perfectly
[15:19] <mandel> kenvandine, in vivid I'm on r64
[15:19] <kenvandine> mandel, vivid isn't working for me
[15:19] <kenvandine> 64?
[15:19] <kenvandine> oh, different device maybe
[15:20] <mandel> kenvandine, yes, diff arch
[15:20] <mandel> :)
[15:20] <kenvandine> mandel, not working for me on vivid/mako/57
[15:20] <mandel> kenvandine, let me record a video for you
[15:22] <kenvandine> mandel, if you have a branch that adds more debug output, i'd be happy get more logs
[15:23] <mandel> kenvandine, give me a few misn
[15:23] <mandel> mins*
[15:32] <mandel> kenvandine, was it this ppa => https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-016 ??
[15:33] <kenvandine> mandel, no
[15:33] <kenvandine> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-002
[15:34] <mandel> ack
[15:42] <sil2100> dholbach: hello!
[15:42] <sil2100> dholbach: are you still around? :)
[15:42] <dholbach> yes
[15:43] <sil2100> dholbach: we have a new gallery-app in the store that we need approved, it has the proper framework and versioning now
[15:43] <sil2100> It's required for our ubuntu-rtm image
[15:43] <dholbach> is it the right version for the right image now?
[15:44] <sil2100> Yeah, I suppose all should be ok now - Mirv changed the framework and rebased the branch to generate a more proper version
[15:44] <dholbach> sil2100, Mirv: approved
[15:44] <sil2100> Thank you! :)
[15:45] <dholbach> anytime :)
[16:07] <mandel> kenvandine, debugging, this is super weird, I promise it was working :-/
[16:07] <kenvandine> mandel, i know
[16:08] <kenvandine> i saw it work too :)
[16:08] <mandel> kenvandine, well, two crazy people are not longer crazy, is called religion ;)
[16:09] <mandel> kenvandine, debugging atm
[16:52] <tedg> mpt, patriciadavila, so I'm looking at audio roles: https://wiki.ubuntu.com/Sound#Primary_sound_output_and_active_output_role
[16:52] <tedg> It seems like the spec basically covers when media is playing and when it's not.
[16:53] <tedg> But we have four volumes.
[16:53] <tedg> Does that mean that volume up/down never effect the other two?
[16:53] <tedg> I'm guessing the answer is now. If nothing else you'd definitely want to do phone when talking on the phone.
[16:54] <tedg> So that leaves alert/alarm
[16:54] <tedg> I'm not sure exactly how to tease those apart (or if they have value other than silent mode)
[16:58] <mpt> tedg, what are the other two?
[16:58] <tedg> mpt, phone/multimedia
[16:58] <tedg> mpt, multimedia is the default for apps that don't specify.
[16:59] <tedg> mpt, alert is ringer
[16:59] <mpt> tedg, so “multimedia” is not used “when media is playing”? What is?
[16:59] <tedg> mpt, Yes, when media is playing multimedia is used.
[17:00] <tedg> mpt, But when should you set the alarm volume for instance?
[17:00] <mpt> So what are the other two? :-)
[17:00] <tedg> phone, multimedia, alarm and alert.
[17:00] <mpt> Ah, sorry, I didn’t see when you posted them before
[17:00] <mpt> What is alert used for?
[17:00] <tedg> Ringer, SMS sounds, etc.
[17:01] <mpt> Notification sounds in general?
[17:02] <mpt> And phone is used during phone calls?
[17:02] <tedg> Yes, so that's what I'm looking to silence in silent mode.
[17:04] <mpt> Silence both phone and ringer?
[17:04] <mpt> errr, both phone and alert, I mean
[17:04] <tedg> No, phone is the headset volume. The phone ringer is on the alert channel.
[17:05] <mpt> The third hard problem in computer science.
[17:06] <mpt> Headset should be an output device, not an output role
[17:06] <tedg> Well, it's kinda both, but we're only talking about the inputs right now.
[17:06] <mpt> e.g. there should be a media volume for headset and a media volume for speaker
[17:07] <mpt> An alert volume for headset and an alert volume for speaker
[17:07] <tedg> It's a switchboard of volumes.
[17:07] <mpt> etc
[17:08] <mpt> tedg, does this work? <https://wiki.ubuntu.com/Sound?action=diff&rev2=136&rev1=135>
[17:08] <tedg> So yes, we're doing that. We technically though have a lot more outputs and inputs than most people would expect :-)
[17:09] <tedg> mpt, No, I think it should only be multimedia when media is playing.
[17:10] <tedg> mpt, Seems like default is adjusting the ringer (alert)
[18:58] <kenvandine> alesage, hey... any more insight into that autopilot problem?
[19:01] <dobey> kenvandine: what autopilot problem? (cursious as i've been having autopilot woes of my own)
[19:02] <kenvandine> dobey, we keep crashing autopilot in the settings tests
[19:02] <kenvandine> alesage thinks it's a tearDown problem with dbusmoc
[19:02] <kenvandine> +k
[19:02] <dobey> kenvandine: link to the log?
[19:02] <dobey> ah
[19:03] <kenvandine> https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/415/?
[19:03] <kenvandine> dobey, so if you have some insight :)
[19:03] <kenvandine> basically the thought is that it can't connect to the bus because the previous job didn't tearDown properly
[19:03] <alesage> kenvandine, a few other things on the plate but will push something in a bit
[19:04] <kenvandine> alesage, thanks, i'm switching gears to something else for now
[19:04] <kenvandine> just curious
[19:04] <alesage> kenvandine, elopio directing me to url-dispatcher as they don't inherit dbusmock there, instead use it as a fixture
[19:04] <kenvandine> i'm done beating my head against the wall for now, until someone has better ideas :)
[19:04] <alesage> kenvandine, very interested in getting this actually landed ;) , will carry it for now and ping you when it appears more working
[19:05] <kenvandine> thx :)
[19:06] <dobey> hmm
[19:07] <dobey> i see a lot of other problems in there anyway :)
[19:11] <dobey> anyway, different from my problems