[00:36] <ahayzen> vthompson, see my latest comment on https://code.launchpad.net/~vthompson/music-app/lookup-file/+merge/229612
[00:38] <vthompson> ahayzen, I see it. that makes sense. Filter should be reset
[00:39] <ahayzen> vthompson, cool :)
[00:40] <ahayzen> vthompson, shall i top approve https://code.launchpad.net/~vthompson/music-app/remove-white-error-labels-1353173/+merge/229713
[00:41] <vthompson> ahayzen, do you agree with the small color tweaks in the error msg and the confirm button?
[00:42] <ahayzen> vthompson, i think so
[00:42] <vthompson> I don't think the confirm button change was necessary, but I didn't like having them both grey
[00:42] <ahayzen> vthompson, but really i want to go through everything and make them use Theme.
[00:42] <ahayzen> yeah
[00:43] <vthompson> lol, I just updated the app and now clicking an album from the scope launches random apps. First clock now browser. lol
[00:43] <ahayzen> hah oh god not that again
[00:44] <vthompson> what'd you do to fix it?
[00:44] <ahayzen> nothing was the platform last time
[00:44] <vthompson> Seems that if I leave the music scope and go back into it it was OK
[00:44] <ahayzen> magic
[00:45] <vthompson> yelp it looks ok again.
[00:46]  * ahayzen hides
[00:46] <ahayzen> vthompson, top approve https://code.launchpad.net/~vthompson/music-app/remove-white-error-labels-1353173/+merge/229713 if u think its ok ...so it fixes the white on white issue for now...but i think we need to do an overall review of the colours at some point
[00:47] <vthompson> ahayzen, yea, I agree. That will probably come with the redesign overall
[00:47] <ahayzen> vthompson, for https://code.launchpad.net/~vthompson/music-app/lookup-file/+merge/229612 .. when the filter is cleared would onFilled not be called? and then trackClicked() ?
[00:48] <vthompson> ahayzen, I dont understand the question. the process function will reset the filters which forces the onfilled to be called
[00:48] <vthompson> when a new album is selected
[00:49] <sergiusens> slangasek: I asked on tech, doko answered; not supported yet; cgo is used to write bindings to c/c++
[00:49] <ahayzen> ok so u click on an album that filters the model... which then gets refilled...on filled is called.. it plays whtever is in the model... then the filter is cleared... the model reloads to the cleared set and would onFilled not be called again here? which would then cause trackClicked to be called on the clear filter model?
[00:50] <vthompson> yea, but selectedAlbum is now false ;)
[00:50] <OrokuSaki> @ogra console=tty? related??? Well I got 13.04 to work on my kernel.. when I run test_glesv2 I don't see the triangles.. unity8 does work...
[00:50] <meetingology> OrokuSaki: Error: "ogra" is not a valid command.
[00:50] <ahayzen> vthompson, ah yes ;)
[00:50] <OrokuSaki> @ogra_ console=tty? related??? Well I got 13.04 to work on my kernel.. when I run test_glesv2 I don't see the triangles.. unity8 does work...
[00:50] <meetingology> OrokuSaki: Error: "ogra_" is not a valid command.
[00:50] <ahayzen> vthompson, hehe i knew that would help when i did my first review lol..not..
[00:50] <OrokuSaki> anyone see my last 2 messages before I resend?
[00:51] <OrokuSaki> Oh well.. console=tty? related??? Well I got 13.04 to work on my kernel.. when I run test_glesv2 I don't see the triangles.. unity8 does work... Ogra???????
[00:51] <ahayzen> vthompson, oh last thing the var track = false ? and then track = musicStore.lookup() ... why not just var track = musicStore.lookup() ?
[00:51] <OrokuSaki> It's odd not to see triangles.. but have unity8 run
[00:51] <vthompson> ahayzen, well I'm glad you found a reason why we'd want to make sure it's reset
[00:51] <OrokuSaki> and see a screen
[00:51] <OrokuSaki> What do you guys think about that?
[00:53] <vthompson> ahayzen, because of the mediascanner2 code throwing an exception when the track is not found. This should leave track as 'false'
[00:54] <vthompson> we really dont need this as the check we do is just for debug... but really in the end we might want to choose to do something
[00:54] <ahayzen> vthompson, if it is throwing an exception then don't u need a try catch?
[00:54] <ahayzen> vthompson, and i thought it just returned null ?
[00:54] <vthompson> well, I'm not sure how we'd catch a c++ exception in javascript
[00:55] <vthompson> maybe it would return null. Undefined?
[00:55] <ahayzen> vthompson, hmmm ok we'll just leave for now
[00:55] <ahayzen> vthompson, i'll check over it when doing content-hub as that touches the same code
[00:56] <vthompson> ahayzen, ah yes, that might allow us to do a nice small test for not finding the requested song
[00:56] <ahayzen> :)
[00:56] <ahayzen> vthompson, i'll approve for now
[00:57] <ahayzen> vthompson, i'm gonna go to bed top approve the approved branches as u wish :) and could u have a check over listitem actions ... other than the colours/sizes i think it is there?
[00:59] <vthompson> ahayzen, yea, you'll merge trunk in the morning?
[00:59] <ahayzen> vthompson, i just did? ...
[00:59] <vthompson> ohhhh you're good
[00:59] <ahayzen> vthompson, well whtever was trunk 23mins ago :P
[00:59] <ahayzen> vthompson, anyway have fun o/
[01:00] <vthompson> ahayzen, ah that's just the ap and dev3 fixes. :)
[01:00] <vthompson> will do! Night!
[01:00] <ahayzen> yep :) u 2 cyas
[01:10] <OrokuSaki> failed to stat "/home/justin/UTATRUSTY/out/target/product/tenderloin/boot.img":
[01:11] <OrokuSaki> There was away around this with 13.04 anyone know 14.04? you have to remove this line in main.mk $(INSTALLED_BOOTIMAGE_TARGET_ANDROID) \ with 13.04
[05:58] <pitti> bzoltan: thanks for fixing the dev focus! (sorry for confusing terms; that's what I meant)
[05:59] <pitti> bzoltan: I think that'll also fix LP translations to now auto-commit to /staging, not to /trunk
[05:59] <bzoltan> pitti:  I might change it back  :D
[05:59] <pitti> and make MPs go to the right place
[05:59] <bzoltan> pitti:  the question is how CI works
[06:01] <pitti> bzoltan: ah, you mean you now need to tell it to land into lp:u-u-t/trunk ?
[06:02] <pitti> bzoltan: somehow it must work; autopilot is the same
[06:02] <pitti> bzoltan: i. e. lp:autopilot points to /trunk which is an actual trunk
[06:02] <pitti> bzoltan: and landings are from the lp:autopilot/1.5 branch, which reflects what's in the archive
[06:02] <bzoltan> pitti: Mirv just told me that CI lands on the lp:ubuntu-ui-toolkit  what is the staging branch
[06:03] <pitti> so thomi/veebers should know how this "real trunk" mode works with CI
[06:03] <bzoltan> pitti:  our case is different ... the lp:ubuntu-ui-toolkit now is the lp:ubuntu-ui-toolkit-trunk
[06:03] <pitti> bzoltan: that's the same in AP
[06:04] <pitti> i. e. development focus points to trunk, not to the archive branch
[06:04] <Mirv> bzoltan: elopio just mentioned autopilot is already exception, so maybe it could work for you too
[06:04] <pitti> TBH, that's the normal mode of development everywhere else in the world..
[06:04] <bzoltan> Mirv:  if we make it an exception :) before the actual landing
[06:05] <pitti> so "I want to upload" then becomes "merge trunk into archive branch"
[06:07] <bzoltan> pitti:  what you say makes sense ... the CI process should use an "archive" branch and let the projects do whatever they want
[06:08] <pitti> bzoltan: yeah, and as AP uses that I thought it would work
[06:09] <pitti> bzoltan: so, if that needs some special setup in CI and this blocks you from landing, I guess you need to switch back temporarily (too bad, but I guess this is not the time for dealing with such things)
[06:51] <dholbach> good morning
[07:04] <Saviq> tvoss, so... bug #1353855
[07:04] <tvoss> Saviq, yup, let me take care of it
[07:20] <Mirv> Kaleo: bzoltan: hey. before I drop this from my mind, have you removed the workarounds required during 5.2 that made app startup slower? bug https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1320823 should be fixed in Qt 5.3
[07:21] <bzoltan> Mirv:  I do not know.
[07:21] <Mirv> bzoltan: do you know how to / from whom to find out? sounds like SDK stuff possibly since Kaleo was the one who mentioned the problem
[07:22] <Mirv> hmm, I can file a bug and assign Kaleo to it
[07:23] <bzoltan> Mirv:  that is a good idea
[07:24] <Mirv> bzoltan: bug #1353863 filed with some subscribers too, seems important enough to double check since it's related to app startup times
[10:26] <Kaleo> Mirv, grep for the bug number in the toolkit: modules/Ubuntu/Components/Label.qml & examples/ubuntu-ui-toolkit-gallery/TemplateRow.qml
[10:27] <mandel> Elleo, I tested the new udm on the browser, app installation, dist upgrade and mms and everything works as expected. Is marked as tested and should be published in a number of hours
[10:29] <Kaleo> Mirv, https://code.launchpad.net/~fboucault/ubuntu-ui-toolkit/remove_relayout_workaround/+merge/229918
[10:31] <sil2100> Kaleo: hi!
[10:31] <sil2100> Kaleo: so, w
[10:31] <sil2100> Damn, keyboard problems...
[10:31] <sil2100> Kaleo: so, we might have to revert camera-app to the previous version in the store
[10:31] <Kaleo> sil2100, what's wrong?
[10:31] <Kaleo> sil2100, bug report?
[10:32] <sil2100> Kaleo: smoketesting shows it regressed test-wise, we get a constant number of 8-9 test failures on all supported platforms and brendand reports that it opens up now in about 30+ seconds
[10:32] <sil2100> brendand: did you fill in a bug for this already ^ ?
[10:32] <brendand> Kaleo, then after it opens it hides itself
[10:32] <brendand> sil2100, nope - going to now
[10:33] <Kaleo> brendand, ???
[10:33] <sil2100> Kaleo: anyway, since we're in traincon-0 we can't really accept any new breakages
[10:33] <Kaleo> sil2100, yes of course but I just don't experience that here
[10:34] <sil2100> brendand: I think davmor2 confirmed the issue on his mako device as well from what I remember
[10:34] <sil2100> I mean, Kaleo
[10:34] <sil2100> Damn, what's wrong with me today... so many typos
[10:34] <davmor2> Kaleo: are you on 176
[10:35] <sil2100> Anyway, brendand could you try maybe installing the earlier version of camera-app to make sure it's at fault?
[10:35] <brendand> sil2100, okay - someone can help me out with that?
[10:35] <brendand> Kaleo, ?
[10:35] <sil2100> We didn't see anything else landing that could affect this, but better be sure
[10:35] <sil2100> I remember popey had some nifty way of downloading old click packages...
[10:36] <Kaleo> davmor2, I'm on 175 with the new cameraz
[10:36] <Kaleo> -z
[10:36] <sil2100> Mirv, popey: could you guys give us a hand with downgrading click packages?
[10:36] <Kaleo> davmor2, I'm looking for my mako now to check (that was on barajas)
[10:40] <brendand> Kaleo, on 175 and it works?
[10:40] <Elleo> mandel: excellent :)
[10:40] <Mirv> sil2100: I know how to upload, but not specifically how to downgrade. I believe that'd be on the store frontend side ie. popey or dholbach
[10:41] <Kaleo> brendand, yep actually, on my 2 devices
[10:41] <Kaleo> brendand, upgrading to 176 now
[10:46] <Kaleo> brendand, sil2100, upgrading to 176 broke it :(
[10:46] <sil2100> :|
[10:46] <Kaleo> hang on
[10:46] <Kaleo> it was very slow to load
[10:46] <Kaleo> but it loaded
[10:47] <Kaleo> oups and very slow to write a pic
[10:47] <Kaleo> no
[10:47] <Kaleo> it's odd
[10:47] <sil2100> Kaleo: does the camera-app use mediascanner in any way?
[10:48] <Kaleo> sil2100, maybe for thumbnaining?
[10:48] <Kaleo> sil2100, is thumbnailing related to it?
[10:48] <sil2100> Since we had a mediascanner landing as well... not sure if anything else could have affected it, still looking at the commitlog
[10:48] <sil2100> hm, not sure
[10:48] <Kaleo> OMG
[10:48] <Kaleo> I have just gotten a popup
[10:48] <Kaleo> "camera wants to access your location"
[10:48] <Kaleo> "yes/no"
[10:48] <ogra_`> popups FTW !!
[10:49] <sil2100> hm, maybe it's related to location then!
[10:49] <Kaleo> now it seems fast too launch
[10:49] <sil2100> We also had location service landing yesterday
[10:49] <ogra_`> depends on what device
[10:49] <sil2100> brendand: ^
[10:49] <ogra_`> location partitally works on mako
[10:49] <Kaleo> that's on mako
[10:49] <ogra_`> but doesnt on others
[10:49] <mandel> ogra_`, partially, that offends me :P
[10:49]  * sil2100 upgrades to do some testing
[10:49] <Kaleo> doing a clean reinstall with wipe now
[10:50] <mandel> ogra_`, will work better in a few days
[10:51] <Kaleo> sil2100, so my guess is that an earlier click won't fix the issue unfortunately
[10:51] <ogra_`> mandel, why does it offend you ... ? not your fault
[10:52] <mandel> ogra_`, joking ;)
[10:52] <mandel> hehe
[10:52]  * ogra_` blames tvoss for not writing hs own AGPS server yet :P
[10:52] <sil2100> Kaleo: right, I would suppose that as well right now, that's why I asked for brendand to try the earlier version - but I guess we have now enough evidence that it might not be related to the new camera upload already
[10:56] <brendand> Kaleo, i'm still going to file the bug on camera-app
[10:58] <Kaleo> brendand, sure
[11:01] <brendand> Kaleo, look at the screenshot in the bug: https://bugs.launchpad.net/camera-app/+bug/1353956
[11:02] <brendand> Kaleo, that's what i see as i pull the launcher out
[11:07] <Kaleo> brendand, nice :)
[11:07] <Kaleo> brendand, yeah the app is there loaded quickly but not shown adequately
[11:07] <Kaleo> brendand, I think it's pending on that location yes/no dialog
[11:09] <Kaleo> brendand, commented
[11:10] <dholbach> Mirv, sil2100, I'm not sure - you mean you want to overwrite a broken version of an app in a click package?
[11:10] <dholbach> in that case you'd need to ship the old source with a newer version
[11:10] <sil2100> dholbach: about that, it might no longer be valid
[11:10] <Mirv> dholbach: oh, there's no "revert the offering to an earlier version" button? anyway, it seems based on above that we don't want it (possibly) since it wouldn't help
[11:10] <sil2100> dholbach: the problem is probably coming from another package
[11:11] <dholbach> ahh ok, I see
[11:53] <Chipaca> Laney: anything I can do to help you re-review https://code.launchpad.net/~chipaca/ubuntu-system-settings/push-helper/+merge/229571 ?
[11:58] <cjwatson> beuno: so, we have a key for you.  elmo is going to transfer it physically to the datacentre (so early next week), and I have a shard of the master key that signs the operational one on a USB stick for you when we next bump into each other
[12:00] <beuno> cjwatson, woohoo! that's great news
[12:00] <beuno> staging seemed to go well, we're going to sign all the existing packages soon
[12:01] <beuno> and hopefully it'll all come together on production next wee once the key is in the DC
[12:01] <beuno> cjwatson, you're taking care of the public key landing on the device?
[12:13] <cjwatson> beuno: Yeah, I'll get that sorted
[12:14] <cjwatson> beuno: Need to polish/land mvo's signing branch too
[12:14] <cjwatson> I gave him a nice long review only to realise that he's on vacation
[12:16] <beuno> cjwatson, one of those "I'm rubber, you're glue" situations
[12:38] <mterry> Wellark, is there any update on bug 1302049?
[12:38] <Wellark> mterry: actually there is
[12:39] <Wellark> as for working with https://bugs.launchpad.net/bugs/1341548 I'm adding a connectivity service to session bus
[12:40] <Wellark> I can easily add an interface needed for bug 1302049 as well
[12:41] <Wellark> mterry: any particular semantics you need for the API?
[12:41] <Wellark> or is simple com.ubuntu.connectivity1.private.UnlockSims() enough?
[12:41] <mterry> Wellark, not especially -- though I'm curious how dual sim would work?
[12:42] <mterry> Wellark, does it start unlocking both?
[12:42] <Wellark> mterry: it would iterate the modems one by one
[12:42] <Wellark> yep
[12:42] <mterry> Wellark, OK.  Yeah, I think we just need a way to start it.  Let me double-check the design
[12:42] <Wellark> just make sure the unlocking dialog is not shown automatically every time somebody tries to dismiss the greeter
[12:44] <mterry> Wellark, if no pins are locked, presumably the call will do nothing, so we can unconditionally call it on boot?
[12:44] <Wellark> mterry: yes.
[12:45] <mterry> Wellark, then yeah I think that dumb of an API is fine  :)
[12:55] <om26er> whats the password for phablet ?
[12:56] <pmcgowan> I believe there is none
[13:00] <t1mp> om26er: it used to be phablet, but there is an email on ubuntu-phone mailing list from a month ago saying it will be changed to blank
[13:01] <om26er> t1mp, thanks :-) so I just found since had set a passcode for lockscreen my password is that now.
[13:03] <mterry> om26er, ah yes -- you're not the first person to not expect that.  I would have mentioned that in my email when making the switch, but I was so embedded in the work, it seemed "obvious" to me
[13:03] <mterry> :)
[13:06] <ogra_> mterry, we should probably add some info about that to the popup dialog ;)
[13:07] <ogra_> or call it "systemwide passphrase" or so
[13:07] <mterry> ogra_, hopefully most users aren't sudo-ing too often  :)
[13:07] <ogra_> heh, true
[13:23] <dpm> hi mterry, when you've got a minute, do you think you could reply to the last comment on bug 1347010? I think it's your area of expertise
[13:25] <mterry> dpm, on it
[13:25] <dpm> awesome, thanks!
[13:35] <mterry> ogra_, did we stop producing grouper images on system-image.u.c?
[13:36] <mterry> oy we did
[13:36] <mterry> :(
[13:36] <ogra_> mterry, about a year ago
[13:36] <ogra_> or 8 months or whatever ... quite a while already
[13:36] <mterry> ogra_, hah, shows how long I've tried to use my grouper
[13:37] <ogra_> heh
[13:37] <jason___> Hello. I just installed ubuntu touch on my nexus 7. But I cannot find Synaptic on the app store. I also don't know how to put it in landscape mode. Can someone please help me?
[13:38] <jason___> The reason I install ubuntu on my nexus 7 is to be able to do c programming using GNU Emacs. Is that possible? Thank  you very much
[13:41] <greyback> jason___: we do not have landscape mode working for nexus7 yet
[13:43] <jason___> oh, is it possible for me to install the old Ubuntu version like 13.04? All I want is do C programming using Emacs for my statistics subject. I cannot find the Ubuntu Nexus 7 Desktop Installer as well. Thank you very much
[13:44] <cwayne> mterry: just added the huge unity8 silo now its asking me for a password, is there a new default pass?
[13:44] <mterry> cwayne, no
[13:45] <jason___> Can I use this command to install older version like 13.04?    $ ubuntu-device-flash --channel=trusty --revision=299     But I dont't what the correct revision number is. 299 is the current one.
[13:45] <mterry> cwayne, did you re-flash?  It'll keep the old password unless you use --wipe
[13:45] <cwayne> mterry: i did a wipe, then added silo 001
[13:46] <mterry> cwayne, what's the contents of /var/lib/extrausers/shadow?
[13:46] <cwayne> phablet::16289:0:99999:7:::
[13:48] <mterry> cwayne, ok so you have no password set as far as the system itself is concerned
[13:48] <mterry> cwayne, let me test myself
[14:01] <oSoMoN> Saviq, is it a known issue that the splash screen displays the app name untranslated?
[14:01] <Saviq> oSoMoN, yes, there's a bug for that
[14:01] <Saviq> oSoMoN, bug #1350360
[14:01] <oSoMoN> Saviq, ok, thanks
[14:09] <cwayne> mardy: hi, any update on the desktop files not showing anything in system settings online accounts?
[14:13] <mterry> cwayne, oh, did you get a scary message when upgrading about pam.d files?
[14:13] <cwayne> mterry: yep
[14:14] <mterry> cwayne, I assume you chose to override the changes, which blew up your PAM settings the way we like them
[14:14] <cwayne> mterry: probably
[14:14] <mterry> cwayne, I've got branches to avoid this problem in the future
[14:14] <mterry> cwayne, but for now I can fix your stuff manually, give me a sec
[14:14] <mterry> cwayne, in /etc/pam.d/common-auth, add the following line before any of the other lines:
[14:14] <mterry> auth    [success=2 authinfo_unavail=ignore default=1] pam_extrausers.so nullok
[14:15] <mterry> cwayne, and in common-password, the following line before any others:
[14:15] <mterry> password        [success=2 default=ignore]      pam_extrausers.so minlen=4 sha512
[14:21] <jgdxx> kenvandine, pushed fixes to reset branch https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/1219793-reset/+merge/228954
[14:21] <kenvandine> jgdxx, great, thx
[14:22] <jgdxx> kenvandine, no, thank you. Wouldn't get anywhere without these reviews. :)
[14:22] <kenvandine> :)
[14:25] <nik90> sergiusens: Hi, did you have time to look at daniel's debian packaging branch?
[14:28] <sergiusens> nik90: do you have the link again? I might have lost it
[14:30] <sil2100> dholbach: hmm... do you know who I should ping regarding calendar-app development?
[14:31] <sergiusens> nik90: just add me as reviewer I guess and I'll see it
[14:32] <tedg> mardy, Is there a signal for when a new account is added?
[14:32] <tedg> mardy, Specifically I want to know when a new U1 account is added.
[14:33] <nik90> sergiusens: done
[14:36] <mardy> tedg: hi! Which API? QML, Qt or glib?
[14:36] <mardy> cwayne: no updates, I didn't work on that yet
[14:37] <tedg> mardy, I'm not using the accounts right now, only libu1-auth. So I can use any of those if needed :-)
[14:37] <tedg> mardy, That's a Qt lib so the Qt version is probably easier in that object though.
[14:38] <sil2100> dholbach: hi! Do you have the power to publish packages to the store? We would need music-app updated, Mirv already uploaded the new version
[14:38] <nik90> sil2100: mihir, kunal on #ubuntu-app-devel
[14:38] <mardy> tedg: so, the classes which you need to use are Accounts::Manager (to get notified when accounts are created/deleted) and AccountService (to get notified when the account gets enabled/disabled)
[14:38] <sil2100> nik90: thanks :)
[14:39] <nik90> yw
[14:39] <tedg> mardy, Okay, cool. Thanks!
[14:40] <sil2100> dholbach: pretty please with cherries on top ;)
[14:40] <sergiusens> nik90: thanks
[14:41] <jgdxx> elopio, hey, I've pushed fixes which addresses your comments in https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/call-fwd-wait-dual-sim/+merge/229774 – thanks
[14:41] <Mirv> dholbach: 1.3.558, that is
[14:52] <tedg> mardy, What is the serviceType string for U1?
[15:01] <mardy> tedg: let me check if I find it...
[15:02] <dholbach> sil2100, Mirv: looking - just coming back from the dentist
[15:02] <mhall119> nik90, renatu my Unity shell becomes unresponsive when an alarm is playing, is that a known bug?
[15:02] <mardy> tedg: "ubuntuone" :-)
[15:02] <nik90> mhall119: nope
[15:02] <nik90> mhall119: image 157?
[15:02] <sil2100> dholbach: thanks!
[15:03] <mhall119> nik90: yeah
[15:03] <tedg> mardy, Cool, thanks1
[15:03] <tedg> thanks!
[15:03] <mhall119> nik90: the welcome screen is responsive, but once I swipe that away nothing works, not even the launcher or top panel
[15:03] <dholbach> sil2100, Mirv, balloons: music approved
[15:03] <sil2100> dholbach: \o/
[15:04] <nik90> mhall119: ah that's due to the snap notification
[15:04] <nik90> mhall119: it takes away all input and forces the user to dismiss the snap notification first
[15:04] <mhall119> nik90: do you know if there's a bug for it?
[15:04] <nik90> mhall119: that's by design
[15:04] <mhall119> nik90: but it lasts long after I dismiss the notification
[15:05] <nik90> mhall119: hmm yeah that is a bug
[15:05] <mhall119> nik90: what project should I file it against?
[15:05] <nik90> mhall119: will have to reflash my phone to 157 to test it out.
[15:05] <nik90> mhall119: report it against the clock app, let me try to confirm it and then investigate where the issue lies
[15:06] <mhall119> nik90: well it was technically a calendar event
[15:06] <mhall119> though if it's in the notification it can probably be caused by either
[15:07] <nik90> mhall119: well the indicator-datetime is the one which triggers the actual notification and the snap decision. This is used by both clock and calendar.
[15:07] <mhall119> ok, I'll file it there
[15:07] <nik90> ok
[15:07] <mhall119> thanks nik90
[15:08] <nik90> np
[15:10] <mhall119> nik90: https://bugs.launchpad.net/indicator-datetime/+bug/1354041 if you are able to reproduce
[15:12] <kenvandine> jgdxx, mind reviewing https://code.launchpad.net/~ken-vandine/gsettings-qt/version_dep/+merge/229953
[15:12] <jgdxx> kenvandine, sure
[15:12] <kenvandine> i'll get that in a silo quickly :)
[15:13] <alecu> balloons: so, were you able to get at the ubuntuone id from your qml app?
[15:13] <balloons> alecu, I ended up spending the day on another bug and didn't get much further. I'll be at it again today, so :-)
[15:13] <alecu> great, let me know how it went :-)
[15:21] <jgdx> kenvandine, done, thanks
[15:22] <kenvandine> jgdx, thx
[16:22] <Wellark> jdstrand: hi
[16:22] <Wellark> just thinking of bug #1341548
[16:23] <robotfuel> Saviq: mzanetti: ping I have this new crasher in unity8 that need triaging https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1354068 let me know if the upstart or syslog will help
[16:24] <Wellark> jdstrand: I'm not familiar with out policy/permission system enough
[16:24] <Wellark> but I would want to have the apps to declare different set of permission they want regarding the connectivity api
[16:24] <mzanetti> robotfuel: hmm... weird one. seems to crash in the/a media player
[16:24] <mzanetti> robotfuel: did you listen to some song in the dash preview?
[16:25] <Wellark> jdstrand: something like connectivity.networkstatus, connectivity.radiocontrol etc.
[16:25] <robotfuel> mzanetti: I am buried in crash files, so I didn't look. It was found by randomly clicking the ui, so that's possible.
[16:25] <Wellark> so that it would not be just a general catch-all "connectivity"
[16:25] <mzanetti> ah ok
[16:25] <Wellark> jdstrand: how would that work?
[16:26] <mzanetti> robotfuel: is this thomi's random input stuff?
[16:26] <robotfuel> mzanetti: yes random input
[16:26] <Wellark> also at some point I would love to see that the user can deny networking from an app entirely, but we are not there yet anyway
[16:26] <mzanetti> ok... will try to find a way to reproduce... atm it looks like some hiccups in the media player backend - just judging from the stack trace
[16:27] <mzanetti> jhodapp: do you perhaps have some input on that one? https://errors.ubuntu.com/problem/8c88c781c702b88274b020e223d66d63e2d34a33
[16:27] <robotfuel> mzanetti: let me know if log files will help, I'll add it to the bug or start collecting it.
[16:27] <mzanetti> robotfuel: hmm... yeah... if you have it around, please send over ~/.cache/upstart/unity8.log
[16:27] <robotfuel> mzanetti: ok I have that one.
[16:28] <jhodapp> mzanetti, I had a thought about that, but am heading out to lunch...I'll ping you when I get back
[16:28] <mzanetti> and if its a really new image, unity8-dash.log might be useful too
[16:28] <mzanetti> jhodapp: sure, no worries. Enjoy your lunch
[16:35] <bregma> so the latest unity-plugin-scopes breaks dependencies in the archive and forces the removal of unity8 on the desktop
[16:35] <jdstrand> Wellark: we can mediate on bus, path, interface and method
[16:36] <mterry> boiko, what's the best way to ask if there is any sim card in any of the modems from qml?
[16:36] <jdstrand> Wellark: we have one connectivity policy group currently. it is for coarse grained connectivity information
[16:36] <boiko> mterry: no way right now, I was discussing with salem_ about that, we need to change the connection status report in telepathy-ofono
[16:37] <mterry> boiko, is there a bug tracking that yet/
[16:37] <mterry> ?
[16:38] <Wellark> jdstrand: so how would it look like if we had finegrained connectivity policies?
[16:40] <jdstrand> Wellark: what would you want to make available?
[16:40] <Wellark> jdstrand: well, for example radiocontrol is one of the simplest examples
[16:41] <jdstrand> Wellark: what do you mean by radiocontrol?
[16:41] <jdstrand> Wellark: turning it on and off?
[16:41] <Wellark> wifi enable, bt enable, flightmode
[16:42] <jdstrand> Wellark: we don't let apps do that currently. if we wanted to, the dbus service would need to have trust-store integration
[16:42] <Wellark> so for an app to access networking status, it would have to define in it's manifest that it needs connectivity.networking_status, for an app to control devices radios it would need to define connectivity.radio_control etc
[16:42] <jdstrand> Wellark: basically, apps in the app store have no review and are considered untrusted
[16:43] <jdstrand> Wellark: we also (by design) don't have installation prompts
[16:44] <Wellark> jdstrand: but we would still make the information available with parts of the system an app requires permissions for?
[16:44] <Wellark> and in technical level at some point would it also be possible for the user to rip off certain permissions from an app?
[16:44] <jdstrand> Wellark: as such, the exposed API must either be safe for everyone to use and not leak info the app shouldn't have. if it grants sensitive information or allows privileged actions, then there needs to be trust-store integration so the user is prompted when the app performs the access
[16:44] <jdstrand> (the answer can be cached for later)
[16:46] <jdstrand> Wellark: apps declare what policy groups they can use. right now, we have an empty 'connectivity' policy group that is defined as what apps can use to obtain coarse-grained network info
[16:46] <Wellark> can that group be splitted up for more fine grained access?
[16:46] <jdstrand> Wellark: we can add an additional policy group, sure. not sure what we would name it, but for this discussion, it can be connectivity.radio_control
[16:47] <jdstrand> Wellark: if the api is well-designed, sure
[16:47] <jdstrand> Wellark: I would suggest using a different path for coarse and radio_control
[16:47] <Wellark> jdstrand: ok. for future in mind, then I think the current connectivity group should be renamed to connectivity.networking_status
[16:47] <Wellark> jdstrand: sure
[16:47] <Wellark> on the service side they would be separate paths
[16:48] <jdstrand> Wellark: I can't really do that. it is long established as what to use for coarse grained network status
[16:49] <jdstrand> we should just do 'connectivity' and 'network-control' or something
[16:49] <jdstrand> I wouldn't worry about what we name it
[16:49] <jdstrand> there is metadata for people to read as well as documentation to explain what it does
[16:51] <robotfuel> mzanetti: the unity8 and unity8-dash logs are attached to https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1354068
[16:51] <jdstrand> Wellark: fyi, if you want to know more, I suggest looking at: http://developer.ubuntu.com/publish/apps/security-policy-for-click-packages/
[16:52] <Wellark> well, if the connectivity group is currently empty, then renaming it should not be a problem. or if you are worried about existing apps already requiring "connectivity" group (which does nothing as it's empty) then we can leave the connectivity group as empty and mark it as deprecated and update the documents to tell people to define connectivity.networking_status
[16:53] <jdstrand> Wellark: (it might help to know that typical users don't see or care about the name of the policy group)
[16:53] <Wellark> sure, but developers do
[16:53] <jdstrand> Wellark: it is documented for more than a year what it does
[16:53] <jdstrand> Wellark: why the hang up on the name?
[16:54] <Wellark> because it gives consistency in the future when we expand the connectivity service
[16:56] <jdstrand> Wellark: I want to provide consistency too. we can just do like with content_exchange or music_files. ie, we do connectivity and connectivity_control like we have content_exchange and content_exchange_source or music_files and music_files_read
[16:56] <jdstrand> anyway, this is a very minor point
[16:56] <jdstrand> the name of the policy group doesn't really have anything to do with the name of the service
[16:57] <jdstrand> or rather, it doesn't have to
[16:57] <jdstrand> it is just something so people have some idea what it does
[17:00] <Wellark> ok, so the existing policy groups use "_" instead of "." to as a namespace delimiter
[17:02] <Wellark> jdstrand: what is the difference between current connectivity and networking ?
[17:02] <jdstrand> right, that too is minor. mostly I just want to use what we've documented for status, and then add a new one for radio control
[17:02] <jdstrand> Wellark: networking gives you access to networking
[17:02] <jdstrand> without it, you can't get online
[17:02] <Wellark> right. ok. I found the descriptions also
[17:04] <jdstrand> maybe it would make sense to add radiocontrol to networking to not add a new policy group
[17:04] <jdstrand> Wellark: are you planning on implementing this radiocontrol API for RTM?
[17:04] <Wellark> actually looking at existing documentation
[17:05] <mzanetti> robotfuel: thanks
[17:05] <jdstrand> Wellark: oh, actually, connectivity is not currently blank
[17:05] <Wellark> jdstrand: so, this is just my initial throught and you can ignore it if you want:
[17:05] <Wellark> jdstrand: way I would feel most comfortable would be that we have (at some point) the following groups
[17:06] <Wellark> connectivity_networking
[17:06] <jdstrand> it has some accesses in there, just not everything that the existing (non-libconnectivity) libs try to use
[17:06] <Wellark> connetivity_networking_status
[17:06] <Wellark> connectivity_bluetooth
[17:06] <Wellark> connectivity_nfc
[17:06] <Wellark> that way they are all consistent
[17:06] <Wellark> and grouped under connectivity topic
[17:07] <mzanetti> robotfuel: hey, do you know if there's any local music on that test device?
[17:07] <Wellark> as in the future when our platform API's expand we are going to have a lot more policy groups
[17:07] <robotfuel> mzanetti: there is none
[17:08] <jdstrand> Wellark: well, there is a balance. we actually don't want a lot of policy groups and complexity. mdeslaur, sbeattie and I designed what we have for simplicity. if you want to redesign it, then this should be taken to a list
[17:08] <mzanetti> robotfuel: a video showing where it started to play music from would be awesome now :)
[17:09] <Wellark> jdstrand: no, I do not want imply that we need a redesign
[17:09] <robotfuel> mzanetti: sometimes I hear grooveshark play
[17:10] <mzanetti> robotfuel: right... /me is located in germany
[17:10] <mzanetti> => no grooveshark
[17:11] <mzanetti> robotfuel: mind trying this: Find some grooveshark song, start playing in the preview, then click on "Open in media player"
[17:12] <mzanetti> must be a combination of already playing some music in unity8 and launching the media player
[17:12] <Wellark> jdstrand: just that for the network_status I would want the policy to be named to more accurately match what it allows you to do. connectivity is a broad topic
[17:13] <Wellark> and if we now reserve the "top-level" 'connectivity' group for just a simple networking status information then it would be highly inconsistent if we then later add some more fine grained connectivity_ groups
[17:14] <Wellark> or not highly
[17:14] <jdstrand> Wellark: this was all discussing over a year ago on the phablet list and it was agreed to. I appreciate what you are saying, however only developers see these policy groups and the SDK shows what they do and the documentation describes them
[17:14] <jdstrand> discussed*
[17:14] <robotfuel> mzanetti: it will be 20 minutes, I have to flash my manual testing phone with today's image.
[17:14] <mdeslaur> Wellark: the name are irrelevant, we can name them whatever...the descriptions can be changed though
[17:14] <jdstrand> well, it is somewhat irrelevant
[17:14] <mdeslaur> If they are already in the policy, that means apps can use them, so it's too late to change
[17:15] <jdstrand> we have connectivity and networking already, and people are using them
[17:15] <mdeslaur> then it's too late
[17:15] <jdstrand> right
[17:15] <Wellark> connectivity does not work
[17:15] <jdstrand> sure it does
[17:15] <jdstrand> WordNet: "the property of being connected or the degree to which something has connections"
[17:16] <jdstrand> that is what it does
[17:16] <Wellark> I mean the current policy does not work. even though apps are using it they can't get the connectivity information
[17:16] <jdstrand> well, yes, that is where you come in
[17:16] <Wellark> which is what I'm fixing.
[17:16] <jdstrand> :)
[17:16] <Wellark> indeed. :)
[17:17] <jdstrand> we can add whatever policy from your connectivity service to any policy group, it doesn't matter
[17:18] <jdstrand> ie, it might make sense to add connectivity service DBus API to the networking policy group in the future. that's fine
[17:19] <Wellark> so in that light, any apps already "using" the connetivity policy group don't actually get the information. so deprecating it in favor of connectivity_networking_status would not be a problem. but sure. it's not a life-or-death situation right now
[17:19] <jdstrand> and in case it was missed in backscroll-- connectivity does actually, today, provide policy for determining some sort of network status. it is just incomplete because the Qt/QML APIs need to much
[17:20] <jdstrand> I was wrong when I said it was blank
[17:23] <Wellark> jdstrand: oh, one more thing, is it possible for a policy group to state it depends on some other policy groups?
[17:24] <jdstrand> Wellark: no
[17:24] <Wellark> ok.
[17:25] <jdstrand> the hope I always had was that the SDK would notice the APIs used and add them for the developer. for now, there is online documention and meta-information in the SDK
[18:03]  * mhall119 is starting to hate the harp noise
[19:05] <popey> mhall119: just starting!
[19:15] <mhall119> popey: I'd had it muted before
[19:46] <Saviq> robotfuel, this looks very much like a media hub crash
[19:47] <robotfuel> Saviq: mzanetti was saying the same thing. I tried using grooveshark to get it to crash, but I couldn't reproduce.
[19:48] <Saviq> robotfuel, and both look almost the same indeed, do you have steps to reproduce?
[19:49] <popey> mhall119: ahhh!
[19:49] <robotfuel> Saviq: no it's a random gesture and click test that found the errors.
[19:50] <Saviq> robotfuel, they're retraced pretty well, so maybe we'll be able to dig something out
[19:51] <mzanetti> Saviq: do we play music/sounds somewhere in unity8 (NOT unity8-dash)?
[19:52] <Saviq> mzanetti, notifications
[19:53] <mzanetti> Saviq: the crash is in /usr/bin/unity8, leads to the media player backend
[19:53] <mzanetti> Saviq: the logs say that last thing happening is opening the Music player app
[19:54] <Saviq> mzanetti, we also have a hud volumepeak detector, but doubt it's related
[20:59] <dobey> is it possible to connect a serial device via bluetooth on the phone yet? or are only audio profiles supported at the moment?
[21:02] <sergiusens> Chipaca: can you ask verterok to join here?
[21:02] <Chipaca> sergiusens: sure
[21:02] <Chipaca> sergiusens: but he's gone to the car shop
[21:04] <sergiusens> Chipaca: ah, ok, I'll be here for a couple more hours
[21:04] <sergiusens> Chipaca: just can't join the internal servers ;-)
[21:04] <sergiusens> and using webchat :-/
[21:05] <dobey> sergiusens: he's in other channels on freenode, so just /query him or something :)
[21:05] <sergiusens> dobey: right :-)
[21:05] <sergiusens> he should still be here :-)
[21:07] <dobey> sure. just saying. i'm only on here because i'm waiting for the sdk to build a "kit" since it's forcing me to do that now, and i was curious about bluetooth serial device support
[21:07] <dobey> and thw weather sucks
[21:33] <MattMa> hello, yesterday I insalled touch on my nexus4 from devel channel.Today I entered with adb (activated ssh) and run the stuf I am used on my ubuntu  desktop (apt-get update and dist-upgrade), after huge ubdates I am asked on the gui of the phone to enter a password (not the sim unlock). I have tried pphable, ubunut password, no password, but nothing works
[21:34] <Fishscene> was "pphable" a typo? If not, try "phablet"
[21:34] <matv1> MattMa phablet should work
[21:35] <MattMa> yes was only a typo
[21:36] <matv1> MattMa mind that a quirk in the OSK means that even in terminal, the first letter will be uppercase. Does that help?
[21:36] <matv1> (when ofcourse the password needs all lowercase characters)
[21:37] <MattMa> no I am sure that i used only lower case
[21:38] <matv1> ok
[21:39] <MattMa> I checked it by waiting a moment until the letter apears when pressing it, and I have also tried Phablet...nothing works
[21:39] <MattMa> I (thinkt I have mounted the filesystem with write access can this cause the problem?
[21:40] <balloons> barry, it seems attempting to remove any python3 package on the phone causes an apt error. Unmet dependencies, python3-aptdaemon.pkcompat : Depends: python3-aptdaemon (= 1.1.1+bzr973-1ubuntu4) but it is not going to be installed
[21:41] <balloons> any thoughts? the apt index is up to date
[21:42] <barry> balloons: weird, i haven't seen that, though admittedly i haven't tried to remove any such packages
[21:43] <balloons> what is the .pkcompat? never seen that before
[21:44] <barry> it's a transitional package.  i don't even know why that's installed or trying to be installed on the phone
[21:48] <matv1> MattMa are you sure about your release version? latest channel devel release is 157. There have been changes concerning developer mode (both adb and ssh being dissabled by default, I believe, and activated only after a pwd change) but they haven't made it to devel
[21:48] <MattMa> ho can I look form my r?
[21:49] <balloons> barry, thanks.. I'll take it to the list
[21:49] <MattMa> I think it was (yesterday) r157
[21:49] <matv1> MattMa System Settings ->  About this phone
[21:50] <MattMa> i can not enter there now...
[21:50] <MattMa> only adb
[21:50] <MattMa> uname -a Linux ubuntu-phablet 3.4.0-5-mako #32-Ubuntu SMP PREEMPT Wed Jul 16 10:39:52 UTC 2014 armv7l armv7l armv7l GNU/Linux
[21:50] <verterok> sergiusens: hi!, was pickingup the car from the shop...whatsup?
[21:51] <barry> balloons: cool.  i think mvo may be the most help here, but it's past his eod
[21:52] <MattMa> I did not enter any pw (exept for ubuntu one, and this does not work eighter)
[21:53] <sergiusens> verterok: discuss the account-polld stuff
[21:54] <sergiusens> verterok: wasn't clear to me if you were going to do the c stuff or I was though
[21:54] <verterok> sergiusens: no idea what the stuff nor c stuff are :)
[21:55] <sergiusens> verterok: about the standup today wrt to implementing the "account created" watch
[21:55] <sergiusens> verterok: and pushing that as a notification
[21:56] <verterok> sergiusens: right, no idea what that implies. can we do a hangout?
[21:56] <sergiusens> verterok: we can try
[21:56]  * sergiusens grabs headsets
[21:56] <MattMa> sorry ubuntu-one is ok but the password is not the one requested here. It looks like a phone unlock pw with title 'Hello' and in the window where to enter the pw is sais: Please enter a password (translated from german 'Bitte geben Sie Password ein')
[22:06] <robotfuel> Saviq: mzanetti, I have another bug to triage for someone on the unity8 team to triage this one is not a crash https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1354182
[22:12] <matv1> MattMa can you run adb shell system-image-cli -i
[22:12] <matv1> and confirm you are on r157 ?
[22:16] <MattMa> matv1: yes:  adb shell system-image-cli -i current build number: 157 device name: mako channel: devel alias: ubuntu-touch/utopic last update: 2014-08-06 22:29:19 version version: 157 version ubuntu: 20140729.2 version device: 20140728.1
[22:18] <matv1> ok sorry in that case i am not sure what you are seeing. Maybe your best bet is to reflash?
[22:18] <matv1> Or else someone else may jump in :)
[22:21] <MattMa> ok thank you! I was thinking in a reflash I try another bit tomorrow and if it does not work i reflash! Thank very much!!!
[22:22] <matv1> MattMa np
[22:23] <anpok> just updated to 177
[22:23] <anpok> on first boot (nexus4) it claimed sim was not present
[22:23] <anpok> .. rebooted again and it worked..
[22:24] <anpok> is there a better way to resolv this? Logs I should look at? services to restart - or debug?
[22:38] <matv1> the Music app crashing is a known issue?
[22:38] <ahayzen> matv1, hey, what are u running it on?
[22:39] <matv1> mako channel devel
[22:39] <ahayzen> matv1, hmm did u get an update recently?
[22:39] <matv1> i just updated the app today yes
[22:39] <ahayzen> matv1, ah damn that update was only supposed to go to devel-proposed :(
[22:39] <matv1> ah!
[22:40] <ahayzen> matv1, it requires the latest mediascanner2 so will explode on devel
[22:41] <matv1> i see
[22:41] <ahayzen> balloons, we were told that -dev-3 apps would not appear as updates to devel as it is on -dev-2 at the moment? appears this is not happening ^^
[22:41] <balloons> ahayzen, ?
[22:42] <ahayzen> balloons, well the latest music-app won't run on older ms2 so it has broken in devel
[22:42] <balloons> ubuntu-sdk-14.10-qml-dev3 and ubuntu-sdk-14.10-dev2 are the current framework
[22:42] <ahayzen> balloons, when i was talking with dpm we thought that because we had bumped to dev-3... so the app would only appear as an update to devel-proposed and not devel
[22:42] <balloons> ahayzen, ohh you mean there was a store update to music that broke devel, gotit
[22:43] <ahayzen> balloons, yep ... music-app requires latest mediascanner2
[22:43] <balloons> ahayzen, well that's obviously not true.. but I was going to say I don't believe any 14.10* would be limited by the minor version
[22:44] <balloons> it's a little weird on devel for this reason
[22:44] <balloons> in theory, they store shouldn't push apps that would break
[22:44] <ahayzen> balloons, matv1, is a bit of a chicken and egg ... we need latest mediascanner2 to land for us to work...but to pass CI we need latest mediascanner
[22:45] <balloons> yep.. I think it's really just a function of running in devel
[22:46] <balloons> and you did need to push in order to keep CI going, so I think the decision made sense no matter what
[22:46] <ahayzen> balloons, this is from the meeting http://pastebin.ubuntu.com/7983532/
[22:46] <ahayzen> balloons, yeah tricky :/
[22:46] <balloons> ahayzen, well.. heh
[22:46] <balloons> I guess we should ask beuno then
[22:46] <ahayzen> balloons, i was just surprised because we were 'told' it would be fine
[22:46] <balloons> are we sure devel is currently -dev2 though?
[22:46] <ahayzen> balloons, hmm maybe not
[22:47] <Velo_> Hello! I have a quick question about installing ubuntu touch
[22:47] <balloons> tricky tricky
[22:47] <ahayzen> balloons, ah well bring on promoted image tomorrow :)
[22:47] <balloons> there you go
[22:47] <ahayzen> matv1, basically just wait for the next image and then music-app will start working again, sorry for breaking it
[22:48] <Velo_> I am looking at installing ubuntu touch on my nexus 7, as a dual boot, next to cyanogenmod, is that possible?
[22:48] <Velo_> Nexus 7 Flo, 32Gb
[22:50] <matv1> ahayzen yes i understand. No problem hope we get a landing tomorow then :)
[22:50] <matv1> or rather a promo
[22:52] <ahayzen> matv1, hopefully :)