[05:51] <didrocks> good morning
[06:53] <oSoMoN> good morning
[08:37] <mardy> Saviq: hi, how can you tell metacity to layout 9 workspaces in a 3x3 grid? I always get 2 rows, with 5 and 4 workspaces
[08:37] <Saviq> mardy: I can't ;)
[08:38] <Saviq> mardy: I hardcoded 3x3 in Workspaces.qml
[08:38] <mardy> Saviq: ahhh :-) OK, I'll try that as well
[08:38] <Saviq> that's something we need to address, too - when _NET_DESKTOP_LAYOUT isn't set
[08:38] <Saviq> we should have sqrt(workspaces) rows
[10:49] <eugenesan> Hi all, anyone here can answer specific question regarding unity-2d code?
[10:53] <njpatel> eugenesan, Kaleo or mardy  should be able to help
[10:54] <eugenesan> Thanks for tip, I suppose they are not here.
[10:54] <mardy> eugenesan: I'm here :-)
[10:55] <eugenesan> Oh, nice.
[10:56] <eugenesan> mardy: I am trying to revive homebutton and fighting next issue: HomeButtonApplet::enterEvent@homebuttonapplet.cpp called twice and I can't figure why. Any ideas why?
[10:58] <mardy> eugenesan: is it the home button applet for the top panel?
[10:58] <eugenesan> `yes, the one removed in recent versions
[11:03] <Saviq> mardy: the jumping background is a regression, I don't observe that in currently released version
[11:04] <Saviq> I've to relogin to check something, brb
[11:06] <mardy> Saviq: I'm trying with the latest trunk, and it's there
[11:07] <Saviq> mardy: yes
[11:07] <Saviq> that's what I meant, a regression between current release and trunk, sorry
[11:07] <mardy> Saviq: ah, you mean that the current release works fine?
[11:07] <Saviq> mardy: if you spread from a workspace with a maximized window, does your launcher still contain the underlying window?
[11:08] <Saviq> mardy: yes
[11:08] <mardy> Saviq: yes
[11:09] <mardy> Saviq: might be because of that geometry change I made to ScreenInfo
[11:09] <Saviq> do you remember if it wasn't like that before?
[11:09] <Saviq> mardy: but that's also there in current release
[11:09] <mardy> can't remember :-(
[11:10] <Saviq> bbiab
[11:23] <mardy> eugenesan: I remember it was functional, but since it was removed I never tried to use it. Try to run the panel in gdb, and see who calls enterEvent
[11:27] <eugenesan> mardy: Thanks for the tip
[12:04] <htorque_> hey everyone! i cannot build unity, getting lots of "error: ‘nux::State’ has not been declared" (i'm on nux trunk). is this known?
[12:05] <Trevinho> htorque_: did you use the nux 2.0 branch?
[12:05] <htorque_> oh, probably not.
[12:39] <htorque_> Trevinho: 'trunk' is actually the same as '2.0', but i guess recent nux commits cause the problem: http://paste.ubuntu.com/714142/ and http://bazaar.launchpad.net/~unity-team/nux/2.0/revision/504
[12:49] <Amaranth> smspillaz: Have you ever had any issues with override-redirect windows painting? It seems all my menus and notify-osd windows aren't rendering correctly, almost as if they aren't getting damaged
[12:50] <smspillaz> Amaranth: nope. What graphics hardware ?
[12:50] <Amaranth> smspillaz: It's intel with my gles changes :P
[12:51] <Amaranth> In an hour or two I'll know if it happens on my panda too but I'm expecting it will
[12:51] <smspillaz> I did make a change to have it so that decorations would paint on windows that didn't receive a damage event yet
[12:51] <smspillaz> (so if an application mapped a window, never drew on it then locked up you'd be able to close it
[12:51] <Amaranth> I get a flash of them drawing then the only part that draws is the part I have highlighted, presumably because the color change on highlight triggers a damage
[12:51] <Amaranth> and notify-osd windows only show up when fading in or out
[12:52] <Amaranth> It's gotta be something I'm doing in unity, I'm afraid it's the FBO stuff
[12:57] <smspillaz> Amaranth: ah
[12:57] <smspillaz> Amaranth: yeah it would be
[12:57] <smspillaz> Amaranth: check if the fbo is still bound after the nux stuff draws
[12:57] <smspillaz> Amaranth: I remember I hit problems with this
[12:57] <smspillaz> Amaranth: you know, its funny, I read over the blur plugin code the other day and finally had the "so that's how it works! moment"
[12:57] <Amaranth> nuxPrologue is handling that, iirc
[12:58] <Amaranth> God blur would be so much simpler if it was using Nux APIs :P
[12:58] <smspillaz> Amaranth: check the viewports are reset correctly
[12:58] <smspillaz> Amaranth: it does use the nux api's. Kind of
[12:58] <Amaranth> Oh, right, I think I don't do that anymore, oops
[12:59] <smspillaz> I still have some pending SRU changes to that fbo code, but I don't think its relevant to what we're doing
[12:59] <smspillaz> I think that the best approach is when the blur plugin itself is ported, we should make compiz specify a screen region to blur
[12:59] <smspillaz> using the same shader
[13:00] <smspillaz> Amaranth: so I finally figured out that compiz does it by doing a horizontal blur on the backbuffer first, then doing a backbuffer-to-texture copy (eg glCopyTexSubImage2D) and then painting that texture into an fbo with a vertical blur shader
[13:00] <smspillaz> (took a bit of jumping around in the code to figure that out)
[13:01] <Amaranth> sounds...fun
[13:11] <smspillaz> Amaranth: I dunno why it does it that way, reading off the backbuffer was hella expensive back in the days of not having a proper memory model
[13:12] <smspillaz> Amaranth: but then again, gaussian blur required fbos which required a memory model, and memory models made it about as expensive to do glCopyTexSubImage2D and glBindBuffer anyways (since you have to flush the pipeline in both cases)
[13:16] <zniavre> hello im experiencing strange behavior of xfce4-panel and indicator-plugin > the indicators are in reverse mode , how can i change the diplaying?
[13:16] <zniavre> (if displaying exists as word ...)
[13:17] <zniavre> http://i.imgur.com/szLEx.png   > top right  check the system indicator(at left side of indicator
[13:18] <zniavre> should i report a bug , against wich package ?
[13:44] <Amaranth> smspillaz: But nvidia was clearly doing FBOs without a proper memory manager
[13:44] <Amaranth> So that argument isn't entirely valid
[13:44] <Amaranth> Although it probably was for this particular case
[13:44] <Amaranth> Actually I think onestone wrote that while using fglrx so...
[13:46] <smspillaz> Amaranth: david wrote the gaussian blur code
[13:48] <Amaranth> Are you sure?
[13:48] <Amaranth> I thought blur was originally a beryl feature that required core changes and then onestone rewrote it for compiz in a way that didn't require those changes
[13:49] <Amaranth> also, ugh, unity takes forever to compile
[13:51] <Amaranth> smspillaz: hehe, resetting the viewport in nuxEpilogue actually makes things worse, now menus don't show up at all
[14:07] <smspillaz> Amaranth: the blur plugin for compiz was originally written by david. blurfx was dropped
[14:11] <kenvandine> njpatel, how can i tell if "All" is active in a CheckOptionFilter?
[14:11] <kenvandine> or didrocks ^^
[14:12] <greyback> 4menot4U
[14:12] <greyback> d'oh
[14:12] <greyback> there goes that password :(
[14:13] <kenvandine> greyback, hahaha
[14:13] <kenvandine> hate it when that happens :)
[14:15] <Saviq> greyback: rotfl
[14:15] <greyback> kenvandine: at least it wasn't an important one *looks around suspiciously*
[14:42] <Amaranth> smspillaz: So if I just wanted to disable UnityFBO usage entirely what would I need to do?
[14:44] <smspillaz> Amaranth: replace the hook points ?
[14:44] <smspillaz> unityfbo is not that complicated
[14:45] <Amaranth> smspillaz: I must be missing something because when I disable using it nothing draws anymore
[14:45] <Amaranth> Oh, actually...
[14:45] <Amaranth> I just forced allowWindowPaint to false all the time, seems to have done the trick
[15:00] <smspillaz> Amaranth: that will force unity to go on top of everything
[15:00] <smspillaz> you probably dont want that
[15:00] <smspillaz> (unless you like it appearing on top of the lock screen too)
[15:01] <Amaranth> smspillaz: Actually other than showing the name of the app I'm running that's a rather nice effect
[15:02] <Amaranth> I can't interact with the top bar but I can see the time, date, wifi status, battery status, etc
[15:02] <Amaranth> Kind of like the gnome-shell lock screen, no?
[15:06] <smspillaz> Amaranth: that's great, except when the app name happens to be "the big world domination red button" or whatever
[15:06] <smspillaz> oh, and the launcher showing $not_child_friendly_app pinned to the launcher
[15:07] <Amaranth> the launcher doesn't seem to be showing at all for me
[15:07] <smspillaz> oh and then the subsequent political crisis and emergency that occurrs claiming that window stacking is broken again and OH MY GOD THE WORLD IS GOING TO END
[15:07] <Amaranth> on the lock screen, I mean
[15:07] <smspillaz> Amaranth: make it not autohide
[15:07] <Amaranth> I wish I could figure out how
[15:07] <smspillaz> move windows out of the way
[15:07] <Amaranth> smspillaz: There are no windows in the way
[15:08] <Amaranth> Except the screensaver window
[15:08] <smspillaz> oh that would do it
[15:09] <Amaranth> there we go, now it listen to my "autohide must die" preference
[15:09] <Amaranth> and now it shows on the screensaver
[15:10] <Amaranth> smspillaz: Got a better suggestion? I was supposed to have a release out already
[15:10] <smspillaz> Amaranth: can I see the code ?
[15:10] <Amaranth> smspillaz: lp:~linaro-graphics-wg/unity/unity-gles2
[15:10] <smspillaz> thx
[15:11] <Amaranth> The unity plugin itself is running in to the same problem I had with the rest of compiz together
[15:11] <smspillaz> hm?
[15:11] <Amaranth> Too much state that you have to know to know what a given codepath is going to do
[15:11] <smspillaz> yeah, its
[15:11] <smspillaz> hacky
[15:12] <Amaranth> Doesn't help that I would normally be in bed a couple hours ago :P
[15:12]  * cwillu_at_work pokes lazy positioning with an smspillaz 
[15:12] <smspillaz> mostly because there is no such support for inserting arbitrary obejcts into the paint stack
[15:12] <smspillaz> cwillu_at_work: I'm not even meant to be working this week :(
[15:12] <cwillu_at_work> there's a pill for that
[15:12] <smspillaz> heh, I wish
[15:13] <Amaranth> hehe, you're not working, you're helping me ;)
[15:13] <smspillaz> well its more like
[15:13] <Amaranth> I don't know why Unity's FBO usage gives me so much trouble
[15:13] <smspillaz> people can still harrass me
[15:13] <Amaranth> I just can't wrap my head around what it does and where
[15:13] <smspillaz> but then I have a legitimate reason to tell them to go away
[15:14] <smspillaz> its like, the only difference is that being paid revokes that right to tell people to go away
[15:14] <cwillu_at_work> you should log on with an appropriate nick when you're being paid
[15:14] <cwillu_at_work> very good.
[15:14] <smslave> hi
[15:15]  * cwillu_at_work nearly avoids making various snarky remarks about that nick
[15:15] <smslave> Amaranth: you should just be able to disable it by making bind () and unbind () return false
[15:15] <smslave> and paint () return
[15:16] <Amaranth> smslave: That should be the same as commenting out the lines those are called on
[15:16] <Amaranth> smslave: Which makes the screen stop painting
[15:16] <Amaranth> That's why I ported this stuff to nux rather than disable it and leave it for someone else to port later :P
[15:17] <smslave> ... so, why do we need to deactivate it again ?
[15:18] <Amaranth> smslave: Menus (and presumably all override-redirect windows) aren't drawing at all
[15:18] <cwillu_at_work> smslave, the lazy positioning fixes aren't in -proposed/don't exist yet, correct?
[15:18]  * cwillu_at_work just wants to make sure it's not considered fixed, and will avoid pestering further if that's the case :p
[15:20] <smslave> Amaranth: http://bazaar.launchpad.net/~linaro-graphics-wg/unity/unity-gles2/view/head:/plugins/unityshell/src/unityshell.cpp#L462
[15:21] <smslave> cwillu_at_work: can you show me the bug # ?
[15:21] <cwillu_at_work> sec
[15:21] <Amaranth> smslave: You change it to mActiveFbo, not me :P
[15:21] <Amaranth> err, changed*
[15:21] <smslave> Amaranth: I added that becauset there was some nuxPrologue/nuxEpilogue wrappers around paintPanelShadow
[15:21] <smslave> so what unityfbo did was it set the "active framebuffer" in unityscreen to the currently bound framebuffer
[15:22] <cwillu_at_work> smslave, bug #874514 is what I reported
[15:22] <smslave> so that when nuxepilogue gets called it will be bound back to the correct one or 0 when there is no buffer bound
[15:23] <smslave> Amaranth: since you don't update mActiveFbo anymore when binding the nux framebuffers, that line can be nuked
[15:23] <Amaranth> hmm
[15:24] <Amaranth> well, no, I can nuke mActiveFbo and set that to 0 though
[15:24] <smslave> cwillu_at_work: that should be fixed with the *next* proposed update (some event matching fixes came in there)
[15:24] <smslave> cwillu_at_work: the reason is because lazy positioning in its current form is really unsafe when we have made configure requests on that window
[15:25] <cwillu_at_work> incidentally, I still get the configure notify missed message thingy occasionally under the current -proposed
[15:25] <smslave> right, those should be fixed with the *next* proposed (dunno when that was uploaded)
[15:26] <smslave> matching configure notify events is surprisingly hard
[15:32] <Amaranth> smslave: http://bazaar.launchpad.net/~unity-team/unity/4.0/view/head:/plugins/unityshell/src/unityshell.cpp#L954
[15:33] <Amaranth> you set it to true then test if its true? :)
[15:33] <Amaranth> I sure hope the compiler optimizes that out
[15:33] <smslave> ret = gScreen->glPaintOutput(attrib, transform, region, output, mask);
[15:33] <smslave> stuff happens
[15:33] <smslave> namely
[15:33] <smslave> http://bazaar.launchpad.net/~unity-team/unity/4.0/view/head:/plugins/unityshell/src/unityshell.cpp#L649
[15:34] <Amaranth> you didn't link to glPaintOutput code you linked to paintDisplay
[15:34] <Amaranth> which is what that if is guarding
[15:35] <smslave> Amaranth: http://bazaar.launchpad.net/~unity-team/unity/4.0/view/head:/plugins/unityshell/src/unityshell.cpp#L1642
[15:35] <Amaranth> I have no idea what you're linking me and why
[15:35] <smslave> glPaintOutput -> base glPaintOutput -> UnityWindow::glDraw -> paintDisplay (if condition met) -> doShellRepaint = false
[15:36] <Amaranth> You set it to true, draw something if its true, set it to false, then another part of code checks if its true or false
[15:36] <smslave> so the idea is
[15:36] <smslave> set it to true
[15:36] <smslave> wait for a window to paint
[15:36] <smslave> if we need to paint directly below that window
[15:36] <smslave> paint
[15:36] <smslave> set it to false
[15:36] <Amaranth> I'm pretty sure this bit is the cause of my problem when turning off FBO usage
[15:37] <smslave> if it is still true, then we didn't paint
[15:37] <smslave> so paint on top of everything
[15:37] <eugenesan> mardy: regarding duplicated HomeButtonApplet::enterEven, looks like appearance of launcher causes additional event.
[15:37] <smslave> Amaranth: the cause of your problem was that
[15:37] <smslave> Amaranth: an invalid fbo was bound
[15:37] <smslave> so nothing was drawn
[15:37] <Amaranth> FBO 0 isn't invalid
[15:38] <smslave> invalid in the logistical sense
[15:38] <smslave> and then nothing would get drawn until  the next paint pass when that state was released
[15:42] <Amaranth> smslave: hello from metacity
[15:42] <Amaranth> smslave: that wasn't the problem :(
[15:43] <Amaranth> afaik binding FBO 0 means frontbuffer
[15:43] <Amaranth> so that couldn't have been the problem
[15:46] <smslave> Amaranth: you should remove that line anyways
[15:47] <Amaranth> smslave: That line has existed since before your UnityFBO stuff
[15:47] <Amaranth> It just used to explicitly set to 0
[15:47] <smslave> because nux paints stuff, it was used to reset state iirc
[15:47] <Amaranth> Because while blur and unityshell aren't doing something 0 is the wrong answer
[15:47] <Amaranth> err, 0 is the right answer
[15:48] <Amaranth> theoretically that line isn't needed because for every bind you do an unbind
[15:48] <Amaranth> but it doesn't hurt to have it and it protects against accidents
[16:00] <Amaranth> I think I'm just going to get some sleep and work on this again when I'm more alert
[16:01] <smslave> sounds like a plan
[16:01] <smslave> night!
[16:22] <smoser> is there a keypress to make the launcher bar go away ?
[16:22] <smoser> when someone says my name in irc, and i'm working, it pops up (which is nice) but sticks around too long.
[16:22] <smoser> as the xchat icon wiggles
[16:49] <njpatel> kenvandine, filtering == false
[16:58] <kenvandine> there goes njpatel with a drive by answer, love that guy :)
[17:08] <kenvandine> although his answer is either not correct or i found a bug
[19:19] <jo-erlend> the other day, I found a page with a description of how to use the launcher API. I can't find it again. Anyone?
[20:24] <kenvandine> jo-erlend, https://wiki.ubuntu.com/Unity/LauncherAPI
[20:40] <jo-erlend> someone is getting two launchers at the same time. Is that a known bug?
[20:46] <jo-erlend> haha, he had used a screenshot as a desktop background :>
[20:47]  * cwillu_at_work hands jo-erlend a knife, to be used in whatever way comes naturally
[20:49] <jo-erlend> actually, it was quite nice to be able to disprove a bug for once :>
[23:03] <Andy80> is there a known bug about drag&dropping files form Nautilus to Launcher? I cannot drop a pdf :\ the çauncher keeps staying transparent
[23:24] <cwillu_at_work> Andy80, yep;  I believe there's a fix in -proposed