[09:17] <sense> good morning
[09:19] <kenvandine> good morning sense
[09:26] <bratsche> Morning.
[09:49] <kenvandine> bratsche, how is the appmenu fallback thing coming?
[09:49] <bratsche> kenvandine: I've got it all setup, testing and working out bugs right now.
[09:49] <kenvandine> ok
[09:49] <kenvandine> thx
[10:03] <klattimer> anyone know how I can test vino-server so the output appears on the command line?
[10:06] <seb128> run it on a command line?
[10:08] <klattimer> seb128: vino-server?
[10:08] <klattimer> hmm
[10:08] <seb128> yes
[10:08] <klattimer> not sure that works as I'm starting/stopping it to test
[10:09] <seb128> does it print output in .xsession-errors?
[10:09] <seb128> otherwise I guess use g_log
[10:09] <seb128> and write in a log file
[10:13] <klattimer> .xsession-errors has it
[10:13] <klattimer> cheers
[10:55] <kenvandine> klattimer, anything you need help with now? or are you good for now?
[10:55] <klattimer> kenvandine: I'm ok for now
[10:55] <kenvandine> great
[10:56] <klattimer> trying to find out a) where the sigterm comes from when disabling vino, and b) why vino_mdns_stop is hanging
[11:01] <klattimer> well vino_mdns_stop is hanging on avahi_entry_group_free
[11:56] <jcastro> kenvandine: is there an acl for allowing klattimer to assign bugs to you guys that he's finished off and is ready to be packaged.
[11:56] <klattimer> jcastro: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/497883
[11:56] <klattimer> that be the bug
[12:03] <kenvandine> jcastro, i really don't know...
[12:11] <davidbarth> klattimer: very cool job with the patch; jcastro just mentioned it and we'll be looking for some n-osd bugs for you right after lunch
[12:15] <klattimer> davidbarth: cool
[12:15] <klattimer> I'm currently poking ibus app-indicator stuff
[12:15] <klattimer> I'd like to get my teeth into this one before i start on n-osd
[13:06] <jcastro> klattimer: also, note the priority will still be app indicator bugs first, but at the rate you're going we might as well queue up a larger batch. :D
[13:06] <thorwil> mpt: meeting?
[13:10] <wers> mpt, you there?
[13:22] <C10uD> hey, any chance someone takes a look at this? https://bugs.launchpad.net/indicator-application/+bug/607831
[13:31] <jcastro> C10uD: ping tedg when he's around, he can help you
[13:32] <seb128> ted might not be around for a while
[13:33] <C10uD> i already told him some days ago, then i wrote some code but this whole appind thing is making my head spin so i don't know if i'm doing right, and if you want this kind of thing
[13:34] <jcastro> sense: what do you think? ^
[13:34] <sense> jcastro, C10uD: I could take a look at some code.
[13:35] <sense> C10uD: Do you have a patch or branch somewhere?
[13:35] <C10uD> branch linked in the bug
[13:35] <sense> Great! I'll take a look.
[13:35] <C10uD> note: it's not working atm
[13:36] <sense> :)
[13:37] <C10uD> quick question: is it possible to put images in appind menus? didn't find a way to do it
[13:38] <sense> Not that I'm aware of.
[13:38] <sense> Maybe it is.
[13:38] <sense> yeah, sounds plausible
[13:38] <sense> It should be possible, just do it the regular way and I think it should just work.
[13:39] <C10uD> i could only set gtk stock icons, not gtk imagemenuitems
[13:39] <C10uD> i'll try again though
[13:39] <sense> ok
[13:40] <iffypop> The sound menu has images in it...
[13:41] <C10uD> you mean, the new one that will be in mav?
[13:41] <iffypop> Yes.... Just pointing out that it is out there already in some form.
[13:41] <C10uD> anyway i always forget to say i'm working with python-appind
[13:42] <sense> C10uD: But the Sound Menu is an Indicator Applet, not an Indicator Application.
[13:42] <iffypop> sense: Ah, important distinction. My bad.
[13:43] <C10uD> ok, well then, supporting gtk imagemenuitems should be done if it's not already (imo)
[13:45] <sense> C10uD: You pushed your branch to lp:~username/indicator-application/ubuntu, but it should have been lp:~username/ubuntu/indicator-application/custom-name since you based it on the packaging branch, not upstream trunk.
[13:46] <C10uD> sense, sorry, i really got confused by all of this :)
[13:46] <sense> ok
[13:47] <C10uD> and don't really know how launchpad-work should be done, i usually use github and stuff
[13:47] <sense> C10uD: You want to work on lp:indicator-application as that is the code the developers are working on, lp:ubuntu/indicator-application (== lp:ubuntu/maverick/indicator-application) is the version packaged in Ubuntu and should only be adapted if we want to diverge from upstream, which we don't want here.
[13:48] <C10uD> ok
[13:49] <sense> C10uD: lp:~username/indicator-application/custom-name is in the repository of the development version, which is different from the Ubuntu packaged one.
[13:49] <sense> C10uD: Could you please try to create a new repository tree based on lp:indicator-application? That would make it much easier for me to test.
[13:49] <C10uD> ok, i'll try
[13:49] <sense> C10uD: Also, try to prevent from including build stuff in the commits. Maybe you could create copies for when building to prevent files from slipping through.
[13:58] <C10uD> so, now i should push to lp:~c10ud/indicator-application/runtime-themepath-change
[13:59] <C10uD> here it is https://code.launchpad.net/~c10ud/indicator-application/runtime-themepath-change
[14:00] <sense> C10uD: Looking at it.
[14:02] <C10uD> i think it's missing some other change..mmm
[14:03] <sense> And what's not working about it?
[14:04] <sense> C10uD: Have you committed the changes to app-indicator.c, the library?
[14:04] <sense> Otherwise the function is not exposed to applications.
[14:05] <C10uD> sense, changes incoming
[14:05] <sense> ok
[14:06] <sense> tedg! Not all files in indicator-application are following the code guidelines! I saw real tabs!
[14:06] <jcastro> sense: oh ted is on holiday for a while
[14:06] <sense> ah
[14:06] <jcastro> sense: I know I know, no one to pick on
[14:06] <C10uD> rev144 avail
[14:06] <sense> good
[14:06] <sense> jcastro: Canonical should mandate one. :)
[14:08] <sense> C10uD: and you said something didn't work. What doesn't work?
[14:09] <C10uD> the thing i was trying to implement :p
[14:10] <C10uD> i think i should make a simple example for testing..
[14:15] <klattimer> anyone know when tedg will be available?
[14:15] <jcastro> he's on holiday
[14:15] <jcastro> klattimer: bratche's your technical contact in the meantime
[14:16] <klattimer> k
[15:04] <sense> C10uD: Just letting you know that I'm still working on your branch. I went through the code, changed a few things and am now building it again as .deb package to test it.
[15:05] <C10uD> sense, great!
[15:17] <sense> C10uD: Have you got an example that can be used to test it?
[15:19] <C10uD> sense, if you could give me the debs i can test it, otherwise there's emesene2 that currently uses that feature
[15:19] <C10uD> s/uses/wants to use/
[15:20] <sense> I'll try something myself.
[15:20] <sense> When it seems to work I'll push it so you can take a look.
[15:20] <C10uD> ok, neat
[15:53] <sense> C10uD: I pushed the changes I made to lp:~sense/indicator-application/runtime-themepath-change so you can see them, but I have to add that your problem isn't resolved yet: nothing happens. Nothing crashes as well, though. I've also removed your NULL checks to allow people to set the theme path to NULL.
[15:56] <sense> found!
[15:56] <sense> I think I may have found the reason why nothing is happening still, related to my name changes.
[16:00] <C10uD> let's hope so :p
[16:38] <sense> C10uD: Could you please test lp:~sense/indicator-application/runtime-themepath-change? I'm not sure if I'm testing it correctly, but I am sure that the theme path is now at least sent up to and including the last signal. Maybe I'm not using the the theme path thing correctly (wrong folders and such), but you could give it a try.
[16:38] <sense> C10uD: I'm now busy with other things, but I hope to have helped you a bit with my changes. Please feel free to merge the code before continuing to work on it yourself.
[16:54] <C10uD> sense, thanks, i'll try it
[16:55] <sense> great!
[16:57] <C10uD> sense, one quick question: how do you test it? get a debian folder from somewhere then package and install or anything else?
[16:59] <sense> C10uD: That's what I did. Make a build copy of the working branch (important to not contaminate your sources), get the source using 'apt-get source indicator-application' (the branch is too old, doesn't work), and then 'dch -n', './autogen.sh' and 'debuild'.
[17:00] <C10uD> ok thanks, will try it
[17:01] <C10uD> oh wait, the indicator-application shipped with lucid is different from trunk (there's a subfolder in the old one)
[17:01] <C10uD> i suppose you're using maverick
[17:02] <sense> yes
[17:02] <sense> You're not?
[17:02] <sense> ah
[17:02] <C10uD> i'll get maverick tgz and try then
[17:02] <sense> You really want to work on the trunk, most certainly not on the Lucid version since that is already much older compared to the trunk.
[17:02] <sense> tgz?
[17:04] <C10uD> tar.gz with debian stuff
[17:04] <C10uD> i guess (hope) there won't be much difference
[17:05] <sense> not sure
[17:05] <sense> You could get problems with dependencies. libindicator, libindicate and libdbusmenu got large updates already
[17:07] <C10uD> ouch
[17:12] <sense> C10uD: Maybe https://launchpad.net/~indicator-applet-developers/+archive/indicator-core-ppa can help you get some more up-to-date dependencies.
[17:12] <C10uD> virtualbox will be my friend then
[17:12] <C10uD> oh let's see that
[17:13] <sense> virt-manager!
[17:13] <C10uD> the ppa seems quite outdated
[17:13] <C10uD> already found a premade maverick VDI thanks
[17:13] <sense> ok
[17:38] <C10uD> lol maverick32 virtualboxed is faster than my "real" lucid x64
[17:52] <sense> And stuff is working somwhat in Deluge! Hurray for step one! :P
[17:52] <sense> The separator in the submenu is picked up! Now the rest of the items.
[17:55] <jcastro> \o/
[17:59] <sense> but first: dinner
[18:09] <C10uD> sense, it works!!!
[18:09] <C10uD> :)
[18:13] <C10uD> ok, now we just need some of the boss to take a look at the branch
[18:13] <C10uD> https://bugs.launchpad.net/indicator-application/+bug/607831
[18:13] <C10uD> i set it to Fix committed, unsure if it's the correct status
[18:37] <sense> C10uD: great!
[18:37] <sense> C10uD: Did you have to change anything?
[18:37] <sense> C10uD: Actually, that's not Fix Committed yet, for that it has to be in the trunk.
[18:46] <C10uD> sense, no change, just got the package source, overwrite files, built package, reboot
[18:46] <C10uD> and it worked as expected
[18:46] <sense> Good news!
[18:46] <C10uD> can you set it to the correct status/people so we can get this reviewed better (?) and/or pushed in mainline?
[18:46] <sense> I've done so.
[18:47] <sense> C10uD: Thank you for working on this, it is really nice that we've got now working support for icon theme path changes.
[18:47] <C10uD> np, i expect to get gtkimagemenuitem support in exchange :p
[18:48] <C10uD> thank you for cleaning up the code so it has a better shape
[18:48] <sense> You're welcome. I'm glad I could help.
[18:50] <sense> I made a lot more changes than what was strictly speaking necessary to get things working because I wanted to take the chance to unify the names used for referring to the icon theme path in the source code. The most important thing I fixed was adding the signal to an XML file.
[18:51] <sense> The rest is mostly unifying variable and function naming and tweaking the selection criteria for the theme path and make everything work in the bindings.
[18:51] <C10uD> you're not done yet, you still need to poke the right people to get this in trunk, because i don't know who i should poke and i see on planet you're having an hard time reviewing patches
[18:51] <C10uD> :)
[18:52] <sense> C10uD: Now the merge request is filed it ought to show up on the lists of people, but with Ted on holiday things might require a little more pushing. :)
[18:52] <sense> This is no patch, but a merge request, which gets reviewed sooner because it's easier and there is less backlog.
[18:53] <C10uD> since (i think) we're far from codefreeze i think it's no big deal waiting, thanks for your interest in this patch, going afk
[18:53] <C10uD> see ya
[18:54] <sense> bye!
[20:51] <atrus> i'm having trouble getting messaging menu blacklists to work.
[20:52] <atrus> i copied everything from /usr/share/indicators/messages/applications/ into ~/.config/indicators/messages/applications-blacklist/ . it seemed to disable at least some of them, but when i logged back in, they all came back again. any suggestions?