[09:29] <klattimer> didrocks: I just added a disable gobject introspection patch
[09:29] <klattimer> to the ibus branch i've got
[09:35] <didrocks> klattimer: hey, we don't ship gobject introspection with the package?
[09:35] <klattimer> didrocks: I want this pushed into maverick, so if building introspection is broken lets just disable it
[09:36] <klattimer> I don't think anything actually uses it right now anyway
[09:36] <klattimer> the patch could be improved, in that I set the configure args in rules rather than set the defaults properly
[09:36] <klattimer> in the patch
[09:36] <klattimer> but I'm going to fix that now
[09:37] <didrocks> klattimer: the build is broken in natty, I didn't test on maverick when I saw it broken in natty
[09:37] <klattimer> k
[09:37] <klattimer> well, atm ibus is unusable on maverick
[09:37] <didrocks> klattimer: but right, from what I see, we don't ship gobject-introspection
[09:37] <didrocks> klattimer: so, sounds good :)
[09:37] <klattimer> so that should be a priority
[09:37] <didrocks> klattimer: I'm building it in a pbuilder, I just don't have a maverick box to confirm
[09:38] <didrocks> klattimer: let me testbuild and upload that then
[09:48] <didrocks> klattimer: did you try to build your branch btw? the 05_appindicator.patch doesn't apply
[09:50] <didrocks> refreshing it is quite easy, but I prefer you to check on maverick first :)
[10:43] <klattimer> kenvandine: I think the current ibus_1.3.7.orig.tar.gz in source repo is corrupted somewhere down the line
[10:43] <klattimer> it says my indicator patch is already applied to it, partly
[10:43] <klattimer> :/
[10:44] <klattimer> didrocks: not sure if this will be causing any difficulties for you :/
[10:44] <didrocks> kamstrup: I would prefer to have ken fixing that and that I just have to sponsor it. I don't really have the time to have a deep look there. We'll see with him once there
[10:45] <didrocks> oupss klattimer ^^
[10:45] <klattimer> k
[13:09] <klattimer> kenvandine: about yet?
[15:02] <seiflotfy> njpatel, kamstrup
[15:02] <seiflotfy> http://paste.ubuntu.com/532376/
[15:06] <njpatel> seiflotfy, https://launchpad.net/~unity/+archive/ppa?field.series_filter= has the compiz you need, and it's about to get the updated bamf you need too
[15:07] <seiflotfy> njpatel, i already installed the latest compiz
[15:07] <seiflotfy> i installed bamf from source
[15:07] <seiflotfy> i am removing my install from the ppa
[15:07] <njpatel> alright, so itlooks like unity can't find the bamf you installed. Where did you install it to?
[15:08] <njpatel> (which prefix)
[15:08] <seiflotfy> heheh
[15:09] <seiflotfy> got it
[15:09] <seiflotfy> :)
[15:09] <seiflotfy> njpatel, changed the prefix
[15:09] <seiflotfy> do u mind if i edit the wiki
[15:10] <njpatel> seiflotfy, please update it dude, with anything that was missing
[15:10] <seiflotfy> ok
[15:10] <seiflotfy> njpatel, first one has to make sure that the ppa stuff is uninstalled if one wants to work form source
[15:10] <seiflotfy> :P
[15:10] <seiflotfy> njpatel, brb got to logout
[15:11] <seiflotfy> ok so unity installed and everyting
[15:12] <seiflotfy> however cant run ccsm
[15:12] <seiflotfy> njpatel,
[15:12] <seiflotfy> i have
[15:12] <njpatel> error or can't find it?
[15:12] <seiflotfy> Compiz 0.9.2.1
[15:12] <seiflotfy> installed
[15:12] <njpatel> you probably need to install it
[15:12] <seiflotfy> Traceback (most recent call last):
[15:12] <seiflotfy>   File "/usr/bin/ccsm", line 126, in <module>
[15:12] <seiflotfy>     context = compizconfig.Context(screens)
[15:12] <seiflotfy>   File "compizconfig.pyx", line 1082, in compizconfig.Context.__cinit__ (src/compizconfig.c:9190)
[15:12] <seiflotfy> TypeError: an integer is required
[15:12] <njpatel> urgh
[15:12] <njpatel> seiflotfy, try on #compiz
[15:19] <didrocks> kenvandine: I think klattimer wanted to discuss some ibus issue with you ^
[15:20] <didrocks> kenvandine: short summary, the patch doesn't apply for me
[15:20] <didrocks> or use the packaged version?
[15:20] <didrocks> seiflotfy: ^^
[15:20] <didrocks> at least, you avoid those trobles
[15:20] <didrocks> troubles*
[15:30] <kenvandine> klattimer, ??
[15:32] <klattimer> kenvandine: I've got all kinds of broken with these patches but I think i've sorted it out
[15:32] <klattimer> and as a result have two patches
[15:32] <klattimer> one to replace 03 and one for 05
[15:32] <klattimer> which should both work properly
[15:32] <kenvandine> klattimer, ok... i was having trouble with those patches too at uds
[15:33] <klattimer> http://bazaar.launchpad.net/~karl-qdh/ubuntu/maverick/ibus/ibus-indicator/files/head:/debian/patches/
[15:33] <klattimer> there they are
[15:33] <klattimer> should work properly now
[15:35] <kenvandine> ok, i'll grab in a few
[15:41] <didrocks> kenvandine: did you try to build the previous ones?
[15:41] <didrocks> as I get stuck when trying them :)
[15:41] <didrocks> kenvandine: also, you need to collapse -0ubuntu4 and -0ubuntu5
[15:43] <kenvandine> didrocks, for ibus?  i couldn't build them... seemed quilt was unhappy
[15:43] <kenvandine> and i didn't have time to figure out why
[15:43] <kenvandine> last i looked
[15:44] <didrocks> kenvandine: why did the sponsor went on my plate then? :) I'm puzzled!
[15:44] <didrocks> I was thinking I just need to sponsor your ack :)
[15:44] <didrocks> hence my surprise
[15:44] <kenvandine> oh... for ibus?
[15:44] <didrocks> yeah :-)
[15:44] <didrocks> no worry, if karl sorted that, it's fine
[15:45] <kenvandine> sorry, no, i never got it properly built while at uds and the few fixes we had tried didn't actually seem to fix ibus for me
[15:46] <kenvandine> klattimer, did you see my comment the other day about focus-in and focus-out events?
[15:46] <klattimer> nope?
[15:46] <klattimer> kenvandine: this is a new pair of patches which fixes all of those issues
[15:47] <kenvandine> klattimer, great
[15:47] <kenvandine> so i found something in debugging the indicator-me entry field, and the hint not getting cleared
[15:47] <kenvandine> the entry gets the focus-in, focus-out and grab-focus events all at the same time
[15:48] <kenvandine> so i was thinking perhaps whatever is causing that problem, was causing the problems you had around focus events
[15:49] <klattimer> kenvandine: it's possible but what I've done works around it solidly
[15:49] <kenvandine> cool
[15:49] <kenvandine> i am pretty puzzled by the indicator-me problem
[15:50] <kenvandine> we need to clear the hint when i grabs
[15:50] <kenvandine> and we need to add the hint back on focus-out if you haven't entered any text
[15:50] <kenvandine> which we can't do... since we don't get focus-out when losing focus :)
[17:30] <kenvandine> tedg, btw, ubuntu-geoip has been uploaded, in the new queue for natty now
[17:30] <kenvandine> tedg, so you might want to merge the ~ubuntu-desktop/ubuntu-geoip/ubuntu changes back now
[17:30] <tedg> kenvandine, Sweet!
[17:33] <tedg> ronoc, Is there a way that the indicator-sound-service could register for media keys so if I hit "play" on my keyboard and Rhythmbox wasn't running it could start it, and hit play?
[17:34] <kenvandine> tedg, i can't seem to file the MIR bug until it gets out of NEW
[17:34] <tedg> kenvandine, Hmm, seems like a bug in the process :)
[17:34] <kenvandine> yeah... :)
[17:35] <seb128> kenvandine, well file the bug and reassign later
[17:36] <kenvandine> nah... i'll just wait
[17:39] <ronoc> tedg, it could start the app and play no problem where do I register for the media key event though way down in the service
[17:40] <tedg> ronoc, I think you ask gnome-settings-daemon for them.
[17:40] <tedg> ronoc, I'm not sure if more than one person can get them.
[17:41] <sense> You might want to edit the actions, rather than creating new actions for the Sound Menu.
[17:42] <sense> i.e. Edit the Play/Pause action that is set to the PlayPause button by default to first try the Sound Indicator.
[17:42] <sense> if that is how you can do it, of course. I'm not really familiar with the technology, just guessing how it probably works.
[17:46] <ronoc> tedg, I think i might have a long outstanding bug about this
[17:47] <tedg> Yeah.  I'm not sure it's a bug.  But, I notice that I tend to "hit play" when I want music to happen.  Then if it doesn't, I figure out of RB is running.
[18:27] <sense> jcastro: You said there were upstreams interested in participating in the One Hundred Paper Cuts project. Which upstreams?
[18:34] <jcastro> yikes, ambush!
[18:34] <jcastro> sense: I can think of a few, why, you need some?
[18:35] <sense> jcastro: I'm currently editing the wiki documentation of the One Hundred Paper Cuts project, specifically the requirement for valid paper cuts. We decided to not only accept paper cuts found in applications part of the default installation, but also paper cuts in featured applications and applications from participating uptreams.
[18:35] <sense> jcastro: I would like to say which upstreams participate.
[18:37] <jcastro> ok I am confused
[18:37] <jcastro> "We decided to not only accept paper cuts found in applications part of the default installation, but also paper cuts in featured applications and applications from participating uptreams."
[18:37] <jcastro> ok so
[18:37] <jcastro> stuff by default and stuff in featured we WANT to participate
[18:37] <jcastro> but stuff outside the scope not so much?
[18:38]  * sense is taking a look at the Gobby notes of the session.
[18:40] <sense> jcastro: I can't find much more than what you can find in the blueprint's whiteboard <https://blueprints.launchpad.net/ubuntu/+spec/other-design-n-papercuts>, but if I remember correctly we did talk about helping upstreams who want to participate.
[18:40] <sense> jcastro: Although it might indeed be a bit too far out of the scope of the project, making things unclear.
[18:40] <sense> vish: ^^
[18:40] <jcastro> ok, I'll start on banshee then
[18:40] <jcastro> that'd be a good target
[18:41] <sense> jcastro: ?
[18:42] <jcastro> yeah
[18:42] <sense> I do think that it would be good to focus on Banshee, but now that it is very likely to be the next default media player it isn't just an upstream project anymore.
[18:42] <jcastro> I believe that was a response to andreas from tbird asking if they can participate
[18:42] <vish> jcastro: banshee is already in the default and is one of the milestone.. i thought the find interested upstreams was for the featured apps?
[18:42] <jcastro> OH.
[18:42] <jcastro> I see
[18:42] <sense> vish: You've already created milestones?
[18:43] <vish> sense: not yet, will announce soon
[18:43] <sense> great
[18:43] <sense> So no random upstreams who want to participate?
[18:43] <sense> ok
[18:43] <jcastro> right
[18:43] <jcastro> ok I remember now
[18:43] <sense> I agree with that.
[18:43] <vish> well, if some upstream wants to, why not …
[18:44] <jcastro> it was something like "Hi $upstream, we're featuring you for ubuntu 11.04, we'd like to work with you on papercuts ... "
[18:44] <sense> That's what you said too at the UDS.
[18:44] <sense> I must have missed that part.
[18:44] <vish> yup..
[18:45] <vish> but its easier to start with the featured apps, and just call for other upstreams interested.. rather than asking every upstream
[18:45] <sense> I do think we need to make sure the scope of the One Hundred Paper Cuts project doesn't get too wide, otherwise it will lose cohesion.
[18:45] <vish> yea..
[18:45] <jcastro> ok just update the WI pls.
[18:45] <sense> I'll don't mention 'upstreams who want to participate' in the requirements, just the default applications and featured ones, to make thigns clear.
[18:45] <jcastro> vish: yeah
[18:46] <jcastro> sense: well, let's start with one
[18:46] <jcastro> getting things gnome for example
[18:46] <jcastro> we know them already
[18:46] <sense> Is that featured? Yes, then it is a valid paper cut.
[18:46] <jcastro> so if we mess it up they won't hate us too much
[18:46] <sense> I'm talking about requirements for paper cuts here, not possible upstreams to participate with.
[18:47] <jcastro> it is
[18:47] <sense> Contacting upstreams is step two.
[18:47] <jcastro> oh
[18:47]  * jcastro goes back to staring at the wall
[18:47] <sense> vish, jcastro: I'm also going to emphasise that papercuts is all about "_applications and upstreams_", like we decided.
[18:47] <jcastro> ok, poke me at 2
[18:47] <sense> jcastro: How is your Flesh Wounds project coming along?
[18:48] <sense> jcastro: Will poke you!
[18:48] <jcastro> but on a semi-related note
[18:48] <jcastro> if we can get a few in for banshee that would be <3
[18:48] <sense> I think Vish already has a milestone ready for Banshee.
[18:48] <sense> So that should be fine!
[18:49] <jcastro> hah
[18:49] <jcastro> once the bugs start coming in they can flesh them out
[18:49] <jcastro> I'm going with "bitesize" instead of fleshwound
[18:49] <sense> Sounds nicer. :)
[18:49] <jcastro> but not enough people can get compiz-ubuntu working yet to have a titanic flood of bugs
[18:49] <sense> We had 400 flesh wounds reported for Unity!
[18:49] <sense> argh
[18:50] <sense> jcastro: I can't get it working either.
[18:50] <jcastro> I suspect the maverick PPA and putting it in natty proper this week will fix that
[18:50] <sense> lets hope so
[18:50] <jcastro> omg?
[18:50] <jcastro> link?
[18:50] <sense> no
[18:50] <sense> No 400 reported! I just want to test how that sounded. ;
[18:50] <sense> )
[18:51] <sense> It sounds a bit awkward.
[18:52] <sense> Sorry for scaring you!
[18:53] <vish> bratsche: hi, when with the gtk resize-grip land in Natty?  we were considering it as one of the milestones for the papercuts , to identify apps/windows which are missing the grip..
[18:53] <vish> when will*
[18:55] <bratsche> vish: I guess whenever it makes it into a gtk+ release and that release goes into Natty.  It's in upstream git.
[18:55] <bratsche> It may be in a release, I'm not even sure.
[18:55] <vish> hmm..
[18:55] <vish> seb128 any idea^?
[18:56] <vish> bratsche: if any window does not have the grip, what do you need? any debugging? or screenshot?
[18:57] <bratsche> vish: Windows should all have grips.  Places that we may need to do some work are finding apps where the grip looks out of place, or is covering some content or an important widget.
[18:57] <vish> ah ha!
[18:57] <bratsche> vish: Those cases will probably have to be handled on a per-app basis.
[18:58] <vish> bratsche: cool! so that would be a bug in the app, and the app needs fixing..
[18:58] <bratsche> Yes.
[18:59] <bratsche> vish: Feel free to file those bugs in Launchpad, but we should also make every effort to get those bugs and any patches we make upstream as quickly as we can.
[18:59] <bratsche> imo
[19:00] <vish> yup.. will be sent upstream as well..
[19:01] <bratsche> vish: As discussed at UDS, I think gnome-terminal will be an exceptional case.  It was pointed out that some people like to disable the scrollbar entirely and may want to disable the resize grip entirely as well, so that may need to be extra UI in the profile options page.  But I think we should consult the upstream maintainer before investing that effort.
[19:03] <vish> bratsche: yea, i dont think we would be patching on a distro basis, as this is grip is in upstream as well, the app maintainers would be than willing to fix the problems, imo..
[19:03] <vish> bratsche: it think mpt was more concerned about the windows not having a grip
[19:04] <bratsche> vish: Oh right.
[19:04] <bratsche> vish: Well, I guess we need to decide whether to keep a backported patch for gtk2 apps.
[19:05] <bratsche> I have done an initial backport to gtk2, but it's a little buggy and I wasn't expecting we would be using it in Natty so I never bothered fixing the bugs. :)
[19:05] <bratsche> (it works fine, but the rendering is a little glitchy)
[19:05] <vish> bratsche: hehe, i got assigned the task to oversee the update https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection-dx-n-resizing-windows
[19:06] <bratsche> Okay
[19:06] <bratsche> vish: I guess it would be worth finding out how many apps will be linking against gtk2 or against gtk3.
[19:07] <vish> bratsche: how do we do that?
[19:08] <bratsche> I'm not sure. :)
[19:08] <bratsche> seb128 might have some idea, but I dunno.
[19:11] <vish> oh well, once the grip lands bugs flowing in will probably give us a good idea. :D
[19:19] <bratsche> Yeah
[19:19] <bratsche> vish: Are you using Natty already?
[19:20] <fagan> bratsche: well ive been making any app since maverick on gtk3
[19:21] <fagan> just crappy little stuff but id say other people are doing the same
[19:26] <vish> bratsche: not in Natty yet...
[19:27] <fagan> vish: there isnt any major issues so there is nothing stopping you
[19:27] <vish> oh!
[19:28] <fagan> Ive been on it for 2 weeks now
[19:33] <sense> vish: Could you please update the description on <https://launchpad.net/hundredpapercuts> to comply with the new requirements as written down at <https://wiki.ubuntu.com/PaperCut>?
[19:43] <vish> sense: can you leave some images in that wiki page?;p
[19:44] <sense> vish: But the only one there was very large and not very helpful!
[19:44] <sense> vish: I removed only one. :)
[19:45] <sense> We shouldn't explain Launchpad in detail on that page.
[19:45] <vish> sense: oh! then add some there! :D
[19:45] <vish> yea..
[19:47] <vish> sense: i think its more of the tiny font size in the wiki which makes it look like there are more crowded?!?
[19:47] <sense> vish: The wiki makes the layout horrible. Not only does it not support italic, but it also screws up the lists.
[19:47] <sense> vish: You don't even notice the lists have subitems!
[19:47]  * vish not a fan of the new theme.. too many bugs.. :/
[19:49] <vish> sense: i dont seem to have the powers to edit the lp main page.. poking iain should be good
[19:49] <sense> The theme around the text isn't too bad. The theming of the text itself is horrible.
[19:49] <sense> vish: Ok, if that will do it, that will make me happy too.
[19:51] <vish> sense: yea, ping iain when he is around, he is quick with that, i usually ask him to update something on the lp page..
[19:51] <sense> ok
[19:51] <sense> will do so!
[22:41] <dashua> Missing some dependencies on the wiki, https://wiki.ubuntu.com/Unity/InstallationGuide
[22:41] <dashua> Should I edit it?
[23:12] <seiflotfy> DBO, u got a moment
[23:12] <DBO> whats up
[23:12] <seiflotfy> DBO, http://pastebin.com/nsVnUQQC
[23:13] <seiflotfy> i ran the ./tools/build-compiz-glib script in unity
[23:14] <DBO> something in compiz did not get the installed properly
[23:14] <seiflotfy> -.-
[23:14] <seiflotfy> i noticed
[23:14] <DBO> Im not sure dude
[23:14] <DBO> Im not big on install systems
[23:14] <seiflotfy> since when i try to run compiz++ its scred up
[23:15] <seiflotfy> brb
[23:16] <seiflotfy> ok back
[23:17] <seiflotfy> DBO, i will try again tomorrow
[23:17] <seiflotfy> i am trying ot work on the unity-ppl
[23:17] <seiflotfy> unity-places-people
[23:17] <DBO> you know the views for that in unity-compiz have not changed
[23:17] <DBO> erm
[23:17] <DBO> have not been made
[23:17] <DBO> the API has not changed however
[23:17] <seiflotfy> DBO, oh
[23:17] <seiflotfy> then how do i test my stuff
[23:17] <seiflotfy> ?
[23:18] <seiflotfy> lets say
[23:18] <seiflotfy> i run the unity-places-sample
[23:18] <seiflotfy> i cant see an icon being added anywhere on the dock
[23:18] <DBO> unity mutter for now
[23:18] <DBO> you wont see anything yet
[23:18] <DBO> I am actually in the process of building those icons a place to live
[23:19] <seiflotfy> DBO, ok cool