[00:13] So, when g_object_unref is called, the finalizer for the object gets called? === chaotic_ is now known as chaotic === chaotic_ is now known as chaotic === chaotic_ is now known as chaotic === chaotic_ is now known as chaotic === chaotic_ is now known as chaotic === chaotic_ is now known as chaotic === chaotic_ is now known as chaotic === chaotic_ is now known as chaotic === chaotic_ is now known as chaotic [07:41] Good Morning [07:44] morning? its 22:44 :-P [09:43] MacSlow, hey... around? [09:49] nigelb, what's up? [09:49] MacSlow, just wanted to talk about the notify-osd and network-manager :) [09:50] nigelb, feature-requests and bug-reports don't work on IRC :) [09:50] nigelb, that's what we have mailing-lists and launchpad for :) [09:51] MacSlow, hehe, well its already on launchpad. I triaged the bug earlier. Just checking with you for details.. :) [09:51] nigelb, or is it about hacking up a integration-patch? [09:52] well, the only thing I wanted to know is, is the bug upstream as of now? i.e. network manager? [09:53] nigelb, bug-upstream for network-manager ... ehm... Dan Williams from RedHat I'd say [09:54] thank you :) [09:54] nigelb, cat /usr/share/doc/network-manager/AUTHORS [09:54] It would be nice to know the facts before I claim so :) [09:54] ah... oh.. [09:55] nigelb, this "cat /usr/share/doc//AUTHORS" works for most pieces of software installed on your system [09:56] thats great to know :) [10:18] [10:21] nigelb: the bug was forwarded upstream , but its not an upstream bug [its ubuntu specific] [10:21] vish, it is an upstream task that first needs to be completed.. if i'm not wrong [10:23] nigelb: upstream in nm ? noo.. as i mentioned in the bug , the way it has to be handled hasnt yet been decided... mpt might be the first person you need to consult [10:24] vish, anyway. All I wanted was a decent enough text to put in future bug reports ;) === DrPepperKid is now known as DrPepperKid|lunc === DrPepperKid|lunc is now known as DrPepperKid [13:47] Good morning [13:49] Good morning Nafai [13:49] Hello, how are things going? [13:52] good here [14:00] brb, rebooting [14:08] back [14:34] hey Nafai [14:34] Hey seb128 [14:34] how are you? [14:34] Doing well, and you? [14:34] I'm good thanks [14:35] do you run lucid? or trunk built for all the indicator stack? [14:36] I'm on lucid [14:38] Nafai, and you get the indicator icon changing? [14:39] Yeah [14:39] I just did an update this morning and rebooted. I'm recompiling and testing again to make sure it isn't broken again [14:40] ok, works now in fact [14:41] I probably didn't restart some service yesterday ;-) [14:41] ah. awesome ;) [14:56] jpetersen, I will create the upstream GNOME bug now, and then you can attach the patch right after [14:56] cool, another patch going upstream! [14:58] jcastro, ok i will do [14:59] jcastro, hey [15:00] Nafai, jcastro: g-c-c uploaded now [15:00] awesome! [15:00] my first code in the distro! [15:00] ;-) [15:01] \o/ [15:02] Nafai, seb128, I've also pinged Rodrigo to weigh on g-c-c [15:04] jpetersen, https://bugzilla.gnome.org/show_bug.cgi?id=609654 [15:04] Gnome bug 609654 in applets "Support for application-indicators/StatusNotifierIcon" [Enhancement,Unconfirmed] [15:04] paste away! [15:04] jpetersen, Nafai, smithj: I've also edited the workflow page to add the step of adding a "patch" tag in launchpad when you attach the patch. [15:05] jcastro, ok [15:06] saw it :) [15:07] woo hoo, 3 sent so far! [15:17] jcastro, patch attached [15:17] so I am off for today :) bye bye [15:18] thanks! [15:18] just got your report, woo! [15:47] Morning jono [16:20] So how compatible are the two specs (kde status icon vs the gnome one). It seems the "menu" property is a requirement for gnome, but what about kde? [16:30] If Google gets a complete API out in time, is there a chance that Google Buzz support might be added to the MeMenu for Lucid? [16:43] Buzz isn't exactly mic [16:43] roblogging, but it is a "broadcast account". [16:44] And so would seem within the scope of the MeMenu. [16:58] Is there a online version of the dbusmenu spec? [17:29] GogglesGuy: We've added menu support into KDE as a patch, but I don't think it's in the spec yet. [17:29] GogglesGuy: http://people.canonical.com/~agateau/dbusmenu/spec/ [17:30] GogglesGuy: I'd recommend not implementing it though :) If you've got glib, you can use libdbusmenu-glib which has no GTK deps. [17:31] tedg: are you expecting the spec to change then? [17:31] GogglesGuy: I don't expect it to change that much, but it's not a simple one to implement. [17:32] GogglesGuy: And I'd always recommend using tested code :) [17:32] tedg: perhaps the spec is too complicated then if it's not a simple one to implement. [17:33] GogglesGuy: heh, well, if you can recommend things to drop, I'm all for it. But, the fact of the matter is that menus are complicated :( [17:33] It's not a lot of code, but it gets abused through everything menus do. [17:35] tedg: Not suggesting that :) I only need a very basic menu [17:36] GogglesGuy: If you look at any of the indicators (indicator-session is a good one) they create simple menus with dbusmenu-glib [17:37] Would I need a glib mainloop if I use dbusmenu-glib? [17:38] GogglesGuy: Yeah, you would. [17:38] You really need a mainloop to use dbus. [17:38] tedg: unfortunately, that would be a no go. [17:38] hey what does gnome-media indicator mean? i mean what will it show. [17:38] currently gnome-media does not have any notification icon right? [17:39] tgpraveen12: I believe that entry was talking about the mixer applet. [17:39] GogglesGuy: What mainloop are you using? [17:40] tedg: mixer applet? u mean sound volume control? [17:40] I use FOX (www.fox-toolkit.org), and integrated dbus into the FOX event handling system [17:40] (it's somewhat primitive, but it works for me) :) [17:44] Just got some good feedback from rodrigo [17:45] GogglesGuy: Wow, hadn't heard of that one. So yeah, you'll have to implement a dbusmenu-glib like thing. You could steal the testsuite from dbusmenu, that'd probably help. [17:45] tgpraveen12: I'm not sure. [17:46] tedg: That's why I like dbus. It makes it really easy to communicate between two totally different applications :) [18:50] Nafai, btw, expect #519625: to be fixed today by bratsche, who clearly rocks the house [18:50] jono: Awesome! I saw that he changed it to in-progress. :) [18:50] :) [19:19] Nafai: I actually changed it to In Progress only so it's easier to track. When I'm on my LP homepage there's a box that shows all the stuff that I have in progress. I wish there were such a box for everything that's assigned to me, that would make things easier. [19:19] But I'll do it today. [19:21] Ok :) [19:21] thanks and let me know if there is anything I can do to help out [19:29] lunch time! [20:02] Does the indicator-application service do any logging? It seems to crash whenever I specify a menu... [20:21] GogglesGuy: Look in ~/.cache/indicator-applet.log [20:28] Nafai: found that one... nothing usefull though... [20:29] sorry, that's all I know about it right now :) [21:57] bratsche, kenvandine: I know today is probably hugely busy for y'all, but if you might have a chance to take a look at the e-mail I sent with questions on how to approach brasero/vino best, especially for upstream, I'd appreciate it [22:05] Nafai, in the morning... sorry [22:05] busy :/ [22:05] I understand :) [22:06] unless someone else can help :) [22:06] Oh, another thing. :) [22:06] For someone. I noticed that the wonderful packages seb128 made didn't have the dependencies updated (neither build-dep or Dependencies) and so appindicator support didn't get compiled in [22:07] urg [22:07] Nafai, fixing that now [22:07] somewhat I took that as a sponsoring request [22:08] applied the patch and uploaded ;-) [22:08] no, that's okay [22:08] I realized I wasn't clear [22:08] Ken was going to fully update the packaging for me [22:08] If I'm working on things that have packaging branches, i can also provide those in the future for sponsoring purposes if ken gets busy [22:17] So regarding the application status. I've got a media player that used have the following functionality: left mouse click => toggle visibility of main window. right mouse click => show context menu. Is that still possible with the ApplicationIndicators? If not, what would be the suggested behaviour? [22:18] GogglesGuy, Probably add the toggle visibility as a menu item [22:18] application indicators are designed to be uniform, so they offer only a standard menu you get from left-click [22:19] Have you seen this? https://wiki.ubuntu.com/CustomStatusMenuDesignGuidelines [22:22] Yes, I quickly glanced through it. Is KDE going to follow the same standard? [22:24] My hunch is yes, but I'm not the one to answer that [22:30] To me it looks like all the usefull functionality was stripped from KDE Application Indicators spec.... [22:31] I don't know anything about the KDE spec. [22:31] tedg or mpt or jono might be ones to bug about it [22:41] Nafai, those packaging details are things I do all week, I was just doing several things at the same time and didn't stop to think about this one ;-) [22:42] heh, that's okay. :) [22:43] I guess I'm confused now. The actual proposed spec (http://www.notmart.org/misc/statusnotifieritem/) is somewhat different than what https://wiki.ubuntu.com/CustomStatusMenuDesignGuidelines describes.. [22:44] or what is being implemented in the application-indicator service.