=== bratsche is now known as br-sleep
=== chaotic_ is now known as chaotic
[11:19] <KuriKai> does anyone know if there will be a menu that shows what programs are running in the background? e.g. gnome-do, gloobus...
=== MacSlow is now known as MacSlow|lunch
=== MacSlow|lunch is now known as MacSlow
=== kenvandine_ is now known as kenvandine
=== br-sleep is now known as bratsche
[16:17] <qense> good afternoon
[16:26] <qense> tedg: Could you please have a look at <https://code.launchpad.net/~qense/indicator-application/doc-intro-fixes/+merge/25835>?
[16:26] <qense> It doesn't fix the Mono bindings, but it does fix some other things.
[16:44] <tedg> qense, Yeah, looks good.  I was a bit confused with the status name changes, but now I realize what you did :)
[16:44] <qense> yeah
[16:44] <qense> Now they're using a way that the generators of GObject can find as well.
[16:44] <tedg> qense, About changing the assemblies directory, have you talked to hyperair about that?  I know that he did some work in getting those dirs cleaned up.
[16:44] <qense> tedg: That was the exact change he made afaik.
[16:44] <tedg> qense, Ah, okay.  I see.
[16:49] <qense> tedg: Thanks!
[17:01]  * hyperair wonders what that was about
[17:01] <jcastro> tedg: hey since qense is here
[17:01] <jcastro> can we talk about the fixes to app indicator so we can finish off gnome-bt, etc?
[17:01] <qense> jcastro: that'd be fine with me
[17:02] <qense> hyperair: I changed the Makefile to install in lib/cli rather than just lib
[17:02] <hyperair> ah cool.
[17:02] <qense> that's all for the hyperair-related changes
[17:03] <tedg> jcastro, Cool.  The big one is getting bratsche's GTK+ patch for add/remove signals backported into Lucid.
[17:03] <hyperair> i see.
[17:03] <jcastro> tedg: do we want it in lucid?
[17:03] <jcastro> tedg: it works in lucid, I was thinking forward for maverick
[17:03] <seb128> tedg, jcastro: I've the gtk change ready for lucid
[17:03] <tedg> jcastro, yes.  We need to get gnome-bt in a better state.
[17:03] <seb128> but it doesn't work
[17:04] <tedg> :(
[17:04] <seb128> or it requires gnome-bt changes
[17:04] <qense> Who did gnome-bt?
[17:04] <bratsche> Nafai I think?
[17:05] <qense> How's he doing? I heard he had some health problems?
[17:05] <bratsche> Oh, I didn't know that. :(
[17:05] <qense> Read it on Twitter.
[17:06] <qense> I'll search for the gnome-bt bug report to see if it contains any details.
[17:06] <qense> jcastro: Who'll be doing hplip?
[17:08] <seb128> qense, bug #558841
[17:08] <ubot5> Launchpad bug 558841 in gtk+2.0 (Ubuntu Lucid) "bluetooth "devices" menu item not working in bluetooth indicator (affected: 12, heat: 92)" [Medium,In progress] https://launchpad.net/bugs/558841
[17:08] <jcastro> qense: not sure yet
[17:08] <qense> ah
[17:08] <qense> seb128: thanks. I was looking at bug #497856, but that's not about the issue.
[17:08] <ubot5> Launchpad bug 497856 in GNOME Bluetooth "Support application indicator (affected: 2, heat: 12)" [Unknown,New] https://launchpad.net/bugs/497856
[17:09] <seb128> qense, tedg: you can get gtk with bratsche's change in the ubuntu-desktop ppa if you want
[17:10] <qense> seb128: I'd love to be powerful enough to have access to the ubuntu-desktop, but unfortunately I'm a mere mortal. :)
[17:10] <seb128> it would be useful if somebody could look why gnome-bt still doesn't work
[17:10] <seb128> qense, it's a public ppa?
[17:10]  * qense is reading the bug report right now
[17:10] <seb128> just add it to your sources.list?
[17:10] <qense> seb128: Ah, the other thing you can do with a PPA, of course.
[17:10] <seb128> https://edge.launchpad.net/~ubuntu-desktop/+archive/ppa
[17:12] <seb128> tedg, qense: if somebody can confirm the gtk there works we can get it in lucid updates
[17:12] <qense> bratsche, seb128: What about the issue mentioned in comment 22? Is that related to the bug we're talking about?
[17:12] <qense> seb128: I'll give it a try.
[17:12]  * tedg doesn't have working bluetooth in his new laptop... :(
[17:12] <tedg> It's going to be hard for me to verify it working.
[17:12] <qense> seb128: But doesn't libappindicator needs changes to use the newly created 'add' signal?
[17:12] <qense> bratsche: ^^ ?
[17:13] <qense> seb128: Also, the latest patch is <http://bugzilla-attachments.gnome.org/attachment.cgi?id=162132>, isn't it?
[17:13] <seb128> qense, look to the bugzilla.gnome.org bug, the change has been updated
[17:13] <seb128> right
[17:14] <qense> good :)
[17:14] <seb128> the ppa build has the new one
[17:15] <qense> installing the new GTK+ right now
[17:16] <qense> But I do think that it won't have any effect as long as nothing is listening to the new signals.
[17:17] <seb128> right
[17:17] <seb128> what should listen to it though?
[17:17] <seb128> is that something ted ish?
[17:17] <seb128> tedg, ^
[17:17] <qense> That's definitely something tedish.
[17:18] <seb128> so not gnome-bt?
[17:19] <qense> Well, the bug is about the menu not updating correctly when changes to it have been made, right?
[17:19] <seb128> yes
[17:19] <seb128> I'm not sure it's the software code that should do the update or the indicator
[17:19] <qense> In that case it is an issue in GTK+ for the new signals and in libappindicator for using those signals.
[17:20] <qense> We're listening to several signals from GTK+ to update parts of the menu and we should add this signal to the signals we're checking.
[17:20] <seb128> tedg, ^ can you confirm that's right?
[17:20] <seb128> seems to make sense
[17:20] <seb128> but I want to be sure before pushing gtk
[17:22] <qense> Pushing GTK+ won't make a different just now, iirc. At the moment we can only test if this change doesn't break anything else.
[17:25] <seb128> qense, right, but if that's required to fix libindicator so we need to get it first in lucid so we can start now
[17:25] <qense> yes
[17:25] <qense> But we can't confirm yet if the signal behaves properly.
[17:26] <seb128> indeed
[17:26] <seb128> so let's wait for you or ted to come with the indicator change
[17:27] <seb128> so we can confirm if it's working
[17:27] <seb128> I will get the change in maverick meanwhile so it will help testing
[17:27] <qense> I'm running the new GTK+ right now and now system crashes yet.
[17:28] <qense> I've restarted the indicator-application-service and plugged my Bluetooth adapter in afterwards and I am still able to confirm the bug.
[17:28] <qense> no crashes
[17:28] <seb128> "now"
[17:28] <seb128> or "no"?
[17:28] <qense> no
[17:28] <seb128> ok
[17:29] <seb128> better ;-)
[17:29] <seb128> right, I can confirm the bug is still there
[17:34] <qense> seb128: Shall I open a bug task for the indicator-application source package and the indicator-application project?
[17:35] <seb128> qense, if you are sure it's the right source to connect the signal yes
[17:36] <qense> Will do and then it's dinner time!
[17:36] <seb128> thanks
[17:36] <seb128> enjoy dinner
[17:36] <qense> thanks
=== SCone is now known as ShroudedCloud
=== ShroudedCloud is now known as SC|Away
=== SC|Away is now known as ShroudedCloud
[23:02] <kermiac> hi tedg :) Did you get my email re the indicator-applet apport hook? - bug 583174
[23:02] <ubot5> Launchpad bug 583174 in Indicator Applet "Apport hook for indicator-applet (affected: 1, heat: 6)" [Low,In progress] https://launchpad.net/bugs/583174