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