[11:40] <C10uD> hello, i updated bug 527061
[11:40] <ubot4> Launchpad bug 527061 in indicator-application "python bindings for libappindicator don't allow to change icon-theme-path (affects: 2)" [Undecided,Confirmed] https://launchpad.net/bugs/527061
[11:40] <C10uD> i'm still unsure on how to test if this actually works, make&&make install the bindings doesn't produce any difference..
[15:00] <jcastro> morning seb128 
[15:00] <seb128> hey jcastro
[15:00] <seb128> how are you today?
[15:00] <jcastro> good
[15:00] <jcastro> did you see Kalle ported Tracker to a-i?
[15:00] <seb128> no I didn't
[15:00] <jcastro> https://bugs.edge.launchpad.net/ubuntu/+source/tracker/+bug/497912
[15:00] <seb128> nice ;-)
[15:00] <jcastro> !!!
[15:00] <ubot4> Launchpad bug 497912 in tracker (Ubuntu) "Support Application Indicators (affects: 1)" [Low,Triaged]
[15:01] <jcastro> seb128: so what's the plan for g-s-d?
[15:01] <jcastro> polkit-1-gnome is also ready!
[15:02] <seb128> g-s-d relies on those libgnomekbd refactoring which neither pitti or I like to get in distro
[15:02] <seb128> I guess I will have to sit down and look at this one this week
[15:02] <jcastro> ok
[15:11] <jpetersen> The code could basically be moved from libgnomekbd to g-s-d
[15:23] <qense> kklimonda: you're afk, but you'll probably read your pings: the text field in the Me Menu also sets your IM status after all. I was wrong.
[15:25] <jcastro> jpetersen: whichever makes it easier to put it in the distro I would guess. seb128?
[15:26] <seb128> jpetersen, I've not looked at the details but your change is change the way the code is structured a bit to make easier to share code between appindicator and notification?
[15:27] <jpetersen> for upstream it should be in libgnomekbd but for lucid just patching g-s-d would maybe be easier
[15:27] <seb128> right that's what I was thinking
[15:27] <seb128> could you work on that change?
[15:28] <seb128> I would prefer a code copy rather than a redesign
[15:28] <seb128> and better to not make those api public if not required
[15:28] <jpetersen> seb128, yes ok i will do
[15:28] <seb128> thanks
[15:28] <seb128> we also need to make sure to not break the screensaver lock screen
[15:33] <vish> tedg: would Bug #391414 be addressed for Lucid?  seems to be an a11y problem
[15:33] <ubot4> Launchpad bug 391414 in hundredpapercuts "Unable to shutdown system from GNOME using keyboard (affects: 1)" [Undecided,New] https://launchpad.net/bugs/391414
[15:33]  * vish thinking of assigning milestone for Lucid
[15:33] <tedg> vish: Yes, please do.
[15:33] <vish> tedg: shall i assign it to you?
[15:34] <tedg> vish: No, all bugs should always be assigned to kenvandine, it makes him feel loved ;)
[15:34] <tedg> vish: Yeah, to me :)
[15:34] <vish> hehe ;)
[15:37]  * vish first searches for dupes
[16:04] <dpm> hi jpetersen, I've been talking to jcastro about a translation issue from the Rhythmbox indicator and he told me you'd be the person to ask.
[16:04] <dpm> Here's the question:
[16:05] <jpetersen> hi dpm
[16:05] <dpm> hi :)
[16:05] <dpm> The "Show Rhythmbox" message on http://imagebin.ca/view/2Vubpv2T.html appears untranslated, and I'd like to find out why it's not translatable. The string does not seem to come from Rhythmbox itself. Any idea where it comes from?
[16:08] <jpetersen> dpm, it is from plugins/status-icon/rb-status-icon-plugin.c
[16:08] <dpm> ah, thanks jpetersen, let me have a look...
[16:09] <jpetersen> dpm, hm the app-indicator patch changed it from "Show Music Player" to "Show Rhythmbox", that was in the original patch
[16:09] <jpetersen> dpm, I am not sure why it was changed
[16:13] <dpm> I'm just looking at why the Show Rhythmbox message does not appear in the Ubuntu translation template, perhaps it was not marked as translatable in the patch
[16:14] <jpetersen> dpm, it is marked translatable
[16:15] <dpm> weird, the only similar message is "_Show Rhythmbox" in the Ubuntu template -> https://translations.launchpad.net/ubuntu/lucid/+source/rhythmbox/+pots/rhythmbox/ca/+translate?batch=10&show=all&search=show+rhythmbox
[16:16] <jpetersen> dpm, yes that is the right one
[16:17] <dpm> it's not, the one shown does not have the accelerator -> "Show Rhythmbox" <> "_Show Rhythmbox"
[16:20] <jpetersen> dpm, it seems there seems to be a problem with accelerators in the indicator applet
[16:21] <jpetersen> dpm, but it is that string
[16:38] <dpm> jpetersen, (sorry, I was on the phone). Ah, ok. Do you know if the problem with accelerators a known bug? If so, I'll subscribe to it, otherwise I'll file a new one, I just want to make sure that that string's translations are loaded
[17:11] <jpetersen> dpm, I have not found any bug
[17:12] <dpm> jpetersen, no worries, if it's actually that string, and if it's discarding the accelerator, I'll file a new one. Which source package would be the best to file it against?
[17:13] <jpetersen> indicator-application
[17:13] <dpm> thanks a lot for your help jpetersen!
[17:16] <jpetersen> dpm, your wlecome
[17:34] <Nafai> Hi guys
[17:34] <Nafai> Back from my appointments
[17:55] <jcastro> Nafai: I believe pitti had some questions outstanding on the vino work
[17:58] <Nafai> Ok
[17:58] <jcastro> Nafai: how's brasero coming along?
[17:58] <Nafai> No comments yet from upstream
[17:59] <Nafai> Fine, got one last issue if I don't figure it out soon I'll reach out for some help
[17:59] <jcastro> Nafai: oh right, you needed a GTK guru right?
[18:00] <Nafai> in general, yes, but for the specific problem now for brasero it is more of figuring out the right callback
[18:00] <jcastro> perhaps jpetersen?
[18:01] <jcastro> we need a box with glass and jpetersend in it ... "Break in case of App Indicator Emergency" 
[18:01] <Nafai> Heh
[18:02] <Nafai> Give me a few minutes and I'll see if I need help this time
[18:02]  * jcastro nods
[18:02] <jpetersen> jcastro, Nafai what is the problem?
[18:02] <Nafai> jpetersen: not an immediate problem at the moment, but are you going to be around for a while?
[18:03] <jpetersen> Nafai, yes I will have dinner soon, but I will continue to work for a bit after that
[18:03] <Nafai> Ok, I'll try to ping you quickly if I need help today
[18:03] <Nafai> thanks for being available
[18:03] <jpetersen> Nafai, ok :)
[18:03] <jpetersen> your welcome
[18:07] <jcastro> qense: hey, did you know we had a karmic app-indicator ppa already?
[18:07] <qense> jcastro: no :P
[18:08] <qense> Where?
[18:08] <jcastro> it's listed on the wiki page
[18:08] <qense> lol
[18:08] <jcastro> heh, it's been there since like December. :D
[18:08] <jcastro> for upstreams who want to play but don't want to run Lucid
[18:20] <C10uD> tedg, (sorry for the pinging) about bug 527061 , i posted a new diff. however, today i managed to correctly build the whole stuff, and seems like the 001 diff works correctly while the new one (002) doesn't. unfortunately there's little (read: no) documentation on bindings creations so i'm walking in the dark (i don't know how duplicate a constructor). any chance some expert can take a look at this? anyway, the 001 seems fine to me, if you wanna test it
[18:20] <ubot4> Launchpad bug 527061 in indicator-application "python bindings for libappindicator don't allow to change icon-theme-path (affects: 2)" [Undecided,Confirmed] https://launchpad.net/bugs/527061
[18:21] <tedg> C10uD: I'm not sure how to do that in Python either.  kenvandine, do you know how to overload a constructor?
[18:23] <C10uD> well, shouldn't be safe to use *_new_from_model? with plain *_new that path is set to Null, so there's little difference i think
[18:27] <Nafai> You don't overload the constructor in Python
[18:27] <Nafai> What I would do is add an optional parameter to __init__
[18:28] <C10uD> Nafai, but the defs file allows to specify optional parameters for the method from what i've read, and that's what i used
[18:28] <C10uD> it's just i'm using _new_from_model instead of plain _new when creating a new appindicator object, and i think there should be no difference (even if i didn't read the source, i admit)
[18:29]  * Nafai nods
[18:29] <C10uD> using _new sets that parameter to Null already 
[18:31] <C10uD> sorry if i'm bothering too much, but i really need that upstreamed in order to hax icons in the indicator :p
[18:32] <tedg> C10uD: I don't think it's an issue, just no one is quite sure how it should work.
[18:34] <C10uD> that sounds very reassuring
[18:34] <C10uD> heh
[18:35] <C10uD> anyway, here's my reference http://live.gnome.org/PyGTK/WhatsNew28#Hand-written_constructors_need_to_be_updated
[18:36] <C10uD> notice that appindicator seems using some going-for-deprecation syntax for bindings creation, but that's another story
[18:38] <C10uD> anyway, if there's something i can do to speed up the process let me know, i fear about python bindings be not ready for lucid.. 
[18:52] <Nafai> bbiab, lunch
[20:01] <jcastro> qense: that was awesome!
[20:01]  * qense blushes
[20:51] <jpetersen_> I am going to leave for the day
[20:51] <jpetersen_> bye bye
[21:11] <Nafai> jcastro: brasero patch attached and ready for review!
[21:11] <Nafai> jcastro: should I go back and separate the vino patch into two patches as suggested by pitti, or work on gnome-bluetooth first?
[21:31] <jcastro> Nafai: pitti's work first
[21:31] <Nafai> okay, figured as much
[21:31] <jcastro> good job on brasero btw!
[21:31] <Nafai> thanks
[21:32] <Nafai> Is the opportunistic developer week going well?  I've forgotten to pay attention today :(
[21:32] <jcastro> yeah, qense ran an app indicator session
[21:32] <Nafai> awesome
[21:32] <Nafai> He rocks
[23:23] <seg|ars> mpt: hey, is that bold/italic thing an official twitter feature? I haven't seen that before
[23:23] <seg|ars> mpt: it appears to be using an egregiously eccentric unicode hack
[23:24] <mpt> seg|ars, no, it's a practical joke
[23:24] <seg|ars> haha
[23:24] <mpt> Feel free to play along or dismiss it at your choice
[23:26] <mpt> seg|ars, I'm sure you could think of some earnest pledge to support all #twitterpremium features in Gwibber 3.0
[23:44] <seg|ars> mpt: http://img268.imageshack.us/img268/6862/gwibber3zomg.png ;-)
[23:45] <mpt> seg|ars, beautiful
[23:50] <mpt> seg|ars, misspelled the hashtag :-(
[23:51] <seg|ars> mpt: fixed. Thankfully, one of the new premium features is support for editing existing messages!
[23:51] <mpt> Yeah, isn't it cool?
[23:51] <seg|ars> indeed