[04:42] <lotuspsychje> morning
[04:47] <xangua> night
[04:47] <lotuspsychje> xangua: hi there :p
[07:03] <dholbach> good morning
[08:05] <cjwatson> alex-abreu,mardy_: did any of you folks get a chance to retest the rebuilt unity-chromium-extension in silo 19?
[08:06] <cjwatson> hopefully just pro-forma but I don't want to publish something untested and get LARTed
[08:17] <jibel> popey, is bug 1227293 still an issue for you? I don't find any issue with video recording and switching between photo and video.
[08:18] <jibel> the main problem I found is that photos are 0byte if zoom level is around 50%
[08:20] <popey> jibel: no, it works now.
[08:20] <jibel> popey, thanks, closing
[08:59] <bzoltan> mvo_: ping
[09:01] <mvo_> bzoltan: pong
[09:01] <JamesTait> Good morning all; happy Don’t Step On A Bee Day! :-D
[09:02] <bzoltan> mvo_: hello, you are the only one onle who might know something about the webapp templates in the SDK ... how is it expected to be packaged?
[09:07] <mvo_> bzoltan: :) I tried to explain that in the branch I recently added, let me search for that
[09:07] <mvo_> bzoltan: but essentially it should really just be "click build path-to-webapp" to make it work
[09:07] <bzoltan> mvo_: I think I know what you mean
[09:07] <bzoltan> mvo_: perfectly enough! I will make it work with the QtC UI
[09:08] <mvo_> bzoltan: excellent, just for refernce, https://code.launchpad.net/~mvo/qtcreator-plugin-ubuntu/webapp-template-with-doc/+merge/224759
[09:08] <mvo_> bzoltan: great that you work on this, I think the webapps are really a nice way to "hook" users into the system, i.e. make it super easy to get the first app done and then they (hopefully) are keen to do something more substantial
[09:09] <bzoltan> mvo_: I think what we need is a manifest file and a standard png in the template ...
[09:10] <mvo_> bzoltan: yeah, a generic png would be great. iirc the manifest gets generated, let me double check
[09:10] <bzoltan> mvo_: the QtC can not generate the manifest as there is no real project type for the webapps ... but i can make a template manifest.json
[09:11] <bzoltan> mvo_: default icons we have, i can add that too to the template
[09:11] <mvo_> bzoltan: oh, then I misremembered, so +1 for a manifest!
[09:13] <bzoltan> mvo_: the only silly thing is that the IDE runs on projects ... like qmake .pro or cmake CMakeList.txt or QML .qmlprojects But the webapps are so simple and so basic that they do not have any :) I might need to create one or make the IDE recognize the webapps based on the structure or content. Let me figure out that.
[09:13] <mvo_> bzoltan: yeah, just a trivial one is probably a good idea
[09:15] <coolman> is there anywhere to download ubuntu touch for the meizu mx3?
[09:26] <mhr3> seb128, ping? got a pkging question
[09:28] <mhr3> seb128, so we have the scopes lib, and devs link against it, and we'd want to support multiple versions of the lib at the same time.. that means we need to do the so handling properly, but my question is, how can we force the image to include both the old and the new version of the lib (ie libunity-scopes2 and ...3) if users of the 2 will be mostly click pkged scopes?
[09:28] <mhr3> seb128, or oem scopes, or basically anything *but* debs
[09:59] <njin> pitti, hi, running ubuntu-bug in ubuntu-next (only) it return..[pid  2518] 22:30:45.803307 write(2, "usage: whoopsie-upload-all [-h] "..., 103usage: whoopsie-upload-all [-h] [-t TIMEOUT]
[09:59] <njin> whoopsie-upload-all: error: unrecognized arguments: linux
[09:59] <njin> ) = 103
[10:00] <pitti> hey njin
[10:00] <njin> hey
[10:00] <pitti> njin: right, figured it out yesterday; it's bug 1339663, will fix ASAP
[10:00] <pitti> njin: in the meantime, you can use "apport-cli"
[10:00] <njin> great, thanks
[10:00] <pitti> which doesn't do that /var/lib/apport/autoreport check
[10:00] <njin> ok, I will try...thnaks again
[10:01] <pitti> njin: sorry for the hassle; I only heared about this yesterday, and after you disappeared jibel told me and filed that bug; so too late to tell you that I don't need the output any more
[10:11] <njin> pitti, no sorry, is always a pleasure to partecipate. Have a great day
[10:11] <pitti> njin: and yoU!
[11:07] <jgdx> kenvandine, \o morning! Can you install Durham
[11:08] <jgdx> kenvandine, (trying again) install these packages http://people.canonical.com/~jonas/system-settings/ on your device, reproduce the itemselector disabling behaviour and send me ur logz plz?
[11:29] <jgdx> and by 'archive' you mean http://people.canonical.com/~kenvandine/libqofono/, right?
[11:39] <bzoltan> mvo_: dpm: do you guys have a know to be working apparmor/manifest file for any webapp?
[11:39] <mvo_> bzoltan: you can take it out of my fastmail.fm app, hold on a sec, I mail it to you
[11:40] <dpm> bzoltan, I don't, sorry, but I see mvo_ comes as usual to the rescue :)
[11:41] <mvo_> bzoltan: check lp:~mvo/+junk/click-webapp please
[11:41] <bzoltan> mvo_: thanks
[11:42] <mvo_> yw
[12:31] <alex-abreu> cjwatson, not yet I will do it now, I have it installed
[13:06] <kenvandine> jgdx, no, the version in utopic
[13:06] <jgdx> kenvandine, ack
[13:10] <kenvandine> jgdx, i'll add some mode debugging output and see if i can get more info
[13:10] <kenvandine> jgdx, i'm suspicious it's something different with t-mobile US
[13:10] <kenvandine> which is why you aren't seeing it
[13:11] <kenvandine> like a tech pref key that you aren't expecting and it gets set to "" ?
[13:12] <kenvandine> jgdx, did you see my inline commens on your MP?
[13:12] <jgdx> kenvandine, I'm expecting all possible values (gsm, lte, umts, any) from https://github.com/rilmodem/ofono/blob/master/doc/radio-settings-api.txt
[13:12] <jgdx> kenvandine, looking
[13:13] <kenvandine> jgdx, and there was another landing last night, can you update your branch from mine?
[13:13] <jgdx> kenvandine, yup
[13:13] <kenvandine> i merged trunk into mine and pushed
[13:14] <kenvandine> then we'll get new debs again :)
[13:15] <jgdx> pitti, I'm getting some errors adding a second modem to the ofono dbusmock. The setup is like this: http://pastebin.ubuntu.com/7775117/ and the error is http://pastebin.ubuntu.com/7775123/ – i.e. add_netreg_api from dbusmock/templates/ofono.py does not use the new modem name from _parameters. Which is unexpected.
[13:16] <jgdx> pitti, runnable from lp:~jonas-drange/ubuntu-system-settings/1319044-carrier-design-dual-sim ubuntu_system_settings.tests.test_cellular.CellularTestCase.test_carrier_item_changes_depending_on_modems
[13:17] <alex-abreu> cjwatson, testing failed for me for silo 19
[13:18] <alex-abreu> cjwatson, so I'd saw remove it from this silo, and wait until fixed
[13:18] <kenvandine> jgdx, oh... so bet it's a race
[13:19] <jgdx> kenvandine, how so?
[13:19] <kenvandine> maybe rdoSettings isn't ready yet?
[13:20] <kenvandine> like right after the pref was changed?
[13:20] <kenvandine> when you set the var pref, that is blank right after i changed the pref
[13:20] <kenvandine> so maybe you need to wait for a signal from rdoSettings before attempting to get the value again
[13:22] <pitti> jgdx: sorry, super-busy; do you mind filing a bug with precise instructions how to run that test, and subscribe me?
[13:22] <jgdx> kenvandine, oh right
[13:22] <jgdx> pitti, sure thing
[13:22] <pitti> jgdx: thanks
[13:22] <jgdx> kenvandine, but did you not see the itemselector being disabled?
[13:22] <kenvandine> jgdx, so maybe change the selectedIndex onTechnologyPreferenceChanged
[13:23] <kenvandine> that's the warning that gets logged
[13:23] <kenvandine> yes, it is getting disabled
[13:23] <pitti> jgdx: the add_netreg_api() stuff hardcodes /%s/operator/op1, i. e. it will always use the same template arg
[13:23] <kenvandine> if i back out to the previous page
[13:23] <kenvandine> and go back in
[13:23] <kenvandine> it's enabled again
[13:23] <pitti> jgdx: i. e. I have a rough idea what's going wrong, but that needs some proper test case and fix
[13:23] <cjwatson> alex-abreu: oh?  how come it failed now when it passed before, and the only change was that build-dep?
[13:24] <cjwatson> alex-abreu: removing from the silo isn't especially helpful - it's already been landed in -proposed in the primary archive, and needs to be fixed there
[13:24] <alex-abreu> cjwatson, I dont know, I didnt do the testing before, I'd have to talk to mardy but he is away for the week
[13:24] <alex-abreu> cjwatson, the failure is not major, part of the functionality is broken, so it can be fixed after I guess
[13:24] <cjwatson> alex-abreu: ok, is it possible that there are variant standards of testing being applied?
[13:25] <alex-abreu> cjwatson, possible yes,
[13:25] <jgdx> pitti, ack. Thanks
[13:25] <alex-abreu> cjwatson, that's why I say i dont think its major, what mardy had in mind is probably not what I had :)
[13:25] <jgdx> kenvandine, /me reads
[13:26] <alex-abreu> cjwatson, although I dont think so, I might be a bit off in terms of what this is supposed to offer un teams of feature
[13:26] <kenvandine> jgdx, although if that's the case, i'm surprised you couldn't reproduce it
[13:27] <jgdx> kenvandine, whether or not the itemselector is enabled depends on rdoSettings.technologyPreference. If that's "", the selector is disabled. That's the only thing disabling the selector.
[13:27] <kenvandine> yeah
[13:27] <jgdx> kenvandine, which is why it should be re-enabled when rdoSettings comes back, right?
[13:27] <kenvandine> that's exactly where i see the warning printed from
[13:28] <kenvandine> so maybe need some debug output from inside that else
[13:28] <kenvandine> to verify
[13:28] <kenvandine> jgdx, perhaps that warning getting printed it making me focus to much on that
[13:28] <jgdx> aah, gotcha
[13:28] <kenvandine> jgdx, so basically it doesn't seem to try to switch the pref if i try to change it a second time
[13:29] <kenvandine> jgdx, unless i back out and back in
[13:29] <kenvandine> maybe it just isn't finished changing?
[13:29] <jgdx> kenvandine, is something selected when it's disabled?
[13:29] <kenvandine> i think so
[13:29] <kenvandine> my phone updated... so don't have your code on it right now
[13:30] <kenvandine> joys of running proposed :)
[13:30] <jgdx> :)
[13:40] <kenvandine> jgdx, ok, so i think that warning was make me chase the wrong issue :)
[13:40] <kenvandine> jgdx, i think it is working fine, it just doesn't output any to make me think it worked
[13:46] <kenvandine> jgdx, it might be useful for the short term to have delegateClicked print output for the pref requested and also print output in onTechnologyPreferenceChanged
[13:47] <kenvandine> so we can be more confident on what is actually happening
[13:47] <kenvandine> jgdx, i do think it's really working... but would be nice to see it happening, especially as more people on more operators start using it
[13:49] <jgdx> kenvandine, agreed. But that's awesome!
[13:53] <mhall119> bzoltan: didn't we use to have a screen to manage chroots in qtc?
[13:54] <mhall119> oh, nvm,I found it
[13:56] <jgdx> Wellark, are those uis in a branch somewhere?
[14:00] <davmor2> guys on the phone in settings → Diagnostics it says previous error reports.  When I click on it it takes me to Error Tracker but shows me nothing should it?
[14:01] <jgdx> kenvandine, addressed your comments. Thanks! :)
[14:01] <kenvandine> thx
[14:02] <ogra_> davmor2, yes, and there is a bug open for that, bdmurray should know about it
[14:02] <ogra_> or ev
[14:02] <davmor2> ev_: ^
[14:02] <davmor2> thanks ogra_
[14:04] <kenvandine> jgdx, how about my question about data roaming vs. cellular roaming?
[14:05] <jgdx> kenvandine, I replied inline, but according to the docs it referers to data roaming.
[14:05]  * kenvandine grumbles about inline comments :)
[14:06] <jgdx> :p
[14:06] <kenvandine> jgdx, did you save your comments?  i'm not seeing them
[14:07] <jgdx> how do I save them? ha
[14:07] <kenvandine> ah... at the top there is some save comments link
[14:07] <kenvandine> it isn't obvious :)
[14:07] <jgdx> right
[14:08] <kenvandine> i did the same thing yesterday :)
[14:08] <jgdx> I'll call the doctor it's so obvious
[14:08] <kenvandine> seb128 schooled me :-p
[14:08] <jgdx> :d
[14:11] <kenvandine> jgdx, so if that's data roaming, how do you toggle cellular roaming?
[14:12] <bzoltan> mhall119: It is still there in the Tools->Options->Ubuntu
[14:12] <mhall119> bzoltan: yeah, just took me a minute to remember
[14:12] <mhall119> bzoltan: we're going to need a way to build scopes for 14.10, but test them on a 14.04 host
[14:13] <mhall119> can I run the scope build in a chroot and display it in the scope test tool running on 14.04?
[14:13] <bzoltan> mhall119: I guess it will need .deb packaging.
[14:13] <mhall119> bzoltan: not installing it on the host system, just being able to test it as a developer
[14:14] <cwayne> couldnt we run it as if it were an app
[14:14] <cwayne> i.e. click pkg it and run in a 14.10 emulator
[14:14] <jgdx> kenvandine, not sure if that's possible atm. not in the spec at least. Note that this branch only updates that switch according to the spec https://wiki.ubuntu.com/Networking#A.2BIBw-Cellular.2BIB0_settings_on_phone
[14:15] <mhall119> cwayne: probably, but then you're not using the test tool that makes testing it easy
[14:15] <kenvandine> jgdx, oh... great
[14:16] <kenvandine> jgdx, ok, waiting for CI to run
[14:16] <jgdx> kenvandine, exiting
[14:17] <mhall119> beuno: alecu: when do we get the ability to browse apps back in the ubuntu store scope?
[14:19] <mhall119> bzoltan: making the click chroot was successful, but it didn't create a new kit for me based on it
[14:19] <mhall119> should it be doing that?
[14:21] <bzoltan> mhall119: no, the kits are auto created when you have a new device
[14:23] <mhall119> any reason why we don't do the same when you have a new click chroot?
[14:29] <bzoltan> mhall119:  a Kit is a link between the app being developped and the sysroot (chroot in our case) and the Device. So when you create a chroot the QtC does make you a Kit, but it does not know what architecture and what device you want to use. So it is not certain. Obviously from that direction it cannot be. But when you create an emulator or plug in a device it will show you the button "Autocreate Kit" in the Device tab... you click on it and it will ch
[14:30] <bzoltan> mhall119: so the automatic Kit  creation when chroots are created is not good and will go away anyway. the workflow is from the Device direction.
[14:31] <mhall119> bzoltan: ok, so what's the plan for supporting scope development? Will we have to run scopes in the emulator to test them or will be able to use the scope test tool?
[14:32] <bzoltan> mhall119: I do not know
[14:33] <mhall119> mhr3: ^^
[14:33] <mhall119> we'll need to get this figured out so we can start growing a community around scope development
[14:34] <mhr3> mhall119, in 1404? no scope tool
[14:34] <alecu> mhall119: we are working on adding that back. But it will probably return as an alphabetically sorted list per department, not as a list of "last submitted", like it used to.
[14:34] <mhall119> mhr3: we need to support developers who have 14.04 on their laptop
[14:35] <mhr3> mhall119, they'll be able to deploy
[14:35] <mhall119> alecu: no plans to have a way to change the order? alphabetical, newest, highest rated?
[14:35] <mhr3> mhall119, either to device or to emulator(maybe?)
[14:35] <mhall119> mhr3: for debugging?
[14:36] <mhr3> mhall119, not known atm
[14:37] <mhall119> mhr3: bzoltan: we'll need to decide on these things, should we setup a call for tomorrow or next week to go over the developer story for scopes?
[14:38] <alecu> mhall119: changing the sort order will not happen for rtm
[14:38] <mhr3> mhall119, that call was today, did you talk to dpm?
[14:38] <bzoltan> mhall119:  sure, if you wish. I would need to know the technical implications of the decision. What need to be backported and what is exactly expected.
[14:38] <pmcgowan> mhall119, emulator, the approach is the same as apps, as I document in the overview
[14:38] <mhall119> pmcgowan: which overview?
[14:39] <mhall119> mhr3: I'll get with dpm so he can update me then
[14:39] <pmcgowan> mhall119, the document I asked you to review and get on d.u.c
[14:39] <pmcgowan> that clarifies all of this
[14:39] <mhall119> pmcgowan: ah, ok, I'll go back and re-read it
[14:39] <dpm> mhall119, ack, let's sync up later on
[14:39] <pmcgowan> mhall119, but a meeting on this would be good
[14:39] <mhall119> the first time I was reading it from the perspective of the website editor, not a scopes author :)
[14:39] <pmcgowan> indeed, author is more important ;)
[14:40] <mhall119> pmcgowan: I'll schedule one for next week so I can get sync'ed with dpm first
[14:40] <pmcgowan> ack
[14:40] <mhall119> pmcgowan: well I want to write a scope now :)
[14:40] <pmcgowan> me too
[14:40] <pmcgowan> first I need to learn go
[14:40] <mhall119> I need to learn C++
[14:41] <pmcgowan> forget that ancient language
[14:41] <cwayne> writing a go scope is super easy
[14:41] <dpm> pmcgowan, indeed you better try with the c++ scopes first, afaiui, we're not yet recommending go scopes
[14:41]  * cwayne was gonna work on a template for it
[14:41] <pmcgowan> nice
[14:41] <mhall119> any progress on supporting javascript for scopes?
[14:42] <mhall119> or was that just a wild idea
[14:42] <pmcgowan> I think there are plans but not sure when
[14:45] <dpm> I believe JS is post-RTM, thostr_ mentioned
[14:45] <thostr_> dpm: yes, js is post rtm
[14:45] <dpm> thanks
[15:59] <bondj> hello
[15:59] <bondj> i just came here to check the progress of available phone images since im in need of a new device 8)
[16:00] <bondj> so nexus is supported best or how are the community maintained images?
[16:02] <bondj> and what about those 2 partners of canonical can anybody here tell me when those phones will be available?
[16:06] <tomdp> It looks to me like we only know who the partners are. Neither of them have, to my knowledge, released any information to the public about the phones. As always, all we know is "it'll be ready when it's ready."
[16:07] <bondj> okay, back to the current state then :) how are the images doing? which devices run best currently? i guess the nexus ones?
[16:08] <ogra_> nexus4, 7 (2013) and 10
[16:09] <bondj> and how are the community maintained ones doing?
[16:09] <ogra_> there is a nexus5 port that seems to do quite well
[16:09] <ogra_> not sure about others
[16:10] <bondj> actually my purchase decision depends on the ubuntu touch support heheh :) i don't mind if the device is a year or 2 old.
[16:12] <bondj> what do you think are the biggest problems currently? hows the availability of apps right now?
[16:13] <bondj> i mean the trailer and all shows youtube, facebook ,etc. but whos developing this facebook app? facebook themselves?
[16:14] <bondj> id really like to see the apps :)
[16:15] <mhall119> bondj: if you want an Ubuntu Phone right now, a Nexus 4 is your best bet
[16:16] <bondj> yeah i already thought so. now what about the available apps? which ones are there already? :)
[16:16] <bondj> cant find em
[16:16] <bondj> xD
[16:16] <mhall119> bondj: there's a lot of them, are you interested in anything specific?
[16:16] <bondj> yeah how about a link to the software center or whatever it is called on ubuntu touch
[16:17] <mhall119> the web front-end to the store isn't up yet, so unfortunately there's no easy way to browse them without a device
[16:17] <mhall119> but it's being worked on already
[16:17] <bondj> ah thats why i didnt find em
[16:17] <bondj> :P
[16:18] <bondj> is there some kind of emulator i can throw the image to eat at and browse the store?
[16:18] <bondj> there must be
[16:18] <bondj> :D
[16:18] <dobey> what are you trying to do?
[16:19] <bondj> well id love to see the published apps
[16:19] <bondj> but i dont have a phone yet :) my phone is like one of the first android phones heheh :)
[16:19] <mhall119> bondj: yes there is an emulator
[16:19] <dobey> oh
[16:20] <dobey> yeah emulator i guess would be the "best" option
[16:20] <dobey> though the x86 emulator won't show you all the apps
[16:20] <mhall119> bondj: http://developer.ubuntu.com/apps/sdk/tutorials/using-the-ubuntu-emulator/
[16:20] <dobey> some apps are arm only
[16:21] <bondj> ah, sweet
[16:24] <bondj> creating emulator  instance right now beyaoutch
[16:24] <bondj> ;D
[16:27] <maffo999> hello room
[16:27] <maffo999> quick question for you guys
[16:27] <maffo999> is flashing ubuntu touch from a aubuntu x64 installation working?
[16:28] <maffo999> i'm trying to flash my device but cannot get it done in any way
[16:28] <maffo999> i've opened a question here https://askubuntu.com/questions/493802/unable-to-install-ubuntu-touch-on-my-nexus-7-32gb but got no response
[16:28] <maffo999> anyone willing to help me please?
[16:37] <kenvandine> jgdx, tested the new debs, work great!
[16:37] <kenvandine> pmcgowan, ^^
[16:38] <kenvandine> jgdx, did you look at the CI failure?
[16:38] <jgdx> kenvandine, goodie
[16:38] <kenvandine> jgdx, i'm guessing that's a transient error... and a rebuild might work
[16:38] <kenvandine> failed to download some file...
[16:38] <pmcgowan> kenvandine, cool will grab those to test with
[16:39] <pmcgowan> maffo999, that should work yes, is that the newer nexus 7 from last year?
[16:39] <pmcgowan> yeah flo should work
[16:40] <pmcgowan> maffo999, did you get the tools from the phablet-team tools ppa?
[16:40] <davmor2> maffo999: the boot where you saw the Ubuntu Logo and the loading bar underneath did you actually let that finish?  That was the device flashing
[16:40] <jgdx> kenvandine, I have currently no rebuild permissions.
[16:40] <kenvandine> i'll do it
[16:41] <jgdx> kenvandine, thanks
[16:41] <davmor2> maffo999: please note it takes a while to setup the system
[16:41] <kenvandine> jgdx, i need to run out for lunch, if that passes i'll approve the branch when i get back
[16:41] <jgdx> kenvandine, aight. I'll pop out too. Later!
[16:56] <maffo999> the point is that when the animation starts the ubuntu-device-flash programs quits
[16:56] <maffo999> i got it from the universe/multiverse repo since i'm running 13.10 and they say the additional repos are only for 12.04
[16:57] <maffo999> i'm not really sure how the proper flashing procedure works since i've never seen it done before
[16:57] <maffo999> once i run the ubuntu-device-flash command what do i have to expect?
[17:01] <dobey> maffo999: ubuntu-device-flash works fine for me
[17:01] <maffo999> would you mind to explain me how it works then?
[17:01] <dobey> it's supposed to exit if your device is at the point of the ubuntu spinner/installing animation
[17:02] <dobey> as everything left to do is on the device itself
[17:02] <maffo999> fine, so there happens the real flashing
[17:03] <maffo999> and all i need to do is wait apparently?
[17:14] <bondj> howdy
[17:14] <bondj> i just wanted to try the emulator to see which apps are available. however i end up with a black screen on the emulator
[17:14] <bondj> it runs though since im logged in at terminal and all
[17:37] <jdstrand> popey: not sure if we talked about this, but I will be fixing bug #1339686 today
[17:39] <popey> super. while you're here... ahayzen had a q for you I think...
[17:39] <popey> nope, I lie, nik90_ did ☻
[17:39] <ahayzen> popey, did i...
[17:39] <jdstrand> nik90_: you mentioned a denial for /usr/share/sounds/ubuntu/ringtones/. did you file a bug? I'll add that path to the audio abstraction
[17:39] <popey> thats the one.
[17:40] <jdstrand> aha :)
[17:41] <bondj> hey guys, can anyone tell me why ubuntu emulator shows a black screen? i just wanted to see the available apps and installed the emulator, created an instance but the screen stays black even though i can login at the terminal
[17:41] <ahayzen> jdstrand, do you know if is there a bug for the ringtones not playing in system-settings, or is that part of the same thing?
[17:42]  * ahayzen hijacks nik90_'s question
[17:44] <jdstrand> ahayzen: I would suspect that to be a different bug since system-settings is not confined
[17:45] <ahayzen> jdstrand, that was nik90_ 's thought as well... i'll check later if there is a bug and file one if there isn't, thanks
[17:45] <jdstrand> ahayzen: it is probably that media-hub-scanner needs rules added
[17:46] <jdstrand> ahayzen: do 'grep DEN /var/log/syslog' when you see the problem and file a bug (ping me if it isn't obvious as to which package)
[17:46] <ahayzen> jdstrand, ok thanks
[17:47] <bondj> i can see that the emulator still is hogging my cpu though
[17:49] <nik90_> jdstrand: hey thanks, so I would need to add audio to the .json file?
[17:49] <nik90_> jdstrand: I haven't filed a bug yet. Which project would I report it against?
[17:52] <nik90_> bondj: are you using the i386 emulator?
[17:53] <nik90_> bondj: it works fine for me
[17:55] <bondj> nik90_, i use ubuntu-emulator which seems to run qemu with arm
[17:55] <nik90_> bondj: ah ok...let me grab a link which shows how to use the new i386 emulator which is so much faster and better
[17:56] <nik90_> bondj: http://davidplanella.org/ubuntu-emulator-quickstart-guide/
[17:58] <bondj> nik90_, thx, i already wondered why the arch parameter didnt work
[17:59] <nik90_> bondj: I think you should try creating the emulator using Qtcreator which provides a nice gui to all this
[18:04] <nik90_> jdstrand: reported the bug at https://bugs.launchpad.net/ubuntu-clock-app/+bug/1340326
[18:05] <jdstrand> nik90_: thanks!
[18:09] <nik90_> charles: I have created bug 1340329 to track the automatic phone unlocking when an alarm is triggered
[18:09] <nik90_> charles: I was told that you were assigned to implement it
[18:09] <charles> nik90_, thanks
[18:17] <jdstrand> jhodapp: hi! did you see my question in bug #1337582?
[18:18] <jhodapp> jdstrand: yes, just haven't had a moment to reply...sorry
[18:18] <jdstrand> that's ok
[18:18] <jdstrand> just wanted to make sure you saw it
[18:19] <jhodapp> jdstrand: yeah, I'll answer it now while I eat my lunch
[18:25] <jhodapp> jdstrand: replied
[18:26] <jdstrand> thanks
[18:28] <jdstrand> jhodapp: ok, so, unless there are implementation flaws (which are just bugs that we can fix later on), a malicious app with access to /android/micshm can't do anything to DoS the service or to record in the background, correct?
[18:28] <charles> rsalveti, does this look correct to you: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1340329/comments/1
[18:29] <jhodapp> jdstrand: correct, because there technically would be a reader on the Android side always open, but it won't be doing any reads unless triggered by kicking off the recording process
[18:30] <rsalveti> charles: yes
[18:30] <charles> rsalveti, cool, thanks for confirming
[18:30] <rsalveti> np
[18:34] <jdstrand> jhodapp: could a malicious app could in theory interfere with an app that is already recording?
[18:34] <kenvandine> ahayzen, i updated my content-hub branch, should do just what you asked for
[18:35] <jhodapp> jdstrand: in theory yes...I need to see if I could have the active reader/writer pair open the named pipe exclusively
[18:36] <jhodapp> jdstrand: so that only one writer is allowed
[18:39] <kenvandine> elopio: hey, about the test peer for your autopilot testing, can that be in a separate debian package?
[18:39] <elopio> kenvandine: yes, it can.
[18:39] <kenvandine> elopio: i'm thinking about adding that in the content-hub source and create a content-hub-test-peer package
[18:39] <kenvandine> which you could depend on
[18:39] <kenvandine> cool
[18:41] <elopio> kenvandine: that would be good. But would you like to have a package for each testability thing that we add?
[18:41] <elopio> lets say that we add a python module to set up a dbus mock for the content hub, would you put it in content-hub-test-dbus, or would it better to group everything in something like content-hub-testability ?
[18:42] <kenvandine> i'd say all together
[18:43] <elopio> kenvandine: ok, then it sounds like you need something more general than content-hub-test-peer. But any name works for me, feel free to ignore it :)
[18:44] <elopio> kenvandine: I have another questions. Is this going to work on the desktop at some point? When I click the address book avatar on the desktop, it just keeps loading forever.
[18:44] <elopio> I'm not sure if this test with the peer will be mobile only.
[18:45] <elopio> s/questions/question. That's it for today.
[18:45] <kenvandine> eventually
[18:45] <kenvandine> i'd think it should work now
[18:45] <kenvandine> oh... yeah i know why
[18:45] <kenvandine> it tries to open the default picture source
[18:45] <kenvandine> which is com.ubuntu.gallery
[18:45] <kenvandine> not gallery-app
[18:45] <kenvandine> it isn't installed as a click on the desktop
[18:46] <elopio> kenvandine: ok, that's cool.
[18:46] <otherjon> hello all -- am I in the right place to ask about a bluetooth daemon failure on Nexus 7 LTE?
[18:48] <otherjon> apparently bluetooth is a real conversation stopper around here :)
[18:48] <otherjon> who should I talk to, or where should I go?
[18:49] <jdstrand> jhodapp: I think that would be a reasonable security improvement. I won't block adding the rule to policy though. pulseaudio itself isn't particularly great on this point aiui, and it too will need to be hardened
[18:49] <jhodapp> jdstrand: indeed...exclusive pipe access would actually be an improvement over how AudioFlinger does it...I'm pretty sure it's using an unprotected pipe
[18:50] <pmcgowan> otherjon, there's a bunch of work on BT about to land so depending you may want to see how that goes
[18:50] <otherjon> pmcgowan: sounds reasonable -- is there a timeframe for the update?
[18:51] <pmcgowan> otherjon, I expect next day or two
[18:51] <pmcgowan> otherjon, you may want to log a bug anyway however
[18:53] <otherjon> pmcgowan: thanks, I'll look for an update over the next several days -- bugs should be reported at https://bugs.launchpad.net/ubuntu-touch-preview ?
[18:53] <otherjon> I just searched for "bluetooth" and got no results
[18:53] <pmcgowan> cyphermox_, where do bt bugs go?
[18:54] <pmcgowan> otherjon, was it a bluez daemon issue?
[18:55] <jdstrand> jhodapp: fyi, filed bug #1340345
[18:55] <jdstrand> jhodapp: does this look good? http://paste.ubuntu.com/7776645/
[18:55] <pmcgowan> otherjon, maybe https://bugs.launchpad.net/ubuntu/+source/bluez
[18:55] <otherjon> pmcgowan: kern.log tells me "bluetooth-main" (I think I'm remembering correctly)
[18:56] <otherjon> pmcgowan: I remember it didn't actually sound like the name of an executable
[18:56] <otherjon> looking it up now
[18:58] <jhodapp> jdstrand: change qtubuntu-camera binder service to be "qtubuntu-camera library"
[18:58] <otherjon> pmcgowan: "bluetooth-touch main process terminated with status 1"
[18:58] <jhodapp> jdstrand: otherwise looks great
[18:58] <otherjon> pmcgowan: I couldn't find a "bluetooth-touch" daemon
[18:58] <jdstrand> jhodapp: thanks!
[18:58] <jhodapp> jdstrand: thanks for doing that
[18:59] <jdstrand> np
[18:59] <otherjon> pmcgowan: so I'm guessing it's not bluez?  but I don't know much about bluetooth
[18:59] <pmcgowan> otherjon, let me check one more place
[19:00] <otherjon> pmcgowan: thanks, I really appreciate your help
[19:00] <pmcgowan> otherjon, https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch I would suppose
[19:01] <jhodapp> jdstrand: are you an LP member of "Ubuntu Developers"?
[19:01] <otherjon> pmcgowan: heh -- I didn't find the executable, so I didn't look for reporting the bug (and I've been vaguel assuming this is a known issue anyway)...  I'll file the bug.  Thanks for your help!
[19:02] <pmcgowan> otherjon, ok vg
[19:03] <jdstrand> jhodapp: probably, what is the launchpad id for that group?
[19:03] <jhodapp> jdstrand: ubuntu-devel-discuss-lists
[19:04] <jhodapp> jdstrand: are you able to change the maintainer of that project? I don't seem to be part of the group that it currently is under, even though I'm mostly driving qtubuntu-camera these days
[19:04] <jhodapp> jdstrand: so I can't triage the bugs
[19:06] <jdstrand> jhodapp: oh, do you mean ubuntu-core-dev?
[19:07] <jdstrand> I am a core-dev
[19:07] <jhodapp> jdstrand: oh, maybe it is...I looked at the wrong thing
[19:07] <jhodapp> jdstrand: yeah, I'm not a core-dev
[19:07] <jdstrand> qtubuntu-camera is in universe
[19:08] <jdstrand> I think if you are a motu, you will be able to upload and triage those bugs. if not, you either need to become one, or get ppu rights (per package upload)
[19:09] <jdstrand> jhodapp: see https://wiki.ubuntu.com/UbuntuDevelopers
[19:10] <jhodapp> jdstrand: yeah, I just won't have time to do that for a while
[19:10]  * jdstrand nods
[19:10] <jdstrand> do you want me to set the triage state for that?
[19:11] <jhodapp> jdstrand: that'd be great, thanks...and set to high priority
[19:21] <jdstrand> done
[19:33] <cyphermox_> pmcgowan: against bluez
[19:35] <cyphermox_> otherjon: the fixes pmcgowan mentioned are lots of design updates and fixes, I'm about to push it to a ppa again if you want to give it a shot
[19:37] <ahayzen> kenvandine, thanks :) any ideas when it will land in an image or when i can add a silo?
[19:42] <kenvandine> ahayzen, i need reviews still
[19:42] <ahayzen> kenvandine, cool
[19:42] <kenvandine> ahayzen, can you comment on the MP?
[19:43] <kenvandine> bfiller, can you review that branch for me?  https://code.launchpad.net/~ken-vandine/content-hub/content_item_move/+merge/226173
[19:43] <ahayzen> kenvandine, what do u want me to say?
[19:44] <kenvandine> just give it a +1 that it does what you need
[19:45] <kenvandine> and a code review wouldn't be discouraged :)
[19:45] <ahayzen> kenvandine, ok will do :)
[19:46] <kenvandine> thx
[19:49] <bfiller> kenvandine: I will look
[19:49] <kenvandine> thx
[19:50] <kenvandine> elopio: i have a rough autoexporter in a branch if you want to play with it
[19:50] <kenvandine> lp:~ken-vandine/content-hub/testability
[19:51] <kenvandine> elopio: that adds a content-hub-testability package, which installs a source for pictures
[19:51] <bfiller> kenvandine: do we need to bump the version or something as this is a new api?
[19:51] <kenvandine> it should show up in the peer picker
[19:51] <kenvandine> bfiller, no, it's not breaking api
[19:51] <kenvandine> just adding new
[19:51] <kenvandine> and it's purely QML api
[19:51] <kenvandine> so nothing will link with it, etc
[19:51] <bfiller> kenvandine: ack
[19:52] <bfiller> kenvandine: how would I test this MR (other than looking at code)?
[19:52] <kenvandine> elopio: when selected, it automatically charges the transfer and exits when it's collected
[19:52] <kenvandine> bfiller, i have a branch of my hub-importer that exercises it
[19:52] <kenvandine> if you want
[19:53] <bfiller> kenvandine: yes please, just put a comment in the MR about how to run it, etc and I'll try
[19:54] <kenvandine> bfiller, commented
[19:54] <kenvandine> bfiller, i'm confident it couldn't break any existing apps, so very low risk
[19:55] <bfiller> kenvandine: let me get a silo
[19:55] <kenvandine> but it would be nice to get ahayzen using it in music-app to get some real testing
[19:55] <pmcgowan> bfiller, hey, known bug? x-ofono-unkown missed call
[19:56] <kenvandine> pmcgowan, did you run the autopilot tests on your phone?
[19:56] <pmcgowan> nope
[19:56] <kenvandine> pmcgowan, i had that after i had phonesim run
[19:56] <bfiller> pmcgowan: thought that was fixed a while ago
[19:56] <pmcgowan> yeah it was I thought
[19:56] <bfiller> pmcgowan: how do you get it?
[19:56] <ahayzen> kenvandine, yeah but we still need some work our end and in the mediascanner2 ....
[19:56] <bfiller> maybe we missed a case
[19:56] <pmcgowan> call from a number not in my book
[19:56] <pmcgowan> the number displayed I think on the notification, I declined the call
[19:57] <kenvandine> ahayzen, well, it'll work you just need to restart your phone to see it :)
[19:58] <pmcgowan> bfiller, maybe the number was blocked, I cant open it in recent calls
[19:58] <bfiller> pmcgowan: probably blocked yes
[19:58] <ahayzen> kenvandine, so how would you expect the movement of the file to occur? would you expect the music app to automatically move to it into the location and then play it... or would you expect the app to ask the user anything?
[19:58] <bfiller> salem_: ^^^
[19:58] <bfiller> see pmcgowan question
[19:59] <kenvandine> ahayzen, that's a design question :)
[19:59] <ahayzen> kenvandine, hah ,.... more design questions
[19:59] <kenvandine> ahayzen, but... i think i'd lean toward showing the user
[20:00] <salem_> pmcgowan, do you see the entry for that call in the call log?
[20:00] <kenvandine> then letting them say yes or no
[20:00]  * ahayzen is making a mega design mail :)
[20:00] <kenvandine> ahayzen, and you can display the metadata you get before the move
[20:00] <kenvandine> instead of relying on the model
[20:00] <pmcgowan> salem_, you mean in Recent, if so yes
[20:01] <salem_> pmcgowan, ok, I supposed that was a blocked number then
[20:01] <salem_> *suppose
[20:02] <ahayzen> kenvandine, yeah so it could say it is going to move the file x to the location y .... yes | no ... and then once done dump you to the now playing with the track selected
[20:02] <pmcgowan> salem_, surely we have a string like "Unknown caller" ?
[20:02] <kenvandine> ahayzen, you can even let them play it before they save it, since you'll have it in MediaPlayer
[20:02] <kenvandine> like a preview before saving
[20:02] <kenvandine> you probably don't want to show them the location
[20:02] <kenvandine> just the song metadata
[20:03] <kenvandine> "Add this song to your library" sort of thing
[20:04] <ahayzen> kenvandine, yeah... we'll just need to make sure that our Player {} is fine with something not in the model then it will automatically work with our toolbar actions/seeking etc :)
[20:04] <kenvandine> cool
[20:05] <salem_> pmcgowan, looking at the code it doesn't seem we are handling that case. is it easy for you to take a screenshot?
[20:05] <ahayzen> kenvandine, i'll have a play about later/tomorrow see what i can get going
[20:05] <pmcgowan> salem_, certainly
[20:05] <pmcgowan> but it just says x-ofono-unknown with the time
[20:05] <salem_> pmcgowan, ahh, then it is certainly a blocked number
[20:06] <kenvandine> ahayzen, cool
[20:06] <pmcgowan> salem_, I wasnt really paying attention, just declined it
[20:06] <pmcgowan> but yeah
[20:06] <ahayzen> kenvandine, too many cool things to work on :)
[20:06] <otherjon> cyphermox_: thanks, I'll be happy to give the new package a try and report back, if you think it's likely to solve my problem ("bluetooth-touch main process terminated with status 1" in kern.log) -- is that likely?
[20:06] <salem_> pmcgowan, we specifically change to that string when the caller number is hidden.
[20:06] <kenvandine> ahayzen, story of my life :)
[20:07] <ahayzen> hehe
[20:07] <pmcgowan> salem_, why?
[20:07] <cyphermox_> otherjon: no
[20:07] <pmcgowan> salem_, need better text I guess
[20:07] <salem_> pmcgowan, well, it's an internal thing, we should be comparing that in the dialer and replace by a proper text.
[20:07] <cyphermox_> for that I suggest you edit /etc/init/bluetooth.conf , add -d to the end of the Exec line, and restart to try to reproduce the bug
[20:08] <otherjon> cyphermox_: too bad, but thanks for the info
[20:08] <cyphermox_> otherjon: when you reproduce it, add /var/log/syslog to the bug report
[20:08] <pmcgowan> salem_, ok will file a bug
[20:08] <pmcgowan> salem_, also in the indicator
[20:08] <otherjon> cyphermox_: it's 100% reproducible -- but why /var/log/syslog?  the error shows up in kern.log
[20:08] <salem_> pmcgowan, we use x-ofono-private and x-ofono-unknown. They are  being replaced in the notification, but probably not in the call log or the indicator.
[20:09] <otherjon> cyphermox_: pmcgowan: bug filed: https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1340352/+activity
[20:09] <cyphermox_> otherjon: if you enable debugging in bluez as above, the logs will appear in syslog
[20:09] <cyphermox_> maybe kern.log too, but syslog usually has all the info you might need, then nothign is missing ;)
[20:09] <cyphermox_> oh, wait a second
[20:09] <cyphermox_> I misread, sorry
[20:10] <otherjon> cyphermox_: I can't find "as above" -- how do I enable debugging in bluez
[20:10] <cyphermox_> this is for bluetooth-touch...
[20:10] <cyphermox_> otherjon: what's the codename for nexus 7?
[20:10] <otherjon> cyphermox_: flo, I think? this is the LTE version, if it makes a difference -- just a minute, I'll confirm
[20:11] <bfiller> pmcgowan, salem_ : I see the same thing, I block caller id then call the phone. the notification correctly shows "Unknonw caller" but the messaging menu and call log show x-ofono-unknown
[20:11] <bfiller> I will file a bug
[20:12] <pmcgowan> bfiller, ok I will stop
[20:15] <bfiller> pmcgowan, salem_ : https://bugs.launchpad.net/telephony-service/+bug/1340386
[20:16] <otherjon> cyphermox_: ro.product.device = deb
[20:16] <otherjon> cyphermox_: that's the codename you were referring to?
[20:16] <cyphermox_> otherjon: right now you should be able to copy /etc/init/bluetooth-touch-mako.conf to /etc/init/bluetooth-touch-deb.conf
[20:16] <cyphermox_> otherjon: should be yes
[20:17] <cyphermox_> or you know, to be safer, copy flo to deb
[20:17] <pmcgowan> bfiller, should that be on dialer and indicator-messages?
[20:17] <cyphermox_> otherjon: I'll fix this very very soon so that this mucking around isn't necessary
[20:17] <bfiller> pmcgowan: dont' think so, the service is what populates those I believe. at least for the menu
[20:17] <bfiller> I'll add dialer too
[20:18] <elopio> kenvandine: woohoo.
[20:18] <pmcgowan> bfiller, it does but salem_ was thinking the UI parts should map it
[20:18] <pmcgowan> although then three places to do it
[20:18] <bfiller> pmcgowan: yeah, we should do it one place only ideally
[20:19] <elopio> kenvandine: the branch that will use it is from Richard that's already EOD. So we'll work on it tomorrow.
[20:19] <kenvandine> elopio: you can take it for a spin if you like... i need to do more work on it still
[20:19] <otherjon> cyphermox_: ugh, "read-only file system", I must not have made it writeable yet (and my cable and dev setup are at home) -- I'll try that mako.conf file tonight.  Do I need to reboot, or is there an easier way to reconfigure?
[20:19] <kenvandine> we need to be able to respond to different content types... so the same exporter could provide pictures, contacts, etc
[20:20] <kenvandine> and it should include real files too... right now it charges the transfer with files that don't exist
[20:20] <salem_> pmcgowan bfiller, the problem is that we don't want to store the final translated string into the history-service db as it needs to be translatable.
[20:20] <cyphermox_> otherjon: to make it writable you'll need to run phablet-config writable-image, and then copy /etc/init/bluetooth-touch-flo.conf to /etc/init/bluetooth-touch-deb.conf and reboot
[20:20] <otherjon> cyphermox_: flo.conf or mako.conf?
[20:21] <cyphermox_> use flo, just in case mako is a little different
[20:21] <cyphermox_> it really shouldn't, but just to be safe
[20:21] <bfiller> salem_: true for the dialer-app
[20:21] <otherjon> cyphermox_: (I don't have the cable here, and don't have phablet dev tools installed here, so it'll have to wait 7-8 hours or so)
[20:22] <otherjon> cyphermox_: I'll give that a try -- thanks a lot for your help
[20:22] <cyphermox_> ok
[20:22] <cyphermox_> wihtout a cable how are you getting on the device, via the terminal?
[20:22] <elopio> kenvandine: got it. Yes, we need a real file to check it back on the address book. But sounds really nice and faster than what I expected.
[20:22] <elopio> thanks.
[20:22] <otherjon> cyphermox_: yes, I'm hoping to eventually use the Nexus 7 as a replacement for my old netbook
[20:23] <otherjon> cyphermox_: that terminal will be getting plenty of use! ... and you can see the reason I want to be using a bluetooth keyboard... :)
[20:23] <cyphermox_> otherjon: I see
[20:23] <cyphermox_> the bluetooth keyboard is going to be another hurdle
[20:23] <cyphermox_> currently we don't handle mouse or keyboard.
[20:24] <cyphermox_> ^ pmcgowan: maybe we want to just enable them, it mostly should work out of the box
[20:25] <pmcgowan> cyphermox_, if you think it will just work, but we are not committed to it
[20:25] <otherjon> cyphermox_: I'm happy to be an alpha tester, or if there's any other way I can help...  I don't know anything about bluetooth, but I can code
[20:26] <cyphermox_> well, in reality mouse just won't show a cursor at all, so that part isn't exaclty useful
[20:26] <dobey> YAY GPS ON NEXUS 5
[20:26] <otherjon> keyboard, on the other hand... well, let's just say that the onscreen keyboard wasn't intended for heavy terminal users :)
[20:27] <dobey> or for people with complex passwords, or that type in URLs :)
[20:27] <tedg> Kaleo, Why is there PopupUtils.open(foo) instead of foo.visible = true ?
[20:27] <dobey> but that's true on android and ios too
[20:28] <otherjon> dobey: very true... but that's why I don't have an android or ios device :)
[20:28] <Kaleo> tedg, PopupUtils.open(foo) is very bad API design
[20:28] <tedg> Kaleo, Heh, will foo.visible work?
[20:28] <Kaleo> tedg, however  foo.visible = true is not a good idea either because we don't want the component to be instantiated all the time even when not needed
[20:29] <Kaleo> tedg, nope it won't; for now you have to use PopupUtils
[20:29] <otherjon> cyphermox_: if there's any way I can help alpha-test BT keyboard support or any other way I can help, let me know
[20:29] <tedg> Kaleo, Ah, okay. It just destroys some of the declarative-ness of the code.
[20:29] <cyphermox_> ok
[20:30] <Kaleo> tedg, it does, it's bad
[20:30] <Kaleo> tedg, sorry about that
[20:31] <tedg> Kaleo, I'll let you go this time, make sure it doesn't happen again! ;-)
[20:32] <tedg> First time I've seen the popup stuff before in this review.
[20:32] <tedg> Now I'm going to use them everywhere! <evil laugh>
[20:32] <Kaleo> tedg, it's actually very old code, 2 years nearly
[20:34] <tedg> Kids these days. "very old" grumble, grumble, "2 years", grumble, grumble.
[20:38] <cwayne> dobey: gps on n5?
[20:42] <dobey> cwayne: yeah, updated today and saw the gps switch was on. and it seems to have got a fix and works in the osmtouch maps app for me
[20:44] <bfiller> kenvandine: MR approved, building in silo 3
[20:44] <bfiller> kenvandine: tested the sample importer and all working well
[20:45] <kenvandine> bfiller, cool
[20:45] <cwayne> dobey: hm, didnt work for me
[20:46] <dobey> cwayne: i think i'll take it with me in a bit when i go out to get food, to see if it locks on
[20:46] <dobey> now if all the other issues could be fixed too…
[20:47] <dobey> battery indicator properly goes all the way to 100% now too
[20:47] <dobey> backlight still stays on forever though :-/
[20:48] <dobey> hmm, clock app fails to start thugh, so can't add an alarm to test that
[20:52] <bfiller> Saviq: around?
[20:56] <kgunn> jhodapp: hey, can i just adb push mp3's into home/phablet/Music ? ...i did, but they're not showing up...curious if i'm "doing it wrong"
[20:56] <kgunn> & yes i verified they're on the device
[20:56] <jhodapp> kgunn: no, they're not owned by phablet then
[20:56] <jhodapp> kgunn: use mtp
[20:56] <kgunn> mm
[20:57] <popey> mtp is busted
[20:57] <jhodapp> kgunn: just chown phablet *.mp3 then
[20:59] <kgunn> popey: jhodapp cheers!
[20:59] <jhodapp> awesome
[21:05] <kenvandine> did i just get a real push notification about an update that's ready?
[21:05] <kenvandine> mind blown!
[21:22] <kgunn> popey: jhodapp ok....so whatever caused local music to stop with screen going off isn't the latest mir...i just test image110 when mir0.4.0 went in...
[21:22] <kgunn> music is continuing to play just fine
[21:23] <kgunn> mir hasn't changed a thing since then
[21:23] <jhodapp> kgunn: ok
[21:24] <dobey> jhodapp, kgunn: just upgraded to 124 on my n5, and music is playing with screen off in music app here
[21:25] <jhodapp> dobey: good to know, thanks
[21:25] <kgunn> sound like the issue was local to popey ;P
[21:26] <popey> kgunn: and your phone isnt plugged into usb?
[21:27] <kgunn> popey: nope
[21:27] <popey> ok
[21:27] <popey> hmm, thanks, and sorry for taking your time on that
[21:27] <kgunn> popey: no worries at all....fwiw, i'm on image 110 on N4, were you testing on n4 ?
[21:28] <popey> yes
[21:36] <ahayzen> popey, so why are only u and me seeing it lol
[21:48] <rpadovani> Hey guys, I need an hand. I red the documentation, but I don't understand... So I have a component. A script create some objects with Component.createObject() function.
[21:49] <rpadovani> How can I destroy all objects at a some point?
[22:05] <popey> ahayzen: well, I'm using your build..
[22:05] <popey> ahayzen: lemme remove that and revert to the store build
[22:05] <ahayzen> popey, ... and ur build....?
[22:06] <ahayzen> popey, hang on my build of the app? surely not ah,... unless our custom clicks we are installing aren't included in the lifecycle exception?
[22:08] <popey> lets see
[22:11] <ahayzen> popey, just installed the store one and its working \o/
[22:12] <popey> yay
[22:12] <ahayzen> popey, so that must be the case then?
[22:12] <popey> your fault
[22:12] <popey> :D
[22:12]  * ahayzen hides
[22:12] <popey> hehe
[22:12] <ahayzen> popey, are you seeing the same behaviour?
[22:12] <popey> well, thats super fab news IMO
[22:12] <ahayzen> popey, note i only did one quick test as well lol
[22:13] <popey> having trouble doing the un-re-install
[22:13] <popey> gimmie 5
[22:13] <ahayzen> popey, cool
[22:13] <popey> doing this inbetween shouting at scottish people on telly
[22:14] <ahayzen> popey, scottish people? what have they done now?
[22:14] <popey> Question Time
[22:14] <ahayzen> popey, ah
[22:15] <ahayzen> popey, are they debating about building hadrian's wall again?
[22:15] <popey> ya
[22:15] <ahayzen> oh dear
[22:15] <popey> ok, a bit of adele is helping
[22:16] <ahayzen> haha not abba?
[22:16] <popey> not today
[22:16] <popey> ABBA is for weekends
[22:16] <ahayzen> haha
[22:16] <popey> love that we now have flight mode
[22:17] <popey> now you can use phones on planes :D
[22:17] <ahayzen> yep flight mode = silent mode for me at the moment lol
[22:17] <popey> i would like a "STFU" mode
[22:17] <popey> no notifications, no sound, no alarms
[22:17] <popey> but allow network
[22:17] <ahayzen> hah
[22:20] <popey> dammit, welcome screen lockup
[22:21]  * popey reboots and tries again
[22:21] <ahayzen> popey, thats really not useful lol
[22:53] <kgunn> jhodapp: do you already have a bug on scrubbing/ff ?...i'll just keep moving on if you say 'yes'
[22:59] <trist_> hello
[22:59] <trist_> Anyone here?
[23:00] <pmcgowan> trist_, better to ask your question then hope for the best
[23:01] <sarnold> trist_: 238 give or take.. :)
[23:02] <trist_> WEll i just completly installed Ubuntu 14.04 onto my pc, however its giving me a few errors finding stuff in the HDD, furthermore it is bringing me to a Login/pass interface on a black screen
[23:09] <trist_> no help?
[23:10] <sarnold> trist_: ah, I was sort of expecting some further details.. but now I notice the channel; this channel is focused on ubuntu's phone/tablet/converged devices development; standard desktop issues are probably better asked in #ubuntu
[23:14] <ahayzen> kenvandine, you still about?
[23:20] <ahayzen> kenvandine, ignore me.... victor came up with the use case of what would happen if the dest already existed and would that be caught....but then we realised that the QFile::rename() will fail and therefore it will return false... so all good :)