[08:01] <Cimi> Saviq, you removed some deps in the cmakelists of mock lightdm plugin - readded
[08:08] <Saviq> Cimi, I was rather aggressive in the removals indeed and didn't verify yet
[08:09] <Cimi> Saviq, fine now
[08:09] <Cimi> Saviq, in my branch
[08:10] <Cimi> Saviq, http://bazaar.launchpad.net/~cimi/unity8/infographics-new-lightdm/revision/826
[08:10] <Cimi> Saviq, fixes -ldlightdm...
[08:11] <Cimi> can't believe I am patching cmakefiles :D
[08:19] <tsdgeos> mhr3: i just fixed your concerns on https://code.launchpad.net/~unity-team/unity-api/unity-shell-scopes-api/+merge/219379
[08:20] <mhr3> tsdgeos, thx, will have another look
[08:20] <tsdgeos> mhr3: do you think you'll have time to add some documentation to the various properties/signals in there?
[08:20] <tsdgeos> honestly i don't think i'm the best person to do it
[08:30] <mhr3> tsdgeos, yea, just didn't get to it yesterday
[08:30] <tsdgeos> mhr3: oki :)
[08:30] <mhr3> tsdgeos, although not exactly thrilled to do it :P
[08:31] <tsdgeos> mhr3: blame Saviq
[08:31] <tsdgeos> it's all his master plan :D
[08:31] <mhr3> sure, i do :)
[08:32] <mhr3> i'm already trying to figure the next nasty thing i do to him
[08:37] <mhr3> tsdgeos, doing the qmltest means the thing needs a ui?
[08:38] <tsdgeos> mhr3: no, why?
[08:38] <mhr3> tsdgeos, cause it's qml? :)
[08:39] <tsdgeos> qml doesn't need an ui
[08:39] <tsdgeos> qtquick does
[08:39] <mhr3> cool then
[08:39] <tsdgeos> mhr3: besides there's other similar tests in there, mine is not the first
[08:39] <mhr3> tsdgeos, although you are importing qtquick
[08:40] <tsdgeos> that's right
[08:40] <tsdgeos> i'm cheating a bit
[08:40] <tsdgeos> actually we do need ui yes :D
[08:40] <tsdgeos> probably
[08:40] <tsdgeos> maybe
[08:40] <tsdgeos> what's your concern?
[08:41] <mhr3> jenkins being happy to run them
[08:41] <mhr3> or doing it in chroot
[08:41] <mhr3> and things like that
[08:41] <tsdgeos> mhr3: since jenkiins is already happy
[08:42] <tsdgeos> i don't see what is the problem :D
[08:42] <mhr3> if other tests are doing it already... whatev
[08:42] <tsdgeos> as said i'm not doing anything that wasn't already done in this project
[09:43] <karni> Saviq: phablet-screenshot has been fixed, and should land shortly in the ppa
[09:43] <Saviq> karni, kk
[09:54] <Cimi> MacSlow, I am in italy from last night till friday - allergy kicking in is awful ='(
[09:56] <seb128> being allergic to Italy, must be annoying for an italian ;-)
[10:01] <mzanetti> do we somehow filter the available apps shown in the scope?
[10:01] <mzanetti> I can find some apps by searching, but they won't show up in the scope normally
[10:09] <mhr3> alecu, pstolowski ^?
[10:13] <MacSlow> Cimi, hope you have you helping cetrizin or the like
[10:13] <Cimi> MacSlow, I have stuff that is making me fall asleep :D
[10:14] <Saviq> tsdgeos, `|| true` are basically a way to ignore a failure in a script
[10:14] <MacSlow> Cimi, yeah
[10:14] <MacSlow> Cimi, I hate that side-effect
[10:14] <pstolowski> mzanetti, I don't see any limit on the results client-side, but I think server does that if search string is empty. see https://search.apps.ubuntu.com/api/v1/search , that's what we get when you're just browsing
[10:14] <Saviq> tsdgeos, I think exiting with a non-0 status would stop the job from running
[10:14] <tsdgeos> Saviq: ok, seems a bit weird to me we want to ignore those errors :D
[10:14] <mzanetti> pstolowski: strange, yes. xbmcremote not in there
[10:14] <Saviq> tsdgeos, they're not required though
[10:15] <Saviq> tsdgeos, in theory ;)
[10:15] <pstolowski> mzanetti, there is a plan to support pagination to remedy exactly this
[10:15] <mzanetti> ah, nice
[10:16] <Saviq> tsdgeos, basically, we want the greeter to start regardless of the other services failing
[10:17] <mhr3> Saviq, preview header looks wrong when there's no icon, is that aftermath of dynamic cards?
[10:18] <tsdgeos> mhr3: may be
[10:18] <tsdgeos> i extracted the old code to the preview header
[10:18] <tsdgeos> i.e. it's nto the same code in cards and preview anymore
[10:18] <tsdgeos> but it was "working"
[10:18] <tsdgeos> obviously i forgot something
[10:18] <tsdgeos> mhr3: can you open a bug?
[10:22] <mhr3> tsdgeos, https://bugs.launchpad.net/unity8/+bug/1319343
[10:23] <tsdgeos> mhr3: can you screenshot it and/or give an example of where it happens?
[10:23] <mhr3> does screenshot work again?
[10:25] <mhr3> nope, doesn't
[10:25] <tsdgeos> mhr3: take a photo :D
[10:25] <tsdgeos> mhr3: or just tell me where it happens
[10:26] <mhr3> tsdgeos, music previews
[10:27] <tsdgeos> mhr3: so it should be left aligned totally i guess?
[10:27] <mhr3> yea
[10:27] <mhr3> unless design changed it again :)
[10:27] <tsdgeos> i'll get this
[10:27] <tsdgeos> nah, that's probably my doing
[10:30] <Saviq> hmm my dconf just got corrupted... not good :|
[10:36] <tsdgeos> mhr3: pstolowski: any idea about this? http://paste.ubuntu.com/7462064/
[10:37] <mhr3> tsdgeos, -shell tests?
[10:37] <mhr3> tsdgeos, fix is being landed
[10:37] <tsdgeos> mhr3: unity8
[10:37] <mhr3> oh?
[10:37] <tsdgeos> don't have any scope
[10:37] <tsdgeos> not sure if because of this
[10:38] <mhr3> tsdgeos, try to rm zmq from XDG_RUNTIME_DIR
[10:39] <mhr3> plus restart registries
[10:39] <tsdgeos> hmmm
[10:39] <tsdgeos> my scope registry seems unhappy
[10:39] <mhr3> sing to it
[10:39] <mhr3> calms it down
[10:39] <tsdgeos> is it a plant?
[10:40] <tsdgeos> seems to be crashing all the time
[10:40] <tsdgeos> i.e
[10:40] <tsdgeos> tsdgeos_work@xps:~$ start scope-registry
[10:40] <tsdgeos> scope-registry start/running, process 14294
[10:40] <tsdgeos> tsdgeos_work@xps:~$ start scope-registry
[10:40] <tsdgeos> scope-registry start/running, process 14328
[10:40] <mhr3> check the log
[10:40] <tsdgeos> where?
[10:40] <mhr3> ~/.cache/upstart
[10:41] <Saviq> tsdgeos, you can't test the split branch alone...
[10:41] <Saviq> tsdgeos, it's built in silo 002 for the purpose of testing
[10:41] <Saviq> tsdgeos, should've made that clearer
[10:42] <tsdgeos> Saviq: yes really, since the description says "Note none of these are needed to build or play around with split"
[10:42] <tsdgeos> i didn't see the need to use any other branch
[10:43] <Saviq> tsdgeos, well, I might be wrong, then
[10:43] <tsdgeos> let's wait for mterry
[10:43] <Saviq> tsdgeos, but I think it's better to just test the silo, that's what it's there for...
[10:43] <tsdgeos> anyone knows why upstart puts his logs in .cache?
[10:43] <tsdgeos> it's the last place i'd look them for in
[10:44] <Saviq> tsdgeos, there's no other semi-persistent place to put them in I think...
[10:44] <Saviq> tsdgeos, where else would you put them?
[10:44] <tsdgeos> .logs
[10:44] <tsdgeos> :D
[10:44] <tsdgeos> or .log even
[10:44] <tsdgeos> to mimic /var
[10:44] <Saviq> yeah, that's not standard, though, .cache is
[10:44] <tsdgeos> well we can start putting binaries in .cache
[10:44] <tsdgeos> since it's in the standard :D
[10:45] <tsdgeos> that's a pretty lame excuse tbh
[10:45] <mhr3> tsdgeos, so anything interesting in scope-registry's log?
[10:45] <tsdgeos> mhr3: scoperegistry: unity::scopes::ConfigException: Cannot instantiate run time for Registry, config file: :
[10:45] <tsdgeos>     unity::scopes::MiddlewareException: cannot initialize zmq middleware for scope Registry:
[10:45] <tsdgeos>         unity::FileException: cannot create endpoint directory /run/user/1000/zmq/priv (errno = 13)
[10:45] <mhr3> told you
[10:45] <tsdgeos> mhr3: may i have been tainted by running unity-scopes-shell tests?
[10:45] <Saviq> tsdgeos, I agree that we're just missing a lsb standard dir for user logs
[10:45] <tsdgeos> mhr3: i removed the folder
[10:45] <mhr3> tsdgeos, no
[10:46] <tsdgeos> i did :D
[10:46] <tsdgeos> it's there again, no clue who's creating it
[10:46] <mhr3> tsdgeos, doesn't upstart keep respawning it?
[10:47] <mhr3> tsdgeos, stop scope-registry and smart-scopes-proxy
[10:47] <tsdgeos> done
[10:47] <mhr3> rm
[10:47] <mhr3> start again
[10:48] <tsdgeos> mhr3: ain't working
[10:48] <tsdgeos> mhr3: http://paste.ubuntu.com/7462104/
[10:49] <mhr3> tsdgeos, weeeird
[10:49] <mhr3> tsdgeos, amd64?
[10:49] <tsdgeos> mhr3: yes
[10:49] <mhr3> tsdgeos, try with this one https://launchpad.net/~ci-train-ppa-service/+archive/landing-015/+files/libunity-scopes1_0.4.5%2B14.10.20140513-0ubuntu1_amd64.deb
[10:50] <mhr3> it's about to land.. so safe
[10:51] <tsdgeos> mhr3: same problem
[10:51] <tsdgeos> i had to +x my zmq folder
[10:51] <tsdgeos> it works now
[10:52] <mhr3> how come that it works on the phone?
[10:52] <tsdgeos> no idea :D
[10:52] <tsdgeos> well kind of doesn't work either
[10:53] <tsdgeos> the registry doesn't shut down
[10:53] <tsdgeos> but my unity8 is still empty
[10:53] <tsdgeos> this is new, yesterday it was working
[10:53] <tsdgeos> let me reboot just in case
[10:59] <pstolowski> mhr3, I had similar issue yesterday when running stuff manually in lxc (so no X and no XDG_RUNTIME_DIR), I had to export XDG_RUNTIME_DIR=/run/user/1000. But perhaps this is something else
[11:01] <mhr3> it is
[11:01] <pstolowski> mhr3, and I just checked with devel; with empty /run/user/1000  the zmq/priv gets created when starting the registry
[11:01] <mhr3> yea, works for me too
[11:02] <mhr3> i guess it's not a good sign that tsdgeos is gone for 10minutes now :)
[11:03] <pstolowski> heh
[11:03] <sil2100> pstolowski: hello!
[11:03] <pstolowski> sil2100, hi!
[11:04] <sil2100> pstolowski: looking at the new unity-scopes-api with your changes in it, I see in the diff some symbols being removed
[11:04] <sil2100> pstolowski: https://ci-train.ubuntu.com/job/landing-015-2-publish/lastSuccessfulBuild/artifact/packaging_changes_unity-scopes-api_0.4.5+14.10.20140513-0ubuntu1.diff <- you can see that some symbols have disappeared - are those private symbols?
[11:06] <pstolowski> sil2100, they were either private or from the path of API that no one has been using yet
[11:07] <tsdgeos> mhr3: it is working now
[11:07] <pstolowski> sil2100, s/path/part/
[11:08] <sil2100> pstolowski: ACK, thanks :)
[11:11] <mhr3> sil2100, you know we see those changes in our MPs, right? ;)
[11:11] <mhr3> sil2100, there is never going to be a "omg, really? a symbol disappeared? what have we done?!"
[11:12] <sil2100> mhr3: ;)
[11:13] <sil2100> mhr3: just wanted to put some context in my question!
[11:17] <Cimi> for infographics and crossfade effect, what you guys suggest?
[11:21] <Cimi> repeater with images crossfading?
[11:30] <tsdgeos> mhr3: https://code.launchpad.net/~aacid/unity8/noiconpreviewheader/+merge/219502
[11:32] <Cimi> tsdgeos, ^
[11:32] <Cimi> crossfading between svg on the same position
[11:32] <Cimi> many solutions... which works best?
[11:33] <tsdgeos> Cimi: so we are rendering svg live?
[11:34] <Cimi> tsdgeos, I have a model of SVG
[11:34] <Cimi> tsdgeos, they are rendered by a daemon iirc
[11:34] <tsdgeos> can we make that be PNG?
[11:34]  * tsdgeos wants his future phone to not waste baterry rendering a SVG
[11:35] <tsdgeos> Cimi: anyway, continue with the description
[11:35] <Cimi> tsdgeos, maybe not
[11:35] <Cimi> tsdgeos, but we could create pngs from svgs in the daemon
[11:35] <Cimi> tsdgeos, but how about resolution?
[11:35] <Saviq> tsdgeos, we can just render them once and cache
[11:36] <Cimi> Saviq, we being who?
[11:36] <tsdgeos> Saviq: or render them in the servers :D
[11:36] <Saviq> tsdgeos, they're not coming from any servers
[11:36] <tsdgeos> Cimi: my phone doesn't usually cahnge of resolution
[11:36] <Saviq> tsdgeos, but ours will, connected to an external device
[11:36] <Saviq> screen
[11:37] <tsdgeos> Saviq: then it's probably docked i don't care about battery
[11:37] <tsdgeos> Cimi: anway sorry for disturbing your train of thought with this svg/png thing
[11:37] <tsdgeos> Cimi: so you have a list of images, what next?
[11:37] <Saviq> tsdgeos, we have to render them on device anyway - whether it's going to be once in the "visualizer" or once in the image caching service, doesn't really matter
[11:38] <Cimi> tsdgeos, talk with pete-woods for changing that
[11:39] <Cimi> otp
[11:53] <Saviq> /food
[11:54] <Cimi> tsdgeos, so the infographics are images
[11:54] <Cimi> tsdgeos, we want crossfade them
[11:54] <Cimi> tsdgeos, I was wondering which is the best solution
[11:55] <Cimi> Repeater with Loader?
[12:05] <Wellark> mzanetti: ping
[12:05] <Cimi> or maybe a simple crossfadeImage
[12:05] <mzanetti> Wellark: pong
[12:05] <Wellark> I see there is unity8 on silo5
[12:06] <Wellark> I'm hoping to be able to land silo9 today which also contains unity8
[12:06] <Wellark> mzanetti: what is the expected landing ETA of silo5 ?
[12:06] <mzanetti> Wellark: hmm... I hope to be able to land it today too. but that's not guaranteed. maybe tomorrow
[12:07] <Wellark> mzanetti: well, there is no guarantee that silo9 lands today either :)
[12:07] <Wellark> so I think it's race time! :P
[12:07] <mzanetti> Wellark: ack. whoever lands first notifies the other
[12:07] <Wellark> mzanetti: let's do that :)
[12:07] <mzanetti> Wellark: fyi: I have most of the logic for the dual sim pin implemented and hope to get design guidance today.
[12:10] <Wellark> mzanetti: ok. cool.
[12:11] <Wellark> mzanetti: have you secured a designer?
[12:11] <mzanetti> Wellark: yep, 2 of them :D
[12:11] <Wellark> if not, then please don't get stuck waiting :)
[12:11] <Wellark> oh, cool.
[12:11] <Wellark> mzanetti: do you have a meeting scheduled?
[12:11] <Wellark> I would love to join
[12:11] <mzanetti> Wellark: no... Jouni said he'll walk through it with Olga today and will give me updated visuals
[12:12] <Wellark> ok.
[12:35] <dandrader> Anyone up for an easy review? https://code.launchpad.net/~dandrader/unity8/remove_revealer/+merge/219511
[12:35] <dandrader> it just removes code!
[12:55] <tsdgeos> dandrader: removal is nice!
[12:55] <tsdgeos> Cimi: using CrossFadeImage to crossfade images sounds good :D
[12:56] <tsdgeos> Cimi: no idea how the class works with multiple images
[12:56] <tsdgeos> Cimi: if not repeater + loader should be ok too
[12:57] <dandrader> Saviq, what about expanding https://wiki.ubuntu.com/Process/Merges/Checklists/Unity8 to make the reviewer add a "Reviewed by: My-Name-Here" entry to the MP commit message
[12:59] <Saviq> tsdgeos, Cimi, it works great with switching sources, that's what it's meant for
[12:59] <Saviq> dandrader, I think we could include that in the CI train instead
[12:59] <Saviq> didrocks, we did have "Approved by: foo, bar" in the commit logs before, could we get those with the ci train again? or were they removed on purpose?
[13:00] <didrocks> Saviq: I guess the request should go to the CI team starting from now (or sil2100)
[13:00] <didrocks> Saviq: you didn't raise it in the call last month, so I wrapped up with what was discussed and agreed to work on before moving to other tasks
[13:01] <Saviq> didrocks, sure, didn't remember it...
[13:01] <didrocks> Saviq: and I would feel unconfortable to dump code on others while not maintaining it
[13:01] <didrocks> I guess it's a few lines change, so sil2100 may do that change?
[13:02] <dandrader> Saviq, sure, but we been waiting for this automation to come back for ages
[13:03] <Saviq> dandrader, I don't think the ones responsible for it knew that, I'm afraid
[13:03] <dandrader> Saviq, I guess you could also put the "Use strip-u8-tags.sh if applicable" in the CI train
[13:03] <Saviq> dandrader, well, that's unity8-specific, and only temporary, I hope to get rid of that task asap
[13:04]  * dandrader says "CI train" having only a faint idea of what it really is
[13:04] <Saviq> sil2100, let me know please if I should file a bug against cupstream2distro or something
[13:04] <didrocks> yeah, was never brought up with us :)
[13:04] <didrocks> (or at least, with me)
[13:05] <didrocks> maybe mentionned once, but not "critical/now"
[13:05] <didrocks> sad, it should be easy
[13:05] <tsdgeos> mterry: ping
[13:19] <mterry> tsdgeos, hello
[13:20] <tsdgeos> mterry: so Saviq mentioned that silo-2 has "split" stuff, but then your MR says that it doesn't really depend on stuff, I was wondering if the problem i have with the greeter being slow to appear was fixed in silo2 but not in that split branch directly?
[13:22] <mterry> tsdgeos, to have the full experience, you need the rest of the silo.  But the basic greeter functionality can be tested alone.  As for appearing slowly...  I would think that wouldn't happen on its own, but maybe some of the session-switching logic in the USC changes is needed.  I haven't tested it on its own in a while
[13:22] <mterry> tsdgeos, I guess I'd recommend doing the whole silo
[13:22] <tsdgeos> mterry: ok
[13:23] <tsdgeos> mterry: do you have the ppa link at hand?
[13:23] <mterry> tsdgeos, that stuff in the MR was before I had a silo and it was easy to test -- i.e. I didn't want my testers to go through the pain of building 6 packages
[13:23] <mterry> tsdgeos, ppa:ci-train-ppa-service/landing-002
[13:24] <mterry> tsdgeos, I just uploaded a crasher fix for logind that was affecting split greeter images yesterday -- so make sure you have a recent image or at least apt-get upgrade on your current one
[13:24] <mterry> tsdgeos, oh, scratch that.  That update is still in proposed
[13:25]  * mterry finds out why
[13:30] <tsdgeos> mterry: there's a few minor things in the MR
[13:31] <tsdgeos> mterry: namely, you killed the x bit for a script
[13:31] <mterry> tsdgeos, hah, I did?  Odd
[13:31] <tsdgeos> mterry: and you're resizing to the size that shouldn't be needed (and hasn't been needed until now, no?)
[13:31] <mterry> tsdgeos, not even sure how I would do that accidentally
[13:31] <mterry> tsdgeos, ah...  that resizing code.  Let me try without it.  I remember doing that for working better on the desktop
[14:00] <dandrader> mzanetti, if I resize unity8 from portrait to landscape (i.e., increase its width) and I have an application on foreground (talking qt compositor here) the stage goes into spread mode, or better, into a broken stage mode
[14:00] <dandrader> s/broken stage mode/broken spread mode
[14:01] <dandrader> mzanetti, so, any hints on where the problem likely is?
[14:02] <mzanetti> dandrader: yeah... need to reset the flickable's contentX to -shift or similar
[14:02] <mzanetti> dandrader: I can look at that if you want
[14:03] <dandrader> mzanetti, oh, that's would be really great! \o.
[14:03] <dandrader>  \o/
[14:03] <mzanetti> ack
[14:03] <dandrader> mzanetti, ok, so I will leave the "make stage resizeable" task to you
[14:03] <mzanetti> ok
[14:06] <dandrader> mzanetti, added a task for you on https://blueprints.launchpad.net/ubuntu/+spec/client-1410-unity-ui-rotation
[14:06] <mzanetti> ack
[14:06] <Saviq> Cimi, we had a bug for scrolling velocity somewhere... can you remember where to find it?
[14:07] <Cimi> Saviq, it's on qt
[14:07] <Cimi> Saviq, I will ping you in 1 min
[14:07] <Cimi> chrome crashed
[14:07] <Saviq> Cimi, k
[14:07] <mzanetti> Saviq: uhh... that might still be mahattan iirc
[14:07] <mzanetti> manhattan even
[14:08] <Cimi> Saviq, https://bugreports.qt-project.org/browse/QTBUG-35608
[14:13] <Saviq> Cimi, we should have a UITK bug for that too
[14:13] <Cimi> Saviq, at this point, yes.
[14:13] <tsdgeos> we do, no?
[14:13] <tsdgeos> i think i opened one
[14:13] <Cimi> I think we have
[14:13] <Saviq> tsdgeos, show me!
[14:13] <tsdgeos> or maybe was about something else
[14:13] <Cimi> or qtubuntu
[14:13]  * tsdgeos digs
[14:14] <tsdgeos> Saviq: ah no, was about cacheBuffer (same thing but different)
[14:14] <tsdgeos> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1279264
[14:16] <Saviq> mzanetti, did that get included in UListView ↑?
[14:16] <mzanetti> Saviq: not in my branch, but I remember zsombor wanted to add that. let me check
[14:17] <mzanetti> Saviq: no, its not in there
[14:18] <Cimi> on my pc unity does not start with ./run.sh
[14:18] <Saviq> mzanetti, kthxbai
[14:18] <Cimi> how do I debug this?
[14:18] <Saviq> Cimi, look in ~/.cache/upstart/unity8.log
[14:18] <Cimi> cat: /home/cimi/.cache/upstart/unity8.log: No such file or directory
[14:18] <Cimi> cool
[14:18] <Saviq> or well... you should see any output in your terminal anyway...
[14:18] <Cimi> silence
[14:19] <Cimi> do I need indicators or so?
[14:19] <Cimi> it's a fresh install of trusty
[14:19] <Saviq> Cimi, ./build.sh -s ?
[14:19] <Saviq> Cimi, TRUSTY?
[14:19] <Saviq> Cimi, that's not supported for u8 dev
[14:19] <Cimi> Saviq, we don't need utopic now
[14:20] <Saviq> Cimi, yes we do
[14:20] <Cimi> Saviq, we can use sbuild or run on device
[14:20] <Saviq> Cimi, well, not for ./run
[14:20] <Cimi> correct
[14:20] <Saviq> Cimi, unless you make ./run.sh build in a chroot
[14:20] <Cimi> I'll run on device
[14:21] <Cimi> Saviq, friends told me utopic is crap now, I'll wait until it stabilises
[14:21] <Saviq> Cimi, "friends"? ;)
[14:21] <Saviq> Cimi, the whole team here works on utopic
[14:21] <Cimi> Saviq, some of our colleagues I am not mentioning :)
[14:22] <Saviq> paulliu, re: https://code.launchpad.net/~paulliu/unity8/fix-typo11/+merge/219536
[14:23] <Saviq> paulliu, prices are going away (replaced by attributes that you're implementing!), so probably no point merging that
[14:23] <paulliu> Saviq: ok. no prob
[14:23] <paulliu> Saviq: Yeah, I'm tracing the codes and found that.
[14:23] <paulliu> Saviq: So just ignore it.
[14:23] <paulliu> Saviq: i'll delete the mereg
[14:39] <tsdgeos> Saviq: fginther: any idea when qmluitests will be back?
[14:40] <fginther> tsdgeos, is this for unity8?
[14:40] <tsdgeos> fginther: yes
[14:41] <fginther> tsdgeos, sorry about that. I'll get back to working on this today. I'll keep you posted on progress
[14:42] <tsdgeos> Saviq: ping?
[14:44] <Saviq> tsdgeos, pong
[14:45] <tsdgeos> Saviq: so i had a look at the qt5.3 patch
[14:45] <tsdgeos> and it almost works
[14:46] <tsdgeos> i think that since it was thought to be for "extra" margins and not for removing
[14:46] <tsdgeos> we need a very small diff
[14:46] <tsdgeos> http://paste.ubuntu.com/7463083/
[14:46] <tsdgeos> that with some coercion i guess i could get upstream
[14:46] <tsdgeos> do you think it makes sense to try?
[14:49] <Saviq> tsdgeos, definitely
[14:49] <Wellark> mzanetti: silo9 is marked ready for publishing
[14:49] <tsdgeos> Saviq: oki, will work in that, i.e. some lobyiing and some tests .D
[14:50] <Saviq> Wellark, so before silo5?
[14:50] <mzanetti> Wellark: ack. I'll rebuild ours
[14:50] <mzanetti> Saviq: yeah, we're not quite there yet. found an issue while testing the silo
[14:50] <Saviq> mzanetti, kk
[14:50] <Wellark> Saviq: me and mzanetti agreed to make a race for it :)
[14:50] <tsdgeos> mterry: waht about the resize thing? any light?
[14:50] <mzanetti> congrats Wellark :D
[14:51] <mzanetti> you made the race
[14:51] <Wellark> well, it has not been published yet
[14:51] <Saviq> mzanetti, Wellark, I left a note for silo 009 to rebuild 002 and 005
[14:51] <mterry> tsdgeos, oh I didn't retry without it.  I'm sure it will work on the phone.  I think that was just for desktop, but apparently we have unity8 preview on desktop so that's already better?
[14:51] <Wellark> Saviq: thanks!
[14:51] <mterry> tsdgeos, I'll check now
[14:51] <mzanetti> Saviq: does that mean it happens automagically?
[14:52] <Saviq> mzanetti, no
[14:52] <Saviq> mzanetti, button needs pushing
[14:52] <mzanetti> ok
[14:52] <Saviq> Wellark, nice track record for bugs fixed on this silo ;)
[14:53] <Wellark> you have to merge lp:unity8 to the pending MR's once silo9 lands
[14:55] <Saviq> Wellark, we just need to push "build" for them
[14:55] <Saviq> Wellark, and that's the comment I left on the silo
[14:56] <Wellark> Saviq: ah, right.. I was mixing up the situation where someone has done a manual upload
[14:56] <Wellark> indeed. a rebuild should be enough
[14:56] <dandrader> mzanetti, that worked indeed http://paste.ubuntu.com/7463133/
[14:56] <mzanetti> dandrader: yeah, pretty much what I would have tried
[14:57] <mzanetti> dandrader: I think the contentX one would have been enough, but the others don't hurt in any case
[14:58] <dandrader> mzanetti, just copy-pasted from onFocusedApplicationIdChanged:
[14:58] <mzanetti> dandrader: right... that is here to hide the spread when a new app shows up
[14:58] <mzanetti> dandrader: do we want to hide the spread when rotating?
[14:58] <mzanetti> dandrader: if not you might want to conditionally do the contentX setting if phase == 0
[14:59] <mzanetti> I think it *should* be able to handle rotation while its on
[14:59] <dandrader> mzanetti, my idea is to add code to the stage to tell shell (via a property) when it can be rotated
[14:59] <mzanetti> didn't really try it though
[14:59] <mzanetti> ah ok. so we'd forbid rotating the shell while in spready
[14:59] <dandrader> mzanetti, ie, that it only "accepts" being rotated it on phase 0 (the app is fullscreen an now right-edge drag taking place)
[15:00] <dandrader> s/an now/and no
[15:00] <mzanetti> works for me I guess. in case design wants us to allow rotating while in spread, its worth a try to conditionally resetting contentX when phase == 0
[15:01] <Cimi> cyphermox, what did you tell me yesterday? I lost  the history
[15:02] <dandrader> mzanetti, I think it would be confusing to rotate while on spread, with some indicator down, right-edge dragging something (launcher, greeter)
[15:02] <mzanetti> dandrader: yeah sure... I think I agree (without actually having tried it)
[15:03] <Saviq> tsdgeos, we should probably also backport that patch to 5.2 to replace the one we were carrying, so that we can move to use the new API
[15:03] <Saviq> dandrader, mzanetti, I think we need to support rotation as long as the screen is "stable"
[15:03] <mzanetti> whatever that means :D
[15:04] <dandrader> hahaha
[15:04] <Saviq> mzanetti, i.e. when you're not touching it
[15:04] <mzanetti> ah
[15:04] <tsdgeos> Saviq: will need to update the other dashviews too
[15:04] <dandrader> Saviq, makes sense
[15:04] <tsdgeos> Saviq: i.e. vJournal, hJournal, organicGrid
[15:04] <Saviq> tsdgeos, indeed, we'll need a silo with a backport + our code port
[15:04] <tsdgeos> Saviq: but yes, makes sense
[15:05] <Saviq> tsdgeos, then we'll be 5.3 ready
[15:05] <Saviq> AFAICT
[15:08] <greyback> 5.3 has some renderer design changes that I'd like a lot
[15:09] <dandrader> greyback, what are they (in a concise way)?
[15:10] <greyback> dandrader: they added a private api QQuickRenderControl component, which I believe one can use to replace the built-in render loop
[15:11] <greyback> which would be handy for our integration with Mir, as Mir wants to be the render loop
[15:11] <dandrader> hmm
[15:11] <greyback> (it isn't right now, but I need to atttempt a redesign to do that)
[15:15] <dandrader> Saviq, resizing while in the spread will be laborious. we will have to resize apps one at a time to avoid choking the device
[15:15] <greyback> Saviq: have updated https://code.launchpad.net/~gerboland/unity-mir/fix-upstart-closed-apps2/+merge/218721 - would appreciate you giving it a second look
[15:15] <Saviq> dandrader, oh no, no resizing/rotating of actual apps until you focus them
[15:16] <dandrader> ie., for each app in spread: wake up app, resize app, suspend app
[15:16] <greyback> dandrader: that would be awful, no way could we do that
[15:16] <Saviq> dandrader, so no, we'll need some design feedback on how to deal with wrongly-orientated apps
[15:16] <dandrader>  I recall webos did exactly that :)
[15:16] <Saviq> dandrader, but it's the same for apps that only support a different orientation than we're currently in
[15:16] <dandrader> (resizing one at a time)
[15:17] <Saviq> dandrader, so yeah, we'll need a way to display apps in a different orientation than the spread is in
[15:17] <dandrader> Saviq, that's why I say: don't rotate while in the spread! :)
[15:17] <Saviq> dandrader, that's not a good solution IMO
[15:17] <dandrader> Saviq, at least not until we get some design for that
[15:17] <Saviq> dandrader, well, ok, sure
[15:21] <Saviq> mzanetti, oh, I just noticed, the phone right edge videos still show the panel being included with the app, is that something that was changed, or is that meant to be like this for maximized environments?
[15:22] <Saviq> mzanetti, on tablet apps seem to have an extension of their surface stretched upwards, which actually looks awful...
[15:23] <mhr3> tsdgeos, shouldn't all the custom Roles start with Qt::UserRole?
[15:23] <elopio> Saviq, kgunn: I've rescheduled the meeting for tomorrow. Please let me know if that works for you.
[15:24] <Saviq> elopio, yes, works for me
[15:25] <tsdgeos> mhr3: if you planned using them with "regular" QWidget itemviews, sure
[15:25] <tsdgeos> if not, well, doesn't matter much
[15:25] <Cimi> tsdgeos, ok I pushed carousel shadow
[15:25] <Cimi> tsdgeos, but I discovered other bugs
[15:25] <Cimi> tsdgeos, not sure who introduced them and when
[15:25] <alecu> hello....
[15:26] <alecu> is there any special way to run unity8 inside an lxc?
[15:26] <Cimi> tsdgeos, so it's fine for now but we need to file bugs
[15:26] <tsdgeos> Cimi: which bugs?
[15:27] <mzanetti> Saviq: no, design didn't want to have the panel in the app surface
[15:27] <mzanetti> Saviq: seems a mistake in the animation, but Martin left so noone updated that
[15:28] <Cimi> tsdgeos, flicking on my music carousel
[15:28] <Cimi> tsdgeos, the black frame with the text does not always appear
[15:28] <tsdgeos> Cimi: can you reproduce that without my patch?
[15:28] <tsdgeos> er
[15:28] <tsdgeos> without your patch
[15:29] <Cimi> tsdgeos, my patch does not touch this
[15:29] <tsdgeos> Cimi: it touches card creation
[15:29] <Cimi> but trying
[15:30] <kgunn> elopio: wfm, will it really be 30 minutes?
[15:31] <Cimi> tsdgeos, maybe it's your patch :)
[15:31] <Saviq> mzanetti, ok good
[15:31] <tsdgeos> Cimi: maybe it is :)
[15:31] <Cimi> tsdgeos, some extra bindings
[15:31] <Saviq> alecu, hey, xnox was looking into that recently, to be able to run the utopic unity8 desktop session on LTS
[15:31] <Cimi> tsdgeos, I can reproduce it with my carousel branch
[15:32] <Saviq> alecu, but I'm not sure how far that got
[15:32] <Cimi> tsdgeos, but I have latest dynamic creation cards
[15:32] <alecu> Saviq: thanks
[15:32] <Saviq> Cimi, they were only meant to be visible for the "focused" item
[15:33] <Saviq> Cimi, granted, we could use a fade-in/out
[15:33] <Cimi> Saviq, item is zoomed
[15:33] <Cimi> Saviq, but they are not displayed here
[15:33] <Cimi> not always
[15:33] <Cimi> after a flick
[15:33] <tsdgeos> Cimi: well if you know which extra bindings are wrong the patch is cool :)
[15:33] <tsdgeos> Cimi: or you say your branch only adds some extra bindings?
[15:33] <Saviq> Cimi, indeed, confirmed
[15:33] <Cimi> Saviq, could be something recent
[15:33] <Cimi> Saviq, not happening with
[15:33] <Saviq> Cimi, it looks like they don't get "you're focused" reliably enough
[15:34] <Cimi> Saviq, 7.86+14.10.20140507.3-0ubuntu1
[15:34] <Cimi> Saviq, that is fine
[15:35] <Cimi> Saviq, my carousel-shadow (that is like trunk with a small shadow) has it
[15:35]  * Cimi bets with new dinamic cards
[15:35]  * greyback realized he forgot lunch, has gone to eat
[15:36] <elopio> kgunn: well, we will have to make it fit in 30 minutes because that's the only space I found on your thursday.
[15:36] <elopio> if it's not enough, we can leave some discussions to malta.
[15:37] <tsdgeos> greyback: may has well have dinner ^_^
[15:39] <cyphermox> Cimi: I have a dnsmasq package you might want to try for your wifi issues, but only if the problem is that everything looks fine (signal looks okay, nm says it's connected)
[15:49] <Saviq> o/
[15:52] <kgunn> Saviq: just fyi...i only proposed this
[15:52] <kgunn> https://code.launchpad.net/~albaguirre/unity8/use-new-display-power-state-interface/+merge/219552
[15:52] <kgunn> for some pre-flight testing in a silo
[15:52] <kgunn> i'm also asking for it not to block
[15:57] <dednick> Saviq: do you know what happens when a Qt app receives SIGTERM? does it quit gracefully or just bomb out?
[15:59] <dednick> Saviq: or rather, do you know if there is a signal we can send a qt app to exit gracefully?
[16:05] <Cimi> tsdgeos, is the dyinamic cards?
[16:05] <tsdgeos> Cimi: i don't know i have not checked,
[16:05] <tsdgeos> i thought you were
[16:05] <Cimi> tsdgeos, I was in a meeting
[16:05] <Cimi> I can check now
[16:06] <tsdgeos> please :)
[16:06] <tsdgeos> i'm eod'ing anyway
[16:07] <tsdgeos> Cimi: send me an email/bug if you find something
[16:07]  * tsdgeos waves
[16:08] <Cimi> cyphermox, now is fine, keep it or send me a mail with the link pls :)
[16:09] <greyback> dednick: I don't think Qt listens for signals like SIGTERM by default
[16:09] <Cimi> Saviq, albert branch introduced the carousel issue
[16:16] <Cimi> Saviq, you know how is this overlay called?
[16:17] <Cimi> trying to debug the js
[16:19] <Cimi> overlay seems like :)
[16:20] <greyback> dednick: actually, now I'm not so sure. I launched a simple Qt app, then kill -SIGTERM -ed it, and it stopped
[16:20] <dednick> greyback: yeah, mir has some shizzle for it.
[16:21] <greyback> dednick: so I'm presuming that libg++ handles it then
[16:21] <greyback> dednick: that it does
[16:21] <dednick> greyback: ah. right. the app does exit, but not cleanly (ie it doesnt go through proper mir shutdown etc. But mir picks up a socket error apparently
[16:22] <greyback> dednick: are you trying to stop unity8?
[16:22] <dednick> greyback: no, trust session participants
[16:23] <greyback> dednick: they are clients of Mir, not mer servers themselves I guess
[16:23] <dednick> greyback: i think it's something to do with the new socket work alan put in. The mir sessions aren't getting closed. He's going to take a look tomorrow.
[16:23] <greyback> ok
[17:08]  * greyback eod
[18:02] <xnox> Saviq: one cannot cross-build anything that does gobject-introspection at the moment.
[18:02] <xnox> Saviq: or one needs to disable gobjects bindings / gir-* which then makes the build half useless.
[19:19] <darklight_> is there someone only who's maintaining unity 7 ?
[19:23] <bschaefer> darklight_, yes
[19:24] <darklight_> bschaefer, can I bother you with this https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1305438 ? it's really annoying, it's a regression from 12.04 for those used to that functionality and it hopefully should be trivial to fix
[19:28] <bschaefer> darklight_, hmm I just set show desktop to bottom left and it worked
[19:29]  * bschaefer is assuming thats what the hot corners are
[19:29] <bschaefer> darklight_, i've not used them that much to be honest, but i can see if someone else knows about it
[19:30] <darklight_> bschaefer, try to restart the unity session, log off and log back in, also I don't remember which but there one hotcorner at the bottom that works fine the others are "forgotten" after every session, from my testing disabling the capture  mouse option for unity in compiz  made things better but there were still triggers (eg, updating or installing a package 90% of the time recreated the issue)
[19:32] <bschaefer> darklight_, i see, thats no good!
[19:33] <darklight_> bschaefer, I also tried other suggestions I found around for past releases like changing the order in which the plugins are loaded and while it worked then the meta+w or meta+s shortcuts made unity crash
[19:33] <bschaefer> darklight_, we'll try to reproduce it and check it out
[19:33] <darklight_> bschaefer, that'd be awesome, it's something "stupid" but that's keeping me off unity for now :\
[19:34] <bschaefer> darklight_, yeah, regressions are no fun :(, sorry!
[19:34] <bschaefer> darklight_, and its only hotkeys that are being forgotten?
[19:34] <bschaefer> err
[19:34] <bschaefer> hot corners
[19:35] <darklight_> bschaefer, yep, as a test you can try and set them in unity tweak tool you'll notice when they're forgotten that they still look activated from there but in fact they are not, disabling and enabling them again fixes the issue but only for the session
[19:35]  * bschaefer has never used unity tweak
[19:35] <darklight_> personally I've tried the expo and scale hotcorners if it matters which  ones but I suspect it's the same with all of them
[19:35] <bschaefer> darklight_, but i should still be able to reproduce this outside of unity tweak?
[19:36] <darklight_> bschaefer, absolutely just use the compiz settings manager
[19:37] <bschaefer> darklight_, cool
[19:39] <darklight_> fyi it's been broken in 13.10 too and possibly 13.04, or so some google searches say
[19:40] <bschaefer> shoot, yeah i dont use hot corners so its hard for me to run into that bug :(
[19:43] <darklight_> actually I'm pretty sure that if you want to do some testing just running a unity --replace or equivalent should trigger it without logging off
[19:44]  * bschaefer tests
[19:45] <bschaefer> darklight_, still set :(
[19:45] <bschaefer> darklight_, ill have to try the reboot a bit later
[19:45] <bschaefer> to many things open atm to close it all :)
[19:45] <darklight_> bschaefer, try setting it on one of the top corners
[19:45] <bschaefer> i have it set to TOP
[19:45]  * bschaefer tries a corner
[19:46] <darklight_> you could try one of my specific ones , scale and expo set right and left
[19:46] <darklight_> top corners
[19:46] <bschaefer> all still working
[19:47] <darklight_> mmmm either it's been fixed or it needs to restart the session , I'm not on unity right now, let me grab a live usb key I'll do some tets
[19:47] <bschaefer> alright, im on 14.10, using trunk unity/compiz/nux sooo
[19:47] <bschaefer> actually just using trunk unity atm
[19:48] <darklight_> oh so it might be that too
[19:48] <bschaefer> but ill try a reboot later, and ill get ChrisTownsend to test it when he gets a chance as well :)
[19:50] <ChrisTownsend> bschaefer: darklight_: The only Compiz change I can think of that *might* fix this is the recent SRU where I fixed the integers values in Compiz Config from being displayed correctly.  When that was broken, I did notice times where int values could get clobbered.
[19:51] <bschaefer> ChrisTownsend, that does make sense, as ive no clue how the hot corners are stored under the hood
[19:51]  * bschaefer would assume an enum
[19:51] <ChrisTownsend> bschaefer: Right, I'm just guessing.
[19:51] <bschaefer> ChrisTownsend, yeah, has that made it into 14.04?
[19:52] <ChrisTownsend> bschaefer: yes
[19:52] <bschaefer> sweet, like last week
[19:52] <bschaefer> ?
[19:52] <ChrisTownsend> bschaefer: Last week or the week before.
[19:52] <darklight_> I'm making a fresh install on my laptop, give me a few minutes and I'll be at your command to run some tests  :)
[19:52] <ChrisTownsend> darklight_: Ok, just make sure you pull in all the updates and then we'll see.
[19:53] <darklight_> sure
[19:53] <bschaefer> last comment 6th and someone confirmed it on the 11th... sooo hopefully that didn't have that :)
[19:54] <ChrisTownsend> bschaefer: I'm not holding my breath:)
[19:54] <bschaefer> ChrisTownsend, haha, ill do it for both of us
[19:55] <ChrisTownsend> bschaefer: heh
[19:55]  * bschaefer has passed out
[20:20] <darklight_> installing the updates
[20:37] <darklight_> bschaefer, ChrisTownsend I'm rebooting and I'm ready to test
[20:46] <darklight_> bschaefer, ChrisTownsend I can reproduce it by rebooting
[20:46] <darklight_> I tried loggin off and on again it still worked, I tried installing something it still worked, I rebooted and the hotcorners don't work anymore
[20:47] <darklight_> they are set in the compiz settings though
[20:48] <ChrisTownsend> darklight_: Ok, thanks.  I'll keep this on my radar, but at least I know a reboot is what is needed to clobber the settings.
[20:49] <darklight_> ChrisTownsend, thanks looking forward to a fix :)
[20:49] <ChrisTownsend> darklight_: heh, I'll try my best:)
[20:51] <darklight_> ChrisTownsend, my opinion is the unity plugin in compiz takes over event and since it's the last one to be loaded or something like that it shows after a reboot, as I told bschaefer I remember disabling launcher capture mouse made things better
[20:51] <darklight_> oh and I just noticed my keyboard shortcuts have not been kept either but for a few
[20:51] <darklight_> this I really can't explain
[20:52] <darklight_> I changed how to switch workspace and close/minimize windows and toggle maximization, the only ones that have been kept are the switch workspace ones
[20:52] <ChrisTownsend> darklight_: Yeah, I think *something* is clobbering many settings, not just hot corners.  This is pretty bad, so I'll make it a higher priority to begin looking at this.
[20:52] <darklight_> that's probably even more serious than the hotcorners
[20:52] <darklight_> ok :)
[20:53] <ChrisTownsend> darklight_: Thanks for the info
[20:53] <darklight_> no problem , you're the ones who do all the work and the heavy lifting at the end of the day :)
[20:56]  * bschaefer reads scrollback
[20:56] <bschaefer> ChrisTownsend, were yo uable to reproduce?
[20:57] <bschaefer> urg i have this weird memory of a problem with remember compiz settings changes after a reboot...
[20:57] <ChrisTownsend> bschaefer: No, I haven't tried since my machines are tied up on other things at the moment.  I'll just put this next on my queue of things to work on.
[20:57] <bschaefer> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/964270
[20:57] <bschaefer> possibly that?
[20:58] <bschaefer> there was one by mc return as well...
[20:58] <bschaefer> a bit ago...
[20:58] <ChrisTownsend> bschaefer: I've been planning on looking at the reset keyboard shortcuts issue.
[20:58] <bschaefer> ChrisTownsend, cool, i think thats the real issue
[20:58] <ChrisTownsend> bschaefer: There have been many of those issues reported recently with activity in different bugs.  It's pretty important at this point.
[20:58] <ChrisTownsend> bschaefer: Yep, I think so too.
[20:59] <bschaefer> ChrisTownsend, i agree
[20:59] <ChrisTownsend> bschaefer: I'll look at this next when I either fix the jumping windows or get tired of debugging that:)
[20:59] <bschaefer> yeah
[20:59] <bschaefer> ChrisTownsend, sweet :)
[20:59] <bschaefer> its been a while since i've done compiz work at this point...
[20:59] <ChrisTownsend> bschaefer: Be thankful;-)
[20:59] <bschaefer> ChrisTownsend, let me know if you need some help! (I've to get ready for malta...)
[20:59] <bschaefer> i am
[20:59] <bschaefer> very
[21:00] <bschaefer> ChrisTownsend, getting some of these things packaged up...
[21:00] <bschaefer> ChrisTownsend, turns out im back at packaging haha