[12:59] <htorque> hello, to which process would i attach gdb to get a backtrace of a unity crash? is it mutter?
[13:09] <didrocks> htorque: right, mutter
[13:09] <htorque> didrocks, thanks :)
[13:09] <didrocks> yw :-)
[14:28] <kermiac> hi tedg or seb128 the indicator-applet hook (bug 583174) is ready for packaging in maverick. Do you want me to package it? Is https://code.edge.launchpad.net/~ubuntu-desktop/indicator-applet/ubuntu the the correct branch to use for packaging the hook in Maverick?
[14:30] <tedg> kermiac, Yeah, that'd be great!  That's the correct branch.
[14:30] <tedg> seb128, That'd be for Maverick, right?
[14:30] <seb128> yes
[14:30] <tedg> seb128, Do we need an SRU to add apport hooks or could we add it to the Lucid package as well?
[14:31] <seb128> we need a SRU since we need an update
[14:31] <seb128> I'm for batching it with other changes
[14:31] <seb128> ie next time we do changes to the lucid source
[14:31] <seb128> let's get it in maverick to start
[14:32] <tedg> Cool, okay.
[14:32] <kermiac> ok, thanks tedg, I'll replace the branch attached to my bug report & poke you over the next couple of days after I've packaged it
[14:32] <tedg> But should we ask kermiac to branch it from the last Lucid version then?
[14:32] <tedg> That way it'd merge cleanly.
[14:33] <seb128> well let's get it in maverick to start
[14:33] <seb128> I can deal with the backporting later
[14:33] <kermiac> ok, thanks tedg & seb128 :)
[14:33] <seb128> kermiac, thank you for doing the work
[14:34] <kermiac> np seb128, glad to help
[14:57] <qense> tedg: Are you on the new ayatana-dev mailing list already? :)
[14:57] <tedg> qense, Oh, I didn't realize there was one.
[14:57] <qense> it was just created yesterday or this morning
[14:57] <tedg> Heh.  I just woke up! :)
[14:58] <qense> It is meant for the implementation side of the Ayatana project.
[14:58] <qense> tedg: Good morning to you, then!
[14:58] <tedg> Eh, so the designers are kicking us out because of the CSD thread on their mailing list ;)
[15:00] <qense> tedg: No, it was more initiated by suggestions posted by me and then the thing got its own life.
[15:00] <qense> tedg: To be honest: I didn't say mailing list: I said 'place'. Mark S. turned that into a mailing list.
[15:01] <tedg> qense, Ah, okay.  Seems like too many mailing lists, we'll see.  Perhaps some good will come out of it.
[15:01] <qense> Lets hope for something good!
[15:01] <tedg> I should really do release announcements if nothing else.
[15:02] <seb128> tedg, qense: did you investigate the bluetooth indicator update bug?
[15:02]  * qense looks at tedg
[15:02] <tedg> seb128, I updated indicator-application but got my package rejected... I need to figure out why this morning :(
[15:03] <seb128> tedg, updated where?
[15:03] <seb128> tedg, can you give me the debdiff? I can test easily
[15:04] <tedg> seb128, I pushed it to my bugfix PPA
[15:04] <tedg> seb128, Let me find the link.
[15:05] <tedg> seb128, Uhg, it totally rejected it.  Didn't even make it to LP :(
[15:06] <tedg> seb128, Just a sec.
[15:09] <tedg> seb128, http://people.canonical.com/~ted/watch.diff
[15:10] <seb128> tedg, I like it
[15:10] <seb128> tedg, let me try that here
[15:10] <qense> tedg: Why could this be rejected? The patch looks good to me.
[15:10] <tedg> qense, I think that I forgot to attach the source.
[15:11] <qense> ah1
[15:11] <qense> !
[15:15] <tedg> qense, It's one of the problems (IMHO) with bzr build-deb -- you have to adding the -sa is hard.  "bzr bd -S -- -sa"
[15:15] <qense> tedg: Bug report!
[15:28] <tedg> bratsche, Can you review this?  I think getting it in will help you test registration.  https://code.edge.launchpad.net/indicator-appmenu/+activereviews
[15:29] <tedg> Eh, wrong URL, but close enough :)
[15:30] <bratsche> Sure.
[15:35] <bratsche> ted: What is the priv->props DBusGProxy for?
[15:39] <tedg> bratsche, Basically to track when the process or the object dies.  dbusmenuclient hides it, so I had to build a new one.
[15:39] <tedg> bratsche, dbusmenuclient will actually reconnect if it comes back.
[15:39] <bratsche> Okay cool.
[15:43] <jcastro> wait, there's a new mailing list?
[15:44] <qense> jcastro: yes indeed!
[15:44] <qense> jcastro: https://launchpad.net/~ayatana-dev
[15:44] <jcastro> oh cool, I can put my status reports here then I guess.
[15:44] <qense> jcastro: That would be a nice way to make the mailing list worth subscribing to.
[15:45] <jcastro> seems like the mailing list is becoming too noisy anyway
[15:46] <qense> yeah, we need to divert some of the technical talk to a separate mailing list, or move technical talk to it when that is still done either in private or not at all
[17:57] <seif_> hey tedg 
[17:57] <tedg> seif_, What do you mean by custom?
[17:57] <tedg> seif_, You want to make an app indicator?
[17:57] <seif_> with a search ba
[17:57] <seif_> :)
[17:57] <seif_> with a search bar
[17:57] <tedg> You mean like a text area similar to the Me Menu?
[17:57] <seif_> yes sir
[17:57] <seif_> :)
[17:58] <seif_> is it doable in pyton
[17:58] <tedg> Unfortunately we only have that code in the Me Menu right now.
[17:58] <seif_> or do i need C or vala for that
[17:58] <seif_> CRAP
[17:58] <tedg> It's on my TODO list for maverick to move it out.
[17:58] <seif_> :(
[17:58] <seif_> :(
[17:58] <tedg> But, I need to nail this appmenu stuff first.
[17:58] <tedg> So I can push it up in the stack, but it's probably a week or two away.
[17:59] <LaserJock> didrocks: is it better to ask Unity questions here or #ubuntu-desktop?
[17:59] <tedg> Yeah, Vala and Python would both work.
[17:59] <didrocks> LaserJock: here is good for Unity
[17:59] <seif_> tedg, thanks
[18:00] <LaserJock> I was just wondering if the launcher side panel is supposed to be able to hide
[18:00] <seif_> will rock it
[18:17] <seb128> tedg, qense: so with the indicator-application fix now devices are listed
[18:17] <seb128> it has a bunch of 
[18:17] <seb128> "(bluetooth-applet:2186): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_property_set_value: assertion `DBUSMENU_IS_MENUITEM(mi)' failed
[18:17] <seb128> "
[18:17] <seb128> though
[18:17] <seb128> and some menus are still not listed like the "visible" one
[18:18] <seb128> which is a toggle item