[07:02] <kvalo> morning
[08:01] <oSoMoN> good morning
[08:25] <kamstrup> hi all
[08:33] <kvalo> kamstrup: hey. how was your trip back home?
[08:34] <kamstrup> kvalo: ok thanks - no problems. How was yours?
[08:34] <kamstrup> you met your connecting flight in Paris?
[08:35] <kvalo> kamstrup: pretty good actually, I got three seats in the over atlantic flight! :D
[08:35] <kamstrup> kvalo: lucky bastard :-) I was crammed
[08:35] <kvalo> kamstrup: plane late 10 mins, bus ride to the terminal and had to run all the way. but made it :)
[08:36] <kvalo> kamstrup: I was sooo lucky. slept like 5 hours on the plane
[08:37] <kvalo> with three pillows and blankets I was able to create one proper pillow :)
[08:38] <kamstrup> So if I have either Firefox or Thunderbird running I get the stacking bug not only in the indicators but also in any menus of all apps....
[08:38] <kamstrup> Known bug?
[08:39]  * kamstrup logs in to a legacy session
[08:46] <seiflotfy> hey guys
[09:13] <smspillaz> alright #ayatana - I need someone who is not using xorg-edgers and someone who is using xorg-edgers to test something for me
[09:14] <smspillaz> hover over a menu to reproduce the "my menu doesn't appear bug". When you hover over where the menu *should* be - I need to know if it appears and if you are using xorg-edgers or normal stock xorg
[09:14] <smspillaz> dbarth: I found something interesting in compiz re all of this btw - onestone's got us hooked up to the damage handler twice for each drawable
[09:14] <smspillaz> once for the window pixmap and once for the window handle itself
[09:15] <smspillaz> kamstrup: yeah it's a known bug - I'm working it out now
[09:16] <smspillaz> kamstrup: it goes deep deep into Xorg - quite nasty
[09:16] <kamstrup> smspillaz: ok, I just only ever saw it in the indicators :-)
[09:16] <smspillaz> yeah
[09:16] <kamstrup> smspillaz: ok, lemme know if there's anything I can do to help
[09:16] <smspillaz> if it is annoying you so much where you don't mind losing window borders and click to focus you can manually disable reparenting :p
[09:16] <kamstrup> (leaving you alone is a valid answer ;-P)
[09:17] <smspillaz> kamstrup: heh
[09:17] <smspillaz> kamstrup: well actually
[09:17] <smspillaz> kamstrup: what card do you have ?
[09:17] <kamstrup> smspillaz: oh, it's the ever wonderful, super powerful, i945
[09:17] <smspillaz> (this bug is actually two different bugs manifesting as one)
[09:17] <smspillaz> kamstrup: ok - can you reproduce the version of this where the menu doesn't appear, but if you hover over where it should be it does ?
[09:17] <smspillaz> on newly created windows
[09:18] <smspillaz> I thought I saw this on my intel machine today, but I might be delusional
[09:24] <kamstrup> smspillaz: meh, so now I can't reproduce it at all anymore...
[09:28] <smspillaz> kamstrup: it's a race condition, that's what makes it a pain :)
[09:29]  * smspillaz just can't get over the look of those new icons in the launcher
[09:29] <kamstrup> yeah it does look awesome
[09:42] <didrocks> smspillaz: hey, we have people complaining about bug #704231. Is it the way compiz works when you assign a value to a grab key or is it a mistake in my code?
[09:53] <smspillaz> didrocks: if you grab the super key, the passive grab activates
[09:53] <smspillaz> didrocks: I think if you return false in your callback it will put back the ButtonPress event
[09:53] <smspillaz> *think*
[09:53] <didrocks> smspillaz: ok, so I should just return false?
[09:55] <smspillaz> didrocks: yeah, try that
[09:55] <smspillaz> didrocks: well return false when you didn't actually eat the event
[09:56] <smspillaz> eg, pressing super when the launcher is *hidden* should return true, pressing it when it is already there should return false
[09:56]  * smspillaz still thinks that launcher-on-super is a bad idea
[09:57] <didrocks> smspillaz: let's see how it goes
[09:58] <smspillaz> didrocks: ok
[09:58] <didrocks> smspillaz: I'm already returning false
[09:59] <didrocks> smspillaz: see in unityshell.cpp, with the showLauncherKeyInitiate and showLauncherKeyTerminate
[10:00] <smspillaz> didrocks: hrm ok
[10:00] <smspillaz> didrocks: is it a necesscity that it need to be the super key by itself
[10:00] <smspillaz> ?
[10:00] <smspillaz> since this problem could easily be avoided if we just changed it to eg super-u or whatever
[10:01] <didrocks> smspillaz: that's how it's planned to work yes
[10:01] <smspillaz> urhg
[10:01] <dbarth> API, rodrigo_: ping?
[10:01] <didrocks> smspillaz: like, if you then super + 0, you open the first element
[10:01] <didrocks> and such
[10:01] <didrocks> smspillaz: in any case, so returning false is already in the code
[10:01] <API> dbarth, pong
[10:01] <smspillaz> didrocks: ok, well does the super key actually need to be opening the launcher ?
[10:01] <didrocks> smspillaz: no idea why compiz grab that?
[10:01] <smspillaz> didrocks: well I know that compiz grabs the key if you have an action set on it - that is what it is meant to do
[10:02] <didrocks> smspillaz: again, it's in the design
[10:02] <smspillaz> but grabbing an entire modifier tree is pretty greedy
[10:02] <smspillaz> didrocks: can we file a design bug? :p
[10:02] <didrocks> smspillaz: hum, you mean, super + 0 then won't work?
[10:02] <didrocks> smspillaz: seems more a compiz bug for me
[10:02] <smspillaz> didrocks: well super-0 will work
[10:02] <smspillaz> if you set an action to super-0
[10:02] <dbarth> API: skype?
[10:03] <smspillaz> didrocks: it's not really a compiz bug - the logical thing to happen here is that when you press the super key it will show the launcher and not do anything else
[10:03] <API> dbarth, I made a upgrade yesterday, lets hope skype working today ;)
[10:03] <API> dbarth, a mon, moving to other room
[10:04] <smspillaz> didrocks: I mean, I guess I could make a returning false action do XPutBackEvent
[10:04] <didrocks> smspillaz: that would be nice
[10:04] <didrocks> at least, we still have the option to prevent or not the action to be passed
[10:04] <didrocks> smspillaz: want a bug report for that?
[10:05] <dbarth> smspillaz, didrocks: what's the status with the top-3 priority bugs btw?
[10:05] <smspillaz> dbarth: still looking into this damage one
[10:05] <smspillaz> dbarth: onestone did something weird in the damage tracking bits of opengl and *gasp* didn't document it
[10:05] <didrocks> damage one?
[10:06] <didrocks> so the stacking issue is fixed?
[10:06] <smspillaz> I haven't started on the stacking one
[10:06] <didrocks> didn't you start on that last week?
[10:06] <smspillaz> I started it and then saw that it was really 2 bugs in one
[10:06] <dbarth> smspillaz: this needs to be your priority sam, it's a major regression
[10:06] <smspillaz> dbarth: I'm aware :)
[10:06] <dbarth> smspillaz: right, i saw your point about one bug actually being 3
[10:06] <didrocks> on the 3, there is still the crash at start, right?
[10:07] <smspillaz> with gconf ?
[10:07] <dbarth> i understand the 1st one is solved, but there are still 2 stacking and damage issues to solve
[10:07] <didrocks> yeah, with gconf
[10:07] <smspillaz> dbarth: yes
[10:07] <dbarth> and then, there is the crasher
[10:07] <smspillaz> didrocks: yes that's on the radar - no time to start it yet
[10:16] <rodrigo_> hi dbarth
[10:20] <dbarth> rodrigo_: hi
[10:20] <dbarth> uh, i lost API in the meantime
[10:20] <rodrigo_> dbarth, he said he was moving to another room, should be back soon, I think
[10:20] <dbarth> rodrigo_: i wanted to do the weekly call i had planned in my calendar
[10:21] <rodrigo_> ok, skype?
[10:21] <dbarth> rodrigo_: yup
[10:21] <rodrigo_> ok
[10:22] <rodrigo_> dbarth, my skype id is rodrigo.moya
[10:23] <rodrigo_> here's API back
[10:30] <Kaleo> good morning
[10:30] <kamstrup> kvalo: I have to follow https://wiki.ubuntu.com/ConnMan/Installation on Natty as well, right?
[10:35] <kamstrup> kvalo: indicator-network seems to remember the password even if it's rejected. Should I file a bug for this?
[10:36] <rodrigo_> dbarth, bug #686672
[10:47] <dbarth> API, rodrigo_: https://code.launchpad.net/~unity-team/unity/places-views
[10:47] <dbarth> API, rodrigo_: https://code.launchpad.net/~gordallott/unity/unity-tile
[10:48] <kamstrup> why do my gtk theme get flipped to Raleigh every time a change a setting somewhere?
[10:50] <seb128> kamstrup, is that the default theme?
[10:50] <seb128> kamstrup, could be gnome-settings-daemon crashing?
[10:52] <API> dbarth, rodrigo_ https://bugs.launchpad.net/unity/+bug/702685
[10:59] <kvalo> kamstrup: yes, follow the maverick instructions.
[11:00] <kvalo> kamstrup: that's by design. what we need to do is to offer the possibility to check and change the passphrase.
[11:08] <njpatel> didrocks, hey dude, did your auto-maximise branch land for last week's release?
[11:08] <njpatel> didrocks, I'm still getting new windows at  near-maximised size but not undecorated
[11:11] <ogra> didrocks, hey, how is the jetlag ?
[11:14] <njpatel> awww
[11:17] <spikeb> you guys killed him!
[11:17] <ogra> heh
[11:17] <kvalo> seb128: hi. do we have a maintainer for empathy?
[11:18] <seb128> hi, sort of, why?
[11:18] <seb128> the desktop team is doing updates, kenvandine and some community people usually
[11:18] <kvalo> seb128: there's an issue with connman, just about to file a bug. just wondering should I create a patch for it
[11:19] <seb128> why should empathy know about connman? I though the api to check online status etc where identic the n-m one?
[11:19] <seb128> or that there was a compatibility wrapper
[11:20] <seb128> well in any case it's not likely than anyone else will write a fix for connman so yeah you should do it if you want one
[11:20] <kvalo> seb128: the implementation in empathy uses libnm for some reason
[11:20] <njpatel> because it's nicer to use lib instead of dbus?
[11:20] <seb128> you can try asking on #empathy
[11:20] <kvalo> seb128: they support also connman, but there's only a compile time switch to enable it
[11:20] <njpatel> (not having a go, but just dbus is a crap API)
[11:21] <seb128> but it's likely what njpatel say, using a lib is nicer than using dbus calls
[11:21] <kvalo> yeah, but I doubt libnm is the best option here. most likely it does more than just checks the state
[11:22] <kvalo> I'll debug what's the problem with libnm
[11:45]  * didrocks wants a working internet connexion :/
[11:46] <didrocks> njpatel: re: automaximize branch: it landed last week, yeah. We have already some wishlist about an option to deactivate it
[11:46] <didrocks> njpatel: do you think we should activate it depending on screen size?
[11:47] <kvalo> seb128, njpatel: yeah, libnm init does more than just checks the network state. seems to query available hw etc and no wonder it fails with connman
[11:49] <njpatel> didrocks, yeah, but we'll come to that in time :)
[11:50] <njpatel> didrocks, okay, i wonder why it isn't working for me :(
[11:50] <njpatel> kvalo, oh, yeah, libnm isn't the right thing to use, but was just saying that they probably when searching for a proper API
[11:52] <kvalo> njpatel: yeah. me, dbarth and kamstrup have been talking about implementing a proper network api for applications. I'm this > < close to writing one :)
[11:53] <didrocks> njpatel: seems to work too well for some people :)
[11:53] <didrocks> njpatel: the only check is > 0.6 of the screen and < 1
[11:54] <didrocks> (and that it's a normal window && maximizable)
[12:04] <njpatel> didrocks, chromium doesn't seem to be automatically maximised :/
[12:05] <didrocks> njpatel: only chromium? let me check. (I have to relaunch unity now because of bug #703140, I can't really use it anymore :/)
[12:08] <didrocks> njpatel: chromium is working here…
[12:08] <didrocks> are you sure you have more than 60% of the workarea coverage?
[12:10] <njpatel> didrocks, yeah, it's basically maximised apart from the titlebar
[12:10] <njpatel> didrocks, I have "use system decorations" checked
[12:11] <njpatel> man, I'd pay money for my keyboard not to reset to en_US every flipping reboot
[12:12] <didrocks> njpatel: I think I have the same option too (I have the unity-window-decorator), but I can't open the option menu because of the stacking issue… the window is undecorated and maximized there when I open it…
[12:14] <didrocks> njpatel: I'll try to have a look
[12:15] <didrocks> I'm wondering why people using Scribes seem to have an issue with the automaximization (like, it's slowing down their system a lot…)
[12:15] <njpatel> didrocks, needs to redraw everything, probably
[12:17] <didrocks> njpatel: yeah, I guess there are a lot of remapping happening… I'll try to confirm that. If so, we should maybe blacklist it?
[12:19] <kamstrup> could someone review https://code.launchpad.net/~unity-team/unity/libunityectomy/+merge/46590 I'd really much like to land it today so we can get a new and separate libunity tarball out there
[12:19] <ogra> didrocks, sooo ... metacity
[12:22] <kamstrup> gord: maybe you have time for https://code.launchpad.net/~unity-team/unity/libunityectomy/+merge/46590 ? It would be relevant with your stamp on it if you are the one who's gonna rewrite the perf logger...
[12:23] <rodrigo_> njpatel, how do the unity branches land? is it running tarmac or does it need to be done manually?
[12:23] <njpatel> rodrigo_, manually right now, tarmac no workie
[12:23] <didrocks> ogra: yes? did you install the patch and rebuild compiz against it?
[12:23] <rodrigo_> njpatel, can you then please merge this one -> https://code.launchpad.net/~rodrigo-moya/unity/a11y-global-listeners/+merge/46242 ?
[12:24] <njpatel> robtaylor, your a unity-team member now, so you can do it :)
[12:24] <njpatel> rodrigo_, ^, even
[12:24]  * njpatel needs some more lemsip
[12:24] <rodrigo_> njpatel, ah, ok
[12:24] <ogra> didrocks, my dist upgrade on my arm machine failed, i'll try again on x86
[12:24] <ogra> (webkit is still broken on armel)
[12:24] <gord> kamstrup, 8169!!
[12:25] <gord> oh wait, its almost all deletions
[12:25] <didrocks> ogra: yeah, that will at least enable you to see it doesn't break unity as well :)
[12:27] <kamstrup> gord: it should amount to simply removing libunity - so that's the main thing you should focus on
[12:27] <kamstrup> gord: hence "libunityectomy" ;-)
[12:29] <gord> kamstrup, i'll take a look after lunch
[12:29] <kamstrup> gord: thanks
[13:03] <\sh> which package gives me unity-2d in natty? all unity-2d-* packages or just one?
[13:04] <didrocks> ogra: ^^
[13:04] <ogra> \sh, none yet, packaging is still being fixed up
[13:04] <\sh> ogra: hurry ;)
[13:04] <rsalveti> but unity-2d-default-settings should install everything
[13:04] <ogra> but if everything is done it should be unity-2d-default-settings
[13:04] <rsalveti> :-)
[13:05] <ogra> the metacity bit is missing
[13:05] <\sh> ogra: kk
[13:05] <ogra> so its uninstallable
[13:05] <ogra> and my laptop is just upgrading to natty now until i can to a testbuild it will take a while
[13:06] <\sh> ogra: armel or x86?
[13:06] <\sh> for x86 and x86_64 I could help
[13:06] <ogra> i guess didrocks only wants a test on x86
[13:07] <didrocks> I think that one test will be enough, right
[13:07] <didrocks> just to ensure we don't see weird effects between sessions
[13:08] <ogra> \sh, metacity needs this patch http://paste.ubuntu.com/555098/ (drop the last line though)
[13:08] <ogra> then compiz needs to be rebuilt against the new metacity development libs
[13:08] <ogra> and then unity (3d) needs to be tested with that
[13:09] <rodrigo_> yay, unity works for me now
[13:09] <rodrigo_> well, it starts, it's got a lot of non-working stuff
[13:10] <\sh> ogra: patch against metacity 1:2.30.3-0ubuntu2 ?
[13:10] <ogra> against whatever is in natty
[13:10] <\sh> kk
[13:10] <ogra> the original patch is from maverick
[13:10] <ogra> i hope it applies cleanly
[13:10] <ogra> would be awesome if you could do that since my dist-upgrade might still take some hours
[13:12] <didrocks> \sh: btw, you might want to use the two Vcs: lp:~ubuntu-desktop/metacity/ubuntu and lp:compiz
[13:16] <\sh> ogra:  90_autotools.patch is neither in bzr nor in the latest natty package
[13:16] <ogra> oh, just ignore that one then
[13:16] <\sh> kk
[13:16] <ogra> just dont apply the last line of my patch
[13:17] <\sh> you mean 99_ltmain_as-needed.patch should still be in the patch set
[13:17] <ogra> (well the unity-2d teams patch, but you know what i meant)
[13:17] <ogra> well, it shouldnt be removed
[13:17] <ogra> that was a mistake
[13:18] <ogra> as i said, the patch was originally for the maverick metacity
[13:28] <didrocks> seb128: if you have a minute, can you try to confirm bug #704413 and if you can (can't find a reproducible testcase), bug #704416 please?
[13:39] <smspillaz> kvalo: so for this menu issue - here's how you can help me debug it
[13:40] <smspillaz> kvalo: sudo apt-get install compizconfig-settings-manager
[13:40] <smspillaz> kvalo: enable the "Debug Spewer" plugin
[13:40] <smspillaz> kvalo: change the "Spew debugging info (or whatever it is)" keybinding to whatever you want
[13:41] <smspillaz> kvalo: now log out, log back in, reproduce the issue and then immediately afterwards press that keybinding
[13:41] <smspillaz> kvalo: compiz will freeze for a few seconds and then unfreeze
[13:41] <dbarth> smspillaz: and so not the damage issue, but the stacking one now, right?
[13:41] <smspillaz> kvalo: after that, drop to a VT (still with the menu open) and DISPLAY=:0 xwininfo -root -all and DISPLAY=:0 wmctrl -l
[13:41] <smspillaz> dbarth: correct
[13:41] <dbarth> smspillaz: ie, click on a menu, see it's not visible and press the shortcut
[13:42] <smspillaz> dbarth: yes
[13:42] <dbarth> ok, trying that now
[13:42] <smspillaz> dbarth: kvalo: but make sure it is the one where click on the menu, see it isn't visible, hover over the menu -> it still isn't visible
[13:42] <smspillaz> and then paste or mail me the output :)
[13:42] <smspillaz> oh
[13:42] <smspillaz> one mor thing
[13:43] <smspillaz> the output for the "debug spewer" output is written to a file in /tmp
[13:43] <smspillaz> called something like /tmp/compiz_state${PID}
[13:43] <kvalo> smspillaz: ok, working on that
[13:43] <smspillaz> thanks
[13:44] <kvalo> damn, I think compiz crashed when I enabled the plugin
[13:44]  * dbarth restart his session
[13:44] <smspillaz> if anyone is feeling really nice, they could tell me how to get from a clean install to that bug, I would give them a cookie
[13:44] <smspillaz> kvalo: yeah, it's a known bug for compiz to crash when enabling other plugins with unity enabled
[13:49] <dbarth> smspillaz: it actually crashed compiz...
[13:49] <smspillaz> :/
[13:50]  * dbarth restarts his session again
[13:51] <kvalo> smspillaz: I mapped the key to super-m. but I don't get any file when a menu is open and I press the key. but if menu is closed, I get the log file
[13:51] <smspillaz> ah rats that's true
[13:51] <smspillaz> it's because the menu has a grab
[13:51] <smspillaz> kvalo: ok, just a second then
[13:52] <smspillaz> kvalo: can you disable unity, enable dbus then enable unity ?
[13:52] <smspillaz> (in ccsm)
[13:52] <smspillaz> well, it will crash anyways, duh
[13:53] <smspillaz> njpatel: just an FTY - unityshell.cpp should destroy the nux input windows on unload
[13:53] <smspillaz> *FYI
[13:54] <kvalo> smspillaz: ok, trying that
[13:55] <kvalo> cyphermox: good morning
[13:55] <kvalo> cyphermox: hey, is libnm meant to be used by applications?
[13:55] <cyphermox> kvalo, yep, that's the point :)
[13:56] <kvalo> cyphermox: that's a lot of information available to them
[13:57] <smspillaz> kvalo: ok - dbus enabled ?
[13:57] <kvalo> cyphermox: and libnm doesn't work with connman compat stuff.
[13:57] <dbarth> smspillaz: doesn't work
[13:57] <kvalo> smspillaz: I think so, let me double check
[13:57] <smspillaz> dbarth: weird. bt ?
[13:57] <dbarth> smspillaz: i've been hit really badly by the gconf crasher
[13:57] <cyphermox> nah... libnm really asks NM about the devices it knows
[13:57] <dbarth> impossible to restart unity in debug mode
[13:57] <kvalo> smspillaz: at least dbus is now ticked in ccsm
[13:57] <didrocks> smspillaz: so, the super + m keybind don't work inside compiz as well? the super keybind is preventing that?
[13:57] <dbarth> and whenever i've tried the spew debugger, it crashed on me
[13:58] <smspillaz> didrocks: works fine
[13:58] <dbarth> i had set alt+super+ctrl as the keybinding
[13:58] <kvalo> smspillaz: what now?
[13:58] <didrocks> smspillaz: oh, ok, it's only when a menu is opened, I read that too quickly, sorry :)
[13:59] <smspillaz> kvalo: ok, so reproduce the issue, then drop to a vt
[13:59] <\sh> smspillaz: good to see you.,..is it correct, that xev doesn't output the Super_L keycode anymore under unity 3d?
[13:59] <smspillaz> kvalo: and then do this dbus-send --type=method_call --dest=org.freedesktop.compiz /org/freedesktop/compiz/debugspew/screen0/spew_key org.freedesktop.compiz.activate
[14:00]  * \sh crap <- meeting <- laters
[14:00] <smspillaz> kvalo: and then DISPLAY=:0 xwininfo -root -tree
[14:00] <smspillaz> and then DISPLAY=:0 wmctrl -l
[14:00] <smspillaz> \sh: yeah I know, I am tracking this one
[14:00] <smspillaz> \sh: Super_L has some weird modifier code
[14:00] <dbarth> ah, now i've managed to get a bt
[14:00] <smspillaz> dbarth: cool
[14:00] <kvalo> smspillaz: ok, working on it
[14:00] <dbarth> it apparently crashes when trying to print a startup notification %s\n
[14:01] <smspillaz> let's see
[14:01] <dbarth> where the string is null
[14:01] <dbarth> ap=0x0
[14:03] <smspillaz> yeah
[14:03] <smspillaz> I figured that might happen
[14:04] <kvalo> smspillaz: I had to add DISPLAY=:0 also to dbus-send. but still no luck, I don't see the log file in /tmp
[14:04] <smspillaz> huh
[14:05] <dbarth> smspillaz: here is the trace: http://pastebin.ubuntu.com/555400/
[14:07] <smspillaz> kvalo: what happens if you use that dbus-send comamnd with the menu closed ?
[14:09] <didrocks> smspillaz: why weird modifier code? it's just unity the compiz option
[14:09] <didrocks> using*
[14:10] <didrocks> kamstrup: dude, do you have a minute to talk about zg & co?
[14:10] <kvalo> smspillaz: hmm, I seem to get the file if I switch from vt back to X
[14:10] <kamstrup> didrocks: sure
[14:10] <didrocks> kamstrup: so, I want to update the stack in natty, what should I know?
[14:10] <didrocks> kamstrup: all latest release is good? what about the fts extension?
[14:11] <kamstrup> didrocks: the fts extension should be compatible
[14:11] <kamstrup> didrocks: the latest release upgrades the internal DB schema, and there's no turning back
[14:11] <lamalex> Is there any design spec about multi-monitor?
[14:12] <didrocks> kamstrup: that's done automagically on first start, right?
[14:12] <didrocks> kamstrup: so, there is no patch to carry on? fts is still part of the extension tarball, isn't it? Should I ship another extension as well?
[14:13] <kamstrup> didrocks: yeah, the DB upgrade is done automagically on first run
[14:13] <smspillaz> didrocks: yeah but the super key is handled weirdly in xkb and I bet we've got the wrong keycode modifier for it hardcoded in to compiz
[14:13] <kamstrup> didrocks: and yes, the fts extension still lives in lp:zeitgeist-extensions - it has seen no changes recently
[14:13] <didrocks> smspillaz: urgh, ok, that's related to the bug I subscribed you in any case…
[14:14] <kvalo> smspillaz: yeah, after dbus-send I need to switch from vt back to x and then I get the log file
[14:14] <smspillaz> kvalo: could you mail me those logs ?
[14:16] <conscioususer> excuse me, sorry to disrupt the current discussion, is there someone here who I can ask a small design question about the appmenu to?
[14:16] <kvalo> smspillaz: copying them to my workstation right now. you will get them in three mins
[14:32] <kamstrup> smspillaz: can https://bugs.launchpad.net/unity/+bug/703411 be marked as bitesize?
[14:32] <kamstrup> seems like a nice self contained task at least
[15:37] <nmarques> tedg, Ted, anyway I could have a minute with ya? There's one question I have around libindicate in which I believe you can help me (gobject-introspection related)
[15:39] <tedg> nmarques, Sure.  What's up?
[15:39]  * tedg is not sure he can answer gobject-introspection questions, but will try.
[15:41] <nmarques> tedg, for the latest version of libindicate, has any special patch been applied to the gtk2 stack ?. I've managed to fix it for the previous version, but this one is breaking on locating CLI files
[15:45] <tedg> nmarques, No, I don't think so.
[15:46] <tedg> nmarques, We had to do some adjustments to the command line parameters for Natty, but that wasn't patching, just cleaning things up.
[15:47] <nmarques> tedg, ok. I'm just asking because I saw a bug report from someone at Frugalware which seems to be running against the same issue
[15:47] <\sh> ogra: metacity building...sorry for taking so long..but real live work as prio 1 :)
[15:48] <ogra> indeed
[15:48] <nmarques> tedg, I'll take a closer look into this. If there's need for patching, I'll submit it.
[15:48] <ogra> my lappie is still on its was maverick -> natty :/
[15:48] <ogra> *way
[15:49] <tedg> nmarques, Great!  Thanks, sorry I'm not that familiar with the introspection stuff.
[15:51] <\sh> ogra: now...when metacity was build .. I have to rebuild compiz?with new libmetacity packages, right?
[15:51] <ogra> yep
[16:23] <\sh> ogra: building..rushing home now will check a bit later if everything is ok..metacity build successfully
[16:23] <ogra> cool
[16:23] <ogra> did the patch apply cleanly to the natty version ?
[16:24] <ogra> or did you have to touch it
[16:24] <\sh> ogra: yes it applied and no i didn't :)
[16:24] <ogra> awesome
[16:24] <\sh> I'll fetch the buildlogs when I'm at home ...
[16:25]  * \sh needs to fix the kitchen first...if not Madame Adig will be not amused ;)
[16:25] <\sh> laters...
[16:25] <ogra> ciao, and thanks a lot !
[16:50] <tedg> kenvandine, Can you see if lp:~ted/dbusmenu/builder-crash fixes your nm-applet issue?
[16:50] <kenvandine> will do
[17:02] <rodrigo_> API, ping
[17:07] <rodrigo_> njpatel, ping
[17:08] <njpatel> rodrigo_, hey hey hey
[17:08] <rodrigo_> njpatel, I have a few doubts on the panel stuff in unity
[17:09] <rodrigo_> there are Panel* classes in src and then the panel service in services/
[17:09] <njpatel> yep
[17:09] <rodrigo_> so, can you explain me what each does?
[17:09] <njpatel> rodrigo_, the panel service loads the indicators and their menus in a separate process, and then exports the state of the indicators (just the top row of labels/icons) as a model over D-Bus
[17:10] <rodrigo_> njpatel, ok, and then the Panel classes do the actual rendering of the panel, right?
[17:10] <njpatel> rodrigo_, Unity (src/Panel*) connects to this D-Bus daemon and renders the panel using this exported state. If something is clicked, it requests that the menu is shown (to the panel-service)
[17:10] <njpatel> rodrigo_, and then there is a bit of code either side to keep things in sync
[17:11] <rodrigo_> and why is it in a separate process?
[17:11] <njpatel> rodrigo_, so if the indicators crash, we can safely reload without having to crash compiz too
[17:11] <rodrigo_> ah ok
[17:11] <njpatel> rodrigo_, it was a common point of failure in the last Unity
[17:11] <rodrigo_> so, the panel service just manages the indicators?
[17:11] <njpatel> yep
[17:11] <njpatel> it might do more in the future, but that's it for now
[17:12] <rodrigo_> and the rest of stuff shown in the panel (home button, etc) is all managed in the Panel* classes?
[17:12] <rodrigo_> that is, no UI in the panel service?
[17:14] <rodrigo_> or rather, who owns the actual menus that are shown when you click on indicators?
[17:15] <kenvandine> tedg, yes it does appear to fix nm-applet
[17:17] <tedg> kenvandine, Sweet!
[17:17] <kenvandine> tedg, should i distro patch?
[17:17] <kenvandine> that is kind of a nasty bug
[17:25] <tedg> kenvandine, Sure
[17:25] <tedg> kenvandine, It's a pretty safe patch
[17:25] <kenvandine> looks like it
[17:25] <kenvandine> will do
[18:32] <jono> tedg, are you experiencing issues with indicator menus not working today in Unity
[18:32] <jono> none of my indicators or menus are working
[18:37] <kenvandine> jono, you mean not opening menus?
[18:37] <kenvandine> or not loading?
[18:37] <jono> kenvandine, not opening
[18:37] <kenvandine> ok, right click on the desktop
[18:37] <jono> I can see the menus, I click them and they don't drop down
[18:37] <kenvandine> i think that is the stacking bug in compiz
[18:38] <kenvandine> if you right click on the desktop, it seems to kick it into gear
[18:38] <jono> kenvandine, aha!
[18:38] <jono> I will check it out soon
[18:38] <kenvandine> jono, and if that doesn't work
[18:38] <kenvandine> like a right click doesn't show you a right click context menu
[18:38] <kenvandine> change workspaces
[18:38] <kenvandine> and right click again
[18:38] <kenvandine> it will work then
[18:39] <kenvandine> don't ask me why... but sometimes i have to do that
[18:39] <kenvandine> very annoying :)
[18:39] <jono> heh
[18:39] <kenvandine> it's like the old TV antennas
[18:39] <jono> kenvandine, works now, thanks!
[18:40] <kenvandine> hold the wire, stand on one foot and stick your arm out ... and hold it to watch tv :)
[18:40] <jono> haha
[18:41] <kenvandine> its kind of sad, my behavior has been altered... after logging in i automatically hit "ctrl-alt-left" then right click
[18:41] <kenvandine> :-p
[18:41] <kenvandine> whoops... ctrl-alt-right
[18:42] <kenvandine> i'll never notice when the bug is actually fixed, i guess
[18:43] <joaopinto> is that bug specific to natty's compiz / unity ?
[18:43] <kenvandine> yes
[18:44] <kenvandine> compiz i think
[18:44] <kenvandine> been there for quite a while
[18:45] <joaopinto> I have a similiar issue with 10.10, at random boot the gnome2 menu does not respond to clicks
[18:45] <joaopinto> boots
[18:45] <joaopinto> I was unable to find a reason, cpu is low and no relevant error :(
[19:18] <lamalex> jcastro, ping
[21:58] <TheMuso`> tedg: Are you ok if I assign the libindicator task to myself in bug 691677? I already have the code for that written here locally, and will push once I have code for all indicators and the applet ready for review.
[21:58] <TheMuso`> s/push/file a merge proposal/
[21:58] <tedg> TheMuso`, Okay, can you throw up the libindicator branch just so I can see it before you port everything?
[21:59] <TheMuso`> tedg: Sure, can do.
[22:33] <lamalex> wow empathy is segfaulting, and apport isn't catchin git
[22:41] <lamalex> appears to be a problem with webkitgtk
[22:41] <lamalex> and debugging symbols have clonflicts
[22:41] <lamalex> cool
[22:41] <TheMuso> Lovely.
[22:45] <RAOF> Is there a -dbg as well as a -dbgsym?  The -dbgsym takes a little while to actually get published, in my experience.
[22:54] <coz_> hey guys.. has anyone noticed  these white triangles showing up on certain docks..dialogs..or applications?  http://dl.dropbox.com/u/132551/screenshots/white-triangle.png
[22:56] <RAOF> Oh, yeah.  I need to file a bug on that.
[22:58] <coz_> RAOF,   ah cool... apparenlty it is showing up for a few people...
[22:58] <RAOF> Presumably everyone using the new GTK
[22:59] <coz_> RAOF,  that must be it... it first showed up ...here... using cairo dock... it is constant  also on a few dialogs for me anyway
[23:29] <coz_> RAOF,   was this t
[23:29] <coz_> RAOF,   was t his intended as a "grab handle" ?
[23:29] <RAOF> Yes, it is.  You're looking at bug #704105
[23:32] <coz_> RAOF,  ok thanks... I wonder if it could just be "transparent"  making the "grab area "  larger but not visible?