[01:01] <d_ken> looking for a working solution to get unity back online with geforce 210
[01:02] <d_ken> I tried at least 6 or 7 different approaches so far
[01:02] <d_ken> ubuntu 12.10
[01:44] <Guest88134> Does anyone here know what the specific config files are for both of the Panels and the window decorations for Unity?   I have had temporary success moving different folders out of ~/.config
[01:45] <Guest88134> I am having issues with no Unity panels and window decorations....
[01:50] <Guest88134> I have absolutely no Unity panels, and no window decorations ( I can open a terminal using Ctrl+Alt+T to run the command gnome-session-quit).
[01:53] <duflu> Guest88134: That usually means you're missing the decor and unityshell plugins. Try running ccsm and tick the boxes to enable them.
[02:00] <Guest88134> duflu: well... this is a bit more complicated I suppose.... I am running LTS fine and Raring is missing the panels, etc.... I have tried ccsm, and unity-tweak-tool.... but to no avail.  my testing user has everything.
[02:01] <Guest88134> there is something wrong with the way raring reads the config files.  I am using the same ~/ for both installations
[02:01] <duflu> Guest88134: OK, I have a simple command for literally deleting all compiz/unity customisations from your config. Let me try and find it
[02:02] <Guest88134> duflu: thanks.... is there a way to make Raring use its own config files somewhere else other than the ~/.config /<whatever>?
[02:03] <duflu> Guest88134: Since quantal, the config has been in gsettings. That's a binary database you can't edit by hand. Let me try to find the old command
[02:03] <duflu> I mean, gsettings uses "dconf", which is a binary database
[02:05] <Guest88134> duflu: Ok... so are you saying I CAN use dconf editor to make Raring use something... all the while LTS will use something else?  or are you saying something entirely different...
[02:05] <duflu> Guest88134: For quantal/raring: dconf reset -f /org/compiz/
[02:06] <duflu> Guest88134: For precise, it was gconf (different tools)
[02:06] <Guest88134> duflu: ok... I kept trying to do stuff like compiz --replace unity --replace  unity --reset, etc... until it would lock up.
[02:07] <duflu> Guest88134: That dconf reset will just delete all compiz/unity customisations. And you will get the default setup like Guest does
[02:07] <Guest88134> So Precise shouldn't be effected by this??
[02:07] <duflu> No, precise used gconf :(
[02:07] <duflu> Potentially similar problems, but different commands
[02:10] <Guest88134> duflu: cool thanks, precise has been fine.... I will test this and I'll come back and tell you if something went awry
[02:21] <love_> duflu: OK... I'm back... last time my name was Guest88134.  That did not work.  I did reboot and check and my precise install is still working just fine.
[02:21] <duflu> love_: OK then please take a copy of ".xsession-errors" and put it in a new bug report on Launchpad :(
[02:22] <duflu> That file is in your home directory. Remember to copy it _while_ you're logged in
[02:22] <love_> duflu: I did start a bug... I'll attach the file thanks.
[02:24] <love_> duflu:  Oh... look at this... I/O warning : failed to load external entity "/home/love/.compiz/session/</*random alpha numerics*/>"
[02:25] <duflu> love_: It's likely not the cause because those errors are common. But you should be able to safely delete the .compiz directory too. That might be part of the issue
[02:26] <love_> I have done that before to temporarily fix it...... I am just wondering if there could be a workaround....
[02:26] <duflu> The ~/.compiz dir only causes problems if you're been compiling your own compiz plugins
[02:27] <duflu> love_: Deleting that plus the dconf reset may be the fix
[02:27] <love_> nope... I don't even use the cube or any of that anymore.... either unity w/ compiz of Lxde with xcompmgr for the transparent terminal
[02:27] <love_> duflu: Ok. I will try that and let you know
[02:38] <love_> duflu: nope. I guess I will go fishing with my bug report....  thanks for the help, though!!!
[02:38] <duflu> love_: No problem. What bug number?
[02:40] <love_> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1128348
[02:40] <love_> duflu: it took me a bit to find it...
[02:42] <duflu> love_: Please attach the .xsession-errors
[02:43] <love_> duflu: in the process.... I had to rename it so I could find it in the attachments dialog
[03:06] <love_> duflu: did you have a chance to look at it yet?
[03:06] <duflu> love_: Not yet but soon
[03:07] <love_> duflu: ok thanks :)
[03:37] <duflu> love_: If that log file came from raring then your problem is that you've somehow made compiz start using gconf instead of gsettings
[03:37]  * duflu boots raring to double check it's still gsettings
[03:39] <love_> duflu: the other file didn't have anything in it except stuff about this current LXDE session.... I can logout, and log into Unity... then logout and check that...
[03:40] <duflu> love_: I'll move the discussion to the bug and add comments there
[03:41] <love_> Ok... that will be easier.  I need to do something else in a little bit... so I will check this out and post in the bug report if I find a different error file...
[06:48] <didrocks> hey mmrazik
[06:48] <didrocks> mmrazik: I got a question on https://code.launchpad.net/~unity-team/libunity/libunity-7.0
[06:48] <didrocks> mmrazik: seems that rev336 was merged by the server
[06:48] <didrocks> merger*
[06:48] <didrocks> however, in todays' daily build: https://launchpad.net/~ubuntu-unity/+archive/experimental-prevalidation/+build/4389883/+files/buildlog_ubuntu-raring-i386.libunity_6.91.4%7Edaily13.03.22ubuntu.unity.experimental.certified-0ubuntu1_FAILEDTOBUILD.txt.gz
[06:49] <didrocks> the symbol check is normally exported in debian/rules
[06:49] <didrocks> I'm puzzled how it passed, even if your env wasn't correct in the merger, it shouldn't :/
[06:49] <mmrazik> let me find the jenkins job
[06:50] <didrocks> yeah, build logs would be useful to understand what happens
[06:51] <mmrazik> didrocks: https://jenkins.qa.ubuntu.com/job/unity-team-libunity-libunity-7.0-raring-amd64-autolanding/12/console
[06:52] <didrocks> mmrazik: dpkg-gensymbols: warning: debian/libunity9/DEBIAN/symbols doesn't match completely debian/libunity9.symbols
[06:52] <didrocks> this should have failed the build
[06:52] <didrocks> we are doing export DPKG_GENSYMBOLS_CHECK_LEVEL = 4
[06:52] <didrocks> in debian/rules
[06:52] <didrocks> are you override that by any chance?
[06:52] <mmrazik> oh...
[06:53] <mmrazik> I might
[06:53] <mmrazik> I copy and pasted this without really understanding if if it is needed and for what
[06:53] <mmrazik> let me check
[06:53] <didrocks> I still don't get it
[06:53] <didrocks> it's in debian/rules
[06:53] <mmrazik> didrocks: it probably overrides debian/rules
[06:53] <didrocks> so normally, it has higher priority and overwrite your env settings
[06:53] <didrocks> ah?
[06:54] <mmrazik> didrocks: yeah... it does. Let me remove that hook completely.
[06:54] <mmrazik> sorry for that
[06:54] <didrocks> mmrazik: yes please, remove it everywhere :)
[06:54] <mmrazik> should have checked with fginther
[06:55] <didrocks> no worry!
[06:55] <didrocks> glad we understand at least why :)
[06:55] <didrocks> I was thinking about a direct push to trunk at first
[06:55] <didrocks> mmrazik: I was doing that when we didn't have the packaging inlined
[06:56] <didrocks> as we didn't force to update in sync
[06:56] <mmrazik> I see
[06:56] <didrocks> now that we are inlined, I'm doing the other way and forcing to be synced :)
[07:48] <mhr3> didrocks, i have branch that updates the symbols
[07:51] <didrocks> mhr3: already in trunk, with bumping the changelog (I had to move it fast)
[07:52] <didrocks> mhr3: should have been in sync, but didn't because of the above issue. Anyway, fixed now :)
[07:52] <mhr3> didrocks, you pushed directly to trunk?! bad didrocks! :P
[07:53] <didrocks> mhr3: had to unblock it, that's when we need to take actions sometimes :)
[07:53] <didrocks> mhr3: and I bzr bd locally :p
[07:53] <didrocks> (contrary to others, hem :p)
[07:54] <didrocks> mmrazik: do you mind looking at ps-unity-100scopes-experimental-autopilot-release-testing/?
[07:54] <didrocks> mmrazik: both ati and nvidia failed
[07:54] <mmrazik> didrocks: looking (but have a call in 5 mins)
[07:55] <didrocks> ssh: connect to host dx-autopilot-ati port 22: Connection refused
[07:55] <didrocks> mmrazik: let me rerun
[08:44] <mzanetti> hey ho
[08:48] <popey> hmm, compiz crash with experimental ppa updated today
[08:49]  * popey tries to reproduce
[08:49] <popey> yup
[08:50] <seb128> popey, stacktrace?
[08:50] <popey> gnome-session[2705]: WARNING: Application 'compiz.desktop' killed by signal 11
[08:50] <popey> yeah, will do
[08:55] <popey> seb128: http://paste.ubuntu.com/5636377/
[08:55] <seb128> mhr3, ^
[08:55] <mhr3> dednick, ^
[08:56] <seb128> mhr3, thanks ;-)
[08:56] <popey> ping me if you need anything else from it
[08:56] <mhr3> dunno why some computers don't like null pointers that much
[08:56] <mhr3> :P
[08:57] <dednick> stupid computers
[08:58] <popey> lets scrap null pointers, they're overrated
[08:58] <dednick> mhr3: you putting null pointers in the scope keyword list? ...
[08:58] <Saviq> tsdgeos, https://code.launchpad.net/~unity-team/unity/phablet.build-hud-deps/+merge/154889
[08:59] <mhr3> dednick, are we?
[08:59] <tsdgeos> Saviq: what was the problem you were having?
[08:59] <mhr3> isn't just the keywords array null?
[08:59]  * dednick shrugs
[08:59] <Saviq> tsdgeos, must have been VM
[08:59] <tsdgeos> okidoki
[08:59] <Saviq> tsdgeos, built fine in chroot
[09:00] <dednick> mhr3: the stacktrace seems to be compaining about string. and assumingly g_slist_next wouldnt return a valid pointer when operating on a null list.
[09:00] <dednick> but that's just assuming
[09:00] <tsdgeos> oh
[09:01] <dednick> i'll check for it anyway
[09:01] <tsdgeos> we have a raring autolander?
[09:02] <tsdgeos> something's wrong :D
[09:02] <tsdgeos> dependencies most probably
[09:02] <tsdgeos> Saviq: mzanetti: https://jenkins.qa.ubuntu.com/job/unity-phablet-raring-armhf-autolanding/1/console
[09:03] <mzanetti> tsdgeos: hmmm...
[09:04] <mzanetti> tsdgeos: yeah... sergio enabled raring all over the place yesterday
[09:04] <tsdgeos> ok :D
[09:04] <mzanetti> tsdgeos: of course all hell broke loose
[09:05] <mhr3> dednick, where did you get that it's keywords though? i don't see full bt there
[09:05] <tsdgeos> mzanetti: so we need some debian packaging massaging to get this working?
[09:06] <Saviq> tsdgeos, I imagine it installs *unity from raring :/
[09:07] <Saviq> yeah "libunity9 armhf 6.90.2daily13.03.06.1-0ubuntu1"
[09:07] <Saviq> and "libunity-core-6.0-5 armhf 6.12.0daily13.03.20-0ubuntu1"
[09:07] <mzanetti> tsdgeos: yep... we also have issues in the way we package autopilot tests (shell and apps)... need to fix that now. if you could try to fix the unity dep it'll be great
[09:08] <Saviq> I wonder what can we do to stay on top of that...
[09:08] <mzanetti> Saviq: rename the package
[09:08] <mzanetti> and install it somewhere else
[09:08] <mzanetti> or merge back
[09:08] <mzanetti> somehow
[09:08] <tsdgeos> mzanetti: i'm the worst person to fix that stuff, my .deb knowledge is →←
[09:09] <mzanetti> tsdgeos: well, make it two.... I guess the issue is more that the correct libs are not yet released
[09:09] <mzanetti> tsdgeos: so not really a packaging issue but more a releasing order thing I guess
[09:09] <tsdgeos> i'd vote for "version number"
[09:10] <tsdgeos> i mean in quantal is using
[09:10] <tsdgeos> libunity9_6.12.0-0ubuntu0.1phablet3~quantal1_armhf.deb
[09:10] <tsdgeos> while in raring is using
[09:11] <tsdgeos> libunity9_6.90.2daily13.03.06.1-0ubuntu1_armhf.deb
[09:11] <dednick> mhr3: it seems to be the only string not protected by a null check
[09:11] <tsdgeos> so your phablet version "loses"
[09:11] <tsdgeos> s/your/our
[09:12] <mhr3> dednick, it might not even be that method if something got inlined :)
[09:13] <tsdgeos> Saviq: do you happen to know what are the differences we need in libunity?
[09:13] <Saviq> tsdgeos, PeoplePreview for the most part
[09:13] <Saviq> tsdgeos, in both libunity and unity-core
[09:14] <tsdgeos> Saviq: too much work to "properly merge"?
[09:15] <Saviq> tsdgeos, to merge upstream? probably, and then upstream is already working on the smart scopes rework...
[09:16] <mhr3> dednick, looking at the code we add string only if they're length > 0, so definitely no nulls
[09:16] <mhr3> *add strings only if their....
[09:16] <tsdgeos> Saviq: ok, so we find a different way to fix this
[09:16] <Saviq> tsdgeos, yeah, we need to
[09:16] <tsdgeos> mzanetti: Saviq: is shutting down the raring autolander out of scope?
[09:17] <Saviq> tsdgeos, the build is going to switch to raring soon enough
[09:17] <dednick> mhr3: std::string value(static_cast<gchar*>(v->data);
[09:17] <dednick> cannot construct a string with null. will pop in strlen (which it does in the stack trace)
[09:17] <tsdgeos> ok, so we need a fix :D
[09:17] <Saviq> tsdgeos, so we should probably think about actually fixing it
[09:18] <mhr3> dednick, hmm, look fine
[09:18] <mhr3> s
[09:18] <mhr3> wow, i need coffee
[09:18] <mzanetti> tsdgeos: yep... sergio wouldn't enable it just for fun... we really need to fix stuff
[09:19] <tsdgeos> mzanetti: the phablet-ppa is there for the autolanders to use i understand, no?
[09:19] <mzanetti> tsdgeos: yes
[09:21] <tsdgeos> so yeah, we just need to fix the " 	6.12.0bzr213raring0 (Newer version available) " that shows up in https://launchpad.net/~phablet-team/+archive/ppa
[09:21] <tsdgeos> trivial fix is just increasing the vNumber with no merge or anything
[09:21] <tsdgeos> Saviq: does this ↑↑ work?
[09:23] <Saviq> tsdgeos, briefly, I'd say... problem is libunity is used by "the other side", too (i.e. scopes)
[09:23] <tsdgeos> hmmm
[09:23] <tsdgeos> sooooo? :D
[09:24] <mzanetti> Saviq, tsdgeos: any of you might have an idea why this fails in raring ppa builders? https://pastebin.canonical.com/87511/
[09:24] <mzanetti> doing the same call from a bash script works. seems to be cmake related
[09:24] <dednick> popey: you just using standard ppa? does it always pop?
[09:24] <Saviq> mzanetti,
[09:24] <Saviq> mzanetti, build-dep python
[09:25] <Saviq> mzanetti, not python2.7
[09:25] <Saviq> mzanetti,
[09:25] <Saviq> https://code.launchpad.net/~saviq/indicators-client/fix-raring-build/+merge/153447
[09:25] <Saviq> for example
[09:25] <mzanetti> Saviq: thanks... I still wonder why I can't reproduce here
[09:25] <Saviq> mzanetti, because you have "python" installed
[09:26] <Saviq> mzanetti, and not just "python2.7"
[09:26] <popey> dednick: "standard ppa"? I'm using the experimental 100scopes one
[09:26] <popey> dednick: http://paste.ubuntu.com/5636433/
[09:26] <Saviq> mzanetti, sbuild proved useful to debug that
[09:26] <mzanetti> but if I do a dpkg -S on that import file, it say its in python-distutilslib (or something like that) and according to the build log that one is pulled in by pathon2.7 too
[09:27] <dednick> popey: ta
[09:28] <Saviq> didrocks, can we have you for 10 minutes please?
[09:28] <didrocks> Saviq: in 30 minutes?
[09:28] <Saviq> didrocks, works
[09:28] <didrocks> Saviq: like, I'm in a hangout in 2 minutes :p
[09:29] <didrocks> will ping you back then ;)
[09:29] <Saviq> thanks
[09:29] <popey> dednick: yes, it always pops
[09:46] <Saviq> dednick, hey, where did "If you’ve installed all the qml plugins to local folders (not in the QML_INSTALL_IMPORT path) you may need to instruct qtcreator where to find the plugins." come from? did you have that issue?
[09:47] <dednick> Saviq: i did in qt creator. it doesnt seem to know about the ./plugins folder. This was just for qtcreator to be able to resolve the sybols
[09:48] <Saviq> dednick, k I thought it was about something external to lp:unity/phablet
[09:49] <dednick> Saviq: nope. nothing to do with building/running. only local to qtcreator
[09:51] <Saviq> dednick, sorry for my ignorance, but where in QtCreator did you set the path? :D
[09:53] <dednick> Saviq: in the qmlproject file. there is a importPaths key. (we should probably actually set this in lp:unity/phablet)
[09:53] <Saviq> dednick, ah
[09:53] <Saviq> dednick, yup
[09:54] <didrocks> Saviq: available now!
[09:54] <Saviq> didrocks, hangout?
[09:55] <didrocks> Saviq: sure ;)
[09:55] <didrocks> just paste a link
[09:56] <Saviq> didrocks, https://plus.google.com/hangouts/_/581ff53bd4b4a1c0d9070050e50e7eb484fd4856
[09:56] <Saviq> mzanetti, tsdgeos, you might want to join in, too
[09:56] <Saviq> if you can
[09:56]  * tsdgeos tries
[10:05] <Saviq> didrocks, will the smart scope *unity get bumped to version 7, though?
[10:05] <didrocks> Saviq: probably, I'm not 100% sure we should and the impact TBH
[10:05] <didrocks> Saviq: but use 7.80
[10:06] <Saviq> didrocks, ok, thanks
[10:06] <didrocks> Saviq: we'll make sure S will inline, even if we don't bump to 7 ;)
[10:08] <tsdgeos> Saviq: you doing it, right?
[10:08] <Saviq> tsdgeos, yeah
[10:08] <tsdgeos> good
[10:09] <mzanetti> Saviq: https://code.launchpad.net/~mzanetti/unity/phablet-fix-python-dep/+merge/154898
[10:10] <dednick> Saviq: fyi. working on 100scopes again. need to get some bugs sorted, then need to fix autopilot tests. probably wont get anything on UnityNext today again...
[10:10] <Saviq> dednick, k
[10:17] <Saviq> tsdgeos, can you add "plugins" to importPaths in the .qmlproject file?
[10:18] <tsdgeos> Saviq: i'm not using qtcreator, maybe makes sense for someone else to? mzanetti?
[10:18] <Saviq> tsdgeos, ah k
[10:18] <Saviq> tsdgeos, what are you using?
[10:18] <tsdgeos> poor's man text editor
[10:18] <tsdgeos> kate
[10:19] <mzanetti> tsdgeos: you're not using qtcreator? thats the best piece of IDE ever made :D
[10:19] <mzanetti> ok... I use kate quite often too
[10:20] <Saviq> mzanetti, approved
[10:20] <mzanetti> cheers. your's too :D
[10:21] <Saviq> sbuild + shm = speed!
[10:21] <Saviq> ==, even!
[10:21] <mzanetti> regarding the .qmlproject file... dunno. I never used them... always go for qmake or cmake directly as I never have qml only stuff
[10:30] <MCR1> sil2100, Mirv: Hi. I've backported the grid-top-left-corner-miscalculation-fix to compiz/raring, please approve it: https://code.launchpad.net/~mc-return/compiz/compiz-raring.merge-fix1139835-grid-wrong-top-left-corner-calculation/+merge/154899
[10:40] <MacSlow> tvoss, regarding testing... are we meant to test pure interfaces too? I thought just real implementations need to be tested. Just wondering about your comment on an MR.
[10:42] <tvoss> MacSlow, I do see implementation in the MR :)
[10:42] <MacSlow> tvoss, touché :)
[10:48] <sil2100> Woha!
[10:48] <sil2100> What happened to MCR1?
[10:52] <MacSlow> Saviq, tvoss: you should be happy now with https://code.launchpad.net/~macslow/unity/phablet-bootstrap-notification-structure/+merge/154748
[11:01] <mzanetti> MacSlow: I just read through this. It looks quite good but I'd like to ask you to adapt Qt coding style a bit more for Qt code
[11:01] <mzanetti> MacSlow: also, instead of marking every signal with Q_SIGNAL its common to use a "signals:" section
[11:02] <mzanetti> MacSlow: whereas Q_INVOKABLE methods with void return value should mostly be declared as "slots:"
[11:03] <mzanetti> MacSlow: for class Notification I'd prefer signals: and slots: instead of using the Q_KEYWORDS for a hundret times
[11:04] <mzanetti> MacSlow: also, include own headers before the Qt ones (to avoid some conflicts where std stuff breaks Qt makros in some rare cases)
[11:05] <MacSlow> mzanetti, ok thx
[11:06] <tvoss> mzanetti, signals: and slots: is a bad idea, it clashes with a lot of things from the c++ std-library
[11:07]  * mzanetti is using signals and slots for 8 years now and it clashed once with a bluetooth stack that had a variable called signals
[11:07] <tvoss> mzanetti, did you use boost::signals recently? :)
[11:08] <MacSlow> so I leave Q_* as is?
[11:08] <mzanetti> tvoss: no... if mixing boost it might be different... I don't consider that c++ std-library tho
[11:08] <tvoss> mzanetti, fair enough, but I would think that boost::signals might well flow somewhere in the codebase
[11:09] <mzanetti> MacSlow: just saying... its more common in the qt world to use the signals: and slots: notation
[11:09] <mzanetti> MacSlow: and I agree with tvoss that there are cases where it can conflict... as long as you don't include boost stuff yourself I see chances quite low tbh
[11:10] <MacSlow> mzanetti, I rather go the safe (more change-proof) way then and leave it as it is now
[11:11] <mzanetti> MacSlow: fine with me... you will notice that all the other Qt code "looks different" though  :D
[11:12] <MacSlow> mzanetti, yeah... but then I've seen both ways
[11:19] <dednick> popey: can you try dist-upgrade your experimental ppa again? looks like there is a new verison of unity in there. I reproduced with the one you had, but seems to have been fixed...
[11:19] <popey> sure can dednick
[11:21] <mzanetti> MacSlow: this is how a long term Qt dev would write it: https://pastebin.canonical.com/87524/ (note that I'm not saying that you have to change it like this. But I'm a strong believer of consistency in coding styles)
[11:32] <tsdgeos> Saviq: i've approved your MR
[11:32] <tsdgeos> s
[11:33] <Saviq> tsdgeos, cheers
[11:33] <Saviq> let's see what that results in...
[11:35] <tsdgeos> yeah :D
[11:38] <hikiko> hello :) I just realized I haven't upgrade my phone/chroot for a long time... any instructions on how to do it?
[11:38] <hikiko> wrong channel
[11:38] <hikiko> :p
[11:41] <sil2100> ;p
[11:43] <popey> seems okay dednick
[11:43] <popey> thanks
[11:44] <dednick> popey: weird. dont know what was going on.
[11:55] <popey> dednick: still get the problem where the dash often doesn't get focus, so keypresses are lost
[11:56] <didrocks> popey: I think it's fixed in unity trunk
[11:56] <didrocks> or there is a branch proposed
[11:56] <popey> groovy
[11:56] <didrocks> so not a 100scopes issues in fact, I guess
[11:57] <didrocks> but if you have time to double check that I didn't dream this morning… :)
[11:58] <popey> you dream about unity?
[11:58] <popey> You may want to see a mental health professional.
[11:59] <didrocks> popey: I guess I should, indeed :)
[11:59] <didrocks> I dreamt that I was pocking jibel for a UTAH issue TBH
[11:59] <didrocks> and it happened this morning :)
[12:00] <popey> ooh, you have "the sight"
[12:00] <popey> what are the lottery numbers this weekend?
[12:01] <didrocks> popey: if only… if only… :)
[12:25] <Mirv> hmm, where did MCR1 go, he updated LP 1 min ago :)
[12:37] <tsdgeos> Saviq: should we mark "fix/improve build scripts" as DONE ?
[12:38] <tsdgeos> Saviq: or there's still something you want to do?
[12:38] <Saviq> tsdgeos, opinion: I don't like the thingy copying the ssh key
[12:39] <Saviq> tsdgeos, I'd rather get rid of it (it caused at least some of kgunn's problems)
[12:39] <Saviq> tsdgeos, and either let people do it themselves
[12:39] <Saviq> tsdgeos, or maybe add another option to run_on_device
[12:40] <tsdgeos> yep
[12:40] <tsdgeos> -key path
[12:40] <tsdgeos> or something
[12:47] <dandrader> any javascript experts around? I've an object created like var application = {'name' : "Foo", desktopFile:"bla"}. Then it's assigned to some var qml properties (foo = application).
[12:48] <dandrader> if I compare var a and var b, both having been assigned to application
[12:48] <dandrader> with a == b
[12:48] <dandrader> I get false
[12:48] <dandrader> even though they hold/point to the same application var
[12:48] <dandrader> because if I do a.desktopFile == b.desktopFile I get true
[12:49] <dandrader> If I print each of them I get: "ModelObject(0x1cc1dc0) == [object Object] is false"
[12:49] <dandrader> so they are not really the same thing. I wonder what's the difference
[13:02] <tvoss> kgunn, MacSlow|lunch ping
[13:03] <kgunn> kgunn: pong (while making a coffee)
[13:07] <Saviq> dandrader, one of them is a ModelObject, the other is just a JS object with the same properties
[13:08] <Saviq> dandrader, they're simply different types
[13:10] <dandrader> Saviq, I think I got it. when I push a JS object (the [object Object]) onto a ListModel, that ListModel creates a ModelObject storing the same properties. As a ListModel holds ModelObject instances and not regular js objs, right?
[13:10] <dandrader> a lot of magic happening behind the scenes :)
[13:11] <tvoss> kgunn, up for a quick hangout? https://plus.google.com/hangouts/_/7a2b5e6fd3ee0ae56e48da542672de9bab0bf8a3?authuser=0&hl=en
[13:11] <dandrader> greyback, ping
[13:12] <Saviq> dandrader, yup
[13:12] <greyback> dandrader: pong
[13:12] <dandrader> greyback, do you know details on how the switch between shell rendering and application rendering takes place on the device?
[13:13] <dandrader> or not "details" but just what actually takes place
[13:14] <dandrader> some context: I'm poking and testing Stage.qml
[13:14] <greyback> dandrader: sure, I do
[13:15] <greyback> dandrader: sorry in a meeting right now, I'll ping you when free
[13:15] <dandrader> so while an application is being rendered, does it render directly to the framebuffer that is being shown or does always renders to an offscreen fb that shell then takes and composites?
[13:15] <kgunn> tvoss: give me like 5 min
[13:15] <dandrader> greyback, ok
[13:16] <tvoss> kgunn, ack
[13:19] <Saviq> sil2100, hey, if you have a chance, can you please have a look at https://launchpadlibrarian.net/134926716/buildlog_ubuntu-quantal-amd64.unity_7.80~phablet1_FAILEDTOBUILD.txt.gz
[13:20] <Saviq> sil2100, and hopefully point me at the correct solution
[13:29] <kgunn> tvoss: ready? sorry for the delay
[13:30] <tvoss> kgunn, no worries, as long as you are dressed now :) https://plus.google.com/hangouts/_/7a2b5e6fd3ee0ae56e48da542672de9bab0bf8a3?authuser=0&hl=en
[13:37] <mzanetti> please mark hangout links with potentially naked people as "use at your own risk" or something like that
[13:37] <mzanetti> :D
[13:51] <MacSlow> kgunn, tvoss: ping
[13:53] <sil2100> Saviq: give me a moment
[13:53] <tvoss> Saviq, MacSlow can you jump on here: https://plus.google.com/hangouts/_/7a2b5e6fd3ee0ae56e48da542672de9bab0bf8a3?authuser=0&hl=en ?
[13:53] <MacSlow> tvoss, one sec...
[13:55] <dednick> Saviq: ping
[13:55] <Saviq> dednick, pong
[13:56] <mzanetti> cyphermox: ping
[13:56] <dednick> Saviq: i'm going to give the standup a miss if that's ok. dont have anything to report on the UnityNext side, and i'm pretty busy with the other things.
[13:56] <Saviq> dednick, k
[13:56] <dednick> ta
[14:00] <tsdgeos> Saviq: ping
[14:00] <Saviq> tsdgeos, pong
[14:01] <tsdgeos> Saviq: unity-core is not part of https://launchpad.net/~phablet-team/+archive/ppa/+packages ?
[14:01] <Saviq> tsdgeos, unity-core is built from unity
[14:01] <Saviq> tsdgeos, next page, btw
[14:01] <tsdgeos> Saviq: ah there's more pages
[14:01] <tsdgeos> ...D
[14:03] <tsdgeos> Saviq: seen unity failed to build?
[14:03] <greyback> dandrader: back. A better person to ask about that would be loicm. He knows more about the lower-end bits
[14:03] <Saviq> tsdgeos, yeah, investigating, it's _weird_
[14:03] <tsdgeos> oki
[14:03] <tsdgeos> Saviq: shout if you want me to have a look too
[14:08] <Saviq> tsdgeos, thing is...
[14:08] <Saviq> tsdgeos, unless we've been building a more recent bamf in the PPA (/me checks)
[14:08] <Saviq> no, we weren't
[14:09] <Saviq> then I don't understand how it could ever have built...
[14:10] <Saviq> the missing symbol was added in lp:bamf in r496
[14:10] <Saviq> and was never backported to lp:bamf/0.3
[14:11] <Saviq> so I don't understand how it could ever work...
[14:12] <Saviq> ah wait
[14:12] <Saviq> got it
[14:12] <Saviq> bamf was built in the other ppa
[14:15] <ChrisTownsend> didrocks: sil2100:  I'm working on fix for Unity 5.0 & 6.0 and wanted to get your opinion on getting this in as an SRU.
[14:15] <didrocks> sure, what about it?
[14:15] <sil2100> What's up?
[14:16] <ChrisTownsend> Ok, here the branches: https://code.launchpad.net/~townsend/unity/no-window-decorations-5.0 & https://code.launchpad.net/~townsend/unity/no-window-decorations-6.0
[14:16] <ChrisTownsend> They are a partial backport of https://code.launchpad.net/~3v1n0/unity/switcher-glowing-decorations/+merge/134019
[14:18] <ChrisTownsend> Trevinho says in bug #1122478 that there are no regressions.
[14:19] <Trevinho> ChrisTownsend: yeah, I can confirm it... We actually are using this in unity for months and nothing has been spotted so far
[14:19] <ChrisTownsend> Trevinho: Yep, it works quite nice:)
[14:19] <Saviq> tsdgeos, let's extract unity-core from lp:unity/phablet, what do you think?
[14:20] <tsdgeos> Saviq: you mean not using it unity-core?
[14:20] <didrocks> I'm letting lukasz looking at it for now, ping me if you need anything (but sounds legit to me)
[14:20] <ChrisTownsend> didrocks: Ok, cool.  Thanks!
[14:20] <Saviq> tsdgeos, so we don't build the whole of unity
[14:20] <Saviq> tsdgeos, just UnityCore, which is what we are doing in ./build anyway
[14:21] <tsdgeos> Saviq: you mean adding unity-core code to the lp:unity/phablet repo?
[14:21] <Saviq> tsdgeos, /me wrong
[14:21] <Saviq> tsdgeos, let's extract it from lp:unity/phablet-mods
[14:21] <sil2100> ChrisTownsend: I'll take care of it then, let me just note it down ;p
[14:22] <ChrisTownsend> sil2100: Ok, cool.  I'll get an MP ready for it and we'll go from there.
[14:22] <tsdgeos> Saviq: so we create a new repo that only builds unity-core and that's the one we use in the ppa
[14:22] <tsdgeos> makes sense
[14:22] <Saviq> yup
[14:23] <tsdgeos> Saviq: maybe we can even reuse lp:unity/phablet-mods just to build unity-core?
[14:23] <sil2100> ChrisTownsend: awesome - the bug is SRUable so feel free to MR against 5.0 and 6.0, we'll prepare the bug descriptions and keep it on our radar
[14:23] <tsdgeos> changing the debian compile files and that's it?
[14:23] <ChrisTownsend> sil2100: Very good, thanks!
[14:24] <Saviq> tsdgeos, CMakeLists.txt, too
[14:24] <tsdgeos> right
[14:24] <tsdgeos> Saviq: want me to work on that? or you do?
[14:24] <Saviq> tsdgeos, I'm good, thanks
[14:25] <tsdgeos> good :-)
[14:28] <mterry> didrocks, does sam hang out in any IRC channels/
[14:28] <mterry> ?
[14:28] <didrocks> mterry: he was before hanging out here, but not for a long time
[14:28] <mterry> I have a question about this merge
[14:28] <didrocks> mterry: you can maybe send him a PM?
[14:28] <mterry> May have added a new regression for me
[14:28] <didrocks> smspillaz
[14:28] <sil2100> mterry: what's up? You can try e-mailing him
[14:29] <sil2100> Although he might be sleeping now
[14:31] <mterry> talking to him now
[14:33] <Saviq> greyback|food, nic-doffay standup?
[14:35] <nic-doffay> one sec Saviq
[14:39] <davidcalle> didrocks, would you have a couple of minutes for 7 quick MPs?
[14:40] <didrocks> davidcalle: I'll ignore 7 and read it as "a" ;)
[14:40] <didrocks> (and ignore the s as well :p)
[14:40] <didrocks> davidcalle: sure, fire on! ;)
[14:41] <davidcalle> didrocks, https://code.launchpad.net/ubuntu-scopes/+activereviews : everything except coloulovers, I've been ping-ponging on it with jamesh, he will have the final word :)
[14:41] <davidcalle> colour*
[14:43] <didrocks> davidcalle: thanks, looking!
[14:49] <sil2100> Saviq: you still have that build problem? From what sources are you building exactly?
[14:49] <Saviq> sil2100, yeah, I think we'll manage, thanks
[14:50] <Saviq> sil2100, it's just us and all of our outdated branches :P
[14:50] <sil2100> ;p
[14:51] <cyphermox> mzanetti: pong
[14:52] <mzanetti> cyphermox: not sure if you missed it or just didn't have the time yet... just in case: https://code.launchpad.net/~mzanetti/autopilot-qt/add-tests/+merge/153695
[14:52] <mzanetti> I have created the bug report as you asked
[14:53] <cyphermox> mzanetti: cool, yeah I hadn't see it yet
[14:59] <cyphermox> mzanetti: just waiting for the release team to chime in
[14:59] <mzanetti> cyphermox: yeah... fine with me. I'm not in a hurry. just wanted to let you know because I guess the releasing thing is better to be done sooner rather than later
[15:00] <cyphermox> I explicitly don't want to block adding tests, but adding the package constitutes a feature. If they're not happy, we could just drop the new package and keep the added tests.
[15:00] <cyphermox> yeah
[15:00] <cyphermox> sorry, I was fixing major computer troubles this morning, so I couldn't look earlier
[15:00] <mzanetti> no problem
[15:05] <mterry> fginther, mmrazik : did the video capture crash X here?  http://10.97.0.1:8080/job/ps-unity-autopilot-release-testing/label=autopilot-intel/133/consoleText
[15:05] <mmrazik> mterry: btw. we are trying to hide internal IPs
[15:05] <fginther> mterry, I haven't figured this one out yet
[15:06] <mterry> mmrazik, sorry
[15:06] <mterry> mmrazik, the ship sailed on that IP a while ago though, right?  :)
[15:07] <mmrazik> I fear so, yes :)
[15:11] <mterry> didrocks, so the intel tests seemed to have experienced a freak error.  Is there anything in the unity stack you particularly wanted released?  (I think it'd be safe to manually publish if you wanted it)
[15:12] <kgunn> mzanetti: so if one were to write a mock/dummy component to add to unity....which directory would it go in "Components" ?
[15:12] <kgunn> at least all the "fakes" are in there now
[15:12] <mzanetti> kgunn: I think the FakeApplicationManager is misleading
[15:13] <mzanetti> kgunn: you are talking about some mock to be used for testing,right?
[15:13] <kgunn> yeah
[15:13] <mzanetti> kgunn: those should go to tests/<type of test>/mocks or something like that
[15:14] <mzanetti> kgunn: the FakeApplicationManager is not used for testing, but to be able to run the shell on the desktop.
[15:14] <mzanetti> kgunn: thats why it is in the real Components
[15:14] <kgunn> :) got it
[15:14] <kgunn> mzanetti: thanks...
[15:14] <mzanetti> np :D
[15:15] <didrocks> mterry: nothing particular as long as we don't have the compiz fix
[15:15] <mzanetti> kgunn: albert started in tests/qmluitests/qml/ for the HUD mocks.
[15:16] <mzanetti> the qml at the end might not be the best name but I'm not sure yet how it will end up (one dir for all mocks vs each moch has its own dir)
[15:16] <mzanetti> kgunn: ^
[15:17] <kgunn> mzanetti: ack...will take a peek
[15:20] <fginther> mterry, I'm assuming X crashed, but no crash was saved
[15:21] <fginther> mterry, the entire run looks hosed, what few test ran failed
[15:22] <fginther> mterry, any chance we can restart just the intel run?
[15:23] <fginther> mterry, actually a full restart wouldn't really hurt anything, but I see a test is in progress
[15:24] <mterry> yeah
[15:24] <dandrader> grantbow, but the shell is always on top of the app, as it has to capture input on the right edge so that shell that show the application switch animation (using screenshots)
[15:25] <dandrader> s/ grantbow / greyback
[15:25] <dandrader> autocomplete failed me
[15:25] <dandrader> s/that show/can show
[15:26] <dandrader> greyback, right?
[15:26] <greyback> dandrader: that's correct, yes
[15:26] <jibel> mterry, hold on, I'm reran 100scopes to check if we can reproduce the panel test failure we had on previous run
[15:26] <jibel> mterry, and also run them on intel since the box didn't restart previously and required a physical action
[15:36] <mdeslaur> sil2100: hi! what exactly creates the "unity" compiz profile when a user logs in for the first time?
[15:36] <mdeslaur> I am trying to enforce default gsettings for unity...but creating gschema.override file only seems to affect the "Default" compiz profile so I'm trying to figure out what exactly is creating the "unity" compiz profile
[15:38] <seb128> mdeslaur, not sure if that's helpful, but profiles use schemas relocation
[15:38] <seb128> mdeslaur, see e.g /usr/lib/compiz/migration/compiz-profile-Default.convert
[15:38] <seb128> [org.compiz.core:/org/compiz/profiles/Default/plugins/core/]
[15:38] <seb128> it means it's not normal org.compiz.. keyname you need to use
[15:39] <seb128> but "schemas:/relocation path"
[15:39] <sil2100> mdeslaur: hi, sadly gsettings overrides do not work for relocatable schemas if anything
[15:39] <mdeslaur> I tried this: http://paste.ubuntu.com/5637288/
[15:39] <seb128> mdeslaur, that's what allows to have the same schemas "deployed/used" at different places
[15:40] <mdeslaur> sil2100: hrm...any idea what the best way to set default values for new users would be?
[15:40] <seb128> mdeslaur, I also think that the user profile is created by a copy happening on first login
[15:40] <mdeslaur> seb128: yeah, but I can't seem to find where that logic lives
[15:40] <mdeslaur> I see all the gconf migration stuff, but can't find where the "unity" one is created
[15:42] <sil2100> mdeslaur: it's been a while, let me think a moment to remind myself of how it all works
[15:42] <mdeslaur> hehe :P
[15:54] <mdeslaur> ah! found it.../etc/compizconfig/unity.ini
[15:54] <mdeslaur> sil2100, seb128: thanks for your help, I think I found what I was looking for
[15:54] <seb128> mdeslaur, great
[15:55] <mdeslaur> so...many...migration hacks... :)
[15:55] <seb128> mdeslaur, yeah, that's the "master" I think
[15:55] <seb128> e.g what is used for the first run copy
[15:55] <seb128> which writes in gsettings
[15:55] <sil2100> mdeslaur: good to hear that, since I'm busy with so many things that it's hard to get a time slice for anything
[15:55] <sil2100> Especially with my GPU hanging
[15:55] <mdeslaur> sil2100: sounds exciting :P
[15:57] <kenvandine> mzanetti, i have an autopilot question
[15:57] <mzanetti> kenvandine: hit me
[15:57] <kenvandine> i used qtcreator to add autopilot functional tests to my project, the stub helloworld example it creates fails
[15:57] <kenvandine> 11:49:59.775 WARNING __init__:197 - Caught exception while searching for autopilot interface: 'DBusException("Could not get PID of name 'org.freedesktop.DBus': no such name",)'
[15:57] <kenvandine> i suspect whatever causes that is the root of the problem
[15:58] <mzanetti> kenvandine: hmmm I haven't seen the template so far...
[15:58] <mzanetti> kenvandine: but really sounds like a bug in the templae
[15:58] <kenvandine> i figured
[15:58] <kenvandine> but what would it be looking for on dbus?
[15:59] <kenvandine> 11:49:59.743 INFO __init__:121 - Launching process: ['qmlscene', '-testability', '-I', '/storage/1/src/gwibber/modules', '/storage/1/src/gwibber/trunk/tests/autopilot/tests/Generic/../../helloworld.qml']
[15:59] <kenvandine> is what is being run
[15:59] <kenvandine> the testabilitity driver?
[15:59] <mzanetti> kenvandine: basically do this: run your app with -testability and look if it prints a line "Loading testability driver"
[15:59] <mzanetti> kenvandine: should be the very first thing it prints
[16:00] <mzanetti> kenvandine: or a error that sould get you further
[16:00] <kenvandine> ok... that works
[16:00] <kenvandine> so maybe it is just the path or something silly
[16:01] <kenvandine> actually, the commands it runs to start it look fine and it prints loading testability
[16:01] <kenvandine> but the looking for autopilot interface step seems to be what's broken
[16:01] <kenvandine> i guess that is in the python code here somewhere
[16:08] <jibel> didrocks, last run of 100scopes is OK on the 3 systems and didn't reproduce the problem we had previously on nvidia
[16:08] <tsdgeos> mzanetti: if you do have time https://code.launchpad.net/~aacid/unity/testParametrizedActions/+merge/154750
[16:09] <tsdgeos> mzanetti: interested if clicking in units.gu(1), units.gu(1) also puts your slider at 10 or not
[16:09] <tsdgeos> mzanetti: besides the regular review of course
[16:11] <mzanetti> tsdgeos: all the tests passed here
[16:11] <mzanetti> so if you were suspecting a retina-screen issue, not it works fine
[16:12] <tsdgeos> good :)
[16:43] <didrocks> jibel: \o/
[16:43]  * didrocks hugs jibel
[16:43] <didrocks> best news from the past 1h30!
[17:01] <didrocks> davidcalle: ok, all approved :)
[17:01] <didrocks> davidcalle: one thing though: the manpages scope is still installing in /usr/share/unity/lenses
[17:01] <didrocks> not scopes*
[17:02] <davidcalle> didrocks, that explains a lot :)
[17:02] <didrocks> davidcalle: isn't it? :)
[17:02] <didrocks> davidcalle: mind fixing it?
[17:02] <davidcalle> didrocks, thanks, will fix it a bit later tonight if you don't mind, I'm on weather previews
[17:03] <didrocks> davidcalle: ok, I think I'll have to trigger a rebuild tomorrow morning anyway
[17:03] <davidcalle> didrocks, ok
[17:04] <mhr3> didrocks, oh, but we'll finish those merges at about 10pm... ish :)
[17:05] <didrocks> mhr3: hence the "tomorrow morning" :)
[17:05] <didrocks> mhr3: thanks btw :p
[17:05] <mhr3> are you saying you won't be here with us?
[17:05] <mhr3> :(
[17:06] <didrocks> mhr3: TBH, when running the build
[17:06] <didrocks> then it has to build
[17:06] <didrocks> then publish
[17:06] <didrocks> then tests running
[17:06] <didrocks> so like 2h30+
[17:07] <sil2100> geh, I love local build problems
[17:07] <didrocks> mhr3: I want to do something else at 1am FYI
[17:07] <didrocks> :)
[17:07] <sil2100> But finally all is tested thanks to popey
[17:07] <didrocks> sil2100: hey hey!
[17:07] <sil2100> https://code.launchpad.net/~sil2100/unity/libunity-7.0-breakage-ref-fix-autopilot/+merge/155017
[17:07] <didrocks> sil2100: \o/
[17:07]  * didrocks hugs sil2100
[17:07] <didrocks> big hug!
[17:07] <sil2100> This is for the DashKeyNavTests failures - really wasted like 1-2 hours trying to build it locally for testing, everything on my system is broken today ;)
[17:07] <didrocks> sil2100: how many failing tests this is fixing?
[17:07] <mhr3> didrocks, and you have to be watching it?
[17:08] <sil2100> This theoretically should fix 5 failures on all platforms
[17:08] <sil2100> dednick is working on the Alt+F2 issue
[17:08] <sil2100> I also might be able to have a fix for the shopping issue till EOD today, but we'll see!
[17:08] <didrocks> mhr3: well, I want then to ensure that the ppa is in good shape
[17:09] <didrocks> mhr3: so that's why I can run it tomorrow morning
[17:09] <sil2100> dednick: could you take a look when you have a moment ^ https://code.launchpad.net/~sil2100/unity/libunity-7.0-breakage-ref-fix-autopilot/+merge/155017
[17:09] <didrocks> and then fetching it back
[17:09] <mhr3> didrocks, i'm just kidding, your work day is over already ;)
[17:10] <sil2100> dednick, didrocks: btw. is there an automerger for the libunity-7.0-breakage repo, or things need to get manually merged in?
[17:10] <sil2100> I mean, branch
[17:10] <didrocks> mhr3: I'll just cry, somewhere… :)
[17:10] <dednick> sil2100: i think it's auto
[17:11] <didrocks> sil2100: great great, can't wait for it!
[17:11] <didrocks> sil2100: automerging automerging, automerging :)
[17:11] <sil2100> Since the pch fix you made is still not merged in, so maybe there's a queue right now
[17:11] <mhr3> didrocks, heh :)
[17:11] <dednick> unless didrocks has feverishly bee merging all our changes :)
[17:11] <didrocks> no no :)
[17:11] <didrocks> I never bypass the merger
[17:11] <didrocks> isn't it mhr3 :)
[17:12] <mhr3> didrocks, right, right :P
[17:12] <didrocks> see ^ :)
[17:12] <didrocks> speaking of which: mmrazik|afk, fginther: see rev 105
[17:13] <didrocks> can you please deploy to have unity-lens-friends?
[17:13] <mmrazik|afk> didrocks: I'll do it
[17:13] <didrocks> that will make the dear kenvandine happy
[17:13] <didrocks> mmrazik|afk: not so afk? :p
[17:13] <didrocks> thanks!
[17:13] <mmrazik|afk> hmpf
[17:13] <mmrazik|afk> :)
[17:13]  * didrocks push the daily release part
[17:15] <mmrazik|afk> didrocks: done
[17:15] <didrocks> thanks mmrazik|afk :)
[17:36] <kenvandine> didrocks, is that a fix for my tiles?
[17:37] <didrocks> kenvandine: no, automerging :)
[17:37] <didrocks> kenvandine: you bug is prioritized
[17:37] <kenvandine> cool
[17:49] <didrocks> sil2100: is anyone reviewing your branch?
[17:54] <bschaefer> didrocks, if its for the 100scopes could you link me?
[17:54]  * bschaefer can review
[17:54] <didrocks> bschaefer: it is!
[17:54] <didrocks> one sec
[17:55] <bschaefer> alright thanks!
[17:55] <didrocks> https://code.launchpad.net/~sil2100/unity/libunity-7.0-breakage-ref-fix-autopilot/+merge/155017
[17:55] <didrocks> bschaefer: what else would I speak about these days? :)
[17:55] <bschaefer> didrocks, thanks!
[17:55] <sil2100> I asked dednick, but he's probably busy now ;)
[17:55] <bschaefer> didrocks, im not sure haha, just wanted to be sure haha
[17:55] <bschaefer> sil2100, yeah im guessing hes got lots to do, so im starting to review as well :)
[17:55] <sil2100> 100scopes is 'the thing' lately
[17:55] <bschaefer> haha
[17:55] <sil2100> bschaefer: thanks :)
[17:56] <didrocks> what I didn't see anything from him?
[17:56]  * didrocks runs :-p
[17:57] <bschaefer> np!
[17:57] <bschaefer> haa
[17:58] <dednick> sil2100: approved
[17:58] <sil2100> dednick: \o/ thanks!
[17:59] <bschaefer> dednick, dang was just getting there! haha
[17:59] <bschaefer> dednick, i've an easy one for you https://code.launchpad.net/~brandontschaefer/unity/overlay-scrollbar-filter-results-fix/+merge/155026
[17:59] <dednick> bschaefer: :) i was painfully aware of the bug
[17:59] <bschaefer> sil2100, or if you could ^
[17:59] <bschaefer> dednick, hah
[18:00] <dednick> bschaefer: ya, i've seen that bug. approved
[18:00] <bschaefer> dednick, cool, thanks!
[18:00] <sil2100> ;)
[18:00]  * sil2100 lost free karma this time, dednick is too fast
[18:01] <dednick> hehe
[18:01] <sil2100> But I'll be faster next time!
[18:01] <sil2100> ;)
[18:01] <bschaefer> haha
[18:01] <dednick> i havent got any karma in about 3 months. i hope i'm going to get 20k lines worth of it now!
[18:01] <bschaefer> haha, you'll get like 100 points maybe
[18:02] <bschaefer> you can split it up into like 20 different branches that all depend on each other :)
[18:02] <dednick> hehe. i had a few, but they've all been merged into the super massive one now.
[18:02] <bschaefer> haha
[18:04] <sil2100> Is there a karma ranking anywhere?
[18:04] <sil2100> ;)
[18:07] <dednick> sil2100: https://launchpad.net/ubuntu/+topcontributors
[18:08]  * bschaefer thinks the jenkins bot cheats
[18:12] <sil2100> I see I have still lots of karma to earn!
[18:15] <sil2100> pstolowski: ping!
[18:16] <pstolowski> sil2100: pong
[18:20] <dednick> bschaefer: you mind taking a look? https://code.launchpad.net/~nick-dedekind/unity/smart-scopes.scope-bar-tabbing/+merge/155030
[18:20] <bschaefer> dednick, on it
[18:21] <dednick> crap. sorry. it's done somthing stupid
[18:21] <dednick> like propose into lp:unity
[18:21] <dednick> :)
[18:21] <bschaefer> dednick, hah, I was wondering about the diff haha
[18:22] <dednick> bschaefer: https://code.launchpad.net/~nick-dedekind/unity/smart-scopes.scope-bar-tabbing/+merge/155032
[18:22] <bschaefer> dednick, cool
[18:22]  * bschaefer reviews
[18:23] <dednick> bschaefer: i've nearly merged into lp:unity with this branch by mistake before. :)
[18:23] <bschaefer> dednick, haha, that would have been interesting if it made it through!
[18:23] <dednick> think didier missed a few heart-beats
[18:24] <sil2100> dednick: you rock
[18:24] <sil2100> dednick: this was also causing a failure in the latest AP run, awesome ;)
[18:24] <bschaefer> ha, yes he would have
[18:29] <bschaefer> dednick, works, approved!
[18:30] <davidcalle> didrocks, regarding manpages installing in unity/lenses I've just checked latest trunk, it doesn't
[18:30] <didrocks> davidcalle: ah ok, so just a rebuild ahead :)
[18:34] <davidcalle> didrocks, getting there http://ubuntuone.com/6KHls5qzH66ZnCHZ6AwJW2 , http://ubuntuone.com/1fYiLxC1TaFi9PXHaTIzfb
[18:34] <didrocks> davidcalle: awesome! (because of the city you have chosen of course ;))
[18:34] <davidcalle> didrocks, ;)
[18:34] <didrocks> davidcalle: but come on! bad weather!!!
[18:34] <didrocks> I held you responsible :p
[18:35] <didrocks> you think you will have an image available?
[18:35] <didrocks> in the preview?
[18:36] <davidcalle> didrocks, I hope so. I mean, I can auto flickr something, but it's hard to get it right. I do hope Design will have a bright idea ;)
[18:37] <davidcalle> if city == "lyon": icon = "cloudy" :p
[18:38] <bschaefer> dednick, so, ChrisTownsend is unable to login with lightdm using the scopes ppa...
[18:38] <bschaefer> didrocks, ^
[18:38]  * bschaefer will give it a try
[18:39] <ChrisTownsend> Yeah, it's strange.  I get a blank screen with the cursor.
[18:39]  * bschaefer re logs
[18:39] <didrocks> davidcalle: tsss :p
[18:39] <didrocks> bschaefer: hum, weird…
[18:39] <didrocks> working here
[18:41] <bschaefer> didrocks, yeah, its working for me as well
[18:41] <bschaefer> ChrisTownsend, strange...
[18:42] <ChrisTownsend> bschaefer: Not sure what to say.
[18:42] <ChrisTownsend> bschaefer: I'll try it again.
[18:43] <bschaefer> ChrisTownsend, hmm yeah, also check the permission of...something
[18:43]  * bschaefer forgot the file
[18:43]  * bschaefer looks it up
[18:52] <bschaefer> didrocks, turns out it was an ~/..Xauthority permission problem
[18:52] <bschaefer> upgrading turning it to 600
[18:52] <bschaefer> turned*
[18:53] <didrocks> bschaefer: I doubt that the components are changing that
[18:53] <didrocks> I would go for a crash or whatever changing it :)
[18:53] <bschaefer> didrocks, well that could make sense, I wonder what caused it to crash
[18:53] <bschaefer> didrocks, cause purging the ppa caused it to go back to 664
[18:54]  * bschaefer shurgs, its fixed now
[18:54] <didrocks> bschaefer: hum, we don't install anything in ~/ ;)
[18:55] <bschaefer> didrocks, well thats nice of you :), but im guessing it was a crash that did it (cause he had a black screen with a mouse)
[18:55] <didrocks> sounds like a xorg crash
[18:55] <bschaefer> yup, interesting
[18:55] <didrocks> not first time I'm hearing that story
[18:55] <bschaefer> but changing the permissions fixes it
[18:55] <bschaefer> yeah, happened to me when messing with my video card driver
[19:16] <didrocks> mterry: around?
[19:17] <mterry> didrocks, yeah hi
[19:17] <didrocks> mterry: hey hey! :)
[19:17] <didrocks> mterry: as cyphermox has an issue with his disk
[19:17] <didrocks> mterry: I wonder if you have time to manually published what can safely be manually published?
[19:17] <mterry> didrocks, alright, let me look
[19:17] <didrocks> mterry: thanks!
[19:18] <didrocks> I think qa as a packaging change
[19:18] <didrocks> blocking indicator
[19:18] <didrocks> and misc
[19:18] <didrocks> hum, no indicator only
[19:19] <didrocks> mterry: in fact qa alone
[19:19] <didrocks> mterry: indicators and oif are yellow because I'm taking that status even if there is nothing to publish
[19:19] <didrocks> mterry: it's a one line change, but I want to cover it by tests before fixing :)
[19:19] <mterry> didrocks, yeah.  qa published
[19:19] <mterry> didrocks, did you say indicators and oif don't even need manual?
[19:19] <didrocks> mterry: thanks!
[19:20] <didrocks> mterry: nope :)
[19:20] <mterry> ok
[19:20] <didrocks> that was easy in fact :)
[19:20] <didrocks> thanks mterry
[19:20] <mterry> :)
[19:25] <cyphermox> Yeah its just qa
[19:27] <cyphermox> Didrocks disk is replaced btw....
[19:27] <mterry> cyphermox, welcome back to the digital world!
[19:27] <didrocks> cyphermox: oh, back on track? :)
[19:27] <didrocks> ssd?
[19:27] <cyphermox> Yup.
[19:28] <didrocks> did you have a ssd before or it was a hd?
[19:28] <cyphermox> Apparently a known issue with think pad x230
[19:28] <didrocks> urgh :/
[19:28] <cyphermox> It was also a SSD
[19:28] <didrocks> ok, so not a huge difference
[19:29] <cyphermox> 60gb and 300$ difference
[19:29] <cyphermox> :-)
[19:30] <didrocks> nyeah :p
[19:30] <cyphermox> Still got to report a bug I found with uefi in the daily
[19:30] <didrocks> cyphermox: your SSD is not covered by the garantee?
[19:30] <cyphermox> Well, yeah, need to rma
[19:31] <cyphermox> But when you do that you need to calculate a few days off time
[19:31] <cyphermox> Both my computers were broken
[19:32] <didrocks> yeah, unfortunate :/
[19:32] <cyphermox> Going to replace the rotary disk on the other one to see if it's the problem
[19:32] <didrocks> cyphermox: you need to work from your tablet! :-)
[19:32] <didrocks> yeah
[19:32] <cyphermox> Haha
[19:32] <cyphermox> I wish I could
[19:33] <cyphermox> I will be able to as soon as we have a console app and good bluetooth
[19:33] <didrocks> ;)
[19:33] <didrocks> cyphermox: go fix bluetooth! :-)
[19:33] <sil2100> ;)
[19:33] <cyphermox> The bluetooth part is almost done :-)
[19:34] <cyphermox> I sent patches on the ml
[19:34] <cyphermox> With this bluetooth starts... You can definitely pair a mouse
[19:34] <didrocks> that would be of help :)
[19:35] <cyphermox> I had some issues with the keyboard which I'm still debugging
[19:35] <cyphermox> Oh.
[19:35] <bschaefer> sil2100, or dednick https://code.launchpad.net/~brandontschaefer/unity/duplicate-dash-home-quicklist/+merge/155044
[19:36] <cyphermox> Yeah, gonna need to run that in gdb, I think I know just what might be the issue
[19:36] <didrocks> cyphermox: nice! good luck
[19:36] <didrocks> and good luck guys
[19:36] <didrocks> running a 100scopes build tomorrow morning
[19:36] <cyphermox> Rock!
[19:36] <didrocks> and testing it before going on weekend
[19:36]  * didrocks waves good evening
[19:36] <cyphermox> Good evening didrocks
[19:37] <didrocks> see you cyphermox!
[19:37] <sil2100> bschaefer: hooo, looking good, one moment
[19:37] <bschaefer> sil2100, thanks, also umm
[19:38] <bschaefer> http://paste.ubuntu.com/5637978/
[19:38] <bschaefer> sil2100, lots of unit tests :(
[19:38] <sil2100> Uuuugh
[19:38] <bschaefer> sil2100, were the unit tests, tested?
[19:38] <sil2100> dednick was working on some of those before, but some probably still fail - good thing we don't care about those that much :D
[19:38] <sil2100> Just kidding!
[19:38] <bschaefer> hahaha
[19:39] <bschaefer> well we just have to prove its the change of code and not regressions
[19:39] <sil2100> But yea, dednick fixed a few of those before, but seems like still some are to be done
[19:39] <bschaefer> which we can fix later
[19:39] <bschaefer> sil2100, I can start looking into those...cause a lot of the 100scopes bugs are...not specific
[19:39] <bschaefer> and more towards the Home Scope branch
[19:40] <kgunn> back
[19:40] <dednick> bschaefer, sil2100: i normally run the unit tests before i merge
[19:40] <bschaefer> dednick, hmm were those failures there?
[19:40] <bschaefer> [  FAILED  ] TestThumbnailGenerator.TestGetManyFileThumbnail, this one is fixed in trunk unity (or about to be)
[19:40] <dednick> um. a couple of them
[19:41] <bschaefer> alright
[19:41] <dednick> havent seen the launcher ones
[19:41]  * bschaefer takes a look at them
[20:10] <bschaefer> pstolowski, hey, do you need a review of this? https://code.launchpad.net/~stolowski/unity-scope-home/privacy-and-disabled-scopes/+merge/155045
[20:19] <pstolowski> bschaefer: yeah. mhr3, or have you started reviewing it already?
[20:19] <bschaefer> pstolowski, I haven't, I figured I could help test it out
[20:19] <mhr3> pstolowski, not yet
[20:19] <mhr3> pstolowski, on skype
[20:19] <bschaefer> i know a little bit of vala but now as much as you guys :)
[20:20] <bschaefer> mhr3, I can start reviewing it, also hello!
[20:20] <bschaefer> s/now/not*
[20:21] <mhr3> bschaefer, hey! :)
[20:21] <sil2100> Ok guys, I think I'll go rest now
[20:21] <sil2100> See you around!
[20:21] <pstolowski> bschaefer: thanks for help
[20:21] <bschaefer> sil2100, thanks! Have a good rest!
[20:21] <bschaefer> pstolowski, np!
[20:22] <mhr3> of course i broke half the tests
[20:22] <mhr3> grrrrr
[20:23] <bschaefer> half is a lot
[20:32] <bschaefer> mhr3, where is the new libunity at? that has unity-protocol-private >= 6.91.7
[20:32] <bschaefer> trunk is only 6.90.2 :(
[20:33] <bschaefer> pstolowski, you would also most likely know ^
[20:33] <pstolowski> bschaefer: libunity-7.0 branch
[20:34] <bschaefer> pstolowski, thanks!
[20:41] <kgunn> dandrader: hey, i know all the autopilot/qmlui tests get run as part of ci
[20:42] <kgunn> dandrader: but when do those component unit tests get run?
[20:42] <kgunn> dandrader: e.g. tst_Carousel
[20:42] <kgunn> or tst_Mathlocal
[20:42] <dandrader> kgunn, as far as I know tests under tests/qmluitests/ are not run by CI yet
[20:43] <dandrader> kgunn, but the ones under tests/unittests are (besides autopilot tests)
[20:58] <bschaefer> pstolowski, while unitys rebuilding...
[20:58] <bschaefer> pstolowski, 22	+ preferences.notify[DISABLED_SCOPES_KEY].connect ((obj, pspec) =>
[20:58] <bschaefer> shouldn't we also update_disabled_scopes (); when its renabled?
[20:59]  * bschaefer could have missed that signal
[21:00] <pstolowski> bschaefer: it's the same key/signal
[21:00] <bschaefer> pstolowski, o nice, well ill be testing it in a couple minutes :)
[21:00] <pstolowski> bschaefer: whenever it changes (scope added/removed), we get it
[21:00] <bschaefer> pstolowski, nice, the DISABLED_SCOPES_KEY made me think there was an ENABLED_SCOPES_KEY
[21:09] <bschaefer> pstolowski, hmm I still seem to get some results flash up from the internet when its turned off
[21:09] <bschaefer> pstolowski, http://i.imgur.com/wehd89M.png
[21:10] <bschaefer> (the scroll bar goes down into more results from the internet)
[21:10] <pstolowski> bschaefer: that's because there is second part of that feature, which lives in a libunity branch which is just MPed
[21:10] <pstolowski> bschaefer: hmm, but more suggestions shouldn't be there
[21:10] <bschaefer> pstolowski, o well nice then, what is something I should test out with this branch?
[21:10] <bschaefer> pstolowski, well it randomly shows up...
[21:10] <pstolowski> bschaefer: did you re-issue the search after changing this flag?
[21:11] <bschaefer> pstolowski, well I had it off we I recompiled with your branch
[21:11] <bschaefer> so its been off the entire time
[21:11] <pstolowski> that's totally weird
[21:11]  * bschaefer goes to make sure its using the right unity-scope-home
[21:12] <bschaefer> because your changes make sense...
[21:14] <pstolowski> bschaefer: btw, my changes only disable comms with smart scope server OR passes list of scopes to disable *on the server* to smart scopes server (the ones defined in disabled_scopes gsettings key); the change in libunity that I mentioned also disables remote search for any local scopes
[21:14] <pstolowski> bschaefer: so without libunity fix, local scopes that do remote queries will continue doing them
[21:15] <bschaefer> pstolowski, well Im a bit behind on the new changes, so im just using the home-scope from what I know
[21:15] <bschaefer> but yeah, let me grab mhr3 branch and give that a test
[21:15] <pstolowski> bschaefer: that's fine, we just realized some of these requirements yesterday..
[21:16] <mhr3> pstolowski, fwiw it works fine for me
[21:16] <bschaefer> pstolowski, well mhr3 is a bit more of a trusted source ;)
[21:16] <bschaefer> pstolowski, and yeah, its seems a few of these requirements would have been nice to have a bit earlier
[21:17] <mhr3> i'm approving it
[21:17] <bschaefer> mhr3, well im going to give it a run just to confirm (for my own sanity)
[21:17] <mhr3> sure
[21:17] <bschaefer> never hurts
[21:17] <pstolowski> thanks
[21:18] <mhr3> i'm glad you're doing that actually :)
[21:18] <bschaefer> :), search/backend stuff is always fun
[21:19] <mhr3> there is definitely some race in lenses though
[21:19] <mhr3> eeeh, scopes
[21:19] <mhr3> i think cancellation isn't handled correctly
[21:20] <bschaefer> i wonder if unity is pushes a request before the private bit gets updated
[21:20] <pstolowski> mhr3: is cancellation already helping in home scope searches?
[21:20] <mhr3> pstolowski, you implemented cancellation?
[21:21] <pstolowski> mhr3: no, I didn't, just wondering if master scopes somehow cancel search for same channel already if new one arrives
[21:22] <mhr3> nope
[21:22] <mhr3> it's complicated for them because of the synchronizer
[21:24] <mhr3> for example if first search queries all subscopes and second just a few of them, even if you cancel the request in between, the scopes don't know about it and will push results into the synchronized model while you're expecting that only the new search results will get there
[21:26] <mhr3> and now that i think about it, this is pretty fundamental issue
[21:26] <mhr3> why oh why on friday....
[21:27] <bschaefer> mhr3, so you have the weekend to think about it!
[21:27] <mhr3> yey me
[21:28] <bschaefer> mhr3, could your force only being able to have 1 search query going at a time?
[21:28] <pstolowski> mhr3: so, the libunity fix works fine for me
[21:29] <mhr3> bschaefer, sure, but that will make searches slow
[21:29] <mhr3> cause you'll be always waiting for the slowest scope
[21:30] <bschaefer> hmm, well I guess I was imagining each scope having only 1 active search going
[21:30] <bschaefer> and a new one cancels the last active search and starts a new one
[21:31]  * bschaefer is also missing most of the details of how things are handled under the hood
[21:32] <mhr3> let's just say that cancelling searches is not as simple as it seems :)
[21:32] <bschaefer> yeeah, its easy to imagine though!
[21:35]  * bschaefer confirms the fix is working super late as well
[21:56] <mterry> fginther, you still around?  what to do for a package like qtubuntu that arm-only?  https://jenkins.qa.ubuntu.com/job/qtubuntu-quantal-i386-autolanding/1/console
[21:57] <fginther> mterry, I'm here. Looking...
[22:02] <fginther> mterry, I need to modify the job config to use armhf instead of i386. Shouldn't take too long, then I'll reapprove
[22:02] <mterry> fginther, thanks!
[22:12] <fginther> mterry, re-approved. Will watch it just in case it fails again.
[22:13] <mterry> fginther, thanks!