[05:19] <guest42315> 𝓐𝓱, 𝔀𝓱𝓪𝓽 𝓪 𝓯𝓲𝓷𝓮 𝓭𝓪𝔂 𝓯𝓸𝓻 𝓢𝓬𝓲𝓮𝓷𝓬𝓮!
[06:17] <guest42315> is OTA6 landing today?
[08:19] <mzanetti> guest42315, no
[09:01] <guest42315> mzanetti, 𝓸𝓱 𝔀𝓮𝓵𝓵, 𝓶𝓪𝔂𝓫𝓮 𝓷𝓮𝔁𝓽 𝔀𝓮𝓮𝓴
[09:01] <mzanetti> didn't even know one could change font in here
[09:01] <guest42315> mzanetti, http://antglove.com/erger/
[09:20]  * guest42315 𝖎 𝖓𝖊𝖊𝖉 𝖇𝖑𝖔𝖔𝖉!
[10:05] <cimi> tsdgeos, ping
[10:06] <tsdgeos> cimi: hi
[10:06] <cimi> tsdgeos, just realised we might have a bug in card anyway, if you set cardData["background"]["type"] to "color" you still have a gradient
[10:06] <tsdgeos> cimi: in the current card?
[10:06] <cimi> tsdgeos, yup
[10:09] <tsdgeos> give me a sec i destroyed my dev env
[10:14] <tsdgeos> cimi: even if there's a bug doesn't mean you should not fix the other bug :D
[10:15] <cimi> tsdgeos, yeah, just saying
[10:15] <tsdgeos> i may have broken that
[10:15] <tsdgeos> let me log
[10:15] <cimi> tsdgeos, because I changed my code a little in the branch, and something is still wrong
[10:15] <cimi> tsdgeos, backgroundMode: cardData && typeof cardData["background"] [10:17] <tsdgeos> or was broken for a long time :D
[10:17] <tsdgeos> since last year at least
[10:19] <cimi> yeah
[10:26] <tsdgeos> cimi: does that work?
[10:31] <cimi> nope
[10:35] <cimi> tsdgeos, I tried putting console.log("card type", cardData["background"]["type"]); \n\ inside the getColor function of that card, and always says cardData["background"] is undefined
[10:35] <cimi> tsdgeos, I am wondering if it ever worked
[10:35] <tsdgeos> well you get gradient or not
[10:35] <tsdgeos> do you?
[10:37] <cimi> tsdgeos, but is always the same color
[10:37] <tsdgeos> wht do you mean it's always the same color?
[10:37] <cimi> tsdgeos, and to be honest, if cardData changes the color won't change
[10:37] <cimi> tsdgeos, the function getColor(0) (1) is not a binding, so is only evaluated at creation
[10:38] <tsdgeos> correct
[10:38] <tsdgeos> that's enough
[10:38] <cimi> tsdgeos, I am not sure when cardData is set
[10:38] <cimi> tsdgeos, is it set before the creation?
[10:39] <tsdgeos> i don't know
[10:39] <cimi> nevermind let me see
[10:40] <tsdgeos> cimi: so you're using the tests?
[10:40] <tsdgeos> because in the tests the color is now driven by cardData but by the template
[10:41] <cimi> tsdgeos, I just realised the test use background "elements"
[10:41] <cimi> let me see
[10:41] <cimi> 5 mins
[10:46] <cimi> tsdgeos, I pushed, test pass now
[10:47] <tsdgeos> tests were passing before too, does it actually work?
[10:49] <tsdgeos> seems it does :)
[10:49] <ltinkl> tsdgeos, hiho, could you please review https://code.launchpad.net/~lukas-kde/unity8/volumeSliderNotification/+merge/268518 for me? should be straightforward
[10:50] <ltinkl> tsdgeos, there's a bug report attached to it
[10:50] <ltinkl> tsdgeos, for more explanation
[10:50] <tsdgeos> sure
[11:25] <tsdgeos> ltinkl: commented on it
[11:25] <ltinkl> tsdgeos, ty
[13:22] <mterry> mzanetti, We have an EdgeDraggable (or something) class that I remember you(?) mentioning doesn't work with mice?
[13:23] <mzanetti> mterry, DDA
[13:23] <mzanetti> mterry, well, all of them
[13:23] <mzanetti> mterry, ah nice. You looking into the emulator issue?
[13:23] <mterry> mzanetti, yeah kgunn mentioned it.  I assume it's not an easy fix?
[13:24] <mterry> mzanetti, (other solution is to disable demo in emulator if we can detect it...)
[13:24] <mterry> But that's gross
[13:24] <mterry> I think we disabled the edge demo in Desktop mode
[13:24] <mterry> For that same reason
[13:24] <mzanetti> yeah... would prolly go for that, given the timeline
[13:24] <mzanetti> yeah
[13:24] <mzanetti> but.
[13:24] <mzanetti> will still be a problem with bringing in the launcher
[13:24] <mzanetti> or the right edge
[13:25] <mzanetti> we might need to run unity8 with -mousetouch in the emulator
[13:25] <dandrader> greyback, mzanetti, about the mousePointer branches: we need a lot of its code in any case as it has the code that makes window borders change the cursor shape and adds the needed API to enable QML to select cursor shapes not available when using Qt's API
[13:25] <mzanetti> dandrader, yep, saw the comment on the MP
[13:25] <mterry> mzanetti, how do we handle launcher/right edge on Desktop?
[13:25] <dandrader> greyback, mzanetti, is the guy making the mir cursor work also doing qtmir & unity8 stuff?
[13:25] <mzanetti> mterry, launcher can be revealed with mouse hovering... I just remember
[13:26] <mzanetti> mterry, the phone spread is not there on desktop, there's the desktop stage
[13:26] <mzanetti> mterry, but I assume we want the phoneStage on the emulator
[13:26] <greyback> dandrader: I don't have good answers for that yet, we need to figure that out next week
[13:26] <mterry> mzanetti, honestly, -mousetouch sounds like a good solution.  The emulator is emulating the phone, were things are touch events
[13:26] <mzanetti> mterry, proper fix would really be to make the emulator convert mouse to touch
[13:26] <greyback> dandrader: you're right, lots of the code there is useful still
[13:26] <mzanetti> mterry, yeah, -mousetouch should do
[13:28] <mterry> mzanetti, so I guess if we can detect it, our upstart job should pass that
[13:28] <mzanetti> mterry, yes
[13:28] <mzanetti> mterry, oh, also:
[13:28] <mterry> rsalveti, do you know how an upstart job (or anything) might detect it's running in an emulator?
[13:28] <mterry> rsalveti, specifically, our Touch emulator
[13:28] <mterry> Not just any emulator  :)
[13:28] <mzanetti> mterry, I heard that it starts in windowed mode. we probably want to override usage-mode with Staged
[13:29] <mzanetti> mterry, just like we do windowed override for desktop
[13:29] <mzanetti> mterry, as we can't know how many mice keyboards people have plugged, we always want it in staged
[13:29] <mzanetti> I guess
[13:29] <mzanetti> for now at least that would do
[13:29] <mzanetti> until we ship pocket desktop
[13:30] <mterry> Hrm.  That's not a command line option, so that would need detection in C/qml
[13:37] <mterry> It looks like maybe the emulator sets ANDROID_PRODUCT_OUT
[13:38] <scriptmonkey00> wondering if anyone can give me some advice on the best way to turn a shell script into an icon on my Unity desktop...
[13:38] <scriptmonkey00> as-is when I doubleclick on it, it just opens it to edit
[13:39] <mzanetti> mterry, getprop should hel
[13:39] <mzanetti> p
[13:41] <mterry> mzanetti, ah fair
[13:46] <mterry> kgunn, I just went through the emulator with a mouse... and it seemed to work?
[13:46] <mterry> kgunn, on vivid
[13:46] <mterry> +overlay
[13:47] <kgunn> mterry: no change ?
[13:47] <kgunn> so vivid+o+silo9
[13:47] <kgunn> ?
[13:47] <mterry> kgunn, oh didn't grab silo9...  does that make it worse?
[13:48] <kgunn> mterry: that's interesting, well, there is a mir fix in there for "screen config reporting"
[13:48] <kgunn> and there's some uitk fix in there
[13:48] <kgunn> (for shader stuff i think)
[13:49] <mterry> kgunn, will try with 9.  where is the report of it not working?
[13:50] <kgunn> mterry: davmor2 irc
[13:52] <kgunn> greyback: so the qtmir proposed fix, check for children....2 ques, are tp's always and forever children ? (wondering if there is some odd case where we did a custom thing and they are not)
[13:52] <kgunn> second, do we not have children in cases other than tp ?
[13:52] <kgunn> it's qwidget call basically right?
[13:53] <kgunn> or sorry qabstractitemmodel
[13:53] <greyback> kgunn: TPs are always children to a session. TP allow data to be shared from one thing to another, so TP need to have a "thing" to share data with
[13:53] <greyback> kgunn: atm, the only children are TPs
[13:55] <kgunn> greyback: browser tabs ?
[13:56] <greyback> kgunn: nope
[13:58] <kgunn> greyback: do you have silo16 on? try browser tabs....specifically open 2, then try to get it into the mode where they are both shown (as in you can choose from what you see)
[13:58] <kgunn> if that makes sense
[13:58] <kgunn> having trouble here
[13:58] <kgunn> on arale
[13:58] <mterry> oh I was testing old emulator image
[13:58] <kgunn> mterry: yeah, wonder if mir might have "regressed" something
[13:58] <kgunn> ?
[13:58] <kgunn> like you were on an old mir
[13:59] <mterry> kgunn, old ubuntu-touch image/channel
[13:59] <kgunn> hmmm...but if you loaded silo9 you would get the new one
[13:59] <mterry> kgunn, testing rc-proposed now
[13:59] <greyback> kgunn: working for me, the bottom swipe up shows me the 2 tabs, and I can select as usual
[14:00] <kgunn> greyback: so, launched clock...tp comes up, don't select, put clock to background, for like a long time (my phone might have even gone into suspend)
[14:00] <kgunn> wake, bring clock fwd
[14:01] <kgunn> select accept
[14:01] <kgunn> clock app goes blank(white) and eventually crashes
[14:01] <kgunn> damn have a 1on1...will check for crash log tho
[14:02] <greyback> trying
[14:14] <greyback> kgunn: ok, similar steps, clock did vanish when I tapped on it. Logs indicate it crashed.
[14:16] <greyback> dunno why yet. Would be flabbergasted if due to that patch, but let's see if I can repro without
[14:19] <mterry> kgunn, ok can reproduce with latest everything + silo9
[14:38] <kgunn> greyback: are you testing on mako or arale ?
[14:39] <kgunn> curious
[14:39] <greyback> kgunn: arale & krillin
[14:39] <kgunn> greyback: are you really not having any trouble with the browser tabs ?
[14:39] <kgunn> bottom swipe
[14:40] <greyback> kgunn: nope, it's fine
[14:40] <kgunn> greyback: what image are you on ?
[14:40] <kgunn> i'm on 95
[14:40] <rsalveti> mterry: what do you want to check?
[14:40] <greyback> kgunn: 95
[14:41] <rsalveti> if you're running on the emulator?
[14:41] <mterry> rsalveti, I think I got it...  getprop ro.hardware == goldfish?
[14:41] <mterry> mzanetti, -mousetouch doesn't fix the issue for me...
[14:43] <mzanetti> ouch
[14:43] <rsalveti> mterry: yes, you can check if the hardware name starts with goldfish, or by checking if you have 'qemu=1' at /proc/cmdline
[14:43] <rsalveti> that's how we check for the emulator in a few scripts we have
[14:47] <mterry> rsalveti, starts with goldfish, not equals?
[14:48] <greyback> kgunn: have reproduced that trust-helper+clock-app crash on vanilla image
[14:49] <rsalveti> mterry: do you have the emulator running? I need to check if the x86 version has _x86 appended to it
[14:49] <rsalveti> creating the image here to check
[14:49] <rsalveti> if you have it around, just call getprop and paste me the output
[14:49] <mterry> rsalveti, it doesn't
[14:49] <mterry> rsalveti, ok, will pastebin
[14:50] <mzanetti> mterry, so if -mousetouch isn't doing, what's the issue then?
[14:50] <mterry> rsalveti, paste.ubuntu.com/12135961
[14:50] <mterry> mzanetti, not sure...  so it's not even letting me drag from left in tutorial mode
[14:51] <mterry> mzanetti, which is even worse than the DDA issue we had when we disabled parts of the greeter on the desktop
[14:51] <rsalveti> mterry: yeah, hardware will be goldfish for both
[14:51] <mzanetti> odd
[14:51] <rsalveti> [ro.build.product]: [generic_x86]
[14:51] <mterry> mzanetti, in that situation, we could drag from left, but not do the more fancy right-edge tutorial
[14:51] <kgunn> greyback: this is what i'm seeing
[14:51] <rsalveti> that would be the one that has _x86, which is usually the one we use when checking for different devices
[14:51] <kgunn> http://www.youtube.com/watch?v=fL3Z8oCtKkY
[14:51] <mterry> mzanetti, I also can't swipe greeter away if I force it to be in phone usagescenario
[14:51] <rsalveti> mterry: so ro.hardware should be all good
[14:51] <mzanetti> but dragging from left (launcher at least) is a touch-only DDA  too
[14:52] <mterry> mzanetti, is it?  maybe it didn't used to be?  but ok
[14:52] <rsalveti> and in case you don't want to use getprop for that, you can just check for 'qemu=1' at /proc/cmdline
[14:52] <mterry> rsalveti, ok thanks
[14:52] <greyback> kgunn: weird
[14:53] <mterry> mzanetti, so we can check for emulator using goldfish.  If we pass -devicename=goldfish or whatever, we can have a different DeviceConfiguration for it or do whatever we want in qml
[14:53] <mterry> mzanetti, so I'll try skipping the whole tutorial instead of just part of it
[14:53] <mterry> mzanetti, but i'm not sure we want it to be in phone usageScenario since we can't swipe greeter away
[14:54] <mzanetti> but that's the whole point of it... emulating the phone
[14:54] <greyback> and that used to work
[14:55] <kgunn> but it's more phone like than being absolutely useless atm :)
[14:55] <mzanetti> kgunn, what's that browser thing?
[14:56] <mterry> mzanetti, I'm not sure why -mousetouch isn't working
[14:56] <mterry> mzanetti, presumably that would fix this
[14:56] <mzanetti> yeah... we should try to find that...
[14:57] <kgunn> mzanetti: see video link ^^^
[14:57] <mzanetti> yeah, I watched the video, and can see the tabs are not animating smooth, but what's the context?
[14:59] <mzanetti> cannot repro the browser thing btw
[14:59] <kgunn> mzanetti: iiuc, the tab should stall on a short swipe, showing all tabs open
[14:59] <kgunn> to choose
[14:59] <kgunn> but good news
[14:59] <kgunn> virgin image does the same thing for me
[14:59] <kgunn> and it might be the user
[14:59] <kgunn> or maybe something landed overnight
[14:59] <mzanetti> yep. that works here, both with virgin o krillin and with silo 16 on mako
[15:00] <kgunn> i flashed rc-prposed....wonder, that is likely not the same as our ota6 phone image
[15:00] <kgunn> since they took a snapshot of ppa
[15:01] <kgunn> hmmm anyhoo...maybe it's just my thumb it doesn't like
[15:05] <tsdgeos> cimi: another regression in our shapes13 branch
[15:06] <mterry> mzanetti, kgunn: ok, have branch to skip tutorial.  will file MP now
[15:06] <mzanetti> mterry, how about the right edge then?
[15:08] <mterry> mzanetti, I haven't fully looked into why drags aren't working
[15:08] <mterry> mzanetti, https://code.launchpad.net/~mterry/unity8/fix-emulator-tutorial/+merge/268607
[15:08] <mterry> mzanetti, that is just a very dumb "skip tutorial entirely in desktop mode" MP
[15:09] <mterry> mzanetti, if we fix drags in emulator and can put it back in phone mode, presumably the tutorial will also work again
[15:09] <mzanetti> yeah, very likely
[15:10] <mterry> oh gosh, I don't know if tests pass with that branch, let me check
[15:10] <mterry> mzanetti, presumably the desktop tutorial was also broken then without this MP
[15:11] <mterry> mzanetti, since it seems we grew the usage of the problematic drag code
[15:11] <mzanetti> at least I didn't hear any complaints
[15:11] <mzanetti> but might well be, yes
[15:12] <kgunn> mzanetti: bfiller says "like silo 17 is building for the fix to qtmir for the ghosting apps that we think is causing the content-hub/MMS crash of https://launchpad.net/bugs/1486890"
[15:12] <mzanetti> kgunn, yep, I'm building that one
[15:12] <kgunn> k
[15:12] <kgunn> didn't know if he jwent and did that himself
[15:13] <mzanetti> kgunn, I've tried reproducing their isse, I couldn't see the crash they're talking about, but the ghost surfaces are definitely involved there
[15:17] <kgunn> mzanetti: are you and gerry ready to say +1 on silo 16 ?
[15:18] <kgunn> i'm seeing 1 or 2 issues, but i think they're rotation related...unrelated to tp change
[15:18] <greyback> kgunn: I'm happy to +1 it
[15:22] <kgunn> wtf.... ubuntu-touch/rc-proposed/ubuntu-developer doesn't have shell rotation ?
[15:22] <tsdgeos> mterry: do we realy want to turn on the screen when getting notifications?
[15:22] <kgunn> but ubuntu-touch/rc-proposed/ubuntu does...
[15:23] <greyback> I've no idea what ubuntu-touch/rc-proposed/ubuntu-developer is, but it seems ancient/broken
[15:23] <mterry> tsdgeos, I'm not 100% sure, but couldn't think of why we'd show something we don't want the user to see
[15:23] <kgunn> greyback: we advertise it on ubuntu public wiki as "good for app devs" cause it has all the extra stuffs
[15:23] <tsdgeos> mterry: because he's not looking?
[15:24] <mterry> tsdgeos, ?
[15:24] <tsdgeos> mterry: the screen is off, means that most probbly the person is not looking at the phone
[15:24] <greyback> kgunn: really? Ok, we'd better get someone to look at it
[15:24] <tsdgeos> how often are you looking at your phone when the screen is turned off?
[15:25] <mterry> tsdgeos, ... I mean the point is that your phone beeps or vibrates and the screen comes on.  Like you get an SMS or something
[15:25] <mzanetti> kgunn, yes, +1 here too
[15:25] <mterry> tsdgeos, like how all phones work  :)
[15:25] <mterry> tsdgeos, we do this today
[15:25] <tsdgeos> mterry: really?
[15:25] <mterry> tsdgeos, that branch is about consolidating code branches
[15:25] <tsdgeos> the phone i use doesn't do that
[15:25] <tsdgeos> one for phone calls
[15:26] <tsdgeos> the rest just beeps and that's it
[15:26] <mterry> tsdgeos, for example, we don't do it on telegram message right now (or any push messages) but we should treat them the same as SMS
[15:26] <tsdgeos> s/one/only
[15:26] <mterry> tsdgeos, well android and ios do it.  We do it for SMS and calls
[15:26] <mzanetti> tsdgeos, the phone you use has a notification LED that makes everyone blind when looking at it
[15:26] <tsdgeos> mterry: that was my other question, you say "unify"
[15:26] <tsdgeos> but there's no more branches?
[15:27] <tsdgeos> i thought unification meant there would be code removed from somewhere else?
[15:27] <mterry> tsdgeos, once we land this we could go and add branches to the places that currently turn the screen off and remove them
[15:27] <kgunn> greyback: one thing, did you see why clock crashed ?
[15:27] <mterry> tsdgeos, but it's harmless to do it twice in the meantime
[15:27] <mterry> tsdgeos, I suppose I could make the branches now
[15:27] <tsdgeos> mterry: ok, you meant "turn the screen on and remove them" and not off, right?
[15:27] <mterry> tsdgeos, I just wanted to get opinions on this first
[15:27] <mterry> tsdgeos, right...  not on-then-off.  I meant turn the screen on and then go and remove the duplicate lines of code
[15:28] <tsdgeos> ok
[15:28] <greyback> kgunn: something weird going on. Here's my stacktrace: https://errors.ubuntu.com/oops/7ec19558-4730-11e5-a7eb-fa163e707a72 - crashed somewhere in dbus of all places
[15:28] <greyback> kgunn: hoping not clash between libdbus-cpp & qtdbus
[15:29] <tsdgeos> mterry: and why we don't do it for confirmation? because they are "ok i did something you asked" and thus not that important?
[15:29] <mterry> tsdgeos, right.  That's like volume change notifications.  For which we don't turn the screen on today intentionally.  I wanted to keep that behavior
[15:29] <tsdgeos> oki
[15:30] <tsdgeos> mterry: i agree that unifying on one place makes sense
[15:30] <tsdgeos> i'll comment on that and we can wait for more comments
[15:30] <kgunn> greyback: minor nit, do we expect a TP to hold the screen on eternally  ?
[15:30] <greyback> kgunn: no
[15:31] <kgunn> i see that
[15:31] <kgunn> and....
[15:31] <kgunn> i left it there for many minutes
[15:31] <kgunn> > 5min
[15:31] <kgunn> i finally hit accept
[15:31] <kgunn> and the recording does not continue
[15:31] <greyback> that's USC's job to timeout the screen
[15:31] <kgunn> ....and now camera app seems frozen
[15:31] <greyback> ah, camera app may be keeping dsplay on
[15:32] <greyback> which is thinks it is justified to do, as it is focused
[15:37] <kgunn> but hmmm...
[15:37] <kgunn> this is messed up
[15:37] <kgunn> shell responsive but camera not
[15:37] <kgunn> at all
[15:38] <mzanetti> kgunn, now stop breaking things :D
[15:39] <mterry> mzanetti, ok I think I fixed the only test broken by my emulator-tutorial branch
[15:39] <mzanetti> ack
[15:40] <mterry> (it's hard to tell, we seem to have multiple failures in trunk, right?)
[15:41]  * mterry wants to make sure it's not just my crazy machine
[15:41] <mzanetti> mterry, we shouldn't have
[15:42] <mzanetti> mterry, but ci being broken atm makes it a bit hard to tell (there's ongoing efforts to fix ci)
[15:42] <dandrader> greyback, and easy one for you: https://code.launchpad.net/~dandrader/qtubuntu/ensureDBusClipboardReady/+merge/268612
[15:44] <greyback> dandrader: ok. you got some comments on ghostApps iin the mean time
[15:45] <dandrader> greyback, yeah. saw the e-mail. guess this has higher priority
[15:45] <dandrader> (ghostApps, that is)
[15:46] <dandrader> greyback, "or crashed of its own accord" <- how can an app crash of its own accord? :)
[15:46] <greyback> dandrader: yes yes
[15:46] <dandrader> I see it can end/stop/close of its own accord, but crashing...
[15:46] <greyback> :)
[15:47] <kgunn> @unity anyone know how to "reset" say camera app to reprompt for trusted prompts
[15:47] <dandrader> greyback, but I get your point
[15:47] <greyback> kgunn: delete ~/.local/share/CameraSomething/trust.db
[15:47] <kgunn> ta
[15:48] <greyback> CameraService
[15:48] <mzanetti> kgunn, actually, to repro this bug you want also ~/.local/share/PulseAudio/trust.db
[15:48] <greyback> dandrader: cool
[15:48] <greyback> I tend to nuke ~/.local/share/UbuntuLocationService/trust.db too
[15:48] <greyback> then reboot
[15:48] <mzanetti> kgunn, and to verify if we dodn't break other trusted sessions you might want ~/.local/share/LocationService/trust.db
[15:49] <mzanetti> yeah.... that: find ~/.local -name trust.db -exec rm {} \;
[15:56] <kgunn> mzanetti: greyback so on either the audio or camera TP within camera app, if you leave for a while...then hit accept
[15:57] <kgunn> camera app becomes unresponsive and camera service spins ~50%
[15:57] <greyback> kgunn: I think I got similar with vanilla image tho
[15:58] <greyback> it's as if they timeout if they don't get a reply within certain time
[16:00] <kgunn> greyback: yes...
[16:00] <kgunn> confirmed
[16:00] <kgunn> so mzanetti greyback i am now +1 also
[16:00] <kgunn> on the silo 16
[16:01] <kgunn> i see same bugs on virgin image i see
[16:01] <mzanetti> kgunn, cool.
[16:01] <mzanetti> kgunn, maybe we should write those bugs down tho
[16:03] <greyback> dandrader: mzanetti found ghost with ghostApps, I confirmed, I added steps to repro in the MR
[16:04] <kgunn> ack, will log
[16:12] <dandrader> greyback, related to those 3 bugs or is it a different, forth, use case?
[16:12] <greyback> dandrader: the symptoms are the same, and steps to repro very close to one of the bugs
[16:13] <greyback> since i can't repro on arale, there still may be a race in there somewhere
[16:35] <o> _O