[02:17] <mhall119> popey: you probably have to do some trickery to get a full download of the specific revision instead of an image diff
[06:20] <tvoss> pitti, good morning :) qtubuntu-sensors is in landing sheet now, and the Mirv set the cmake branch to approved
[06:20] <pitti> tvoss: good morning -- great to hear! so it should auto-merge into trunk soon?
[06:21] <tvoss> pitti, yup
[06:21] <pitti> cool; I'll work on qtubuntu-sensor tests then this week
[06:27] <x245475233> nexus 5
[06:28] <imjm> hello developers, this is imjm
[06:29] <imjm> i want to know about ubuntu for my device
[06:30] <imjm> :(
[06:30] <tvoss> pitti, great, that sounds good
[06:30] <tvoss> imjm, just ask your questions then
[06:34] <x245475233> any link for the status of development for Nexus 5?
[06:36] <x245475233> preview release
[06:51] <Guest82215> What is Ubuntu Touch like on the Nexus 4 these days?  I tried it at one point, but had problems with the keyboard and the UI kept hanging.  How are things coming?
[06:56] <x5255252> any news about nexus 5?
[07:07] <tvoss> Guest82215, I use it as my primary phone these days. Glitches: yes, but very usable
[07:15] <Guest82215> tvoss, Does bluetooth function?  Specifically, can you use a bluetooth keyboard?  I sometimes use my phone as a laptop replacement that way.
[07:16] <tvoss> Guest82215, I'm not sure tbh, would need to check. However, you can now dual boot android and ubuntu, so easier to keep Ubuntu Touch around on your phone
[07:18] <Guest82215> I've thought about going the dual boot route, but I only have an 8GB model, so I've been hesitant to do that.  But it's probably my best bet at the moment.
[07:18] <Guest82215> Thanks, tvoss.
[07:18] <tvoss> Guest82215, sure, yw :)
[07:45] <dholbach> good morning
[09:03] <Mirv> tsdgeos: Saviq: hi! I seem to have found out how to reproduce the ubuntu-ui-toolkit segfaults locally.. I wonder if you could help? at least I don't find any existing upstream reports yet. bug #1268507
[09:06] <tsdgeos> Mirv: i can have a quick look
[09:07] <tsdgeos> let me see if i can repro
[09:07] <tsdgeos> Mirv: can i unmount proc on my running system and hope nothing will explode?
[09:08] <Mirv> tsdgeos: haha :) just a second, I'm ready for a reboot, I'll test what happens
[09:09] <Mirv> tsdgeos: it's possible, via sudo umount -fl /proc - system still works, and I can launch more gnome-terminals but not more firefoxes
[09:09] <Mirv> tsdgeos: I can then launch firefox again after sudo mount -t proc proc /proc
[09:10] <Mirv> so seems "safe" for short periods
[09:10] <tsdgeos> ok
[09:12] <tsdgeos> Mirv: yeah happens here too
[09:14] <Mirv> if builders do their builds in similar procless chroot, that might explain why it isn't gotten locally normally when proc is mounted but is seen in the PPA.
[09:16] <tsdgeos> Mirv: is not even qt
[09:16] <tsdgeos> it's just pthreads
[09:16] <tsdgeos> Mirv: http://paste.ubuntu.com/6743566/ crashes if you don't have proc mounted
[09:17] <tsdgeos> Mirv: basically i'd say not having proc mounted doesn't seem a good idea :D
[09:17] <tsdgeos> that is the code inside Qt that's crashing when proc is not mounted
[09:17] <tsdgeos> i tried valgrind-ing it
[09:18] <tsdgeos> but valgrind doesn't like the fact proc is not mounted either
[09:18] <tsdgeos> :D
[09:18] <tsdgeos> maybe some error checking is missing in that code
[09:18] <tsdgeos> let me see
[09:19] <Mirv> eh..
[09:20] <tsdgeos> right checking the funcions return makes it not crash
[09:20] <tsdgeos> not sure i can still make the Qt code be meaningful (i.e. that code that crashes is what i copied out from the Qt code that is crashing)
[09:20] <tsdgeos> it's not like i invented it from nowhere :D
[09:22] <Mirv> I've compiled all the Qt modules themselves including tests at least without /proc, so it seems not too common to have that without error checks
[09:22] <Mirv> since I tend to compile them locally on another machine inside chroot and I don't bother mounting the /proc usually
[09:24] <tsdgeos> ok
[09:24] <tsdgeos> i think i can make it not crash easily
[09:25] <tsdgeos> but it seems that is the code used to check how big the stack is
[09:25] <tsdgeos> so may have side effects
[09:32] <tsdgeos> Mirv: yes, running QML stuff needs pthread_getattr_np to succeed that needs /proc/self/maps to be there, don't think there's much we can do here, i don't think i'll be able to convince the Qt guys not having /proc around is a priority for them
[09:32] <tsdgeos> but i can try
[09:33] <Mirv> cjwatson: do the builder build environments have /proc mounted? there is a crasher that happens when using pthread without error checking and /proc not mounted, and I wonder how it is on builders
[09:34] <Mirv> tsdgeos: if error checking is something usually done in that situation, I'd guess they'd accept a patch at some point even if not a priority
[09:34] <tsdgeos> Mirv: the thing is that i can't see how to trivially add error checking
[09:35] <tsdgeos> they are using the pointer to do nasty stack collection stuff from what i can see
[09:35] <tsdgeos> so they need that value
[09:35] <tsdgeos> trying to see if i can think of something that makes some kind of sense
[10:13] <tsdgeos> Mirv: ok, ended up with https://codereview.qt-project.org/#change,75282 seems to work enough for the unittests, let's see how the review goes
[10:17] <WebbyIT> With last two rev on Nexus 4 wifi doesn't work. I have no dual-boot. what could be the cause?
[10:23] <sergiusens> WebbyIT, you need the 4.3 radio firmware
[10:24] <WebbyIT> sergiusens, this is weird, I have Ubuntu Touch since september I haven't flashed Android since then...
[10:25] <WebbyIT> sergiusens, so, I have to flash Android 4.3 and then reflash Ubuntu Touch?
[10:25] <sergiusens> just the radio image
[10:25] <WebbyIT> let my try, thanks
[10:32] <Mirv> tsdgeos: and first approval already! I'll do a test build with that included.
[10:52] <davmor2> Morning all
[11:01] <Saviq> didrocks, "TypeError: expected tuple for callback user_data", rings a bell?
[11:02] <Saviq> didrocks, and it's python-gi
[11:02] <Saviq> -gobject doesn't affect
[11:03] <Saviq> pitti, didrocks said you might now something of the above ↑?
[11:04] <didrocks> Saviq: yeah, really looking like the warning/check in latest changelog
[11:04] <pitti> Saviq: do you have a pointer to the code that causes this?
[11:04] <didrocks> Saviq: stupid question, do you have a tuple as the callback in your code (even if you don't use it)?
[11:04] <Saviq> pitti, http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/tests/autopilot/unity8/shell/emulators/create_interactive_notification.py
[11:05] <cjwatson> Mirv: yes they have /proc mounted
[11:06] <Saviq> didrocks, not sure ↑ that's the code that triggers it
[11:06] <Saviq> didrocks, action_callback I think
[11:07] <pitti> Saviq: https://developer-next.gnome.org/libnotify/0.7/NotifyNotification.html#NotifyActionCallback says that the callback just receives one user_data argument
[11:08] <pitti> Saviq: I don't have an off-hand idea, I'm afraid; could you turn this into something small and runnable and file a bug report?
[11:10] <didrocks> pitti: it seems it started with latest python-gobject, do you think it's a side-effect of the additional checks or it started to show a real issue in the code itself?
[11:11] <pitti> didrocks: it's more likely to be a regression; but I don't have a firm idea yet
[11:11] <didrocks> ok ;)
[11:49] <pitti> tvoss: I figured out the cmake/gtest/QtPlugins integration now and committed a first sensor API integration test case: http://bazaar.launchpad.net/~pitti/qtubuntu-sensors/integration-tests/revision/46
[11:50] <tvoss> pitti, great, let me have a look
[11:50] <pitti> tvoss: I'll make it more Qtish now and drop some C stuff (mkstemp/write -> QTemporaryFile etc., but this part was copy&pasted from platform-api)
[11:51] <tvoss> pitti, ack
[11:58] <asac> rsalveti: !!
[11:58] <asac> wake up mate
[11:58] <ogra_> asac, mup him :P
[12:00] <asac> nah :)
[12:00] <asac> not important enough
[12:00] <asac> i think he first checks public comm before checking /msg when getting up, so pinged him here :)
[12:18] <Laney> can I read D-Bus annotations using QDBus somehow?
[12:25] <Saviq> pitti, bug #1268578
[12:51] <pitti> Saviq: thanks
[13:10] <nik90> tvoss: ping
[13:11] <nik90> tvoss: (related to app lifecycle)
[13:20] <tvoss> nik90, shoot
[13:23] <nik90> tvoss: when the clock app is running a timer and is sent to the background by navigating to the dash etc, how does clock app signal that the timer is completed to the user?
[13:24] <nik90> tvoss: I read a small part of https://docs.google.com/document/d/1ij8RtPsR_eYMW3mys8Gu1Y2CVFZpjXdMpdIjIGZ1SCA/edit#
[13:25] <nik90> tvoss: where Zygmunt mentions that the clock app has to let the system know to trigger a notification in a certain amount of time which in turn will trigger a snap decision.
[13:25] <nik90> tvoss: am I right? If yes, any idea how the clock app sends a message to the system?
[13:27] <tvoss> nik90, first of all: yes, the clock app needs to hand over to the system to complete this task. Second: libnotify should be your friend here. I don't know if we have a qml binding, yet.
[13:27] <tvoss> thostr_ is the best person to ask here.
[13:28] <nik90> tvoss: but how does the clock app detect that it has been sent to the background by the user?
[13:28] <nik90> tvoss: is there some sort of platform api for that?
[13:28] <tvoss> nik90, sure, your app is being informed of about to be suspended
[13:28] <tvoss> nik90, you then have a grace period to clean up/setup notifications and such
[13:29] <nik90> tvoss: ok..do you happen to know the qml api for that? something like onSuspended: create notification ?
[13:29] <nik90> or where I can find the docs for that
[13:29] <tvoss> nik90, yup, something like that
[13:29] <tvoss> mhall119, can you help nik90 here?
[13:30] <tvoss> nik90, sorry, but I rarely use the qml apis myself
[13:30] <nik90> tvoss: no worries
[13:34] <pitti> kalikiana, tvoss: to confirm, in qtubuntu-sensors we currently only support accelerometer and orientation, no light and proximity, right?
[13:35] <tvoss> pitti, correct
[14:03] <asac> ChickenCutlass: !!
[14:04] <sil2100> greyback, ricmm_: hi guys, any progress on getting https://code.launchpad.net/~ricmm/unity-mir/sidestage-reenable/+merge/198489 merged in?
[14:17] <annerajb> good day!
[14:21] <plars> didrocks: who was it that was looking for the qmlscene crashes? We have some more of those showing up again
[14:21] <didrocks> plars: earlier, it was Mirv
[14:22] <annerajb> any updates on cm-11.0 based ubuntu touch??
[14:22] <plars> didrocks: also, I thought the dialer-app crash was supposed to be fixed, at least according to  bug #1257844
[14:23] <plars> didrocks: but http://ci.ubuntu.com/smokeng/trusty/touch/mako/125:20140113:20140107.1/6032/dialer-app-autopilot/ seems to indicate otherwise
[14:23] <didrocks> plars: we didn't get any new release of dialer app requested
[14:23] <plars> hmm, I wonder why he marked it fix-released then?]
[14:24] <didrocks> I guess we are waiting a landing ask from bfiller
[14:24] <didrocks> plars: well, it's an upstream task
[14:24] <didrocks> not dowstream
[14:24] <plars> true
[14:25] <bfiller> plars: this shouldn't have been marked fixed released, we have not figured it out yet
[14:25] <plars> Mirv: there are a couple of qmlscene crashes in the maguro results from today if you are looking for some still
[14:25] <plars> bfiller: ack, thanks
[14:26] <bfiller> boiko: any progress on this? https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1257844
[14:28] <asac> pitti: is it better from your perspective to implement a workaround in unity8 for the pygi regression (compared to just backout pygi changes?)? whats the real fix?
[14:28] <pitti> asac: if you need to fix it right now, you can add the workaround (it won't hurt after the fix)
[14:29] <pitti> asac: I need to catch simon feltman about this, but he's asleep, so will need to wait until tomorrow
[14:30] <asac> pitti: so just reverting the pygi isnt feasible technically? point is that unity8 would have to land with a workaround and unity8 is pretty big beast
[14:31] <asac> we can do that, but from outside perspective i see both options as valid and would choose whatever is less work :)
[14:31] <asac> (assuming that we solve this problem upstream anyway)
[14:31] <pitti> asac: certainly it's feasible
[14:34] <asac> pitti: so is the change/workaround in unity8 the right thing to do? if its the right thing anyway, i would go the unity8 route; otherwise only if its more work than a revert upload ..
[14:34]  * asac still wonders how python is hitting us at all in phone
[14:34] <asac> thought we dont do python there :/
[14:34] <pitti> yeah, I thought that, too
[14:34] <pitti> asac: currently testing a reversion of the corresponding commit in pygobject
[14:35] <asac> cool
[14:35] <asac> let me also ask in bug why we use python
[14:35] <asac> or directly here
[14:35] <didrocks> asac: autopilot?
[14:35] <asac> oh :)
[14:35] <asac> lol
[14:35] <ogra_> asac, we obviously ship a lot more python since friday http://people.canonical.com/~ogra/touch-image-stats/20140110.1.changes
[14:35] <ogra_> :)
[14:35] <didrocks> ogra_: well, not relevant to the current discussion
[14:36] <ogra_> asac, system-image uses python all over the place too
[14:36] <didrocks> asac: the unity8 revert is risky, we are going to use latest trunk of unity8, and so, way more code
[14:36] <asac> ogra_: on the device?
[14:36] <ogra_> yes
[14:36] <asac> didrocks: i know. we woul dhave to cherry pick land
[14:36] <pitti> asac: it's from unity8's emulators, so only for tseting
[14:36] <asac> which we also can do of course
[14:36] <ogra_> system-image-cli is all python afaik
[14:36] <asac> yeah
[14:37] <pitti> shouldn't be actual functionality from the phone
[14:37] <asac> right. but doesnt matter
[14:37] <pitti> but if this wreaks havoc, I can upload pygobject
[14:37] <asac> once we have not 100% we cant land anything anymore as it might hide new regressions etc.
[14:37] <asac> pitti: it would help a lot... we will soon have image == trunk, then it would be easier to land just cherry picks for unity8 and friends
[14:37] <asac> at least the costs forunity8 workarounds should go down then
[14:39] <boiko> bfiller: nope, I am still trying to find a way to reproduce it
[14:40] <bfiller> plars: any ideas how to help boiko reproduce/debug the issue with dialer?
[14:40] <plars> bfiller, boiko: you don't see it by just running the dialer-app autopilot tests on mako?
[14:41] <boiko> plars: nope, I see another issue, but not this crash that causes the QUbuntu's cannot create application instance message
[14:41] <plars> boiko: what issue are you seeing?
[14:42] <boiko> plars: so, there is one test for incoming calls, after the call is accepted (and the snap decision is dismissed), dialer-app gets focused again, and the screen turns black
[14:42] <boiko> this one I can reproduce all the time
[14:43] <plars> boiko: I'm installing 125 locally right now, let me see what I can do
[14:45] <boiko> plars: ok
[14:45] <mterry> ogra_, so no more maguro builds?  Effective when?  Does this mean I don't need the results of your nested-mode testing on maguro?
[14:46] <ogra_> mterry, ?
[14:46] <ogra_> mterry, we might drop support for it but i dont see a reason why we should stop building it
[14:46] <ogra_> comes with no extra cost
[14:51] <timp> wow. is it intentional in the latest image that the phone vibrates hard on every tap?
[14:51] <timp> ah not every tap, but many
[14:52] <mterry> ogra_, sorry, got disconnected.  asac's recent mail to ubuntu-phone is what I was talking about
[14:52] <ogra_> asac, err, why should we stop doing builds ... we can just stop doing tests, it costs us nothig to leave builds running
[14:52] <ogra_> asac, i agree if they start to cause work we should probably drop them
[14:53] <pitti> Saviq, asac: pygobject uploaded
[14:53] <ogra_> mterry, sorry, hadn't seen the mail
[14:53] <ogra_> (i see it now)
[14:53] <davmor2> timp: it is the start of haptic feedback
[14:54] <davmor2> asac, didrocks: time for me to chat with my boss about getting an n4 then apparently  meh
[14:55] <ogra_> rsalveti, seen asacs mail ?
[14:55] <didrocks> davmor2: right ;)
[14:55] <Laney> can you still get nexus 4s?
[14:55] <didrocks> thanks pitti!
[14:55] <timp> davmor2: good to have a start :) but I hope in the end it will be a bit more subtle :)
[14:55] <davmor2> Laney: no
[14:59] <asac> davmor2: yes, absolutely!
[15:00] <asac> davmor2: there is a PO approved for something related... CC me on the mail you send to jfunk
[15:00] <davmor2> asac: I'll talk it through with jfunk fisrt
[15:01] <asac> ok tell him to talk to me :)
[15:01] <asac> lol
[15:02] <asac> ogra_: happy to explain to you the details in private conversation later today or tomorrow morning
[15:02] <rsalveti> ogra_: yup
[15:03]  * rsalveti checks backlog
[15:03] <ogra_> asac, i just think we should keep them building and just drop them from the tools (phablet-flash etc) so people can still effectively fiddle around with them
[15:03] <asac> i know that you think that.
[15:03] <ogra_> :)
[15:04] <rsalveti> mterry: we still want to support it officially for a couple of weeks
[15:04] <rsalveti> mterry: do you have any issues with maguro specifically?
[15:05] <mterry> rsalveti, there is a bug in u-s-c that ogra_ found.  I have a fix in hand, just needs to be tested.  Was curious how much I should bother with it.  But sounds like yes
[15:06] <ogra_> rsalveti, both, grouper and maguro currently block the nexted mir mode
[15:06] <ogra_> *nested
[15:06] <ogra_> both require some work
[15:06] <rsalveti> right, we'll land the grouper fix probably later today
[15:06] <ogra_> (hybris and some testing)
[15:07] <rsalveti> mterry: but yeah, please push the maguro fix forward
[15:07] <ogra_> mterry, where are these debs, the MP doesnt have a link
[15:08] <mterry> hm
[15:08] <mterry> that's weird
[15:08] <ogra_> did you get them in the mail ?
[15:08] <ogra_> (i'm not subscribed to that one)
[15:09] <mterry> ogra_, no
[15:09] <ogra_> weird
[15:11] <annerajb> rsalveti, any updates on cm-11.0 based ubuntu touch ports?
[15:11] <annerajb> or rather merging cm-11.0 framework to ubuntu phablet frameworks.
[15:11] <rsalveti> annerajb: got the first working image for mako (nexus 4), but still fixing some final issues
[15:11] <annerajb> rsalveti, any public repos that i can start looking at?
[15:12] <rsalveti> annerajb: not yet, will upload it later today
[15:12] <rsalveti> still a bunch of diffs locally :-)
[15:12] <annerajb> allright
[15:13] <mterry> ogra_, well I guess just build it the old fashioned way.  Doesn't take too long
[15:14] <mhall119> nik90: what API do you need help with?
[15:19] <kenvandine> tedg, bfiller: i proposed a branch for UAL which constructs the appid from the triplet
[15:19] <nik90> mhall119: the platform API to detect if the clock app is going to be suspended or not
[15:20] <nik90> mhall119: a little backstory..when the clock app is running a timer and is suspended, it is supposed to send the system a message that the timer is running
[15:20] <nik90> mhall119: but first I need to get a signal when the app is going to be suspended
[15:21] <bfiller> kenvandine: nice
[15:23] <tedg> kenvandine, Ah, cool.  I'll take a look, did you grab all the tests too?
[15:23] <kenvandine> i added tests
[15:26] <tedg> Cool
[15:27] <mhall119> nik90: ok, and where should that signal be? which component?
[15:29] <nik90> mhall119: in the timer page I guess, where if the signal is triggered it checks if the timer is running and if it does then do something special like sending a message etc
[15:30] <kenvandine> tedg, only think i don't like is it adds a click depends to the lib
[15:30] <tedg> kenvandine, Yeah, that should hopefully switch to a libclick depends here in a little while, which is better.
[15:30] <kenvandine> good
[15:31] <kenvandine> it's not enough to meet the need of url-dispatcher though
[15:31] <kenvandine> i don't think anyway... but it's a start :)
[15:33] <mhall119> bzoltan1: what version are we going to call the SDK for 14.04?
[15:34] <mhall119> nik90: I mean in the SDK APIs, where would you expect this to be documented?
[15:34] <nik90> mhall119: oh that..let me check
[15:36] <nik90> mhall119: I am guessing under platform services with a title "App Lifecycle"
[15:38] <plars> boiko: ok, I was able to reproduce it here at home too
[15:39] <mhall119> nik90: hmm, I don't know if there is such a component
[15:39] <mhall119> in QML anywya
[15:44] <cwayne> cyphermox: bah, after scrapping my MR cus of failing on maguro, now we go and drop maguro support :)
[15:44] <cyphermox> the what?
[15:44] <cyphermox> oh?
[15:44] <cyphermox> you mean on the customized image or on all images?
[15:45] <dholbach> cyphermox, https://lists.launchpad.net/ubuntu-phone/msg05889.html
[15:47] <cyphermox> dholbach: thanks, I hadn't looked yet
[15:48]  * cyphermox dives right into code, not email in the morning
[15:54] <kenvandine> tedg, any insight into why CI is failing for me?  It's failing to generate the source package, can't find click.pm, but i didn't make any packaging changes and click-dev is a build dep
[15:54] <kenvandine> i'd assume this isn't a new problem...
[15:54] <tedg> kenvandine, Hmm, no I thought we'd fixed it.
[15:54] <tedg> kenvandine, Basically the build system can't install new dh hooks.  They have to already be there.
[15:55] <tedg> kenvandine, So fginther needs to install the click-dev into the base image.
[15:55] <kenvandine> ah... fginther ^^
[15:55] <tedg> Basically it fails on the original dh_clean before it installs the deps.
[15:56] <kenvandine> maybe this is fallout from the transition they did recently
[15:56] <tedg> kenvandine, He'll probably want a link to your failure :-)
[15:56] <kenvandine> fginther, https://jenkins.qa.ubuntu.com/job/upstart-app-launch-trusty-amd64-ci/61/console
[16:01] <cwayne> dpm: any chance for the call for community help translating today?  the dialer-app, messaging-app and address-book-app are almost completely untranslated, seems bad :(
[16:01] <fginther> kenvandine, got it, I'll take a look after my meeting
[16:01] <kenvandine> fginther, thx
[16:04] <MacSlow> hm... since when does "adb poweroff" or "sudo shutdown -h now" no longer really shutdown a N10, but always cause it to reboot?
[16:04] <MacSlow> did the method for shutting a device down change recently?
[16:05] <oSoMoN> elopio, hey, I just filed bug #1268640 (related to some code you manually merged in lp:ubuntu-calendar-app apparently), would you mind confirming it?
[16:05] <ogra_> try: sudo poweroff -f
[16:05] <MacSlow> ogra_, good lord... ok I'll try :)
[16:05] <ogra_> (not sure if anything changed on N10, but that should alsways power off a device)
[16:05] <MacSlow> ogra_, but why would a simple command like poweroff need the force-option? :)
[16:05] <elopio> oSoMoN: can it wait ~1 hour?
[16:06] <oSoMoN> elopio, sure, no urgency
[16:06] <elopio> ok, I'll be back with you.
[16:06] <ogra_> MacSlow, it tells the kernel to power off immediately
[16:06] <ogra_> (no shutdown process)
[16:07] <MacSlow> ogra_, ok
[16:07] <MacSlow> ogra_, thx
[16:13] <sil2100> dpm: hello!
[16:14] <dpm> cwayne, sorry, on a call, I'll get to it tomorrow morning, this time for real!
[16:14] <dpm> hey sil2100
[16:14] <sil2100> dpm: https://code.launchpad.net/~sil2100/account-plugin-evernote/more_minor_fixes/+merge/201450 <- these are the final small fixes to packaging that are needed before we can release
[16:15] <sil2100> dpm: after those are in, I'll test and publish ;)
[16:17] <dpm> sil2100, nice and easy to review, makes sense, approved. Are you taking care of the merge? I see you already did the latest merge. Otherwise I can look at it after the call
[16:18] <boiko> plars: how did you reproduce it? just running phablet-test-run? or anything different I have to do?
[16:24] <sil2100> dpm: all is ok, thanks for approving!
[16:24] <dpm> super, thanks
[16:31] <elopio> oSoMoN: that's not my code, at least not while being awake.
[16:31] <elopio> I might be blamed because I touched everything to fix pep8.
[16:31] <elopio> but I've been working with the osk last week, so I can probably help you.
[16:32] <MyExHatesMeButMy> Hello there I am trying to use libstartup-notification in my cmakelists file and it can not find it did the name change in 14.04 or was it  replaced by something ?  thanks
[16:33] <MyExHatesMeButMy> I also can not get autopilot to be found by cmake :(
[16:33] <oSoMoN> elopio, well I don’t have time to work on this myself, was just pointing out the problem and hoping you could acknowledge it
[16:34] <elopio> oSoMoN: yes, I agree with everything you say on the bug. I confirmed it.
[16:34] <elopio> I'll try to make some time to take a deeper look, but this week it's going to be hard.
[16:34] <oSoMoN> elopio, cool, thanks, hopefully balloons can work on it
[16:35] <elopio> what I'll do this week is the text field emulator, hopefully with nice support using the OSK emulator.
[16:36] <elopio> so it will be a lot better for tests, they won't have to pay a lot of attention to the OSK.
[16:36]  * balloons wonders what is up
[16:37] <pitti> tvoss: do you happen to know a cmake+Qt project where a test uses signals/slots?
[16:37] <pitti> I'm currently fighting my way through those, trying to connect a sensor's readingChanged() to a slot in my test code
[16:37] <elopio> oh, this is so weird. This is my branch, merged as rev 168: https://code.launchpad.net/~elopio/ubuntu-calendar-app/autopilot-1.4/+merge/192631
[16:38] <tvoss> pitti, got a pastebin for me?
[16:38] <MyExHatesMeButMy> pitti,  I am not him but unity8 does that
[16:38] <elopio> it has none of that code related to maliit. I suppose they added some code and merged it all together.
[16:38] <tvoss> pitti, got a pastebin for me?
[16:38] <pitti> tvoss: if I just send this to a "normal" method, it never gets called; so apparently I need the Q_OBJECT+Q_SLOTS+moc stuff
[16:38] <pitti> tvoss: yes, sec
[16:38] <pitti> MyExHatesMeButMy: ah, good
[16:38] <tvoss> pitti, you need automoc enabled
[16:38] <pitti> $ cat obj/tests/test_sensor_api_automoc.cpp/* This file is autogenerated, do not edit*/
[16:38] <pitti> enum some_compilers { need_more_than_nothing };
[16:38] <tvoss> pitti, or you use QMetaObject::invoke
[16:38] <pitti> tvoss: that gets built
[16:39] <pitti> tvoss: http://paste.ubuntu.com/6745521/
[16:39] <pitti> tvoss: I just added the Q_OBJECT and Q_SLOTS bits; without those, it compiles but the slot never gets called
[16:40] <tvoss> yup, Q_OBJECT AND Q_SLOTS are needed unfortunately
[16:41] <MyExHatesMeButMy> pitti,  do you know what is up with autopilot not getting founf by cmake in my app ?  in cmakelists.txt ;  include(autopilot)        declare_autopilot_test(directions directions.shell ${CMAKE_SOURCE_DIR}/tests/autopilot/)
[16:41] <MyExHatesMeButMy> cmake says that it can not find autopilot :(
[16:42] <pitti> MyExHatesMeButMy: I'm afraid I've never seen autopilot being used like that
[16:42] <MyExHatesMeButMy> thanks for looking
[16:42] <pitti> MyExHatesMeButMy: sure you don't mean add_subdirectory() instead?
[16:42] <MyExHatesMeButMy> it is stange it use to work
[16:43] <MyExHatesMeButMy> pitti,  I have that else-where
[16:44] <MyExHatesMeButMy> do you think that I should use find_package ? maybe
[16:46] <pitti> MyExHatesMeButMy: no, no; autopilot isn't a cmake/C thing, it's just a command that your test suite calls
[16:46] <MyExHatesMeButMy> << python n00b and knows nothing about autopilot just trying to add some tests to my app
[16:47] <tvoss> fginther, can you help MyExHatesMeButMy
[16:47] <tvoss> fginther, he has got some issues with adding autopilot tests
[16:47]  * MyExHatesMeButMy goes back to the documentation but is lurking
[16:48] <fginther> tvoss, sure, I'm in the middle of a meething, but will get back to MyExHatesMeButMy soon
[16:48] <MyExHatesMeButMy> cool fginther  just ping me when you get some free time
[16:48] <MyExHatesMeButMy> I love this IRC channel !
[16:54] <tvoss> fginther, thank you, very much appreciated
[17:00] <fginther> MyExHatesMeButMy, I don't know much about cmake, so I might not be real useful but... autopilot is installed to /usr/bin/autopilot with the python-autopilot package. It's just an executable python script
[17:02] <savagejen> I don't suppose anyone has gotten ubuntu touch running on the chumby?
[17:03] <savagejen> may be incompatible, idk
[17:03] <MyExHatesMeButMy> thanks fginther  yeah I myself know nothing about autopilot and am just learning. But it seems like all apps have it and I guess that My app should also . Only thing is I wish it was c++ lol
[17:03] <bzoltan1> mhall119:  it could be 1.1 or 2.0 ... or we can stick to the 1.0 with updates
[17:07] <fginther> MyExHatesMeButMy, lp:autopilot-gtk executes autopilot tests from cmake, you might give that a look
[17:07] <MyExHatesMeButMy> thanks fginther
[17:26] <om26er> Will Sidestage now work on 7" tablets ? given we wont officially support the Nexus 10 ?
[17:27] <mhall119> bzoltan1: when will you decide on which of those it will be?
[17:27] <ogra_> om26er, the new N7 has a fullHD resolution
[17:27] <ogra_> so it should work there
[17:28] <om26er> ogra_, but I thought it was kept limited to certain screen size. Since lets say nexus 5 is a fullHD phone but clearly it wont have sidestage
[17:28] <ogra_> iirc it was bound to resolution
[17:29] <mhall119> I thought it was based on gridunit size
[17:29] <popey> \o/ consensus
[17:30] <mhall119> that is, how many gridunits wide the screen is, not how many pixels there are in a gridunit
[17:31] <MyExHatesMeButMy> why not just use QScreen ?
[17:31] <MyExHatesMeButMy> does not work on mir ?
[17:31] <MyExHatesMeButMy> or does qt-mir have its own class for screen info ?
[17:32] <MyExHatesMeButMy> http://qt-project.org/doc/qt-5.0/qtgui/qscreen.html#physicalSize-prop
[17:34] <MyExHatesMeButMy> anyone else in here using GPS in there app ?  It takes forever for it to work. meaning that I have to wait like 15 minutes for it to start working on the phone.
[17:35] <MyExHatesMeButMy> shuts on and off like crazy also
[17:39] <mhall119> bzoltan1: what is this? find /home/mhall/ -name *img
[17:40] <mhall119> it grinds HDD every time I launch the SDK
[17:40] <MyExHatesMeButMy> example of code that takes 15 minutes for the GPS to kick in  http://pastebin.com/RpCf2hxJ
[17:40] <MyExHatesMeButMy> mhall119,  that looks for anything with the name *.img
[17:40] <mhall119> MyExHatesMeButMy: I know that, I just don't know *why*
[17:40] <MyExHatesMeButMy> maybe find /home/mhall/ -name "*img"
[17:40] <mhall119> and since I have a lot of files under ~/, it takes a long time
[17:40] <sergiusens> popey, https://myapps.developer.ubuntu.com/dev/click-apps/118/
[17:41] <fginther> kenvandine, the missing cli-common-dev issue should be resolved. I've rebuilt https://code.launchpad.net/~ken-vandine/upstart-app-launch/appid_from_triplet/+merge/201433
[17:41] <MyExHatesMeButMy> mhall119,  what is it looking for a emulator ?
[17:41] <popey> sergiusens: ack
[17:42] <kenvandine> fginther, thx
[17:43] <MyExHatesMeButMy> mhall119,  I would figure that Qdir and Qfile would take care of all of that and would not run external command
[17:43] <popey> sergiusens: approved
[17:43] <mhall119> MyExHatesMeButMy: I have no idea, I just want it to stop :)
[17:43] <MyExHatesMeButMy> but who knows maybe that would slower but I doubt it.
[17:43] <MyExHatesMeButMy> bzoltan1,  what is it for ?
[17:44] <MyExHatesMeButMy> bzoltan1,  and why not QDir and QFile to find it ?
[18:03] <cwayne> hey mardy, just saw ssweeny's MR finally went through!  Should we setup a landing ask, or should we wait til all 3 click-related MR's go through?
[18:07] <mhall119> pmcgowan: https://plus.google.com/u/0/106250186908628485422/posts/WejtdUeFsBC
[18:13] <pmcgowan> mhall119, great, I expected someone would
[18:14] <mhall119> pmcgowan: it seems (reading older posts in that community) that they're stuck needing 4.4 support too, what's the status of that?
[18:15] <pmcgowan> mhall119, very soon, working in the lab kind of thing
[18:16]  * annerajb anner can't wait for 4.4 to start on LG G2 Series
[18:21] <mhall119> pmcgowan: is there anything we can release to people like them who are trying to port to a device that needs it?
[18:23] <pmcgowan> mhall119, rsalveti would have the latest, I think its close
[18:24] <rsalveti> mhall119: pmcgowan: in progress, hope to be done by the end of this week
[18:26] <mhall119> rsalveti: can you let that G+ community (linked above) know when it's available for them to try with their port?
[18:26] <rsalveti> mhall119: sure, everybody will know :-)
[18:39] <boiko> plars: so, any suggestions on how to reproduce the dialer-app's crash on smoke tests?
[18:42] <plars> boiko: I ran the provision script like we run in the lab, which really just combines all the steps you need like phablet-flash, the network setup, etc
[18:42] <plars> boiko: then I just ran the jenkins.sh script to reboot the device and run the dialer-app tests
[18:43] <boiko> plars: where can I get this jenkins.sh script?
[18:43] <plars> boiko: are you unlocking by hand and running autopilot directly I guess?
[18:43] <plars> boiko: lp:ubuntu-test-cases/touch
[18:43] <boiko> plars: yep, launching the tests using phablet-test-run on desktop
[18:43] <plars> boiko: let me try it like that also
[18:44] <boiko> plars: thanks for the link, I will check it out
[18:49] <plars> boiko: ok, I got it by running phablet-test-run dialer_app also
[18:49] <plars> hmm
[18:50] <plars> boiko: dialer-app version I have is 0.1+14.04.20131209-0ubuntu1 - same as you?
[18:51] <boiko> plars: same version
[18:52] <boiko> plars: what output you get when running the tests?
[18:52] <plars> boiko: none, just that it ran 6 tests in 72.400s and OK
[18:52] <plars> boiko: I'm didn't run verbose there
[18:53] <plars> boiko: in the lab, you can see all the output clicking on the tests - the tests all pass though
[18:53] <plars> boiko: so perhaps it's just crashing at the end?
[18:53] <boiko> plars: no idea :/
[18:54] <plars> boiko: it does just end up at a black screen at the end - or is that just the other issue you described?
[18:54] <boiko> plars: that might be the other issue I described
[18:54] <boiko> plars: in the output it says it is due to a known Mir crash
[18:57] <plars> boiko: I'm watching the directory a bit more closely this time
[18:57] <plars> for the crash file
[18:58] <plars> boiko: does seem to show up right at the end
[19:04] <plars> boiko: with -v, and watching for the file to show up, it looks like it happens toward the end of the test_incoming test, around the time it hangs up. I see the incoming call, and hear the ringtone start to play before it hits hangup and that's about the time I see the crash file show up
[19:12] <boiko> plars: so, the screen turning black happens right after the snap decision is dismissed (when clicking accept), and the focus get back to the app
[19:33] <plars> boiko: any chance that's all related to the crash we're getting?
[19:33] <plars> boiko: the timing of it is certainly in line
[19:35] <boiko> plars: maybe, but I'm not totally sure yet
[19:35] <boiko> plars: just testing something with real calls before switching back to debugging this
[20:23] <lool> slangasek, sergiusens, beuno, popey: I changed click-sync.py from lp:click-sync into: get-all-clicks.py as: http://paste.ubuntu.com/6746725/ real quick
[20:24] <slangasek> lool: ObNamingBikeshed: clearly this should be named get-ALL-the-clicks.py
[20:24] <beuno> ack
[20:25] <sergiusens> lol
[20:26] <beuno> get-_ALL_-the-clicks.py please
[20:26] <popey> http://paste.ubuntu.com/6746744/
[20:26] <popey> 401 here
[20:26] <sergiusens> popey, you need oauth credentials ;-)
[20:27] <popey> bah
[20:27]  * popey files a bug against lool
[20:28] <popey> how do I get that?
[20:28] <nessita> hello everyone
[20:28] <beuno> popey, lool, nessita here can help you get those credentials
[20:29] <beuno> (if you give her context :))
[20:29] <nessita> may I please have some context?
[20:29] <lool> sergiusens: the auth credentials didn't work  :-(
[20:29] <lool> I get a 401 too
[20:30] <lool> nessita: hey, trying to get some credentials to pull all free click apps from the app store with a local client
[20:30] <lool> nessita: apparently we have one such setup already with a format like http://paste.ubuntu.com/6746701/
[20:30] <nessita> lool: are you hitting staging or prod?
[20:30] <sergiusens> lool, hmm, well you just need to generate some; let me try again; they may have accidentally expired
[20:31] <nessita> lool, sergiusens: that dict of credentials has empty strings, which are not valid (I guess you already found out that much :-))
[20:31] <sergiusens> nessita, he wants those fields filled with your help ;-)
[20:31] <lool> sergiusens: will generate some
[20:31] <nessita> lool: you need to grab credentials from the phone itself, or from an desktop box?
[20:31] <lool> nessita: desktop
[20:32] <lool> but I think sergiusens has pointed out a script that might help
[20:32] <lool> let me try that
[20:32] <nessita> lool: staging or prod?
[20:32] <nessita> so I provide the proper command
[20:32] <sergiusens> prod
[20:33] <nessita> ok, building the curl query
[20:34] <lool> sergiusens: bah trying to install the click-toolbelt thing I ended up with errors in easyinstall of "stevedore"
[20:35] <sergiusens> lool, just wait for the magic curl line
[20:36] <sergiusens> oauth is black magic to me
[20:37] <nessita1> hum, network hiccup
[20:37] <nessita1> lool: replace email and password with values from an existing account https://pastebin.canonical.com/102880/
[20:37] <lool> nessita1: thanks!
[20:38] <nessita1> lool: hum, let me confirm the url
[20:38] <nessita1> I tried it IRL and got an error
[20:38] <sergiusens> it says staging
[20:38] <nessita1> sergiusens: remove it! :-D
[20:38] <lool> of course my password has a single quote
[20:40] <lool>           <p>There's no page with this address in the Ubuntu One service. Check that you entered the address correctly and try again.</p>
[20:42] <nessita1> lool: yeah, missed a /oauth suffix. New command, IRL tested: https://pastebin.canonical.com/102882/
[20:44] <nessita> lool: did it work?
[20:44] <lool> nessita: looking at your new URL
[20:45] <nessita> if you are considering using your canonical account it will fail requiring 2fa, let me know and you can send the next otp via the query as well
[20:45] <lool>     "message": "2-factor authentication required.",
[20:45] <lool>     "code": "TWOFACTOR_REQUIRED",
[20:45] <lool> nessita: Yup, OTP would be nice  :-)
[20:46] <nessita> lool: add "otp": "123456" to the json encoded dict sent as data in the POST
[20:47] <nessita> of course 123456 has to be the next valid otp for you
[20:47] <lool> worked, thanks
[20:47] <nessita> anytime
[20:48] <nessita> lool: is this something you need to automate or is this procedure enough for your needs?
[20:50] <lool> nessita: it's fine for now; thanks!
[20:51] <lool> slangasek: so with https://pastebin.canonical.com/102882/ + "otp": "123456" in the request, I get credentials that I filter down to these http://paste.ubuntu.com/6746701/
[20:51] <lool> slangasek: then this get-all-clicks.py script http://paste.ubuntu.com/6746884/ works with: mkdir d && ./get-all-clicks.py --credentials-file ~/.click-credentials d
[20:52] <lool> feel free to rename it to get-\*-clicks.py
[20:52] <slangasek> lool: no way to get these without having to pass passwords on the commandline?
[20:53] <popey> now i get TypeError: __init__() got an unexpected keyword argument 'openid'
[20:53] <slangasek> lool: seems to not be working for me, anyway
[20:53]  * lool ran this on his laptop in a "sh" instance to avoid shell history
[20:54] <lool> popey: you have to filter down to the list in http://paste.ubuntu.com/6746701/
[20:54] <lool> slangasek: which part doesn't work for you?
[20:54] <slangasek> lool:     "message": "Provided email/password is not correct.",
[20:54] <slangasek>     "code": "INVALID_CREDENTIALS",
[20:55] <lool> slangasek: that's with your login.u.c credentials?
[20:55] <slangasek> yes
[20:55] <lool> I had to escape my password as it had special chars
[20:55] <popey> ah, thanks
[20:55] <popey> hope we don't kill the store, all beating it up like this ☻
[20:55] <lool> slangasek: BTW there is no actual <> around the email or password
[20:55] <lool> popey: if we do it's a good test
[20:56] <slangasek> lool: yeah, I didn't put any there
[20:56] <popey> alan@deep-thought:~/all_the_clicks$ ls -l *.click | wc -l
[20:56] <popey> 26
[20:56] <popey> working here
[20:56] <beuno> popey, lool, I welcome the scalability testing  ;)
[20:56] <lool> it's about 54M of downlaod
[20:56] <popey> 50M of that is one click
[20:56] <popey> the bitcoin one
[20:57] <lool> popey: ah note that I dont see UK-only apps
[20:57] <lool> I do see the FR-only apps though
[20:57] <lool> :-P
[20:57] <lool> beuno pointed out that this is geofiltered
[20:57] <popey> be interested to know how many we each get
[20:58] <lool> 97
[20:58]  * lool quickly uploads 10 webapps
[20:58] <lool> for 10 French websites
[20:58]  * popey uploads webapps depicting french presidents in compromising situations
[20:59] <lool> slangasek: I guessed you used an actual 2fa OTP code?
[20:59] <slangasek> yes
[20:59] <lool> slangasek: no idea what else could be in play; perhaps nessita can help
[20:59] <popey> dodgy characters in password?
[20:59] <slangasek> no comment
[20:59] <slangasek> :P
[21:00] <slangasek> (there are no escaping issues in my command ;)
[21:02]  * lool goes off for dinner
[21:03] <slangasek> lool, popey: so instead of having all of us fight with credentials, does one of you want to post the batch where I can grab them?
[21:04] <popey> slangasek: sure
[21:06]  * lool uploads
[21:07] <popey> http://people.canonical.com/~alan/click/
[21:07] <popey> 100 total
[21:09] <popey> done
[21:09] <slangasek> popey: ta
[21:09] <popey> np
[21:10] <lool> bah
[21:10] <lool> my upload bandwitdh sucks!  :-)
[21:15] <slangasek> popey: 100 total? http://people.canonical.com/~alan/click/click_list is 98 lines long
[21:16] <popey> my bad
[21:16] <popey> i was doing ls ☻
[21:16] <popey> didn't realise there were not just click files in there
[21:16] <popey> alan@deep-thought:~/all_the_clicks$ ls -l *.click | wc -l
[21:16] <popey> 98
[21:31] <sergiusens> lool, add a space in front of the command and it won't go into history with bash at least
[21:34] <barry> where's the right place to get qt5.2, e.g. as a build-dep for ubuntu-ui-toolkit?
[21:37] <sergiusens> barry, probably one of the qt5 edgers ppas
[21:38] <sergiusens> I think Mirv sent out and email wrt
[21:38] <barry> sergiusens: cool, thanks.  i'll check the archives
[21:44] <genii> barry: Apparently https://launchpad.net/~ubuntu-sdk-team/+archive/ppa but it looks like  "ubuntu-ui-toolkit 3 days ago Failed to build: amd64 armhf i386" might be problemmatic
[21:45] <barry> genii: yeah, that's the one i'm trying to build locally.  looking
[22:12] <Aaron1011> Hello
[22:12] <Aaron1011> I just saw that development on Ubuntu Touch for tablets is going to be focused only on the 2013 Nexus 7
[22:13] <Aaron1011> About how long will it be until it's possible to get a build of Ubuntu Touch for it?
[22:20] <sergiusens> slangasek, popey lool there are no armhf packages here: http://people.canonical.com/~alan/click/click_list
[22:21] <sergiusens> it's not 'all clicks' per se :-)
[22:22] <sergiusens> the query itself doesn't return them either
[22:22] <daker> sergiusens: yep i do have 9apps, i only see 8 of them
[22:23] <slangasek> sergiusens: well, er, that's decidedly unhelpful for what I'm trying to do then
[22:23] <sergiusens> slangasek, I imagined it was about that; reason for checking
[22:25] <sergiusens> beuno, is there a query that we can ru that would return the list of arch specific packages?
[22:25] <beuno> sergiusens, you can filter by arch, yes
[22:25] <beuno> let me find the query parameter...
[22:26] <sergiusens> or a !all :-)
[22:29] <beuno> maybe JamesTait is around?
[22:33] <popey> slangasek: any particular package you're expecting to see?
[22:33] <slangasek> popey: no, I don't know anything about what is or isn't arch-dependent in the app store
[22:34] <popey> oh okay
[22:34] <popey> bitcoin is an arch dependent one
[22:34] <popey> and its not in https://search.apps.ubuntu.com/api/v1/search?q=
[22:34] <slangasek> but it's the arch-dep ones that I need to look at :)
[22:36] <beuno> sergiusens, https://search.apps.staging.ubuntu.com/api/v1/search?q=architecture:armhf
[22:36] <beuno> https://search.apps.staging.ubuntu.com/api/v1/search?q=architecture:i386
[22:36] <beuno> and https://search.apps.staging.ubuntu.com/api/v1/search?q=architecture:amd64
[22:36] <beuno> would be !all, I think
[22:37] <sergiusens> ty
[22:37] <popey> slangasek: ok, modded script, am getting all the armhf ones too, will upload those to the same place
[22:37] <slangasek> popey: cheers :)
[22:38] <heathkh> On the GalaxyNexus running Ubuntu Touch, the camera app can only take pictures (not video)... Is this a UI issue or is video recording not supported by the underlying platform / libraries?
[22:51] <popey> 156
[22:51] <popey> thats more like it
[22:54] <sergiusens> popey, \o/
[22:54] <sergiusens> popey, for the sake of it; have you seen any amd64 or i386 packages?
[22:55] <popey> sergiusens: not tried.. lemme see
[22:56] <popey> slangasek: lots in http://people.canonical.com/~alan/click/ now
[22:56] <sergiusens> popey, just in case you haven't noticed; make sure the staging part is removed :-)
[22:57] <popey> i did
[23:00] <sergiusens> popey, no i386 or amd64 :-)
[23:00] <sergiusens> not many armhf either
[23:00] <sergiusens> http://paste.ubuntu.com/6747470/
[23:00] <sergiusens> slangasek, ^^
[23:00] <sergiusens> some seem improperly added as such
[23:01] <popey> yeah, none
[23:02] <sergiusens> lool, I'd say it's safe to call for a recompile for framework-14.04
[23:02] <sergiusens> or whatever it's going to be called
[23:07] <slangasek> popey: thanks, snarfing
[23:49] <annerajb> rsalveti, any luck with uploading cm-11.0 hardware libs?
[23:54] <annerajb_> weird