[00:04] <smspillaz> nerochiaro: I'm not sure but I think everyone gets ClientMessages on the root window
[00:04] <smspillaz> but the fastest way to check is to just run an event loop and check for them, since you don't register for ClientMessages
[00:06] <smspillaz> basically the rule of thumb is that the message goes to client that actually owns the window that the ClientMessage was sent to, but yes, there isn't anything clear in the X doc about who gets ClientMessages on the root window
[00:08] <nerochiaro> smspillaz: yep, i did check. i don't get them
[00:08] <smspillaz> nerochiaro: ok
[00:08] <nerochiaro> smspillaz: i thought i had to register for them in some special way, but if you say you don't have to, then there's little left for me to check
[00:09] <smspillaz> nerochiaro: nope, all Clients get SelectionNotify/Request and ClientMessage by default
[00:09] <smspillaz> nerochiaro: what are yo utrying to check exactly? when the window gets minimized ?
[00:09] <nerochiaro> smspillaz: yeah
[00:09] <smspillaz> there might be an EWMH prop for that
[00:12] <smspillaz> nerochiaro: XSelectInput (dpy, yourwindow, PropertyChangeMask);
[00:13] <smspillaz> nerochiaro: switch (event->type) { case PropertyNotify: if (event->xproperty.type == XInternAtom (dpy, "_NET_WM_STATE", 0)) { /* XGetWindowProperty _NET_WM_STATE */ and check for _NET_WM_STATE_HIDDEN
[00:13] <smspillaz> whcih I think is (1 << 8)
[00:14] <smspillaz> see http://standards.freedesktop.org/wm-spec/wm-spec-latest.html#id2541720
[00:14] <nerochiaro> smspillaz: looks good, even thought i need to do that for all the windows, not just mine
[00:14] <smspillaz> the description there says that this was written exactly because pagers need to tell :)
[00:14] <smspillaz> nerochiaro: sure, just XQueryTRee
[00:15] <smspillaz> not sure how well this will work with reparenting though
[00:15] <nerochiaro> smspillaz: hmm, i'll give it a shot tomorrow morning regardless
[00:16] <smspillaz> *cough* might just need to assume that non-override redirect windows are going to have 2 parents
[00:16] <smspillaz> eg frame -> wrapper -> client
[00:17] <nerochiaro> smspillaz: what i think i will do is get the list of windows from bamf, then XSelectInput on them
[00:18] <smspillaz> nerochiaro: yeah, because bamf uses _NET_WM_CLIENT_LIST (or something like that) so this will be correct
[00:19] <smspillaz> nerochiaro: XGetWindowProperty (dpy, root, XInternAtom (dpy, "_NET_CLIENT_LIST_STACKING", 0);
[00:19] <smspillaz> http://standards.freedesktop.org/wm-spec/wm-spec-latest.html#id2505795
[00:20] <nerochiaro> smspillaz: good. i already use bamf's window list in other places, and it's correct
[00:20] <smspillaz> :)
[00:21] <nerochiaro> smspillaz: hopefully it will work this way. thanks for the tip
[00:21] <smspillaz> yeah
[00:21] <smspillaz> _NET_WM_STATE_HIDDEN is supposed to be set by the wm when the window is minimized only
[00:21] <smspillaz> or rather
[00:21] <smspillaz> only when it is minimized
[00:22] <nerochiaro> smspillaz: hopefully before it is minimized
[00:22] <smspillaz> let me check
[00:24] <smspillaz> nerochiaro: we unmap the frame and client before setting the state
[00:24] <nerochiaro> smspillaz: damn. so I can't use it
[00:25] <smspillaz> what are you trying to do exactly?
[00:26] <nerochiaro> smspillaz: monitor when windows are about to be minimized and save somewhere their pixmaps, so i can display some meaningful thumbnail. it's basically #1 from your article
[00:26] <smspillaz> ah right
[00:26] <smspillaz> yeah, that's why I said it needs to be done inside the wm
[00:27] <smspillaz> the good thing is that I made w->minimize () wrappable so we can write a simple compiz plugin which will do this I guess
[00:28] <nerochiaro> smspillaz: that sounds good, for compiz. i'm gonna need something that works for metacity though. i was going to try and backport the "stack below desktop" patch from mutter
[00:28] <smspillaz> mmm
[00:29] <smspillaz> I guess you could do that, it just seems like asking for trouble
[00:29] <nerochiaro> smspillaz: what would you suggest ?
[00:29] <smspillaz> shaping, but like we discussed earlier you can't use that :)
[00:29] <nerochiaro> smspillaz: indeed :)
[00:29] <smspillaz> I suppose you could just do #1 in metacity too
[00:30] <nerochiaro> smspillaz: do you think it's less messy than backporting that patch ? i will need some way to get these pixmaps out from the wm into the unity2d task switcher though
[00:31] <nerochiaro> if i end up doing #1
[00:31] <nerochiaro> #1 inside metacity, i mean
[00:31] <smspillaz> nerochiaro: I would say that you could probably just save the pixmap handle into a window property
[00:31] <nerochiaro> smspillaz: i was thinking the same
[00:32] <smspillaz> you just need to watch out for when the pixmap goes away
[00:32] <nerochiaro> smspillaz: sounds like the simplest way
[00:32] <nerochiaro> smspillaz: i'm gonna copy that into a raster on the client, so even if it goes away it's gonna be ok
[00:32] <smspillaz> ok
[00:33] <smspillaz> is there a zero-copy implementation of creating an XRenderPicture from a pixmap ?
[00:34] <nerochiaro> smspillaz: i don't think so, but that copy doesn't seem like a major overhead in most cases we've seen so far
[00:35] <smspillaz> yeah
[00:36] <nerochiaro> smspillaz: plus we need to scale it and keep only the shaped areas, so in the end manipulating the image is more efficient in qt than doing the same thing on an x pixmap
[00:37] <nerochiaro> smspillaz: anyway, time for me to go to bed now :)
[00:47] <Omega> Hmm, icon themes aren't applied in realtime?
[00:56] <rbnswartz> DBO you around?
[00:57] <smspillaz> nerochiaro_sleep: indeed
[06:41] <kvalo> morning
[07:27] <smspillaz> kvalo: morning :)
[07:28] <kvalo> smspillaz: good morning. how's the summer down there? :)
[07:29] <smspillaz> hot
[07:29] <smspillaz> well actually, we were meant to have a hurricane, but that never happened
[07:29] <smspillaz> *shrug*
[07:29] <kvalo> smspillaz: wow
[07:29] <smspillaz> it was slightly stormy though a few days ago
[07:36] <smspillaz> hrm
[07:36] <smspillaz> TIL that the decoration actually renders relevant to the client window size and not the frame size

