[07:24] <AlanBell> anyone know how the new messaging menu API works?
[07:24] <kenvandine> AlanBell, talk to larsu in #ubuntu-desktop
[07:25] <AlanBell> thanks kenvandine
[07:25] <kenvandine> np
[09:39] <tsdgeos> Trevinho: reuploaded https://code.launchpad.net/~aacid/unity/fix_panek_title_escaping_1067357/+merge/130111 to fix a merge conflcit in CMakeLists.txt can you reapprove?
[10:10] <MCR1> smspillaz: Hi :) Are you here ?
[10:14] <MCR1> sil2100: Hi :) Sorry for f*cking up the ARM build with my GL_BLEND fix recently - I will take & have taken more care of that now...
[10:16] <Trevinho> tsdgeos: sure
[10:17] <Trevinho> tsdgeos: in these case you can safely re-approve it yourself, btw ;)
[10:18] <tsdgeos> it did reapprove it myself to get the merger to try again
[10:18] <tsdgeos> but since there was a "code" change i thought it was better if someone reapproved it :-)
[10:19] <sil2100> MCR1: Hi! No problem, things like that might happen - testing all code paths before submitting is impossible ;)
[10:19] <MCR1> sil2100: I could have seen it ;)
[10:20] <MCR1> sil2100: I got already another GL_BLEND fix - this time it fixes the opaque selection rectangle of the screenshot plug-in...
[10:20] <MCR1> sil2100: But this time I used #ifndef...
[10:28] <MCR1> Trevinho: Are you familiar with bool UnityWindow::place(CompPoint& pos) ?
[10:28] <MCR1> Trevinho: Hi :), btw
[10:28] <Trevinho> MCR1: hi
[10:28] <MCR1> Trevinho: We have a big problem with unityshell overrriding the Place plug-ins working functionality
[10:28] <Trevinho> MCR1: not strictly, what's the problem?
[10:30] <MCR1> Trevinho: bug 874146
[10:32] <MCR1> I have solved it, but Sam does not like my approach, so I am trying to fix it by making sure PlaceWindow::place (CompPoint &pos) will be called in unityshell.
[10:33] <MCR1> This is the desired behaviour: https://bugs.launchpad.net/compiz-core/+bug/874146/+attachment/3406177/+files/UnityAndPlacePluginWorkingTogether.webm
[10:33] <Trevinho> MCR1: you should only make sure that the base function is called...
[10:34] <Trevinho> MCR1: i.e. calling at the end window->Place(pos), does not work?
[10:37] <MCR1> Trevinho: That was the idea - I just wanted to ask if that would be okay ? - So instead of returning the result - calling PlaceWindow::place (CompPoint &pos) ?
[10:37] <Trevinho> MCR1: the problem could be that it would ignore what unity changes...
[10:38] <Trevinho> MCR1: so... mh, probably we should call it before our modifications
[10:38] <MCR1> Trevinho: A big problem is that we are doubling functionality... that creates several problems...
[10:39] <MCR1> Trevinho: If we have a dedicated Place lugin it ideally should do all the placing work IMHO
[10:39] <MCR1> *plugin
[10:40] <MCR1> Trevinho: Fact is also that the placing of windows across monitors does not work at all at the moment, which is a big issue for multimonitor users.
[10:42] <MCR1> Trevinho: From what I see in the unityshell code Unity cares just about the launcher regarding the placement and also about the monitor, but this is somehow broken...
[10:44] <MCR1> Trevinho: Another problem is that we have multiple settings for the same thing in CCSM -> namely the "placement mode" which is in general options and then you can set it once again in the place options... we should eliminate one of those settings
[10:44] <MCR1> The one in General options seems to be fake anyway, but I'll have to analyze more carefully here...
[10:46] <MCR1> Trevinho: Currently, if you start the Place plugin after unityshell its functionality is working again, because it overridess the broken unityshell place behaviour...
[10:46] <MCR1> Trevinho: It is the same problem like we had with showdesktop, which now also works...
[10:47] <MCR1> (enable CCSM->show desktop, Hit Super+D and your windows fly off screen now in trunk)
[10:53] <MCR1> Trevinho: I do not have much time today, but if you have a idea on how to best ensure that the place plugins functionality is called in unityshell, please comment on my merge request...
[10:54] <MCR1> c ya
[11:25] <tsdgeos> Trevinho: and the same thing for 6.0 branch https://code.launchpad.net/~aacid/unity/fix_panek_title_escaping_1067357_for_6.0/+merge/130545
[11:37] <MCR1> back...
[11:37] <MCR1> :)
[11:40] <MCR1> Trevinho, sil2100: We have another problem I think I've found a solution for. Please see this video: https://bugs.launchpad.net/unity/+bug/1069242/+attachment/3406760/+files/Multimonitor-LauncherHidesIfRevealedWithMouseAlthoughPointerHoversIt.webm
[11:42] <MCR1> The problem here is that although Displays Settings is aware of all monitors, unityshell seems to not fully know that it is possible to have more than 2 monitors attached...
[11:43] <MCR1> At least the mousepointer hovering the launcher is just detected on 2 monitors, but not on the third.
[11:44] <MCR1> I think we could fix this by tuning unityshell, where you can set the Launcher to either show on "Primary Desktop" or "All Desktops".
[11:57] <phanimahesh> is didrocks around?
[12:05] <popey> phanimahesh, he's just powering his laptop on
[12:08] <phanimahesh> we were trying to get the unity-reset script promoted on webupd8 when we were asked why is this better than using dconf directly.
[12:08] <phanimahesh> and we need didrocks to answer that, since he recommended using gsettings.
[12:09] <sil2100> MCR1: interesting find this bug
[12:10] <MCR1> sil2100: I am currently updating the description to narrow it down.
[12:11] <MCR1> sil2100: Conclusion is that it works on 2 of 3 monitors only - here of course the one monitor it does not work on is the one I want the Launcher to be on :P
[12:16] <sil2100> MCR1: ;p Well, it's not hight priority though, since I think auto-hide on multimonitors is not that popular
[12:17] <MCR1> sil2100: I will try to fix it, because it breaks the Launcher here ;)
[12:17] <MCR1> sil2100: Here is another fix: https://code.launchpad.net/~mc-return/compiz/compiz.merge-fix1047788-screenshot-selection-rectangle-opaque/+merge/130547
[12:18] <MCR1> sil2100: Video showing the fix in action ;) : https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/771875/+attachment/3406112/+files/ScreenshotPluginAfterFixes.webm
[12:46] <phanimahesh> didrocks: can you explain why using Gsettings is preferred over invoking dconf?
[12:47] <phanimahesh> Relevant discussion here: http://chat.stackexchange.com/transcript/message/6586493#6586493
[13:54] <desrt> why is gsettings sucking so much?
[13:54] <desrt> dconf seems a lot easier to use...
[13:54] <didrocks> desrt: http://chat.stackexchange.com/transcript/message/6586493#6586493
[13:57] <phanimahesh> didrocks: argparse is now the preferred method according to python docs.Can i switch from optparse to argparse? ( unity.cmake )
[13:57] <didrocks> phanimahesh: oh sure
[13:57] <didrocks> phanimahesh: for R only though, not Q ;)
[13:58] <didrocks> you can even switch to python3 please :)
[13:59] <phanimahesh> Gimme a couple of days. :D
[14:00] <phanimahesh> will the --reset get into Q or will it have to wait for R?
[14:05] <didrocks> phanimahesh: --reset can go into Q as a SRU if you don't change argparse and so on for it
[14:05] <didrocks> phanimahesh: so, I would say, propose 2 different branches
[14:05] <didrocks> one for Q with the minimal change
[14:05] <didrocks> and one for R with tests ;)
[14:07] <phanimahesh> I'll make a pull request with the minimal changes version. Amith's last one had a small typo.
[14:07] <phanimahesh> and I'll rewrite and port it to python3 for R.
[14:08] <didrocks> excellent, thanks phanimahesh!
[14:09] <phanimahesh> the pleasure is mine. :)
[14:26] <phanimahesh> didrocks: using subprocess.call("unity") is what we have been doing. both you and me. can setsid unity be preferred over this because it releases the terminal and doesn't kill unity when the terminal is closed?
[15:06] <balloons> mmrazik, ping
[15:06] <mmrazik> balloons: pong
[15:06] <balloons> mmrazik, will you have a chance to add something to the slides?
[15:07] <balloons> I know it's a traveling week for everyone -- I don't want to end up with a time crunch :-)
[15:08] <mmrazik> balloons: do you have a deadline?
[15:09] <mmrazik> I need chris/thomi for that
[15:09] <mmrazik> they will be here wednsday
[15:09] <mmrazik> is Thursday fair for you?
[15:09] <balloons> mmrazik, yes that's fine. I'm going to be traveling until Sunday -- so I wanted t touchbase with you today
[15:10] <mmrazik> balloons: ok. There should be something by Thu EOD in the slides
[15:10] <balloons> btw, I didn't have much success trying to run an example autopilot test -- is there more than this on the wiki someplace? https://wiki.ubuntu.com/Unity/QA/Autopilot
[15:11] <mmrazik> balloons: I think the wiki is terribly outdated...
[15:11] <mmrazik> balloons: thomi has a branch with new documentation somewhere...
[15:11]  * mmrazik is looking for them
[15:13] <mmrazik> balloons: lp:~autopilot/autopilot/improved/documentation
[15:13] <mmrazik> the docs should be built with: "python setup.py build_sphinx"
[15:16] <balloons> mmrazik, ty.. trying that now
[15:18] <balloons> hmm.. not finding it
[15:18] <balloons> is it under thomi?
[15:18] <mmrazik> balloons: can you try this: lp:~autopilot/autopilot/improved-documentation
[15:18] <mmrazik> there was a typo in the previous one
[15:19] <balloons> that's it
[15:19] <mmrazik> balloons: I fail to build it, though
[15:19] <balloons> :-) same
[15:21] <mmrazik> balloons: sudo apt-get install python-sphinx
[15:22] <mmrazik> balloons: it should be in build/sphinx/html
[15:22] <mmrazik> the result I mean...
[15:24] <balloons> i see it
[16:11] <bobweaver> hello there How do I start llvm or get it to work ?
[17:20] <maxb> In quantal, in my multimonitor setup, sometimes it seems that the edge stop / launcher reveal between the two monitors does not always work. I'm unsure if this is a bug, or a feature. It seems that Unity might be trying to be helpful, and guess when I don't want the launcher based on having quickly moved the pointer between screens a couple of times recently
[17:22] <maxb> bug 1020058 sounds related
[17:45] <pavolzetor> Hello, I reported a bug while ago and it seems like nobody is going to fix it
[17:48] <pavolzetor> https://bugs.launchpad.net/unity/+bug/934431
[17:52] <pavolzetor> http://bazaar.launchpad.net/~unity-team/unity/trunk/view/head:/plugins/unityshell/resources/launcher_pip_ltr.png
[17:52] <pavolzetor> http://bazaar.launchpad.net/~unity-team/unity/trunk/view/head:/plugins/unityshell/resources/launcher_pip_rtl.png
[17:52] <pavolzetor> these two icons needs higher res, I do not have original ones
[19:16] <kruptos> I've upgraded to Ubuntu 12.10 automatically from 12.04 and I have lost all sound.  Can someone help me get sound back?
[19:40] <ceolin> hi folks, could someone tell me if appmenu requires patched versions of gtk and qt to work ?
[20:33] <crazydip> how do i order scropes in a lens?
[20:35] <crazydip> i can't find anything in the "Unity lenses and scopes" online docs
[20:40] <Deluxo> hello
[20:40] <Deluxo> id like to report a bug
[20:41] <Deluxo> active blur in compiz creates a very sluggish experience to the interface
[20:41] <Deluxo> i am using a decent notebook with optimus
[20:42] <Deluxo> so the bug is the following: when i change the active blur to no blur in CCSM
[20:42] <Deluxo> i get artifacts in dash and launcher area
[20:42] <Deluxo> when the dash overlaps a window
[20:43] <Deluxo> it make the window behind the dash all over the dash area
[20:43] <crazydip> what plugin in that in?
[20:43] <Deluxo> i have screenshots to show it exactly how does it look
[20:44] <Deluxo> it is the unity plugin in CCSM
[20:46] <Munchor95> ello
[20:46] <Munchor95> Hello*
[20:47] <Munchor> I'm an elementary OS Dev and we need some help from (you guys?). The bluetooth indicator is calling gnome-control-center (obviously). Does anybody have any idea of in which package that piece of code is? We couldn't find it anywhere on Launchpad and we really want to remove that link for elementary OS. Thank you in advance.
[20:47] <crazydip> Deluxo: submit the bug report with pictures to lauchpad's bug report - i would report one bug to compiz and then add "unity" to that bug report - go here to submit it: https://bugs.launchpad.net/compiz
[20:48] <Deluxo> right on it, thanks
[20:50] <crazydip> Deluxo: once you submit the bug to the compiz project, click "also afects project" to add unity
[20:50] <Deluxo> Alright, i'll do it
[20:50] <crazydip> good luck!
[21:10] <Deluxo> the report is complete.
[21:10] <Deluxo> so now i wait?
[21:11] <Munchor> Deluxo, I'm pretty sure so.
[21:12] <Deluxo> i reported some long time ago to launchpad, but i still very new to it.
[21:12] <Deluxo> alright, Thanks Munchor. Good bye!