[01:59] <Subhadip> HI, I am using Ubuntu 12.04. The version of Unity installed on my computer is 5.18 but I can see the latest version in 5.0 branch is 5.20 on launchpad. Anyone have any idea why is it so?
[04:13] <Mirv> (5.20 has not yet veen uploaded)
[06:56] <Saviq> didrocks, ping
[06:56] <didrocks> Saviq: pong
[06:57] <Saviq> didrocks, hey, when you have the time, could you please look over https://code.launchpad.net/~saviq/unity-api/fix-packaging-multiarch/+merge/163564
[06:57] <Saviq> didrocks, and potentially explain why we only use macro version in SONAMEs
[06:57] <Saviq> s/macro/major/
[06:58] <didrocks> Saviq: sure, I'm catching up on hundreds of emails though, so maybe tomorrow morning, is it fine?
[06:58] <Saviq> didrocks, sure
[06:58] <didrocks> will do :)
[07:17] <mzanetti> good morning
[07:18] <greyback> hey there
[07:20] <mzanetti> greyback: jono contacted me and asked for a video of unity-next running on mir
[07:20] <mzanetti> greyback: I tried to create that but I fail unlocking the screen because of the missing mouse cursor :D
[07:20] <mzanetti> greyback: any chance you have the cursor visible already?
[07:21] <greyback> mzanetti: lp:~unity-team/unity/phablet-integrate-mir/
[07:22] <greyback> mzanetti: from your terminal, do "./run -m" and it should open a new VT, and run Mir + Unity inside that
[07:22] <greyback> the usual Ctrl+C to quit
[07:22] <MCR_> didrocks, hi - do you have 3 min. ? :)
[07:22] <didrocks> hey mzanetti, greyback!
[07:22] <greyback> didrocks: hey there, hope you had a good holiday!
[07:22] <didrocks> MCR_: still on the catchup, but sure, what's up?
[07:23] <mzanetti> hey didrocks
[07:23] <MCR_> it is about EZoom
[07:23] <MCR_> I want to disable it by default
[07:23] <didrocks> greyback: yeah, nice weather! Helped to change my mind :-)
[07:23] <didrocks> MCR_: the plugin you mean?
[07:23] <MCR_> because of these arguments:
[07:23] <MCR_> yes
[07:23] <MCR_> https://code.launchpad.net/~mc-return/compiz/compiz.merge-ezoom-cleanup/+merge/159991/comments/360604
[07:24] <greyback> didrocks: sunshine is good for the soul.
[07:24] <mzanetti> greyback: hmm... explains why I haven't been able to unlock it... with your branch I see the cursor, but I can't move it
[07:24] <mzanetti> greyback: its stuck in the top left corner
[07:24] <greyback> mzanetti: did you chmod the /dev/input ?
[07:25] <mzanetti> lol
[07:25] <mzanetti> thanks man
[07:25] <didrocks> MCR_: you didn't address my main concern
[07:25] <MCR_> which is ?
[07:25] <didrocks> MCR_: we have no way for people to enable the plugin easily
[07:25] <greyback> mzanetti: there are times when we truly use our own language :)
[07:25] <didrocks> MCR_: for people needing that a11y support
[07:25] <didrocks> in g-c-c though, you can setup the shortcuts
[07:25] <MCR_> didrocks, but there is no way without CCSM either
[07:25] <didrocks> which is what the current situation enabled
[07:26] <MCR_> that is possible ?
[07:26] <didrocks> yep
[07:26] <didrocks> not for plugin
[07:26] <didrocks> but for the zoom shortcut
[07:26] <MCR_> I did not find those shortcuts when I looked
[07:26] <didrocks> so the current situation is still better
[07:26] <MCR_> strange
[07:26] <didrocks> it's there IIRC
[07:26] <MCR_> I searched
[07:27] <MCR_> I am quite sure it is not in All Settings->Keyboard->Shortcuts...
[07:28] <didrocks> MCR_: if not, we should expose it
[07:28] <MCR_> there is just some "Zoom in/Zoom out" and "Turn zoom on or off", but this is not for EZoom
[07:29] <didrocks> MCR_: anyway, I'm not thrilled to change the default configuration as long as we ship unity 7 by default
[07:29] <MCR_> I just want to optimize things
[07:29] <MCR_> but now I know where you would want to go...
[07:30] <MCR_> thanks
[07:30] <MCR_> didrocks, ok - I won't change the config then, although I really have to say it is "not the most efficient solution"
[07:31] <didrocks> MCR_: thanks :)
[07:31] <MCR_> I'll look into exposing the shortcuts in gcc... but it won't be main priority
[07:33] <didrocks> MCR_: sure, making sense
[07:33] <MCR_> ok, ack - thx
[07:33] <didrocks> MCR_: I really wish we had a better a11y story in Unity 7 tbh :(
[07:35] <MCR_> didrocks, Compiz would be capable of delivering that of course...
[07:35] <didrocks> MCR_: yeah, it's all on nux/unity side, I know
[07:35] <MCR_> we are moving really fast forward with Compiz now
[07:36] <MCR_> the best solution in the long run would be to give users CCSM back, but I know you do not want that
[07:36] <MCR_> gcc's configuration is kindergarten compared to CCSM in terms of functionality
[07:37] <MCR_> CCSM coders were really intelligent guys
[07:37] <MCR_> it is the perfect configuration utility
[07:39] <didrocks> hem, no time to argue on this "perfect", a perfect configuration utility should prevent you shooting on your feet IMHO :)
[07:40] <MCR_> didrocks, exactly that is CCSM's strength
[07:40] <MCR_> just Compiz could not cope with some issues in the past (and still WIP)
[07:40] <MCR_> we are working on making it rock-solid
[07:40] <MCR_> didrocks, have you seen: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/745159/+attachment/3660185/+files/GridAllFunctionalityFullyFixed.mp4
[07:41] <MCR_> ?
[07:41] <seb128> MCR_, if modern industry success show anything is that "exposing a zillion options users don't understand" is everything but perfect...
[07:41] <MCR_> seb128, that is why we have tooltips explaining things to users
[07:41] <seb128> MCR_, what users want is something that just work, with only simple options for things they need
[07:41] <seb128> MCR_, you miss the point
[07:41] <MCR_> seb128, which I cannpt find in gcc for example
[07:41] <seb128> I don't want to go through 15 panels reading tooltip for half an hour
[07:42] <seb128> if you need tooltips you loose
[07:42] <MCR_> seb128, I still do not know what  "Zoom in/Zoom out" and "Turn zoom on or off" means
[07:42] <seb128> the tooltip concept doesn't even work on a touch screen
[07:42] <MCR_> in gcc
[07:42] <MCR_> seb128, sorry I do not care about touchscreens too much...
[07:43] <seb128> well, that's only one limitation of the tooltips
[07:43] <seb128> but let's not argue about that
[07:43] <MCR_> sure
[07:43] <seb128> ccsm is a fine power user tool agree
[07:43] <seb128> normal users just don't want that much complexity
[07:43] <seb128> and "zoom in/zoom out" does what it says
[07:43] <seb128> it zooms in or out
[07:44] <seb128> and turn zoom on or off is pretty self explanatory as well
[07:44] <seb128> it turns zoom on or off...
[07:44] <MCR_> seb128, which zoom ?
[07:45] <seb128> that settings is coming from GNOME
[07:45] <MCR_> I know
[07:45] <seb128> and zooming is built in for gnome-shell
[07:45] <MCR_> but it is not ideal to configure Compiz
[07:45] <seb128> how the zoom is implemented doesn't matter to users
[07:45] <MCR_> and is far less powerful
[07:46] <seb128> well, it's not the UI that is buggy there, it's our integration
[07:46] <seb128> we should ping a plugin that can do zoom
[07:46] <seb128> and bind those actions to the increase/decrease zoom effects
[07:46] <MCR_> yes
[07:46] <MCR_> I'll look into that (see above)
[07:48] <seb128> cool
[08:31] <nic-doffay> Anyone available for a QML review?
[08:32] <laptopgobooboo> hi, i have my friend's laptop and the keyboard works in the start and the resposnse in a funny way; like the CTRL(control) button was pressed hard
[08:32] <laptopgobooboo> can anyone help
[08:32] <laptopgobooboo> pls
[09:00] <luv> mardy: Hi, I would like to add GUI for signon_identity_signout to gnome-control-center-signon - I understand I will need signond from branch lp:~mardy/signon-keyring-extension/lp1172710 ... that's all fine, what I don't know how to do is how to build .deb packages from that branch.
[09:01] <luv> (or anyone else who can help, is there a easy way how to build .deb from a "custom branch" (for an already packaged software) on launchpad?)
[09:01] <luv> Thanks!
[09:01] <Saviq> luv, `bzr bd`
[09:02] <Saviq> luv, and if you want it to build in a PPA
[09:02] <Saviq> luv, `bzr bd -S` and then push to the PPA as usual - `dput ppa:something package-file.dsc`
[09:02] <Saviq> where the dsc file was created by bzr bd -S
[09:32] <didrocks> mzanetti: hey, do you install desktop-autopilot or the touch one when you run the medium tests to merge unity8? (and maybe you know about apps as well?)
[09:32] <didrocks> sil2100: ^
[09:33] <mzanetti> didrocks: desktop for now. touch too as soon as we have the hardware set up to run them
[09:33] <didrocks> mzanetti: so the apps and media medium tests should run just fine with desktop-autopilot for now?
[09:34] <didrocks> autopilot-desktop* (sorry)
[09:34] <mzanetti> didrocks: yes. om26er fixed them all and is currently re-enabling the jobs...
[09:34] <mzanetti> didrocks: btw: quite some broke already...
[09:35] <didrocks> mzanetti: excellent, finally a clear info! we saw some failures as well. Thanks :)
[09:35] <nic-doffay> Saviq, when I run the greeter via ./run touch events aren't being picked up. Any idea as to why?
[09:35] <mzanetti> didrocks: actually introducing bugs that would have been catched if tests would have been enabled
[09:35] <sil2100> mzanetti: yes, we saw some AP failures finally and were wondering what was happening
[09:35] <nic-doffay> Sorry not ./run
[09:35] <mzanetti> sil2100: yeah... they were disabled too long
[09:35] <nic-doffay> on the device.
[09:35] <didrocks> mzanetti: I asked fghinter to enabling them back during the sprint, that didn't happen?
[09:35] <mzanetti> didrocks: no
[09:36] <didrocks> shrug :(
[09:36] <mzanetti> didrocks: yesterday I decided to take care about it myself
[09:36] <didrocks> mzanetti: yeah, I was away for a week. I thought that asking it was enough…
[09:36] <didrocks> mzanetti: thanks for taking care of that
[09:37] <mzanetti> didrocks: np... it has been a lession for us all...
[09:50] <sil2100> didrocks: https://code.launchpad.net/~sil2100/cupstream2distro-config/oif_fix_dest_typo/+merge/163670
[09:57] <Saviq> nic-doffay, not really, are you sure there's nothing on top of what you're looking at that eats the events?
[09:58] <nic-doffay> Saviq, most likely. Any idea who is best to ask about this.
[09:58] <Saviq> nic-doffay, you mean it works fine on desktop, broken on device?
[09:59] <Saviq> nic-doffay, just put a MouseArea at the bottom of Shell.qml and see if inClicked gets fired
[09:59] <Saviq> *onClicked
[09:59] <nic-doffay> Saviq, will try.
[09:59] <Saviq> nic-doffay, we never had any such issues, anything I could try on one of mine devices?
[10:00] <nic-doffay> Saviq, https://code.launchpad.net/~unity-team/unity/infographics-with-lightdm
[10:00] <nic-doffay> If you have time could you do the review too?
[10:01] <Saviq> nic-doffay, I'll try and get to it soon, yeah
[10:01] <nic-doffay> ta Saviq
[10:23] <nic-doffay> Saviq, who wrote the shell?
[10:23] <nic-doffay> There's a comment I'd like to enquire about.
[10:25] <greyback> nic-doffay: lots of people contributed. Which comment, or in what part of the shell?
[10:26] <nic-doffay> greyback, Shell.qml line 517
[10:27] <greyback> nic-doffay: "his should be handled in the input stack, keyboard shouldnt propagate" ?
[10:27] <nic-doffay> greyback, yep
[10:27] <nic-doffay> greyback, basically trying to figure out why the touches are being swallowed on the infographics.
[10:29] <greyback> nic-doffay: it's there because at the moment, the shell receives _all_ touch events, even those destined for the application. For the case when the OSK was open on top of the shell, we wanted to stop the shell reacting to a keyboard press. Hence that mousearea, which is the same size as the OSK.
[10:30] <greyback> nic-doffay: I doubt that mousearea is to blame for your issue anyway
[10:39] <Saviq> mzanetti, do you remember what to do for cobertura to find the source files? https://jenkins.qa.ubuntu.com/job/unity-api-raring-i386-ci/13/cobertura/src_unity/Exception_cpp/
[10:40] <mzanetti> Saviq: use the latest build
[10:40] <Saviq> mzanetti, that is the latest build, no?
[10:42] <mzanetti> Saviq: hmm... it seems it is..
[10:42] <nic-doffay> greyback, any idea how to propagate the touch events to the infographics?
[10:42] <mzanetti> Saviq: ah... I guess the workspace is not exported to the public jenkins
[10:43] <Saviq> mzanetti, ah, might be
[10:43] <Saviq> nic-doffay, does it work on your desktop and not on the device?
[10:43] <Saviq> mzanetti, yeah
[10:44] <nic-doffay> Saviq, yeah
[10:44] <Saviq> nic-doffay, I will try in 5 mins, bear with me
[10:44] <nic-doffay> Saviq, I'm used onPressed.
[10:44] <nic-doffay> The branch a linked you to has onClicked.
[10:44] <nic-doffay> *using
[10:45] <Saviq> nic-doffay, both should work
[11:13] <Saviq> nic-doffay, it works just fine here on a Nexus 10
[11:13] <nic-doffay> Saviq, O_o
[11:15] <Saviq> nic-doffay, only issue I can see straight away is that it changes the data source twice for some reason
[11:16] <nic-doffay> Saviq, I'd ask pete-woods about that.
[11:16] <nic-doffay> I need to find out why it's not working on my device too.
[11:16] <Saviq> nic-doffay, i.e. for each user switch in tablet mode I get two "Data sets for..." one "old" and one "new"
[11:17] <Saviq> and there's an error, too:
[11:17] <Saviq> Greeter/Infographics.qml:75: TypeError: Cannot read property 'presentUnlockAnim' of null
[11:17] <nic-doffay> Saviq, I'm using a Galaxy Nexus.
[11:17] <Saviq> nic-doffay, mine's charging, will try as soon as its usable again
[11:17] <nic-doffay> Saviq, that error is also related to the data sets from what I recall.
[11:18] <Saviq> there's some blocking, too, when switching users
[11:18] <nic-doffay> greyback, any idea why touch events wouldn't be working for the infographics on a Galaxy Nexus, but working on Saviq's Nexus 10?
[11:18] <Saviq> i.e. the user doesn't switch smoothly, it jumps once or twice
[11:18] <Saviq> nic-doffay, does everything work when you run shell from the image?
[11:18] <Saviq> nic-doffay, when did you last flash?
[11:19] <nic-doffay> Saviq, now.
[11:19] <pete-woods> nic-doffay, Saviq: the present unlockAnim error is one nic will have to sort out, it happens when the data set is empty - I'll investigate the double data set change issue
[11:19] <nic-doffay> pete-woods, right. I'll handle that when I'm writing the tests then.
[11:20] <greyback> nic-doffay: is the MouseArea where it should be on the phone - check by putting a Rectangle inside it. I'd need to see code to investigate further
[11:20] <pete-woods> in terms of the non-smoothness, I know that changing user was very slow after mterry's phablet-greeter-lightdm branch for a while, then he added some performance-related change that helped a lot
[11:20] <nic-doffay> greyback, I see no reason why not if it's in the correct place when running on the desktop.
[11:20] <pete-woods> it might still be in tat area
[11:21] <Saviq> pete-woods, yeah we fixed that
[11:21] <Saviq> pete-woods, and I'll merge that branch in today if everything's fine
[11:21] <pete-woods> cool
[11:21] <Saviq> pete-woods, nic-doffay, so you'll be fine working on top of trunk
[11:21] <pete-woods> our's depends on that branch (being more lightdm stuff)
[11:22] <pete-woods> Saviq: woo! hopefully I can get to the bottom of the double change thing, then
[11:22] <greyback> nic-doffay: nor do I. Phone and desktop should behave the same. But there are differences, the GU definition for instance
[11:22] <nic-doffay> Saviq, if it is fine then yes. I'd like to get to the bottom of this Galaxy Nexus issue though so I can check the frames of the circles.
[11:23] <nic-doffay> If everything is ok then I'll begin writing tests.
[11:23] <nic-doffay> And make amendments.
[11:23] <nic-doffay> But I'd prefer to do that after potentially re-writing code for any GL related changes.
[11:24] <pete-woods> nic-doffay: see line 64 "if(presentCircles.count [11:24] <pete-woods> that's where I "fixed" one of the empty data set issues
[11:24] <pete-woods> you might need to robust that up a bit
[11:24] <pete-woods> me not knowing QML at all
[11:31] <pete-woods> strange that the diff in launchpad is nonsense - it seems to be including the changes from mterry's branch
[11:31] <pete-woods> even though that's down as a prerquesite
[11:32] <Saviq> pete-woods, yeah that happens sometimes, I'm about to approve mterry's branch so that should be gone soon
[11:32] <Saviq> just checking if it works on the galaxy
[11:32] <pete-woods> okay, cool
[11:39] <Saviq> katie, ping
[11:40] <katie> saviq pong
[11:40] <Saviq> katie, hey, can we ask you for a comment on https://code.launchpad.net/~nick-dedekind/unity/phablet-greeter-indicators/+merge/157330
[11:40] <Saviq> katie, re: tap on indicators in greeter opens device menu
[11:40] <katie> sure
[11:42] <katie> Saviq, is this in the latest build?
[11:42] <Saviq> katie, no, it's not merged yet
[11:43] <Saviq> katie, I wasn't sure we should merge it before that issue was raised
[11:43] <nic-doffay> pete-woods, I'm doing some subtle changes to the way the animations are done.
[11:43] <nic-doffay> I'll let you know when I've pushed it, mind checking if it's broken anything I'm unaware of?
[11:44] <katie> Saviq, what would you like me to comment on in particular?
[11:45] <nic-doffay> pete-woods, will there always be past circles?
[11:45] <nic-doffay> I mean surely not?
[11:45] <nic-doffay> Regarding your check on line 64...
[11:46] <pete-woods> nic-doffay: no - not if a particular user has no data yet, or you're on the guest account
[11:47] <katie> Saviq, just realised what you're talking about :) will comment now
[11:47] <nic-doffay> pete-woods, mind pushing a branch for me where there are no past circles?
[11:47] <pete-woods> nic-doffay: that was just a quick hack to stop it from crashing all the time
[11:47] <pete-woods> nic-doffay: just select the guest account
[11:48] <nic-doffay> pete-woods, ok great!
[11:48] <pete-woods> I'll change some of the user's data so that they have some present and no past, though, just to test that situation
[11:49] <nic-doffay> pete-woods, awesome cheers. I'd like to cater for every situation.
[11:50] <nic-doffay> Even before testing.
[11:51] <pete-woods> nic-doffay: just to be clear about the API - it will always try and give you "complete" months, just the data values might be null - this way it carries the concept of the length of the month, and for days without any data
[11:51] <nic-doffay> pete-woods, I see. I assuming 0 would be passed. I guess that's the reason so many things are breaking.
[11:51] <nic-doffay> *assumed
[11:54] <Saviq> nic-doffay, works fine on a Galaxy Nexus, too
[11:54] <nic-doffay> Saviq, this is weird.
[11:54] <nic-doffay> Any ideas?
[11:54] <nic-doffay> Saviq, what's the frame rate like?
[11:58] <Saviq> nic-doffay, seems fine
[12:03] <Saviq> pete-woods, one thing I can see is bad for sure: nextDataSource() takes 250ms
[12:04] <pete-woods> nic-doffay: I'm getting two calls to setUesrname from the GUI in the API
[12:04] <Saviq> pete-woods, it needs to be asynchronous
[12:05] <Saviq> pete-woods, that might be the hiccup when switching users
[12:05] <pete-woods> Saviq: I'll have a look at it
[12:05] <pete-woods> wonder what on Earth I could be doing
[12:06] <pete-woods> I'm only copying two lists with 30 floats in
[12:09] <Saviq> pete-woods, generateFakeData() needs to be called as a slot
[12:10] <Saviq> pete-woods, nextDataSource should be a signal
[12:10] <pete-woods> Saviq: okay, will make that change! :)
[12:10] <Saviq> pete-woods, to which generateFakeData() is connected
[12:10] <Saviq> pete-woods, this way nextDataSource() will return straight away
[12:11] <pete-woods> Saviq: I'm still concerned about why it's so slow, though
[12:11] <Saviq> pete-woods, generateFakeData looks quite intensive
[12:11] <Saviq> a lot of rand()s
[12:12] <pete-woods> Saviq: that's only called once
[12:12] <Saviq> ah right
[12:12] <pete-woods> I get 50 ms on a desktop machine, which is still not great
[12:12] <Saviq> pete-woods, /me can't read
[12:13] <Saviq> pete-woods, yeah
[12:16] <Saviq> nic-doffay, here's the dump from a single data switch http://pastebin.ubuntu.com/5664285/
[12:16] <Saviq> nic-doffay, at first it's fine, but as the count of circles grows we're getting past the 16ms mark
[12:18] <Saviq> nic-doffay, pete-woods remember you can connect to the device with the QML profiler to see a lot of profiling data
[12:19] <Saviq> nic-doffay, pete-woods, ./run_on_device; Analyze > QML Profiler (External) and give it the IP of your device
[12:19] <nic-doffay> Saviq, brilliant thanks.
[12:20] <nic-doffay> Saviq, still stumped as to why the infographics don't have any touch events on my phone though.
[12:21] <Saviq> nic-doffay, does the shell at all? i.e. put a huge MouseArea at the bottom of Shell.qml and console.log() onClicked
[12:21] <nic-doffay> Saviq, how will I be able to test that one the phone? I won't see any output...
[12:22] <Saviq> nic-doffay, with ./run_on_device you get all the output
[12:22] <Saviq> nic-doffay, it's just like you'd run it locally
[12:22] <Saviq> but it goes over adb+ssh to the device
[12:23] <nic-doffay> Saviq, ah ok.
[12:23] <Saviq> brb
[12:24] <pete-woods> Saviq: that doesn't work for me
[12:26] <pete-woods> maybe I'm doing something wrong
[12:26] <pete-woods> bash: cd: shell: No such file or directory
[12:26] <pete-woods> maybe that's the right error message
[12:33] <Saviq> pete-woods, run_on_device doesn't? did you run_on_device -s first?
[12:33] <pete-woods> nope!
[12:33] <pete-woods> rtm :$
[12:45] <pete-woods> Saviq: just trying to wrap my head round this asynchronous stuff
[12:45] <pete-woods> currently nextDataSource is a slot
[12:45] <pete-woods> you were saying it should be a signal
[12:46] <pete-woods> the UI reacts to the signals directly from the data i.e. the QAIM and label properties
[12:47] <Saviq> pete-woods, yeah, but it's calling it as any other method, not as a slot
[12:47] <pete-woods> Saviq: so how do I call it as a slot? (completely have no knowledge of QML here)
[12:47] <Saviq> pete-woods, so it's blocking until it return
[12:48] <Saviq> pete-woods, if nextDataSource would be a signal
[12:48] <Saviq> pete-woods, infographic.model.nextDataSource() would emit that signal
[12:49] <pete-woods> so I listen to my own signal?
[12:49] <Saviq> pete-woods, yes
[12:49] <pete-woods> Saviq: right, okay, that makes sense, thanks!
[12:50] <Saviq> pete-woods, but regardless, it shouldn't take so long indeed ;)
[12:53] <pete-woods> Saviq: I found the crunch point, it's the call to data.first_month.setVariantList(new_data->first_month.variantList());
[12:53] <pete-woods> clearly I must be doing something dumb in there
[12:54] <pete-woods> I think I'm inadvertently copying the list about 5 times
[12:54] <Saviq> something like that must be happening, yeah
[12:57] <mzanetti> Saviq: lightdm is merged! \o/
[12:57] <Saviq> mzanetti, indeed
[13:07] <mzanetti> mterry: approved
[13:08] <mzanetti> thanks!
[13:08] <mterry> mzanetti, Saviq: thanks, sorry that took so long!
[13:08] <Saviq> mterry, right back at you :)
[13:08] <mzanetti> mterry: no worries. it was a quite complex merge
[13:09] <mzanetti> mterry: do'h! now that its merged I've found a small issue :D
[13:09] <mzanetti> mterry: I think we don't need qtdeclarative5-xmllistmodel-plugin in the deps any more
[13:09] <mterry> mzanetti, hah
[13:09] <mterry> mzanetti, I believe we used it elsewhere
[13:10] <mterry> mzanetti, at least we did back when I started it
[13:10] <mterry> maybe things have changed in the last months  ;)
[13:10] <mzanetti> mterry: hmm... I remember adding that dep for the greeter... but I'll check again and will clean it up if not needed any more
[13:13] <tedg> alesage, Howdy, it seems we have a branch not autolanding: https://code.launchpad.net/~ted/hud/context-api/+merge/158939
[13:15] <Wellark> alesage: hi
[13:18] <kgunn> greyback: any joy ? (segfault, efence)
[13:19] <greyback> kgunn: some, that old segv has been cured anyway. I'm hitting the issue racarr mentioned in his mail, re who gets the Surface first.
[13:20] <greyback> kgunn: I'm looking more into that, and learning the code on the way
[13:20] <nic-doffay> pete-woods, all the dots are filled for the first infographic too. Any idea what's going on?
[13:21] <dandrader> Cimi, tsdgeos I'm getting this when running tests: http://paste.ubuntu.com/5664445/
[13:22] <kgunn> greyback: cool, feel free to pester alf & alan_g in #mir
[13:22] <tsdgeos> dandrader: your sdk is old
[13:22] <kgunn> oops/#mir/#ubuntu-mir
[13:22] <dandrader> tsdgeos, ok. will dist-upgrade
[13:22] <greyback> kgunn: yep understood
[13:22] <tsdgeos> dandrader: make sure you have the sdk ppa
[13:23] <dandrader> tsdgeos, http://ppa.launchpad.net/phablet-team/desktop-deps/ubuntu not enough?
[13:23] <tsdgeos> no clue
[13:23] <tsdgeos> not what ./build adds
[13:23] <dandrader> tsdgeos, you don't use that ppa?
[13:24] <tsdgeos> i do
[13:24] <tsdgeos> but the sdk doesn't seem to be there
[13:24] <tsdgeos> is there?
[13:25] <dandrader> tsdgeos, seems not. I must be getting it from raring itself
[13:26]  * dandrader checks the ppas added by the build script
[13:29] <Saviq> mzanetti, we're using it for the video preview
[13:29] <Saviq> mzanetti, xmllistmodel, that is
[13:30] <mzanetti> Saviq: ah. thanks
[13:30] <tsdgeos> dandrader: that's not good enough anymore, get the ppa
[13:31] <dandrader> tsdgeos, yeah, I'm running "./build --setup" now. lot's of packages being installed or upgraded (I also didn't have qt-edgers ppa)
[13:36] <nic-doffay> Saviq, I'm not getting any output with ./run_on_device ...
[13:36] <nic-doffay> Adding a MouseArea test to shell works on the desktop too.
[13:40] <pete-woods> nic-doffay: I don't know what would cause all the dots to be filled
[13:40] <pete-woods> it's not something I've been able to reproduce
[13:40] <Saviq> nic-doffay, what do you mean no output? none at all? or just nothing you'd expect?
[13:40] <nic-doffay> Saviq, none at all.
[13:41] <Saviq> nic-doffay, did you ./run_on_device -s first?
[13:41] <nic-doffay> Saviq, no, what does -s do?
[13:41] <tsdgeos> setup
[13:41] <Saviq> nic-doffay, read CODING
[13:42] <Saviq> nic-doffay, or at least ./run_on_device -h
[13:42] <nic-doffay> Will do ta Saviq
[13:48] <dandrader> Saviq, as requested: https://code.launchpad.net/~dandrader/unity/phablet_move_test_targets/+merge/163715
[13:49] <Saviq> dandrader, aactually... do we actually still have the "check" target?
[13:49] <Saviq> dandrader, I think that might be why alltests failed, 'cause we dropped the "check" target that was make-specific
[13:50] <Saviq> s/failed/didn't run everything/
[13:52] <dandrader> Saviq, right, there's no "check" target now.
[13:53] <Saviq> dandrader, problem is "test" is not really a target
[13:54] <Saviq> dandrader, that's why we had a custom "make test" target
[13:54] <Saviq> dandrader, if you can find a way to do "$generator test", that would work then
[13:55] <dandrader> Saviq, I'll add a commit to this MP that removes "check" and "alltests"
[13:55] <Saviq> dandrader, k
[13:55] <dandrader> Saviq, after that, what else would be missing or needed
[13:55] <dandrader> ?
[13:56] <Saviq> dandrader, nothing, if we can live without the "alltests" target
[13:56] <dandrader> Saviq, without the "check" target it doesn't make sense anymore
[13:57] <Saviq> dandrader, yeah I agree
[13:59] <tsdgeos> MacSlow: i totally reproduce the problem in my local chroot
[13:59] <tsdgeos> chroot pow3r
[13:59] <MacSlow> tsdgeos, hm
[14:00] <tsdgeos> i'm going to randomly guess the need for a waitForRender call
[14:00] <MacSlow> tsdgeos, before the mouseClick()?!
[14:01] <dandrader> Saviq, done
[14:02] <tsdgeos> MacSlow: yep
[14:03] <MacSlow> tsdgeos, waitForRendering(object) ?!
[14:03] <tsdgeos> MacSlow: see ./tests/qmltests/Dash/tst_PeoplePreview.qml
[14:03] <pete-woods> guys, I'm still having trouble running the run_on_device script
[14:03] <MacSlow> tsdgeos, ./Dash/tst_PeoplePreview.qml yes....
[14:03] <dandrader> Saviq, actually, without alltests tests/plugins/Utils won't be run by any "top-level" test target. should it be added to qmlunittests?
[14:03] <pete-woods> I deployed networking and ssh
[14:03] <pete-woods> and ran the run_on_device -s stage
[14:03] <pete-woods> but running the shell I get a strange error
[14:03] <Saviq> dandrader, won't it run with "test"?
[14:04] <tsdgeos> MacSlow: i'm randomly guessing that what happens is that at the second 000000 you are getting both buttons at the same position since they haven't been layouted yet
[14:04] <tsdgeos> if that's the case, it makes qmltest a bit too flacky
[14:04] <tsdgeos> but oh well
[14:04] <pete-woods> saying debug port option not recognised, but split over like 30 lines, one character each
[14:04] <MacSlow> tsdgeos, going to try now... thanks for the hint
[14:04] <dandrader> Saviq, ah, right. yes, it will
[14:05] <Saviq> pete-woods, that's just a warning, not an error
[14:08] <pete-woods> Saviq: whoops, then it says "Cannot mix incompatible Qt library (version 0x50001) with this library (version 0x50002)"
[14:09] <pete-woods> have I managed to install an incorrect version of Qt somehow?
[14:09] <pete-woods> (I just reflashed the tablet)
[14:09] <Saviq> pete-woods, apt-get upgrade
[14:09] <pete-woods> d'oh, it's my computer that's out of date then
[14:09] <pete-woods> Saviq: thanks
[14:09] <Saviq> pete-woods, no, it's the device
[14:09] <Saviq> pete-woods, but it's installed some Qt 5.0.2 packages
[14:10] <Saviq> pete-woods, and left the previously installed 5.0.1 not installed
[14:10] <pete-woods> oh, right
[14:10] <Saviq> s/installed/upgraded/
[14:10] <pete-woods> okay
[14:11] <pete-woods> all a bit confusing, but okay, feel a proper noob today
[14:14] <pete-woods> all working now, thanks muchly! :)
[14:14] <tsdgeos> MacSlow: actually you can probably replace that wait(0) with the waitForRendering
[14:14] <tsdgeos> everywhere we have a wait(0) we should have a waitForRendering i'd say
[14:15] <MacSlow> tsdgeos, sounds about right... still waiting for the currently started build to finish (and hopefully succeed)
[14:25] <alesage> tedg, Wellark, investigating
[14:27] <tedg> alesage, Thanks!
[14:34] <alesage> tedg, fginther with a question for you about the context-api branch which needs autolanding
[14:34] <alesage> tedg, a prerequisite has landed in hud/phablet but not in lp:hud, question mark?
[14:35] <tedg> Hmm, phablet should have merged into lp:hud.
[14:35] <tedg> Perhaps the resolver there can't see that?
[14:36] <tedg> alesage, Checked, yes, all of phablet is in lp:hud
[14:37] <fginther> tedg, hmmm. would it be possible to resubmit the merge proposal without the prerequisite?
[14:37] <tedg> fginther, Sure
[14:39] <fginther> tedg, thanks, that should allow the MP to land. I don't think I tools are complex enough to recognize the lp:hud/phablet has merged into lp:hud
[14:43] <tsdgeos> MacSlow: failed it seems :-/
[14:43] <MacSlow> tsdgeos, yeah :/
[14:44] <tsdgeos> good thing
[14:44] <tsdgeos> is if i remove the wait(0)
[14:44] <tsdgeos> i can reproduce the error in my chroot all the time
[14:44] <tsdgeos> finding how to fix it
[14:44] <tsdgeos> i.e. remove the wait0 and see what needs to get added
[14:44] <tsdgeos> since the wait0 seems just a workaround
[14:45] <tsdgeos> and is probably speed dependant
[14:46] <tsdgeos> MacSlow: do you know how do i make jenkins run a +junk branch of my own?
[14:46] <MacSlow> tsdgeos, actually no... I just use to rebuild a job mzanetti once set up
[14:47] <MacSlow> tsdgeos, just hijack one of my older ones http://s-jenkins:8080/job/unity-phablet-qmluitests/863/ and use your own branch there (once you click "Rebuild")
[14:48] <tsdgeos> i see
[14:55] <tedg> Wellark, Landed!
[14:55] <tedg> Thanks fginther and alesage!
[14:55] <alesage> tedg, our pleasures!
[15:00] <tsdgeos> MacSlow: this http://bazaar.launchpad.net/~aacid/+junk/unity-phablet-notification-renderer-debug-buttons/revision/674 works on my chroot, ran a qmluitest now, let's see
[15:00] <ubot5`> Launchpad bug 674 in loop-aes-source (Ubuntu) "update to kernel 2.6.10?" [Medium,Fix released]
[15:01] <tsdgeos> lol
[15:01] <MacSlow> tsdgeos, that's with or without the wait(0) at the top?
[15:01] <tsdgeos> nope, without
[15:01] <MacSlow> tsdgeos, also trying it like this http://bazaar.launchpad.net/~macslow/+junk/unity-phablet-notification-renderer-debug-buttons/revision/612
[15:02] <ubot5`> Launchpad bug 612 in openssh-krb5 (Ubuntu) "ssh-krb5 will not install on Ubuntu due to malformed dependancies?" [Medium,Fix released]
[15:02] <tsdgeos> not sure notification helps
[15:02] <tsdgeos> sicne what we really want to make sure has been layouted is the buttons
[15:02] <tsdgeos> but let's see
[15:03] <MacSlow> tsdgeos, yeah
[15:06] <MacSlow> tsdgeos, although... buttonRow is only visible if the passed notification is a snap-decision... not that waitForRendering(buttonRow) will wait forever if a non-snap-decision notification is processed
[15:07] <tsdgeos> MacSlow: well, the tests passed here
[15:07] <MacSlow> tsdgeos, sweet
[15:07] <tsdgeos> not sure waitForRendering cares about "visible"
[15:07] <dandrader> Saviq, any idea on how to we deal with device-specific settings/defines? through some CMake parameter ?
[15:07] <dandrader> s/we//
[15:07] <MacSlow> tsdgeos, well it does not seem to, since it passed on your system
[15:09] <Saviq> dandrader, we should avoid them if possible - we're not building in a device-specific way, what's your issue?
[15:10] <bregma> so, who made the decision to remove CCSM?
[15:11] <dandrader> Saviq, the max deviation property of DirectionalDragArea is like a filter for noise in movement of a touch point. and this is likely touch-screen specific
[15:11] <nic-doffay> pete-woods, can you increase the average scale of the past circles by 0.3?
[15:12] <nic-doffay> Or do both past and present have the same scaling code?
[15:12] <nic-doffay> From the backend?
[15:12] <pete-woods> nic-doffay: the scale is 0.0 -> 1.0 for both
[15:12] <pete-woods> I see it as the UI's job to translate that into something pretty for the UI
[15:12] <nic-doffay> pete-woods, ok nm then. It's best it stays the way it is.
[15:12] <pete-woods> :)
[15:15] <Saviq> dandrader, then that will probably go in device-specific defaults for $settings_backend_that_we_don't_yet_have
[15:16] <dandrader> Saviq, well, we can leave it as a qml property for now
[15:16] <Saviq> dandrader, yup, let's
[15:18] <mzanetti> hmm... is the device still Qt 5.0.1 based?
[15:18] <Saviq> mzanetti, no, but the image seems not to have all 5.0.2 packages, just apt-get upgrade
[15:19] <Saviq> mzanetti, or, it doesn't have any 5.0.2 packages, but whatever you install on top of the image will be 5.0.2
[15:19] <Saviq> and that's when it starts to complain about 0x50001 != 0x50002
[15:25] <nic-doffay> Saviq, for the Infographics tests should I base them off running a standalone version of the Infographics?
[15:25] <nic-doffay> And then just take things from there.
[15:26] <pete-woods> nic-doffay: I've pushed a commit that makes the infographic the exact same size as the old fake PNGs
[15:26] <nic-doffay> Ok great pete-woods I pushed something also a few mins ago
[15:27] <nic-doffay> I had the scale hard coded before the data was introduced which I missed. So that's gone.
[15:27] <pete-woods> awesome!
[15:27] <pete-woods> I'm looking at the user set twice issue now
[15:27] <nic-doffay> Cool, any ideas yet?
[15:28] <kenvandine> sil2100, https://code.launchpad.net/~ken-vandine/cupstream2distro-config/uoa_tests/+merge/163736
[15:28] <kenvandine> sil2100,  please :)
[15:32] <pete-woods> nic-doffay: I think I've fixed it
[15:32] <pete-woods> pushed
[15:43] <mzanetti> Saviq: I'm trying to grab an ApplicationScreenshot of the currently active app with this: http://paste.ubuntu.com/5664827/
[15:43] <mzanetti> works fine on the desktop but not on the phone
[15:50] <tedg> Trying to build Unity and getting a bunch of deprecation warnings on g_icon_info_free()
[15:50] <tedg> Is there a branch to fix that?
[15:51] <Wellark> alesage: where did the packages land from that HUD MR?
[15:53] <alesage> Wellark we're not sending them to ppas; they'll be in a daily release
[15:53] <sil2100> kenvandine: done!
[15:56] <Wellark> alesage: I have a branch depending on those new packages in the HUD MR, so how do I get my MR to pass now?
[15:56] <kenvandine> sil2100, thx
[15:57] <alesage> Wellark, let me confer with colleagues
[15:59] <tsdgeos_> MacSlow: worked :-)
[15:59] <tsdgeos_> MacSlow: http://10.97.2.10:8080/job/unity-phablet-qmluitests/869/ well, now it failed in     qmltestrunner.ListViewWithPageHeader::test_headerPositionAfterDownMove but that0s a different story ;D
[15:59] <MacSlow> tsdgeos_, yeah... same here too
[16:00] <tsdgeos_> greyback: did you do .ListViewWithPageHeader::test_headerPositionAfterDownMove ?
[16:00] <greyback> tsdgeos_: yep
[16:00] <tsdgeos_> any idea why it may be failing on MacSlow's branch?
[16:01] <greyback> tsdgeos_: nothing hits me immediately
[16:01] <MacSlow> All is fine with http://s-jenkins:8080/job/unity-phablet-qmluitests/868/
[16:02] <MacSlow> tsdgeos_, there no issue with ListViewWithPageHeader in http://s-jenkins:8080/job/unity-phablet-qmluitests/868
[16:03] <tsdgeos_> good stuff
[16:03] <tsdgeos_> so let's go ahead with that
[16:03] <MacSlow> tsdgeos_, got to run (EOD), but will be back later
[16:03] <MacSlow> tsdgeos_, thanks for the hint with waitForRendering()
[16:03] <tsdgeos_> i might not be here :D
[16:03] <tsdgeos_> close to eod too
[16:03] <MacSlow> tsdgeos_, see you tomorrow then
[16:03] <tsdgeos_> MacSlow: you're welcome :-)
[16:05] <Wellark> alesage: I need to grab some dinner.. ping me and I will get back to you
[16:06] <alesage> ok Wellark, have a second to discuss now?
[16:18] <mterry> racarr, heyo!  Did I hear you are involved with integrating Mir with the phablet images?  I'm looking forward to that for some lightdm work.  Is there anything I can help test or do?
[16:21] <racarr> mterry: It's true. What needs to go on for lightdm in this context?
[16:22] <mterry> racarr, well, lightdm isn't capable of using surfaceflinger, so either we stuff X on momentarily, or we wait for Mir before we can use lightdm
[16:22] <mterry> racarr, so I just need Mir on the images for my purposes
[16:22] <mterry> "just"  :)
[16:26] <racarr> Ok. I'm just not aware of the full scope of what lightdm is going to be doing on the phablet I guess. Hmm
[16:27] <racarr> so. in terms of mir/unity
[16:27] <racarr> things are kind of being reconstructed and it involves building a bunch of branches that don't work at this exact moment (though should again very soon ;)) anyway
[16:27] <racarr> but perhaps you just need mir as the system compositor, or some sort of mir in which casssse
[16:28] <racarr> mterry: http://unity.ubuntu.com/mir/installing_prebuilt_on_android.html
[16:28] <racarr> Maybe this can get you going or do you need full unity mir?
[16:30] <mterry> racarr, sorry, didn't notice you were talking here, got distracted by vUDS
[16:30] <racarr> No worries :)
[16:30] <racarr> I'm fully asynchronous :p
[16:30] <mterry> racarr, lightdm itself just needs probably the system compositor.  But the greeter it will use is basically a slightly modified unity binary.  So if we can't run unity on Mir yet, we can't run the greeter on Mir
[16:31] <racarr> Ok. Ill get back to you in just 2-3 hours then :)
[16:31] <mterry> racarr, well, I'm happy to help with branches or test things if that would help you
[16:31] <racarr> the basic story is we got it going, then did some refactoring in mir to make the same code work on android/desktop
[16:32] <racarr> then now updating the Qt bits...
[16:32] <racarr> then I will give you some branches to test which would definitely be helpful :)
[16:32] <mterry> racarr, cool, looking forward to it  :)
[16:34] <racarr> mterry: Great. Cheers :)
[17:33] <racarr> More multimonitor fun :) trying to set desktop wall to switch seperately per monitor
[17:33] <racarr> but it doesn't seem to do anything
[17:33] <racarr> is there an additional step? Is this just broken?
[17:42] <kgunn> greyback: ping
[17:42] <greyback> kgunn: pong
[22:20] <DX099> hello
[22:20] <DX099> I have a problem with unity : I tried to enable Window previews plugins in CCSM but I saw it didn't work well. I disabled it, logged out and logged in again but now the Autohide feature isn't working. Launcher won't show up unless I summon it with Super key...
[22:23] <kgunn> DX099: did you actually restart unity ?
[22:24] <DX099> I log out from the session and logged in again .. wasn't that enough ?
[22:24] <DX099> also, I did a "pkill unity"
[22:24] <kgunn> DX099: i'm no expert myself...but "setsid unity"
[22:25] <kgunn> should restart unity
[22:25] <DX099> It did
[22:25] <DX099> but the problem remains
[22:27] <kgunn> DX099: curious how did you "reset" ccsm ? ....was it "dconf reset -f /org/compiz/"
[22:27] <DX099> I didn't.
[22:28] <DX099> I just unticked the "window previews" option after noticing bad behaviour from Unity
[22:28] <kgunn> DX099: its my understanding "dconf reset -f /org/compiz/" will take ccsm back to the defaults
[22:28] <DX099> should I try to reset compiz ?
[22:30] <kgunn> DX099: well that's what ccsm is....its just a gui for settings for compiz
[22:30] <kgunn> http://wiki.compiz.org/CCSM
[22:30] <kgunn> again i'm no expert...but alot of folk always seem to raise an eyebrow at the mention of ccsm :)
[22:30] <DX099> kgunn, thanks ! It worked ! Reset compiz and relaunching Unity did the trick
[22:31] <kgunn> DX099: hey glad it worked
[22:31] <DX099> kgunn, unfortunately, most of us can't spend hours in dconf-editor maze...
[22:33] <kgunn> DX099: i understand