[08:01] <oSoMoN> good morning
[08:09] <MacSlow> greetings folks
[08:11] <MacSlow> hey didrocks
[08:11] <didrocks> hey MacSlow
[08:31] <smspillaz> hi @ all
[08:51] <kvalo> kamstrup: morning. I updated the branch: https://code.launchpad.net/~kvalo/indicator-network/libconnman-service-properties/+merge/48034
[08:53]  * kamstrup looking
[08:57] <kamstrup> kvalo: approved!
[08:57] <apw> anyone reporting 'focus' issues with yesterdays unity... i am seeing the wrong cursor and lack of sensitivity on some elements ... actiling like one of the semi-transparent places boxes is on the screen; though there is nothing visible
[08:58] <apw> as in the area that one of those covers seems to be the area in which window specific cursor and click behaviour does not work
[08:59] <smspillaz> apw: I am looking into this now
[09:08] <didrocks> smspillaz: some than the bug I showed you yesterday
[09:09] <didrocks> smspillaz: btw, I'm on this weird state right now, with stuck mouse and working keyboard
[09:09] <didrocks> smspillaz: tried xwininfo, but got a "can't grab the mouse"
[09:13] <didrocks> smspillaz: because I restart unity ^^
[09:13] <didrocks> before*
[09:13] <smspillaz> something has a stale mouse grab
[09:13] <didrocks> if I can add any useful info
[09:13] <smspillaz> what did you do just before your mouse became frozen ?
[09:13] <didrocks> is there a way to find the guilty? :)
[09:13] <didrocks> just chatting on weechat :)
[09:13] <didrocks> so, nothing fancy
[09:13] <smspillaz> did you click on anything, alt-tab ?
[09:13] <smspillaz> and suddenly your mouse became frozen
[09:14] <kvalo> kamstrup: thanks a lot!
[09:14] <didrocks> maybe ctrl + alt + arrow
[09:14] <didrocks> but really, nothing IMHO
[09:14] <smspillaz> right
[09:14] <smspillaz> its a bit difficult to trace unless we know exactly what grabbed the mouse and didn't ungrab it
[09:14] <smspillaz> but ctrl-alt-arrow says that wall might be the cause
[09:14] <smspillaz> I'll look into it when I get some time
[09:15] <didrocks> smspillaz: not sure it's wall, weird that mouse is grabbed but not the keyboard
[09:15] <didrocks> smspillaz: there is no tool to try to know which ones is doing that?
[09:15] <smspillaz> nope
[09:16] <didrocks> hum… ok, let's see running processes
[09:16] <smspillaz> the only thing I can think of is that we activated a mouse grab (eg raising or focusing a window) and didn't call XAllowEvents for some reason
[09:16] <didrocks> not using the mouse is a "fun" exercice :)
[09:16] <smspillaz> let me see if there's something the code that can cause that to happen
[09:16] <didrocks> smspillaz: ok, I keep that state meanwhile (not too long please) :)
[09:18] <smspillaz> didrocks: hrm, so we call XAllowEvents if the number of grabs is empty
[09:18] <smspillaz> lets see if the debug spewer plugin can come to the rescue here
[09:18] <didrocks> smspillaz: do you really think it's compiz calling the grab?
[09:18] <smspillaz> didrocks: it could be
[09:19] <didrocks> smspillaz: I see no obvious process that can be guilty btw
[09:19] <smspillaz> ah, yes
[09:19] <didrocks> smspillaz: did you look at the xwininfo -root -tree I posted on the bug reports?
[09:20] <smspillaz> didrocks: have you got dbus enabled ?
[09:20] <smspillaz> didrocks: I haven't really had time to look into them yet
[09:20] <didrocks> smspillaz: the plugin isn't
[09:20] <smspillaz> didrocks: hrm, mabye you can try this
[09:20] <didrocks> smspillaz: didn't njpatel put that as a priority? :)
[09:20] <smspillaz> have you got a netbook or something?
[09:20] <didrocks> smspillaz: yeah, one sec
[09:20] <smspillaz> didrocks: it is :) I just took some rest yesterday (I only work part time :))
[09:20] <didrocks> smspillaz: sure, just thinking you worked on the gconf bug recently
[09:21] <didrocks> smspillaz: ok, ready
[09:21] <smspillaz> I worked on the decoration issue just before that, but it is fixed
[09:21] <smspillaz> didrocks: ok, you should be able to ssh -X in and launch ccsm with COMPIZ_CONFIG_PROFILE=ubuntu
[09:21] <didrocks> k
[09:21] <didrocks> smspillaz: can you look at the xwininfo trace meanwhile? (starting my netbookà
[09:21] <smspillaz> sure
[09:21] <didrocks> it's on the bug report, you have two of them :)
[09:22] <smspillaz> did you have the bug # off the top of your head ?
[09:23] <didrocks> smspillaz: if I can click, I could
[09:23] <smspillaz> hehe
[09:23] <didrocks> smspillaz: better look at your bug
[09:23] <smspillaz> ok :p
[09:23] <didrocks> smspillaz: ok look for "invisible" on the bug title
[09:24] <didrocks> bug #709461
[09:24] <smspillaz> ah, found it :)
[09:25] <didrocks> great, the ssh connexion died? what's this wifi? :/
[09:25] <smspillaz> heh
[09:25] <smspillaz> let me know when you get it up and running
[09:25] <didrocks> smspillaz: started
[09:27] <smspillaz> cool
[09:27] <smspillaz> can you enable d-bus ?
[09:27] <didrocks> smspillaz: you know that enabling/disabling a plugin with unity crash compiz
[09:28] <didrocks> is that what you wanted me to try? :/
[09:32] <smspillaz> oh
[09:32] <smspillaz> right
[09:32] <smspillaz> damn that
[09:32] <smspillaz> err ok
[09:32] <smspillaz> well if you get it again, what you can do is this
[09:32] <smspillaz> 1) make sure dbus is enabled
[09:32] <didrocks> smspillaz: so I should enable dbus from now on
[09:32] <smspillaz> 2) indeed
[09:33] <didrocks> smspillaz: ok, the dbus plugin will enable us to know if compiz is grabbing the mouse?
[09:33] <didrocks> smspillaz: again, maybe it's not compiz, not sure about it
[09:34] <smspillaz> didrocks: well we can't activate the debug spewer action because something is grabbing the screen
[09:34] <smspillaz> ... are you still in the bug mode actually ?
[09:34] <didrocks> yeah
[09:34] <smspillaz> didrocks: debug spewer keybinding set ?
[09:34] <didrocks> not the new unity in any case as I got it before and seems that I see nothing process-wise
[09:34] <didrocks> smspillaz: let me check
[09:35] <didrocks> smspillaz: I reset to the default recently, so debug spewer isn't set
[09:35] <didrocks> smspillaz: but yeah, it should work for new time
[09:35] <smspillaz> is it enabled though ?
[09:35] <didrocks> next*
[09:35] <smspillaz> didrocks: maybe try disabling unity first then enabling debug spwer
[09:35] <smspillaz> the mouse should still be grabbed
[09:36] <didrocks> smspillaz: no, it's not :/
[09:36] <didrocks> hum, trying
[09:36] <didrocks> ccsm is a pain with keyboard :)
[09:36] <smspillaz> :)
[09:36] <smspillaz> you can always ssh -X
[09:36] <smspillaz> that's why I said to :p
[09:37] <didrocks> smspillaz: yeah, but ssh -X is breaking the connection a lot
[09:37] <didrocks> smspillaz: hum, interesting, I can't set a keybinding on ccsm
[09:37] <didrocks> like clicking on ctrl/alt… doesn't do anything
[09:37] <didrocks> to define it
[09:38] <didrocks> no forget it :)
[09:38] <didrocks> my bad
[09:38] <smspillaz> lol
[09:38] <didrocks> ok
[09:38] <didrocks> so, it should be activated
[09:38] <didrocks> not that nothing happened when I removed the unity plugin
[09:38] <didrocks> and add it back
[09:39] <didrocks> smspillaz: nothing in /tmp
[09:39] <didrocks> smspillaz: seems the plugin isn't loaded in fact
[09:40] <didrocks> smspillaz: so restarting unity and waiting for next time?
[09:40] <didrocks> smspillaz: should I still enable the dbus plugin as well?
[09:46] <didrocks> smspillaz: so, this was interesting, I restarted compiz, I've been only to click on the focused application on ws 1 (which was chromium), not on any other
[09:47] <didrocks> smspillaz: even starting a new application (appearing above chromium) and the mouse events were going through
[09:47] <didrocks> smspillaz: I had to restart metacity to get it working
[09:48] <smspillaz> weird
[09:48] <smspillaz> why do you keep hitting all the weird bugs now :)
[09:48] <didrocks> as I told, it's maybe a bad new X <-> compiz interaction
[09:48] <smspillaz> there is always one person who keeps getting tons of bugs
[09:49] <didrocks> smspillaz: I'm not the only one… we already have 10 people reporting the same issue
[09:49] <didrocks> since yesterday
[09:49] <smspillaz> focus issues?
[09:49] <didrocks> yeah
[09:49] <smspillaz> what changed since yesterday?
[09:49] <didrocks> smspillaz: well, since yesterday == since last compiz
[09:49]  * smspillaz looks at the changelog
[09:49] <didrocks> the one we uploaded (because I got that bug this week-end)
[09:50] <didrocks> smspillaz: 1:0.9.2.1+glibmainloop4-0ubuntu4
[09:50] <didrocks> is the version introducing it (I was on that version all the week-end and I got it)
[09:51] <smspillaz> hrm
[09:51] <smspillaz> so many last minute bugs. argh! why does this always happen :/
[09:51] <didrocks> because it's "always like that"? ;)
[09:52] <didrocks> smspillaz: ok, so after restarting metacity and switching back to compiz, all is fine now
[09:52] <didrocks> smspillaz: I have the spewer and dbus plugin enabled
[09:52] <didrocks> smspillaz: did you find anything useful in the xwininfo trace?
[09:52] <smspillaz> not really
[09:52] <smspillaz> I'm going to try and reproduce this myself
[09:52] <didrocks> ok, nothing weird apparently :/
[09:52] <didrocks> smspillaz: I'll let you know as soon I have it again
[09:53] <smspillaz> its basically just 1) make chromium demands-attention 2) shit hits the fan ?
[09:53] <didrocks> smspillaz: not sure it is really to the chromium demanding attention
[09:53] <didrocks> smspillaz: I was just describing what I got as told :)
[09:53] <smspillaz> it might not be related, but it might trigger something else
[09:53] <didrocks> yeah, unity was showing the icon
[09:54] <didrocks> but this time, I didn't get this or I didn't pay attention
[09:55] <smspillaz> ok
[09:55] <smspillaz> this focus bug might be related to the empathy fix
[09:55] <didrocks> smspillaz: anyway, next week, we switch back to master?
[09:55] <didrocks> hum, let me check
[09:55] <didrocks> no, the empathy fix wasn't in 1:0.9.2.1+glibmainloop4-0ubuntu4
[09:55] <smspillaz> didrocks: yes, if we can confirm the gconf issue is gone then I will merge glib into master
[09:55] <didrocks> where did you look the changelog?
[09:55] <smspillaz> lp:compiz
[09:56] <didrocks> smspillaz: look at 1:0.9.2.1+glibmainloop4-0ubuntu4
[09:56] <smspillaz> ok
[09:56] <didrocks> the empathy fix was after
[09:56] <smspillaz> I'll just dist-upgrade and look at that changelog :p
[09:56] <smspillaz> or has the empathy fix been packaged ?
[09:56] <didrocks> right, yesterday
[09:56] <didrocks> it's the version I'm running
[09:56] <smspillaz> ok
[09:56] <didrocks> smspillaz: think that there is a new Xorg again :)
[09:57] <didrocks> not sure if the landing time was unfortunate
[09:59] <smspillaz> didrocks: hrm the latest version is ubuntu8
[09:59] <smspillaz> so it was ubuntu4 that introduced the bug ?
[09:59] <didrocks> smspillaz: correct
[10:00] <smspillaz> oh wow, ok that's a lot to get through
[10:00] <didrocks> smspillaz: yeah, it's basically all the patches you gave to me for alpha2
[10:00] <smspillaz> oof
[10:00] <didrocks> hum… and there is this ABI break
[10:00] <smspillaz> ok, time to debug this manually
[10:00] <didrocks> otherwise, I would have revert
[10:01] <didrocks> and see if it's really compiz's fault
[10:01]  * smspillaz builds the package
[10:01] <didrocks> smspillaz: you see, stop breaking the ABI! we can't see if it's because of you or now (</kidding>) :)
[10:04] <didrocks> smspillaz: I can't trigger it on purpose. I tried… but it's desperatly working there…
[10:16] <smspillaz> didrocks: I think we need to define a stable API/ABI
[10:16] <didrocks> smspillaz: yeah that will be easier for git/bzr bissect and such
[10:16] <smspillaz> didrocks: right now the code is just a clusterf... of random API that we've added because "some plugin needs it"
[10:17] <smspillaz> unfortunately, doing that is just going to take a lot of time
[10:17] <smspillaz> and there is so much else going on
[10:17] <didrocks> right :)
[10:17] <smspillaz> it does need to be done though, the current code is a disaster-zone
[10:18] <smspillaz> compiz++ was a half step there
[10:19]  * smspillaz goes to dinner
[10:40] <didrocks> RAOF: do you think new Xorg can be linked to new issues we got (like bug #709461)
[10:40] <didrocks> RAOF: more info, xwininfo tells me "can't grab mouse focus", is there an easy way to know which app grabbed it?
[10:41] <RAOF> didrocks: That bug pre-dates the Xserver upload, so it's not that.
[10:41] <RAOF> I'm not sure how you can tell which app has grabbed the mouse, sorry.
[10:42] <didrocks> RAOF: ok, at least this scenario is moved away
[10:42] <didrocks> thanks
[10:42] <RAOF> I've seen that problem too, once.
[10:43] <didrocks> I got it 4/5 times already :/
[10:44] <RAOF> Maybe the new X will magically fix it for you? :)
[10:44] <didrocks> RAOF: I like this kind of magic when it happens :)
[11:02] <kamstrup> How do I debug segfaults in libunityshell.so? Compiz seems to be chugging happily along even though I get (this is from my custom branch):
[11:02] <kamstrup> compiz (core) - Error: Couldn't load plugin '/usr/lib/compiz/libunityshell.so' : /usr/lib/compiz/libunityshell.so: undefined symbol: _ZN19LauncherEntryRemote16StaticObjectTypeE
[11:02] <kamstrup> Segmentation fault (core dumped)
[11:03]  * kamstrup should probably have his C++ license revoked
[11:04] <agateau> kamstrup: sounds like an ABI breakage
[11:04] <didrocks> yeah
[11:04] <kamstrup> i'm just trying to hack in support for the new launcher api
[11:04] <didrocks> agateau: weird that you have system unity with system compiz
[11:04] <didrocks> (as it's in /usr/lib)
[11:04] <agateau> kamstrup: one side of the code needs to be rebuild
[11:04] <didrocks> oupss kamstrup ^^
[11:05] <kamstrup> so adding a few functions/classes to libunityshell.so here and there, but breaking libunityshell.so's ABI should matter afaik?
[11:05] <didrocks> kamstrup: which version of compiz-dev do you have?
[11:06] <kamstrup> didrocks: 1:0.9.2.1+glibmainloop4-0ubuntu8
[11:06] <kamstrup> lemme try a clean rebuild
[11:06] <didrocks> hum… weird, you should be all right
[11:07] <agateau> kamstrup: did you add a *virtual* function?
[11:08] <kamstrup> agateau: nope, shoul i? :-)
[11:08] <agateau> kamstrup: if you want to break ABI, it's a good idea, otherwise no :)
[11:09] <kamstrup> agateau: but i'm hacking purely inside unity... so there should be no issue in breaking the ABI since it's only internal and libunityshell.so is dlopen()ed by compiz?
[11:10] <agateau> kamstrup: well, for some reason something changed in the LauncherEntryRemote class since libunityshell was build and it doesn't like it
[11:22] <kamstrup> agateau: just tried a clean rebuild, and it's definitely something in my linking that is messed up, see http://paste.ubuntu.com/560898/
[11:23] <agateau> kamstrup: wow
[11:23] <kamstrup> agateau: so what kind of newbie C++ mistake would cause this? :-)
[11:23] <agateau> kamstrup: nm --demangle will make it easier to read
[11:24] <kamstrup> agateau: http://paste.ubuntu.com/560900/
[11:25] <agateau> kamstrup: what's weird is that this symbol is not a method...
[11:26] <agateau> kamstrup: I am wondering if it could have something to do with rtti (given that it talks about object type)
[11:26] <agateau> kamstrup: maybe there is a mixup in build options
[11:26] <agateau> ?
[11:26] <kamstrup> agateau: perhaps...
[11:28] <kamstrup> agateau: I think it's something Nux related...
[11:28] <ronoc> kamstrup, thx for the feedback on that merge, I was nearly sure I was doing it right the first time :) with the occasional leak eek !
[11:28] <agateau> kamstrup: could be, because google does not know much about "StaticObjectType"
[11:29] <agateau> kamstrup: does grepping for StaticObjectType in nux src yield something?
[11:30] <kamstrup> agateau: yep, it gives tonnes of lines
[11:30] <agateau> kamstrup: ahah!
[11:30] <agateau> kamstrup: can you post an url or pb an excerpt?
[11:31] <kamstrup> agateau: http://paste.ubuntu.com/560908/
[11:32] <kamstrup> njpatel: !!! your eyes are needed!
[11:32] <agateau> indeed
[11:32] <agateau> kamstrup: maybe nux ABI changed?
[11:32] <kamstrup> njpatel: what's the deal with this StaticObjectType in Nux and why do I get http://paste.ubuntu.com/560900/ ?
[11:33] <kamstrup> agateau: but I just did a clean rebuild on libunityshell.so and I still get the error
[11:34] <kamstrup> agateau: the class in question derives from nux::InitiallyUnownedObject, and I guess that's why... in some way...
[11:35]  * kamstrup will ponder this over lunch
[11:38] <kamstrup> agateau: I think I maybe got it... one needs a NUX_DECLARE_OBJECT_TYPE (LauncherEntryRemote, nux::InitiallyUnownedObject); in the right place...
[11:39] <agateau> kamstrup: ohoh
[11:39] <agateau> kamstrup: glad you found it, I would have been quite useless here :)
[11:41] <njpatel> kamstrup, yeah, you should be copying from an existing source :)
[11:41] <njpatel>  /header
[11:41] <njpatel> kamstrup, it's for some advanced debugging that it's like that
[11:42] <njpatel> apparently we can do some funky things with object allocation/lifecycle/refcount debugging thanks to the NUX_* magic
[11:43] <kamstrup> njpatel: ok  - i don't complain... i'm used to GObject boilerplate after all ;-)
[11:43] <kamstrup> njpatel: it's just a bit tricky to reverse engineer :-)
[11:43] <njpatel> yeah, I started to complain and then remembered about GObject and decided to keep my mouth shut :)
[11:43] <kamstrup> lol
[11:43] <njpatel> i mean, if I inflicted GObject on Jay, he can inflict this on me
[11:44] <ion> I’d love to try Unity (3D). If only bug http://launchpad.net/bugs/686698 were fixed. :-) Perhaps i’ll get around to trying to fix it myself some day.
[11:45] <kamstrup> njpatel: now I am at a loss... I still get the unresolved StaticObjectType, but my class looks like this now http://paste.ubuntu.com/560913/
[11:45] <kamstrup> which to my research should be ok
[11:48] <njpatel> kamstrup, uno momento
[11:49] <njpatel> ion, we're working on it with the AMD guys...sorry it's taken so long, please bear with us :)
[11:51] <njpatel> kamstrup, do you have NUX_IMPLEMENT_OBJECT_TYPE (LauncherEntryRemote); in the cpp?
[11:51] <ion> Nice :-). No worries. I was just making noise every now and then because i wasn’t sure it had been noticed that the bug is still there, with the status still as “fix released” and all. Now that i have a response, i’ll just wait patiently. Thanks. :-)
[11:52] <njpatel> ion, could you change it back to confirmed? as you obviously still have the issue
[11:53] <ion> It was the first thing i tried but i don’t seem to have the rights to modify the status.
[11:54] <njpatel> ion, ah, I've done that now
[11:54] <ion> Thanks :-)
[11:55] <kamstrup> njpatel: zomg! that did the trick
[11:55] <njpatel> MAGIC!
[12:46] <dnivra> hello. what is the command that locks the screen in unity similar to gnome-screensaver in gnome? i would like to download the source so wanted to know.
[12:48] <RAOF> dnivra: That would be gnome-screensaver.
[12:48] <dnivra> RAOF: it is same in unity as well?
[12:49] <RAOF> dnivra: Unity's just a shell; it does the same job as gnome-panel+compiz.  The rest of the gnome stack is the same.
[12:49] <ogra> given that unity is a frontend ...
[12:50]  * ogra dislikes the word "shell" ... we had a week long discussion why ubuntu replaces bash with unity on the ubuntu-users ML
[12:50] <ogra> :)
[12:52] <dnivra> i have another question. I want to create a few controls(buttons) that get displayed when the screen is locked. i wish to do it in python. any suggestions how I possibly could?
[12:53] <RAOF> dnivra: I think by patching gnome-screensaver to allow you to extend it with python.
[12:54] <dnivra> RAOF: sorry but what did you mean by patching?
[12:55] <dnivra> i mean gnome screensaver isn't written in python right?
[13:20] <kamstrup> njpatel: I have https://code.launchpad.net/~unity-team/unity/launcher-api/+merge/48152 up - we may have to get DBO involved for the remaining bits
[13:34] <njpatel> kamstrup, sounds good, I think he was working on the rendering aspect yesterday, so just sync with him?
[13:34] <kamstrup> njpatel: sure, i'll try to catch him later
[13:37] <njpatel> sweet
[13:57] <smspillaz> didrocks: if you remembered correctly was the invisible area about the same width as your screen and about 50 px high ?
[13:58] <smspillaz> I'm looking at
[13:58] <smspillaz> 0x460118c "chromium-browser": ("chromium-browser" "Chromium-browser")  1758x50+119+83  +119+83
[13:58] <didrocks> smspillaz: it was more like if it was fullscreen
[13:58] <smspillaz>         1 child:
[13:58] <smspillaz>         0x460118d (has no name): ()  1x1+-1+-1  +118+82
[13:58] <smspillaz>      0x1200167 (has no name): ()  1920x1176+-1920+-1176  +-1920+-1176
[13:58] <smspillaz> hrmm, but maybe it had a pointer grab like you said
[13:58] <didrocks> smspillaz: didn't I added a new comment specifying that after killing all chromium processes, I was still having the invisible window?
[13:58] <smspillaz> ok
[13:59] <smspillaz> it was something else then
[13:59] <didrocks> yeah
[13:59] <smspillaz> dammit I hate it how in the pre-dbus days applications would abuse creating unmapped windows + ClientMessage for IPC
[13:59] <smspillaz> ok, I don't see anything particularly odd
[13:59] <smspillaz> didrocks: maybe next time post your xprop -root and xwininfo -root -tree
[13:59] <smspillaz> just so I can confirm this
[13:59] <didrocks> "I tried to kill all chromium process because of the "emergency state relationship", and but it didn't fix it…"
[14:00] <didrocks> smspillaz: ^^
[14:00] <didrocks> on the bug report :)
[14:00] <smspillaz> because what I think is happening is that some window is getting created but not tracked so it is not reparented obviously
[14:00] <didrocks> smspillaz: so, ok, xprop -root in addition to xwininfo
[14:01] <didrocks> smspillaz: you can look at the reporter one as well for xwininfo
[14:09] <multiplatinum> hey ivanka
[14:09] <multiplatinum> ivanka,  are you free now?
[14:10] <smspillaz> didrocks: yeah, so I think I know what is happening
[14:10] <didrocks> smspillaz: really? :)
[14:10] <smspillaz> didrocks: I don't get the issue that often, so it is difficult for me to test but I will put together a patch
[14:12] <smspillaz> ok, there goes that theory
[14:12] <didrocks> smspillaz: ok, I didn't get it again since this morning. The first 30 minutes was just horrible though…
[14:12] <smspillaz> what do you find "provokes" it?
[14:12] <smspillaz> (also, how long have we got till a2 is cut?)
[14:12] <njpatel> yesterday
[14:13] <smspillaz> fun
[14:13] <smspillaz> can we still upload? :)
[14:13] <smspillaz> (bugfixes etc)
[14:13] <njpatel> depends, when's the last time you bought didrocks beer?
[14:14] <smspillaz> I couldn't buy him beer in the united states because I was 18
[14:14] <didrocks> that's just an excuse!
[14:14] <smspillaz> but I'll buy him a beer in spirit
[14:14] <njpatel> i forgot, your barely legal
[14:14] <didrocks> smspillaz: well, really depends, if it small, really small… maybe there is a chance :)
[14:14] <smspillaz> ok
[14:14] <smspillaz> I'll look into it
[14:15] <didrocks> smspillaz: and of course, the chance are bigger if njpatel buy me a beer as you can't :)
[14:15] <njpatel> smspillaz, whenever you feel like like chilling out from the bug flow of natty and, generally, want to relax, feel free to fix unity-w-d to allow for large shadow radii ;)
[14:15] <didrocks> "beer backup" :-)
[14:15] <njpatel> didrocks, you know I owe you lots of beers
[14:15] <smspillaz> njpatel: what do you mean, "large shadow radii?"
[14:15] <smspillaz> it supports anything you want
[14:15] <didrocks> njpatel: we owe you a lot as well!
[14:15] <smspillaz> just specify it in the theme
[14:16] <njpatel> smspillaz, making the shadows larger so they don't look as strong
[14:16] <njpatel> smspillaz, i.e. making them stretch out to 3-50px
[14:16] <njpatel> smspillaz, oh, interesting
[14:16] <njpatel> smspillaz, in the metacity theme?
[14:16] <smspillaz> njpatel: vim /usr/share/themes/Ambiance/metacity-1/metacity-theme-1.xml
[14:16] <njpatel> smspillaz, ohh, I see it
[14:16] <njpatel> thanks
[14:17] <didrocks> njpatel: yeah, but that needs the other fix by smspillaz first (I think all is working now) so that the shadow isn't taken by the grid :)
[14:17] <smspillaz> njpatel: yes, just tweak the radius, opacity and offset fields to your liking
[14:17] <didrocks> or you will cry :)
[14:17] <smspillaz> heh
[14:17] <njpatel> aah man, this looks beautiful
[14:17] <smspillaz> while I was implementing that I managed to accidentally implement a funny behaviour
[14:17] <smspillaz> the window maximize gets offset by the frame border size AND the shadow size
[14:18] <smspillaz> so you could actually have smaller maximized windows than unmaximized ones
[14:18] <didrocks> yeah, hence my comment :)
[14:18] <smspillaz> I have a fix for that now though, see your mailboxes and the bug for the patch
[14:18] <didrocks> smspillaz: yeah, but not for alpha2 :p
[14:18] <smspillaz> it also fixes the resize rectangle appearing outside of the window
[14:18] <smspillaz> and snap-to
[14:18] <smspillaz> and a few other things
[14:19] <njpatel> i'm in love
[14:19] <smspillaz> njpatel: screenshot ?
[14:19] <njpatel> with my window decorator
[14:19] <smspillaz> :)
[14:20] <njpatel> uno moment
[14:20] <njpatel> o
[14:21]  * smspillaz wonders if njpatel is applying his "mac os x lookalike theme"
[14:21] <njpatel> i make the borders 0px too
[14:21]  * njpatel happy
[14:21] <njpatel> smspillaz, http://i.imgur.com/MGW5k.jpg
[14:21] <njpatel> it's my desktop, though, so biiiiig screenshot
[14:21] <smspillaz> that's how big my desktop is too
[14:22] <njpatel> 4096x1152?
[14:22] <njpatel> nice
[14:22] <smspillaz> erm
[14:22] <smspillaz> not that big :)
[14:22] <smspillaz> 3360x1050
[14:22] <njpatel> thought so. You can't handle that size, child
[14:23] <multiplatinum> ivanka,  are you free now?
[14:23]  * njpatel doesn't know what he implied there
[14:23] <spikeb> he3h
[14:23]  * smspillaz giggles
[14:23] <smspillaz> njpatel: I suppose there's a minimum age for handling such a size (resolution) and that makes me barely legal huh?
[14:24] <njpatel> smspillaz, exactly, you have a lot to learn before you even approach 4k pixel width
[14:24] <smspillaz> like the fact that my driver can't handle texture sizes that big?
[14:25] <smspillaz> YAY INTEL
[14:25] <njpatel> exactly
[14:25] <njpatel> :)
[14:25] <njpatel> though my laptop intel could
[14:25] <smspillaz> not an i915?
[14:25] <njpatel> 4500
[14:25] <smspillaz> nice
[14:25] <njpatel> with displayport and vga
[14:26] <njpatel> but I got a 450 GTS for my desktop which had 2x DVI, HDMI and VGA
[14:26] <smspillaz> nice
[14:26] <njpatel> so I can run most the screens in my house off it ;)
[14:26] <smspillaz> that's way overpowered
[14:26] <spikeb> haha njpatel
[14:26] <smspillaz> njpatel: well how many crtcs does it have ?
[14:26] <njpatel> it is, but makes njpatel happy
[14:26] <smspillaz> all those ports are useless without crtcs
[14:27] <njpatel> smspillaz, how would I even begin to find that out?
[14:27] <njpatel> smspillaz, I've tested with both DVIs and VGA. Haven't tested HDMI yet
[14:27] <smspillaz> njpatel: try connecting lots of monitors and it should max out at some number likely to be less than the number of ports on your card
[14:27] <smspillaz> ok, so you have at leat 3
[14:27] <smspillaz> *least
[14:27] <njpatel> yeah
[14:28] <njpatel> which is honestly what I bought it for, having the HDMI is like a nice side-effect
[14:28] <smspillaz> when I actually get a desktop, I plan to get a triple-head setup
[14:28] <smspillaz> heh, I use hdmi all the time
[14:28]  * smspillaz has a hdmi -> dvi connector
[14:28] <njpatel> apparently in the windows world ATI is the best
[14:28]  * spikeb uses a singular 40" screen on his desktop
[14:28] <smspillaz> my friend has one of those
[14:28] <njpatel> however in Ubuntu world I like my nvidia
[14:28] <smspillaz> ATI is nice in the ubuntu world
[14:28] <njpatel> spikeb, nice, what res?
[14:29] <spikeb> njpatel, only 1920x1080. that is about as high as i need though
[14:29] <smspillaz> there's point where the hardware is just so overpowered that even the fact that the driver is not yet optimized doesn't even matter anymore
[14:29] <njpatel> smspillaz, really? I should get you one so you make sure unity runs on it ;)
[14:29] <smspillaz> njpatel: only on fglrx
[14:29] <njpatel> spikeb, ah, so you've gone for nice, large, text :)
[14:29] <spikeb> njpatel, yes.
[14:30] <spikeb> hey is the FOSS ATI driver good enough to run unity-compiz?
[14:30] <njpatel> smspillaz, yes, like my card :) However when I feel like it booting in to windows and playing some Team Fortress 2 is nice :)
[14:30] <njpatel> spikeb, FOSS one should work, yes. Having troubles with fglrx right now
[14:30] <spikeb> ok
[14:41] <Kaleo> kamstrup: who/what uses libunity/src/unity-appinfo-manager.vala ?
[14:41] <kamstrup> Kaleo: u-p-a
[14:42] <Kaleo> kamstrup: ok, thanks
[15:16] <kamstrup> DBO: you there?
[15:16] <DBO> kamstrup, yes
[15:16] <kamstrup> DBO: you can haz present! https://code.launchpad.net/~unity-team/unity/launcher-api/+merge/48152
[15:17] <DBO> kamstrup, you is da bomba
[15:17] <kamstrup> DBO: I was thinking that you would be the guy to review this, and maybe hook the remaining bits up in the UI or hold my hand while i do it? :-)
[15:17] <DBO> I will hook up the UI
[15:17] <DBO> I want to do that :)
[15:18] <kamstrup> \o/ less work for me!
[15:18] <DBO> is there a dbus api with this I can play with on d-feet
[15:18] <DBO> so I could say set the progress of something
[15:18] <kamstrup> DBO: yes and no...
[15:19] <kamstrup> DBO: the client side API currently lives in libunity trunk - which i'll release unless show stoppers pop up
[15:19] <kamstrup> DBO: the unity side of this just listens for some DBus signals, so not much you can instrument from d-feet i'm afraid
[15:19] <DBO> oh you biznatch
[15:20] <DBO> so you basically ignored everything I said about dock-manager
[15:20] <kamstrup> DBO: but I have a sample vala proggy here I can paste you, it's easy to work with
[15:20] <kamstrup> DBO: i didn't ignore it, I carefully evaluated it, and decided (together with my accomplice njpatel) that the dockmanager API was not good enough
[15:21] <kamstrup> DBO: I can give you the reasons on a mumble call if you want, to elaborate to type out here :-)
[15:21] <DBO> I just wish you had included me in something like that
[15:22] <kamstrup> DBO: then live in the *correct* time zone ;-) You americans have your sleeping pattern all wrong!
[15:24] <njpatel> DBO, it's still possible to implement dockmanager, just outside of unity (as we spoke about the first time), as far as I understand it
[15:26] <jcastro> njpatel: gord: you guys got time to talk about Places API today real quick?
[15:27] <njpatel> jcastro, sure, what's up?
[15:27] <jcastro> https://wiki.ubuntu.com/Unity/Places
[15:28] <jcastro> first off, is that up to date ^^
[15:28] <jcastro> I'd like to move it to developer.u.c
[15:28] <njpatel> jcastro, also, kamstrup and me probably better for Places API stuff
[15:29] <jcastro> oh ok, got confused
[15:29] <njpatel> jcastro, mostly, some of it won't be supported in natty
[15:29] <jcastro> ok so kamstrump is places guy, got it
[15:29] <njpatel> (which is good, it's cruft(
[15:29] <jcastro> cool, can you comment out the sections that won't be in natty? but leave them in there so I can keep them around
[15:29] <njpatel> either of us, kamstrup is better at the whole documentation thing :)
[15:29] <jcastro> ok, go back to work then. :)
[15:30] <jcastro> kamstrup: ping.
[15:30] <jcastro> (heh)
[15:30] <njpatel> :)
[15:31] <kamstrup> jcastro: hey
[15:32] <jcastro> kamstrup: can you check out that Places wiki page and let me know if it's complete?
[15:32] <jcastro> I'm supposed to snag all the Places docs you guys make and put them on unity.ubuntu.com
[15:34] <jcastro> njpatel: does the youtube places app still work?
[15:34] <jcastro> we're going to need like code examples and all that jazz, just like we did for app indicators
[15:35] <njpatel> jcastro, it should, will have a look over the weekend
[15:35] <jcastro> I was thinking of starting the push to getting people looking at Places right after A2
[15:35] <jcastro> so whenever you guys finish the tarballs if you could just get the Places docs done then I can take it from there
[15:38] <kamstrup> jcastro: the current Places wiki page is "correct" but slightly misleading
[15:39] <kamstrup> jcastro: because it specs out the lowlevel DBus interactions, but you're really meant to be using libunity to work with the API
[15:39] <kamstrup> jcastro: and it must be emphasised that the API *will* break
[15:40] <jcastro> right, these are old
[15:40] <kamstrup> jcastro: also the youtube and sample place a subtly broken right now - they are easy to fix though
[15:40] <jcastro> can you update them before say ... Monday end-of-day?
[15:40] <jcastro> (the docs)
[15:47] <kamstrup> jcastro: yes, putting on my todo for this week
[15:48] <jcastro> thank you sir!
[15:53] <lamalex> hey didrocks, about your killall panel service merge
[15:53] <lamalex> shouldn't you do that before you start unity?
[15:53] <didrocks> lamalex: yeah?
[15:53] <didrocks> lamalex: no, because unity can already be started
[15:53] <didrocks> lamalex: and it can restart the panel service then
[15:53] <lamalex> but you start unity, and then kill the panel service
[15:54] <lamalex> can't you hit a condition where you kill the one unity just spawned?
[15:54] <didrocks> lamalex: I tried that and it seems there is no issue killing the one unity is just spawning
[15:54] <lamalex> didrocks, it seems wasteful
[15:54] <lamalex> like it could impact start up time
[15:54] <didrocks> lamalex: keep in mind that we don't use the wrapper in the session…
[15:55] <didrocks> triggering a python script will cost too much
[15:55] <didrocks> so it's just for us when debugging
[15:55] <lamalex> ah, ok. I guess it doesn't matter so much then
[15:55] <didrocks> yeah, hence the merge :)
[15:55] <didrocks> lamalex: other, the script will be way way different :)
[15:55] <didrocks> otherwise*
[16:04] <lamalex> API, what's the status of https://code.launchpad.net/~rodrigo-moya/unity/panel-a11y/+merge/47277
[16:04] <lamalex> is it mergable?
[16:05]  * API checking
[16:06] <API> lamalex, no
[16:06] <API> this was a first prototype
[16:06] <API> when rodrigo was planning to
[16:06] <API> implement the panel accessibility on unity
[16:06] <API> but for now, we are going to do that on the seervice panel
[16:07] <API> so in fact this rodrigo should cancel this merge proposal
[16:10] <lamalex> API, I will reject
[16:10] <API> lamalex, ok
[16:10] <API> lamalex, btw, it is ok if we add you as reviewer of our a11y related branches?
[16:11] <API> or there is any other policy?
[16:12] <lamalex> API, there's no official policy
[16:12] <lamalex> You're fine to add me, I will probably be doing most of them anyway
[16:14] <API> lamalex, ok thanks
[17:09] <jcastro> njpatel: DBO: lamalex: last call for tagging bitesizers if you want them in today's blog entry
[17:10] <njpatel> jcastro, honestly, I can't stand LP today, need to see some C++
[17:11] <jcastro> hah
[17:12] <didrocks> jcastro: btw if the desktop team meeting report can help you doing your blog post: https://wiki.ubuntu.com/DesktopTeam/Meeting/2011-02-01
[17:12] <jcastro> ooh, I will so steal some of that
[17:13] <didrocks> jcastro: every tuesday dude (and I include the link to the milestone for the bugs as well)
[17:42] <nmarques> guys I'm trying to run Unity on openSUSE, and eventually implement it from that point on. I have a couple of questions, being one of them what's the best way to launch unity from a GNOME2 session and to enable all the possible debugging modes. I've also noticed that a unity --reset will use the ini backend, is this supposed to happen, or it should be gconf (Ubuntu is using gconf right?).
[17:43] <njpatel> nmarques, it should use GSettings
[17:44] <nmarques> njpatel, that's a start ;) and the correct way to launch it would be using the unity wrapper provided ?
[17:44] <njpatel> nmarques, unity --replace should call compiz with the right plugin args
[17:44] <njpatel> didrocks, ^
[17:44] <dbarth_> nmarques: welcome!
[17:44] <nmarques> dbarth_, hi and thanks
[17:44] <njpatel> nmarques, yeah, that does some killing of daemons etc which is helpful right now :) Mucht he same as the gnome-shell startup script
[17:44] <didrocks> njpatel: it doesn't, it's using our compiz profile rather
[17:45] <njpatel> didrocks, ah, right :)
[17:45] <didrocks> nmarques: you shouldn't use the wrapper I think
[17:45] <didrocks> we don't
[17:45] <dbarth_> nmarques: didrocks is your man, i think
[17:45] <didrocks> njpatel: we don't use gsettings btw :)
[17:46] <didrocks> got trapped /o\ I'm testing something right now quite urgent for alpha2
[17:46] <njpatel> didrocks, huh? unity does
[17:46] <nmarques> didrocks, keep it on ;) I have all the time the world :)
[17:47] <njpatel> nmarques, apparently I know nothign about how we actually launch unity in ubuntu
[17:47]  * njpatel shuts up now
[17:47] <didrocks> njpatel: unity, not compiz :)
[17:47] <njpatel> ah, right
[17:47] <nmarques> well, if I try to run Unity --replace it resets compiz config, tries to redraw the screen and falls back to gnome2 session
[17:48] <didrocks> njpatel: that's good, I can break you and you won't be able to unbroke ahahah :)
[17:48] <nmarques> didrocks, one thing, FireGL and Unity? is that a problem ?
[17:48] <nmarques> FireGL as in fglrx
[17:52] <didrocks> nmarques: one sec
[17:57] <didrocks> nmarques: ok back, sorry for the delay :)
[17:58] <didrocks> nmarques: so, unity is a python wrapper which is quite hackish and more for debugging
[17:58] <nmarques> didrocks, no worries
[17:58] <didrocks> you shouldn't use it
[17:58] <didrocks> (I mean for proper integration)
[17:58] <didrocks> nmarques: do you know about compiz profiles?
[17:59] <nmarques> didrocks, a bit, but I can dig more information and help from the compiz packagers so I get the requirements accomplished
[18:00] <didrocks> nmarques: yeah, so we basically have two profiles: the default one and the unity one
[18:00] <didrocks> nmarques: both are the same, we just enable the unity plugin in addition to it
[18:00] <didrocks> nmarques: so you need to ask to the compiz people in opensuse to add a profile for you
[18:00] <nmarques> didrocks, what do I need to add on that profile ?
[18:00] <nmarques> didrocks, the contents of unity.ini ?
[18:01] <didrocks> nmarques: depends, you use the ini backend?
[18:01] <nmarques> by default yes, we use ini
[18:01] <nmarques> we don't use gconf in opensuse, but I can work that out
[18:01] <didrocks> ok, so yeah, you should refer from the profile this file
[18:01] <didrocks> (don't really know how it works with the ini backend)
[18:02] <nmarques> assuming we have the ini working out with unity.ini
[18:03] <didrocks> it should, there is nothing strange there
[18:03] <nmarques> how do we go from there to launch unity with the 'adviced' debugging options
[18:03] <didrocks> nmarques: we simply don't. you mean, running it in gdb, isn't it?
[18:04] <jcastro> lamalex: do you have cando's trashcan/quicklist branch handy? i'd love a screenshot.
[18:04] <nmarques> didrocks, yeap, that can be done, and has been done in the past, but don't we have some sort of logging feature ?
[18:05] <didrocks> nmarques: hum, not really, the logs ends up in ~/.xsession-errors for now, but we will try to add some debugging to a default file soon
[18:05] <ronoc> jcastro, I merged Trevisan's libnotify work - is that what you were on about
[18:05] <didrocks> nmarques: spamming ~/.xsession-errors isn't good :)
[18:05] <jcastro> ronoc: yep
[18:05] <Amaranth> no more unity for me
[18:05] <Amaranth> gonna be a great alpha 2 :)
[18:06] <ronoc> jcastro, okay cool
[18:06] <jcastro> ronoc: omg has a good video of his thing so I will just link to that
[18:06] <nmarques> didrocks, awesome. I am using your git snapshots and your patches for now, Im going to ask Dimstar to take a look on the profiles
[18:06] <ronoc> jcastro, will build some test debs before it gets to trunk
[18:06] <ronoc> jcastro, good stuff
[18:06] <didrocks> Amaranth: intel driver? bad X update? :)
[18:06] <nmarques> didrocks, and then try to boot compiz from the profile we will create
[18:06] <Amaranth> didrocks: yep
[18:06] <didrocks> nmarques: excellent :)
[18:07] <Amaranth> compiz itself works, I guess FBOs are broken
[18:07] <didrocks> Amaranth: ok, you are the second one, you had the info about "can't run unity"?
[18:07] <Amaranth> didrocks: yeah
[18:07] <Amaranth> pretty sure FBOs are broken
[18:07] <didrocks> Amaranth: hum, can you tell that on #ubuntu-devel
[18:07] <nmarques> didrocks, it currently does try to launch it, but after it tries to draw the screen, it just falls back to GNOME session. This is probably lacking the proper profile
[18:07] <Amaranth> #ubuntu-x would probably be better
[18:07] <didrocks> Amaranth: and hilight RAOF and bryceh?
[18:08] <Amaranth> but let me get debug symbols and see what happens
[18:08] <didrocks> Amaranth: I think people on the release team should know as well
[18:08] <didrocks> Amaranth: so otherwise #ubuntu-release :)
[18:08] <didrocks> Amaranth: pretty serious and you are the second one reporting it
[18:08] <Amaranth> didrocks: Pretty sure everyone with a 965 is screwed
[18:08] <nmarques> didrocks, I won't be able to help much with code, but there might be a couple of things I can help with, and I will. Really thanks for your time, I'll work this profile itches now :)
[18:08] <didrocks> Amaranth: "nice"
[18:09] <didrocks> nmarques: you're really welcome, if you have any question, do not hesitate :)
[18:10] <nmarques> didrocks, I will :) I really would love to see this implemented on openSUSE alongside with other software from Ubuntu, and I think it will happen soon ;) By the way, nice job on improving user desktop experience, you guys doing an awesome job
[18:11] <didrocks> nmarques: hehe, thanks a lot on behalf the dx and other teams :) and that's awesome you're trying to get that happening!
[18:15] <lamalex> jcastro, did you get a screenshot yet?
[18:15] <lamalex> ha uh actually I can
[18:15] <lamalex> 't get one anyway. Double monitor bug keeps me from seeing the bottom of my launcher
[18:16] <jcastro> bummer
[18:22] <Amaranth> didrocks: Part of this is going to be a nux issue
[18:22] <didrocks> right, as it's the one unity FBO
[18:22] <Amaranth> didrocks: There is no crash in the drivers, this case seems to just not be handled correctly in nux
[18:23] <didrocks> s/unity/using
[18:23] <didrocks> autotyping*
[18:23] <Amaranth> Something with intel is broken to cause the FBO setup to fail but then nux crashes because it doesn't handle it correctly
[18:23] <didrocks> ok
[18:23] <lamalex> jcastro, i thought we had unity dailies going
[18:24] <jcastro> I thought they stopped working?
[18:24] <jcastro> last I tried them they didn't work
[18:25] <jcastro> hey, they appear to work now!
[18:25]  * jcastro tries
[18:25] <lamalex> just build from source
[18:25] <lamalex> it's easy
[18:25] <lamalex> it's not like the old days
[18:26] <lamalex> where you needed to build compiz and nux and this and that
[18:27] <jcastro> segfault, same thing I was getting in natty unity today
[19:10] <Omega> Oh great, and I was just updating :<
[20:50]  * apw wonders if anyone but him is seeing unity core dump as of whats in the archive right now?
[20:51] <jcastro> mine is segfaulting
[20:51] <cando_> mine too
[20:51] <jcastro> I'm in unity-2d
[20:52] <apw> jcastro, ahh how is u-2d working?
[20:52] <apw> jcastro, seems that a2 is blocked by it, so release has their boots on someones neck
[20:52] <jcastro> 2d is working great for me
[20:53] <apw> jcastro, tempting
[20:53] <jcastro> cando_: that logo is perfect, updating
[20:53] <cando_> jcastro, awesome..
[20:55] <jcastro> https://launchpad.net/~unity-bitesizers
[20:55] <jcastro> yeah!
[20:56] <cando_> yeah! rock!
[21:14] <Omega> jcastro: I'm still getting used to launchpad etiquette, who is "authorized" to change the status
[21:14] <jcastro> depends on what it is
[21:14] <Omega> jcastro: I'm still getting used to launchpad etiquette, who is "authorized" to change the status (like to "confirmed")?
[21:14] <jcastro> link?
[21:14] <Omega> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/696620
[21:14] <Omega> I was just about to file a bug, but that describes it.
[21:14] <jcastro> you can confirm any bug if you see it
[21:15] <jcastro> the bad form is confirming your own bug
[21:15] <Omega> Ah
[21:15] <jcastro> confirm is basically "I see this too, so you're not crazy"
[21:15] <Omega> I thought that is what the "does this affect you?" is for
[21:16] <jcastro> that's for "a bunch of us aren't crazy, it's a big deal"
[21:16] <Omega> Also, do I change it on all the "affects"?
[21:16] <jcastro> What should happen is this affects me should autoconfirm the bug, but it doesn't do that
[21:16] <jcastro> if you're using the package, the (ubuntu) one
[21:16] <Omega> OK.
[21:16] <jcastro> if you can confirm it in a trunk build then just plain Unity, which is the upstream
[21:17] <jcastro> but usually the one with (ubuntu) is good enough
[21:17] <Omega> Thank you for your help :>
[21:17] <jcastro> no worries, thanks for confirming!
[22:29] <hyperair> ronoc: where would i go to file a bug about the soundmenu spec?
[22:29] <hyperair> ronoc: i think it's counter-intuitive to have media players terminate automatically when you close them and something is paused/isn't playing, and then media keys stop working.
[22:30] <hyperair> ronoc: perhaps soundmenu should grab the GNOME media keys and automatically re-launch the players if they are not running?
[22:44] <arow> hyperair, you've got a point, but I'm going to have to disagree with part of it
[22:44] <arow> (note: I am not a dev, but anyway)
[22:45] <arow> I think the intuitive thing is for programs to terminate when you close them
[22:46] <arow> however, I do understand that having the media player play in the background is a desirable thing
[23:17] <Omega> Now that was an annoying bug :< https://bugs.launchpad.net/ubuntu/+source/unity/+bug/711567
[23:29] <Omega> Hmm, it's a duplicate
[23:34] <Omega> Or hmm, not? The other one is supposed to be fixed.