[03:17] <veebers> ah man, mk-build-deps fails for unity8 with this error: dpkg-gencontrol: warning: can't parse dependency g++-4.9:native.
[03:18] <veebers> changing native -> armhf works for me right now, but is this a bug in the debian/control or in mk-build-deps
[06:49] <Mirv> mzanetti: can you share the unconfined app you used to test the qtsystems, if I try to test it on wily?
[07:38] <tsdgeos> mzanetti: ping
[07:38] <tsdgeos> ping is a too dangerous word, half of the times i write pig and have to retype before offendign people :D
[07:39] <mzanetti> lol
[07:39] <mzanetti> tsdgeos, no worries... I wouldn't get mad
[07:40] <tsdgeos> mzanetti: does Staged here https://code.launchpad.net/~mzanetti/unity8/inputinfo-default/+merge/263969 mean "one stage" on the Nexus4 and "2 stages" on whatever we support the tablet mode?
[07:40] <mzanetti> tsdgeos, yes
[07:41] <tsdgeos> and does it still work on the desktop? i.e. do i get windowed there?
[07:41] <mzanetti> basically it means !Windowed
[07:41] <mzanetti> tsdgeos, no, one needs to set that to Windowed or Automatic
[07:41] <mzanetti> tsdgeos, so the reason for this branch is that Autopilot triggers the mouse detection
[07:42] <tsdgeos> yeah i saw the bug
[07:42] <tsdgeos> mzanetti: but then shall this be accompanied by something else so we don't regress on the desktop?
[07:42] <mzanetti> tsdgeos, well, it has been staged so far, only changed to automatic on friday
[07:42] <mzanetti> so far people are used to manually change it to windowed
[07:43] <tsdgeos> hmmm, i've never changed it manually and i get windowed mode on the desktop
[07:43] <tsdgeos> maybe some other package is already changing it to windowed?
[07:43] <mzanetti> oh...
[07:43] <mzanetti> right
[07:43] <mzanetti> so that would still work I guess
[07:43] <tsdgeos> like the unity8-desktop-session or something?
[07:43] <mzanetti> because it's an override
[07:45] <tsdgeos> ok, i'll give it a try
[07:45] <mzanetti> Mirv, http://notyetthere.org/data/untitled5.mzanetti_0.1_all.click
[07:45] <tsdgeos> mzanetti: shall you link the bug to the MR ?
[07:46] <mzanetti> it's not a fix for the bug actually. because eventually we will have to enable this
[07:46] <mzanetti> rather just a temporary workaround to not break peoples AP test runs
[07:48] <mzanetti> tsdgeos, actually veebers has been looking into this and turns out the call to "Touch.create()" causes this.
[07:48] <mzanetti> so maybe there's only a small property in that code that needs to be changed to make it a touch device (instead of a mouse) for real
[07:48] <tsdgeos> ok, so don't review it for the moment? or do we still to land this nevertheless?
[07:49] <mzanetti> not sure yet
[07:49] <tsdgeos> ok, so let's wait :D
[07:52] <mzanetti> Mirv, if you're using that app, don't look at the label on the screen
[07:52] <mzanetti> Mirv, instead tail -f ~/.cache/upstart/application-click-untitled5.mzanetti.log and see if it says "enabled/disabled" there
[07:52] <mzanetti> I didn't bother to make the app pretty
[08:10] <Mirv> mzanetti: thanks!
[10:35] <tsdgeos> mzanetti: ltinkl: i thought this was "on hold" pending the other AP fix? https://code.launchpad.net/~mzanetti/unity8/inputinfo-default/+merge/263969
[10:35] <mzanetti> tsdgeos, yeah... will drop it, now that the issue is about to be fixed in AP
[10:35] <mzanetti> sorry ltinkl :/
[10:35] <ltinkl> tsdgeos, if that's the case, sorry, it hadn't been marked as such
[10:35] <ltinkl> mzanetti, no probs
[10:35] <mzanetti> tsdgeos, btw: https://code.launchpad.net/~mzanetti/autopilot/dont-use-touchpad-for-touch/+merge/264011
[10:36] <mzanetti> I guess we'll leave it to the AP people to review/land it
[10:36] <tsdgeos> yep saw it
[10:36] <tsdgeos> +1
[14:19] <seb128> where does unity8 store that it already displayed the tutorial/first run demo?
[14:21] <seb128> seems like it's in accountsservice as demoEdges
[14:22] <seb128> not as easy than touching a file to skip it on an iso
[15:56] <tsdgeos> cimi: there?
[15:57] <cimi> tsdgeos, sure
[15:57] <tsdgeos> cimi: i don't understand the question you made on the MR
[15:57] <tsdgeos> " I'm missing where this is needed... maybe you wanted to add this check for the model of the repeater?"
[15:57] <tsdgeos> to which line does that relate?
[15:57] <tsdgeos> to   readonly property var actions: root.widgetData ? root.widgetData["actions"] : null ?
[15:57] <cimi> tsdgeos, if you grep for it, nothing is row.actions iirc
[15:58] <tsdgeos> damnit the email puts suff in the wrong order
[15:58] <tsdgeos> i should have opened the web
[15:58] <tsdgeos> email is
[15:58] <tsdgeos> > +        id: row
[15:58] <tsdgeos> I'm missing where this is needed... maybe you wanted to add this check for the model of the repeater?
[15:58] <tsdgeos> > +        readonly property var actions: root.widgetData ? root.widgetData["actions"] : null
[15:58] <tsdgeos> which made me think it was about id: row :D
[15:58] <cimi> tsdgeos, and since the model of the repeater is root.widgetData["actions"] I thought you planned to do model: row.actions
[15:58] <tsdgeos> sorry ^_^
[15:59] <tsdgeos> cimi: yeah good question i've no idea what i wanted to do with that :D
[15:59] <cimi> tsdgeos, lol
[15:59] <tsdgeos> cimi: i guess i'll do what you said model: row.actions
[16:00] <tsdgeos> and i'll set the sourcesize
[16:01] <tsdgeos> tomorrow though, i'm going to try to find somewhere in the house that is not so hot and try to not melt there :D
[16:01]  * tsdgeos waves
[16:23] <seb128> is anyone looking at making the messaging menu "delete" action use the red icon rather than the old label?
[16:37] <seb128> dednick, there are some approved ubuntu-settings-components merges (and some pending reviews), do you know if anyone is looking at landing those?
[16:37] <seb128> mzanetti, ^
[16:37] <seb128> https://code.launchpad.net/~ubuntu-settings-components-team/ubuntu-settings-components/trunk/+activereviews
[16:38] <mzanetti> seb128, I didn't really have them on screen tbh
[16:38] <dednick> seb128: no, i don't know who is looking after that. mzanetti?
[16:38] <mzanetti> thanks for pointing it out
[16:39] <seb128> yw
[16:39] <mzanetti> ok. added to my list
[16:39] <seb128> thanks
[19:18] <dandrader> tedg, you might be interested in that: https://docs.google.com/document/d/15yq0ziuINo7zLflvcLCuThjY2grftcFMynMcGFLl0uk/edit
[19:40] <mzanetti> dandrader, erm... my krillin's greeter is locked to landscape :)
[19:41] <dandrader> mzanetti, have you been abusing your phone?
[19:46] <mzanetti> dandrader, not really, no
[19:46] <mzanetti> dandrader, just using it normally
[19:46] <mzanetti> I think the last thing I used was telegram
[19:48] <mzanetti> dandrader, anything I can do in terms of information gathering before I restart?
[19:49] <mzanetti> seems the focused app is the dash, according to the logs
[19:49] <dandrader> mzanetti, maybe check for anything interesting in unity8.log. other than that, I don't know
[19:50] <mzanetti> nothin interesting in there...
[19:50] <dandrader> mzanetti, we do have a bug on that already, right?
[19:50] <mzanetti> dandrader, something like this on N7. but I can't be 100% sure it's the same thing
[19:50] <mzanetti> also popey reported this on a krillin today morning
[19:50] <mzanetti> I'll try to repro
[19:51] <mzanetti> hah! found a workaround
[19:51] <mzanetti> launch the settings via indicators, then turn off the screen and on again, it'll rotate
[19:51] <dandrader> mzanetti, thing the only sane next step for debugging this is me prepping a special unity8 version where you can tap somewhere on the screen to have the values of some key properties printed in the log
[19:51] <dandrader> mzanetti,  s/thing/think
[19:52] <mzanetti> dandrader, I can run such a thing, no prob
[19:52] <popey> yeah, i found it happens if the screen times out while you're playing a landscape game
[19:52] <mzanetti> if the area is not preventing me to use it as a phone
[19:52] <mzanetti> popey, you have a way to repro and didn't tell us? :D
[19:53] <popey> i thought i said how in the bug?
[19:53] <mzanetti> but now that you're saying it, seems I had machines-vs-machines open indeed
[19:53] <mzanetti> oh...
[19:53] <mzanetti> lol
[19:54] <popey> changed all my pin numbers so they dont have zeros in :(
[19:54] <mzanetti> haha
[19:54] <mzanetti> popey, saw the workaround ^^
[19:54] <mzanetti> ?
[19:54] <popey> no
[19:54] <mzanetti> launch settings from the indicators, then turn off/on the screen
[19:54] <popey> i cant
[19:54] <popey> indicators are off for me
[19:55] <mzanetti> huh?
[19:55] <popey> on the lock screen
[19:55] <mzanetti> on the greeter?
[19:55] <popey> yeah, i switch them off in settings
[19:55] <mzanetti> oh. I see
[19:57] <mzanetti> popey, can you intentionally reproduce it?
[19:57] <mzanetti> seems I can't
[19:57] <popey> i think you have to let the phone lock itself
[19:57] <popey> not lock it with pwr button
[19:59] <mzanetti> yeah, just tried twice didn't work either
[19:59] <mzanetti> but I did see this issue now twice by now
[20:00] <popey> yeah, i have seen the issue twice but can't reproduce it
[20:01] <mzanetti> maybe it's something weird, that you a) need to let the screen time out in landscape and then b) unlock it in InvertedPortrait or so :D
[20:01] <greyback_> dandrader: don't forget about a tool like Gammaray, allows you to inspect the internals of a qt app
[20:03] <dandrader> never used it
[20:03] <dandrader> greyback_, does it work with QML?
[20:04] <greyback_> dandrader: sure. they're just qobjects under it all
[20:04] <greyback_> I've a reasonably recent build in my PPA: https://launchpad.net/~gerboland/+archive/ubuntu/unity-mir
[20:04] <dandrader> greyback_, so you run gammaray on the desktop to inspect some qt process on the device?
[20:05] <mzanetti> greyback_, can it work remote to the phone?
[20:05] <greyback_> dandrader: that is possible yes.
[20:05] <mzanetti> nice
[20:05] <dandrader> greyback_, have you done it?
[20:05] <greyback_> I think so. It was ages ago
[20:05] <greyback_> sadly the full qml integration does not work from device-to-PC
[20:06] <greyback_> but you can still get the tree of qobjects and inspect their state
[20:06] <mzanetti> that should be enough I think
[20:06] <greyback_> it's not too hard to figure which qobject corresponds to what qml
[20:06]  * mzanetti installs
[20:07] <mzanetti> greyback_, are you running wily?
[20:07] <greyback_> mzanetti: no
[20:07] <mzanetti> odd
[20:07] <mzanetti> gammaray : Depends: qtbase-abi-5-3-2 but it is not installable
[20:09] <greyback_> hmm, will need to bump what's in the ppa
[20:09] <mzanetti> dandrader, anyhow, if you prepare some qml file with a MouseArea that prints stuff I'll run it on my phone and send data your way
[20:09] <greyback_> 32 weeks old. Where does time go
[20:09] <mzanetti> dandrader, if possible, enable it only when the greeter is visible, so I can still use the phone normally otherwise
[20:10] <mzanetti> maybe even just hook it up to the tease() method that passes through Shell.qml
[20:11] <mzanetti> greyback_, indeed :D
[20:11] <mzanetti> I still remember the conversation we had when you uploaded those packages
[20:11] <mzanetti> can't believe that's 32 weeks :D
[20:52] <veebers> mzanetti: available? Your branch errored on a flake8 issue, if you're not I'll branch, fix, push and approve etc.
[20:58] <mzanetti> veebers, fixing
[21:04] <veebers> mzanetti: thx awesome. I'll get the silo wheels turning once it's approved && merged
[21:18] <mzanetti> veebers, hey, having an issue here :/
[21:19] <mzanetti> seems with this change click_object() doesn't work properly any more
[21:35] <veebers> mzanetti: just click_object? or any touch/click/tap etc.
[21:36] <mzanetti> veebers, I was just trying the webbrowser tests and they use click_object() everywhere... the _uinput file has tap_object... but I can't access that from the test
[21:37] <veebers> mzanetti: when you say doesn't work properly that's as in there is no touch event logged?
[21:45] <mzanetti> veebers, it seems it presses but never releases
[21:45] <mzanetti> veebers, sorry, was distracted in another channel
[21:46] <veebers> mzanetti: no worries. That's really odd as you've only changed the touch device, nothing else. Only what gets created
[21:46] <veebers> mzanetti: and if you change it back it all works? I know there was some input work/fix gone into mir and or unity8 recently
[21:47] <mzanetti> yeah... it does...
[21:48] <mzanetti> veebers, I might have found something
[21:48] <veebers> oh? /me waits on the edge of his seat
[21:51] <mzanetti> veebers, hehe. I think I found it
[21:51] <mzanetti> finger_down() finger_up()
[21:51] <mzanetti> they used BTN_TOOL_FINGER instead of BTN_TOUCH too
[21:52] <mzanetti> replacing all makes it work
[21:52] <veebers> mzanetti: oh no way, ugh what a bug. Good catch
[21:54] <mzanetti> veebers, pushed
[21:54] <veebers> mzanetti: awesome, thanks
[21:55] <mzanetti> veebers, this is actually quite cool. should be easy to create a touchpad/mouse/touchscreen/wacomtablet and whatnot input methods
[21:55] <veebers> mzanetti: I'm tempted to suggest to use _get_touch_tool in the finger_up|down methods, but not sure if it's worth it
[21:56] <mzanetti> I thought about that too
[21:56] <veebers> mzanetti: yeah ^_^
[21:56] <mzanetti> but decided if you want to refactor parts of the code it's probably faster if you do it yourself instead of playing ping-pong with a python noob
[21:57] <mzanetti> oh...
[21:57] <mzanetti> that
[21:57] <mzanetti> I thought about getting rid of that method
[21:57] <mzanetti> I can change the other I guess
[22:00] <mzanetti> veebers, pushed
[22:02] <veebers> mzanetti: that will fail, _get_touch_tool isn't an instance method (no need for self.)
[22:10] <mzanetti> hmm... really.. I did run it tho and it didn't complain
[22:13] <mzanetti> veebers, ok... removed it.. still wondering why it didn't complain before
[22:13] <veebers> mzanetti: not sure, I just tried using it and got the expected error
[22:13] <mzanetti> ok... then I'm doing something wrong
[22:14] <mzanetti> ok... verified. now I'm getting same results at least
[22:15] <veebers> mzanetti: yeah, https://jenkins.qa.ubuntu.com/job/autopilot-wily-amd64-ci/37/console
[22:17] <veebers> mzanetti: just to bombard you with requests :-) any news on being able to cross build unity8 for vivid-ar,
[22:17] <veebers> err vivid-armhf
[22:18] <mzanetti> veebers, not really. But I've reported a bug pete said he'll look into it
[22:18] <veebers> coolio, thanks mzanetti
[22:34] <veebers> mzanetti: which device where you running your test on?
[22:34] <mzanetti> veebers, mako
[22:34] <veebers> mzanetti: sweet thanks