[01:02] <jono> kenvandine, around?
[01:16] <jono> kenvandine, can you ping me when back?
[02:17] <kenvandine> jono, ping
[02:18] <jono> mind coming over to #ubuntu-app-devel for two mins?
[02:19] <kenvandine> sure
[02:22] <kenvandine> jono, jcastro g-p-m with app indicator patch uploaded
[02:23] <jono> kenvandine, nice!
[02:49] <jono> kenvandine, still here?
[02:57] <kenvandine> hey jono
[02:58] <jono> kenvandine, any idea why my indicator applet is not loading, and when I try to type it into a shell to run it doesnt autocomplete
[02:58] <jono> indicator-applet: command not found
[02:58] <jono> it is installed
[02:58] <kenvandine> it is in /usr/lib
[02:58] <jono> I did install indicator-sound and it kept trying restart the i-a so I uninstalled it
[02:59] <kenvandine> /usr/lib/indicator-applet/indicator-applet
[02:59] <jono> when I run that or restart my session it doesnt show
[03:00] <kenvandine> you don't have a "reload applet" dialog hidden somewhere?
[03:00] <jono> nope
[03:00] <jono> it just didnt start it
[03:01] <kenvandine> not sure... lets debug tomorrow or harass ted :)
[03:01]  * kenvandine wants to land some of these docs :)
[03:01] <kenvandine> sorry
[03:01] <jono> no worries, I am away tomorrow, but I will play with it
[03:09] <kenvandine> cool
[03:46] <Nafai> I found another application I Might want to convert to application indicators...but it's not even in Ubuntu yet: http://kaizer.se/wiki/kupfer/
[14:34] <funkyHat> I'm not sure if this is quite the right place to discuss this, but I had a thought re. the shutdown 60 countdown. It seems to me as though it would make sense to display a list of any applications that are inhibiting shutdown alongside the countdown, rather than waiting until the end. I think this would reduce the likelihood of someone cliking shutdown and coming back some time later to find the computer is still running
[14:35] <funkyHat> Sorry if this has been discussed already, I do follow the mailing list and hadn't noticed it come up before
[14:53] <vish> funkyHat: m_p_t would be the person to poke regarding this ^
[14:54]  * funkyHat goes ahead and pokes mpt
[14:54] <mpt> ooh
[14:54] <mpt> funkyHat, actually I'm just about to re-spec them without the countdown at all
[14:55] <funkyHat> Ah, ok
[14:56] <funkyHat> Is there still some kind of confirmation?
[14:56] <funkyHat> *will there still be
[14:58] <mpt> funkyHat, yes
[14:59] <funkyHat> mpt: would be nice if that was combined with the inhibiting apps list, I guess you've considered that ⡈)
[15:00] <mpt> funkyHat, I think the list of inhibiting apps shouldn't appear until after those applications have been given a chance to sort themselves out
[15:03] <mpt> funkyHat, currently I get the alert saying "A program is still running: gedit" *on top of* the Gedit alert saying "Save changes to document 'Untitled 1' before closing?" That's a bit bong.
[15:04] <funkyHat> mpt: do we need another inhibit state that says "I'm asking for user input *right now*" so those apps can be kept off the list?
[15:05] <mpt> funkyHat, I don't know the mechanics of the API. Probably it needs someone like me or djsiegel to write up a spec for how the interface should work, and then someone like tedg to work out how that maps to what Gnome/XDG already has, and whether it needs anything new.
[15:06] <hyperair> aren't you supposed to see the existing interface before proposing a brand new one?
[15:06] <mpt> Sorry, by "interface" there I meant the human interface. I just saw it.
[15:06] <hyperair> ah i see
[15:09] <funkyHat> mpt: sounds good. I think it could be neater if the confirmation and inhibit windows were combined. perhaps we could have a morphing dialog which expanded to include the list of non-responsive apps after some delay/they didn't respond
[15:13] <mpt> funkyHat, maybe, but what would it look like during the delay?
[15:13] <mpt> it's an intriguing idea
[15:16] <funkyHat> mpt: you've got me there... I was thinking it would be the initial confirmation dialog with "shut down" and "cancel" buttons (or similar), morphing into a window listing inhibiting apps, still with "shut down" and "cancel" but perhaps with "cancel" focussed. But I've basically turned it back into a countdown window, just without a visible countdown...
[15:16] <funkyHat> Oh wait no I haven't
[15:17] <funkyHat> ⢁)
[15:19]  * hyperair shivers. that smiley is scary
[16:03] <Nafai> Good morning, a little late start this morning, sorry.
[16:03] <seb128> hey Nafai
[16:03] <seb128> how are you?
[16:03] <Nafai> Not bad, just fighting some allergies this morning.  Other than that, well.   Ready to tackle code today :)
[16:03] <Nafai> You?
[16:04] <seb128> good thanks
[16:04] <seb128> Nafai, did you have a chance to look at updating the rhythmbox change to git?
[16:04] <seb128> I'm sorted of blocking on that to update rhythmbox in lucid
[16:04] <seb128> and feature freeze is today for new versions
[16:04] <Nafai> I haven't yet, been busy with my other assignments, sorry. :(
[16:04] <seb128> that's ok
[16:05] <seb128> let me talk to jcastro or jono when they will be around to see if that can be bumped on your todolist
[16:09] <Nafai> thanks
[16:47] <djsiegel> DanRabbit: hey
[16:47] <djsiegel> DanRabbit: did you see my suggestion about status icons?
[16:47] <djsiegel> DanRabbit: who did those btw?
[17:09] <seb128> hey jcastro
[17:10] <jcastro> hi
[17:10] <jcastro> bah no wonder I wasn't getting any responses
[17:10] <seb128> weird irc split
[17:11] <seb128> usually you don't see people on the other side of the split
[17:11] <seb128> well we didn't see you there
[17:11] <jcastro> I saw you, odd
[17:11] <jcastro> anyway, what can I do for you?
[17:11] <seb128> yeah, pitti had the same issues hours ago
[17:12] <jcastro> Nafai, anything blocking today I can help with
[17:12] <seb128> jcastro, can you get "updated rhythmbox change to git version" priority bumped for Nafai?
[17:12] <seb128> jcastro, it's blocking me to update rhythmbox in lucid
[17:12] <seb128> I would like to get a new snapshot in before feature freeze
[17:12] <seb128> upstream is going to roll a new tarball this weekend
[17:13] <jcastro> he's trying to finish off gnome-bluetooth, brasero, AND vino since then.
[17:13] <jcastro> er, before feature freeze
[17:13] <seb128> hum ok
[17:13] <seb128> I'm pondering just dropping the indicator from rhythmbox for now
[17:13] <seb128> jcastro, thanks
[17:14] <jcastro> the rb patch was originally cody's but he has no time to update it
[17:14] <seb128> right
[17:14] <jcastro> jpetersen has finished main mostly and is moving on to the opportunity targets, perhaps he can update it
[17:14] <seb128> and the patch is not trivial
[17:15] <jcastro> davidbarth, I suppose bratche's workload is pretty much filled for this week?
[17:16] <jcastro> seb128, I would prefer getting upstream the testing they need over app-indicators and have us revisit it after FF.
[17:16] <seb128> jcastro, well I need to get rhythmbox updated in lucid
[17:17] <seb128> and I don't have a day to spend on updating that change
[17:17] <jcastro> I'm pondering just dropping the indicator from rhythmbox for now <-- I agree
[17:17] <seb128> ok thanks
[17:18] <jcastro> jono is on vacation for the rest of the week, so depending on what Nafai's workload is when he's around I will reprioritize one of them
[17:20] <seb128> yeah, no problem
[17:20] <seb128> thanks jcastro
[17:21] <seb128> feature freeze is a busy time for everybody ;-)
[17:21] <jcastro> I just hope we can get the bugs worked out for bluetooth and co.
[17:22] <jcastro> tedg, can you make yourself available when Nafai starts so we can unblock his bugs?
[17:22] <tedg> jcastro: No, not really.  FF effectively today.
[17:23] <jcastro> we can't fix bugs after FF?
[17:23] <jcastro> :p
[17:25] <tedg> jcastro: Heh, no apparently the goal is to ignore bugs before FF as they take away from features you can't develop after.
[17:26] <jcastro> don't worry ted, I have faith that you will fix his problems with elegance and good character
[17:41] <jcastro> jpetersen, I've just sent you guys a mail
[17:44] <vish> djsiegel: that was me [icons]
[17:44] <djsiegel> vish: ok
[17:44] <djsiegel> vish: I just had some suggestions about shape
[17:44] <djsiegel> also, now that you;re using color, there's not need for superimposed shapes
[17:44] <djsiegel> the arrow is extremely busy in the empathy buddy lisr
[17:44] <djsiegel> list*
[17:45] <djsiegel> *away icon arrow
[17:45] <vish> djsiegel:  the color icons are for use in the app , the memenu need to be fixed to use the monochrome icons.. 
[17:45] <vish> djsiegel: the fallbacks aernt in place yet..
[17:46] <jpetersen> jcastro, The bug caused by g-p-m seems to be in indicator-application or indicator-applet
[17:46] <jcastro> ah
[17:46] <jcastro> jpetersen, is there a bug?
[17:46] <jcastro> bug filed I mean
[17:47] <jpetersen> https://bugs.launchpad.net/bugs/523041
[17:47] <ubot4> Launchpad bug 523041 in gnome-power-manager (Ubuntu Lucid) (and 1 other project) "gnome-power-manager crashed with signal 5 in dbus_g_connection_register_g_object() (affects: 26) (dups: 2)" [Critical,Fix released]
[17:47] <jcastro> tedg, can you take a look?
[17:47] <vish> Nafai: hi.. was the rhythmbox app indicator work done by you?
[17:47] <jpetersen> I get the same with gnome-settings-daemon when it is started too early in the session
[17:49] <jpetersen> so maybe it is raised when indicator-applet is not running yet or so
[17:49] <jcastro> vish, the original patch was by bratsche
[17:50] <vish> jcastro: the icons have been switched.. :(   the app now starts[not-playing] with a playing icon instead of the not-playing icon
[17:50] <tedg> jcastro: jpetersen: That's going to take some investigation.  But I'd be suspect of the (GList *)0x1 in the parameters to register_object.  But that shouldn't be an application issue.
[17:51] <vish> jcastro: but after that the icons work correctly , its only during start , it has changed.. [with notification area , it used to use the not-playing icon]
[17:51] <jcastro> vish, seb is going to upload a git snapshot of rb without the app indicator patch until we update it
[17:52] <vish> cool
[17:53] <jcastro> tedg, can you investigate? We need to get jpetersen unblocked
[17:53] <seb128> vish, did you upgrade today? I fixed that icon issue this morning I think
[17:53] <tedg> jcastro: Not really.  Sorry.
[17:53] <jcastro> tedg, when will you have time?
[17:54] <tedg> jcastro: Probably tomorrow afternoon after releases are out.
[17:54] <jcastro> ok, I will hold you to that
[17:55] <vish> seb128: oh.. seems i have missed that update.. nice there already was a bug for that :)
[17:55] <jcastro> jpetersen, so until he can look at that then update the rb patch please.
[17:56] <seb128> \o/
[17:59] <Nafai> I'm back
[18:03] <jcastro> Nafai, I've just sent you all a mail
[18:03] <Nafai> checking
[18:04] <Nafai> jcastro, Ok, sounds good.  I'll be able to make progress today without major help (at least as I see it right now)
[18:04] <jcastro> \o/
[18:04] <jcastro> ping early and often if you have any problems
[18:06] <Nafai> definitely
[18:07] <Nafai> So my guess is ted and others are too busy with their own FF stuff to help me with my gnome bluetooth bugs today at least
[18:07] <seb128> yes
[18:07] <seb128> don't expect anybody from distro to have time before friday
[18:08] <seb128> distro or dx
[18:08]  * Nafai nods
[18:08] <Nafai> I hope it isn't too much of a problem that I didn't meet FF for some of these
[18:09] <jcastro> if people got in trouble for not meeting FF we'd all be homeless.
[18:10] <jcastro> Nafai, let's just keep grinding at it, everyone is in the same boat so at least it's shared pain. :D
[18:10] <Nafai> :)
[18:10] <vish> seb128: awesome , its fixed by the update  :)
[18:10] <Nafai> yay for comiseration (is that a word?)
[18:11] <seb128> vish, good
[18:11] <vish> hehe , i was more worried i'd get bugs in humanity for doing the icon like that ;p
[18:12] <jcastro> jpetersen, if you can get me a best-guess estimate of how much work it would take to update the rb patch that would be great.
[18:12] <jcastro> jpetersen, here's the bug btw: https://bugs.edge.launchpad.net/ubuntu/+source/rhythmbox/+bug/498588
[18:12] <ubot4> Launchpad bug 498588 in rhythmbox (Ubuntu) "Rhythmbox's "Status Icon" plug-in is broken. (affects: 3)" [Medium,Fix released]
[18:16] <Nafai> jcastro: w00 for being appointed to replace lucasr on the Gnome board! :) http://blogs.gnome.org/lucasr/2010/02/17/resigning-from-the-board/
[18:18] <qense> jcastro: !!! Yay! Congratulations on your appointment! I didn't you were selected.
[18:18] <Nafai> qense, well, lucasr appointed him :)
[18:19] <qense> *I didn't know
[18:20] <seb128> Nafai, not really, he was rather next on the previous election list
[18:20] <Nafai> oh
[18:20] <Nafai> cool
[18:20] <Nafai> either way, it's awesome if he does join
[18:22] <jcastro> thanks guys!
[18:25] <jcastro> qense, I've left some comments on your banshee patch bug
[18:26] <qense> jcastro: I say them, I'm now working on the crash.
[18:26] <qense> jcastro: Did your installation also crashes everytime you pressed Play, Next or Previous in the tray menu?
[18:27] <jcastro> nope
[18:27] <qense> aww
[18:27] <jcastro> just the one time actually, I've been using it since then 
[18:27] <qense> great
[18:27] <qense> jcastro: that's really weird
[18:28] <qense> jcastro: so no crash notices after the first?
[18:28] <jcastro> yeah, if I turn notifications back on
[18:28] <qense> ok
[18:30] <jcastro> qense, IMO there shouldn't even be a checkbox for notifications there, it should just do it like rhythmbox does
[18:30] <qense> jcastro: which is?
[18:30] <jcastro> upstream currently has this custom odd popup thing 
[18:31] <jcastro> qense, it should just fire off a notify-osd thing 
[18:32] <qense> jcastro: I thought that it was already using Notify OSD on Ubuntu. Or am I wrong?
[18:32] <jcastro> yeah but that seems to be currently broken
[18:32] <qense> ah
[18:43] <Nafai> Question.  In Vino, there are several calls like this: screen = gtk_status_icon_get_screen (GTK_STATUS_ICON (indicator)); where screen is a GdkScreen object.  Is there something similar and appropriate I can do for app indicators?
[18:43] <Nafai> This looks to be an important call
[18:45] <qense> jcastro: the "show notifications" toggle does appear to be the toggle for using Notify OSD or showing nothing with the default Banshee from the repositories.
[18:48] <C10uD> hi
[18:49] <C10uD> [19:45] <C10uD> i wanted to add appindicator support to my app, i've seen the examples and it's real easy, thanks for the flawless job
[18:49] <C10uD> [19:45] <C10uD> however i have two issues i currently can't sort out:
[18:49] <C10uD> [19:46] <C10uD> i don't know how to/if i can set "my" icons (as gtk pixbufs or paths)
[18:49] <C10uD> [19:46] <C10uD> i don't know how to/if i can "hotplug" items in my indicator's gtk menu
[18:49] <C10uD> tia
[18:49] <Nafai> C10uD: On the icons issue, app indicators load things from the icon path.
[18:49] <Nafai> Do you have a standard place your app installs icons?
[18:49] <Nafai> If so, the easiest thing to do is to replace your call of app_indicator_new with app_indicator_path
[18:50] <Nafai> Here's the prototype:
[18:50] <Nafai> AppIndicator                   *app_indicator_new_with_path      (const gchar          *id,
[18:50] <Nafai>                                                                   const gchar          *icon_name,
[18:50] <Nafai>                                                                   AppIndicatorCategory  category,
[18:50] <Nafai>                                                                   const gchar          *icon_path);
[18:50] <C10uD> is that available in the python bindings?
[18:50] <Nafai> So that last parameter is the path where your icons may be
[18:50] <Nafai> and then you just refer to the icon name, i.e., the part of the name without the extension
[18:51] <Nafai> Let me double check, I've mostly been using the C api
[18:51] <C10uD> ok
[18:53] <Nafai> hrm, I'm not sure, let me try something
[18:55] <Nafai> I don't know, since I haven't used them, and it's not obvious to me looking at the classes in the interpreter
[18:55] <C10uD> np
[18:55] <Nafai> kenvandine: I think you are familiar with the Python bindings, could you give a little guidance?
[18:58] <qense> C10uD: If I'm correct there is no Python equivalent for that function, but let me have a look.
[18:58] <C10uD> ok, what about the other "issue"?
[18:58] <Nafai> So you may have to manually add your icon directory to the path
[18:58] <Nafai> So you want to update your menu after you have set it?
[18:59] <C10uD> yep, it's an im, i add some stuff after login, and i allow plugin to plug their own stuff
[18:59] <qense> C10uD: nope, no _with_path in Python.
[18:59] <C10uD> qense, ok thanks
[18:59] <Nafai> I've actually run into a bug with that one in the C API and I know they are going to look at it
[18:59] <qense> Nafai: that doesn't work when passing the icon to the indicator.
[18:59] <Nafai> qense, Oh, it doesn't?
[18:59] <qense> nope
[18:59] <qense> The applet looks the icon up using the name you gave it.
[18:59] <Nafai> I notice, however, when looking at the docstring for the class in Python, there is this property:
[19:00] <Nafai>   icon-theme-path -> gchararray: An additional path for custom icons.
[19:00] <Nafai>     An additional place to look for icon names that may be installed by the application.
[19:00] <qense> ah, where did you find that?
[19:00] <Nafai> Right, but don't you add the icon directory to your theme path and then pass the name?
[19:00] <Nafai>  print appindicator.Indicator.__doc__
[19:00] <qense> Nafai: that is what *app_indicator_new_with_path does, yes.
[19:01] <qense> C10uD: you could have a look at the "icon-theme-path" property of the appindicator object for the custom directory.
[19:01] <C10uD> wow, thanks for the finding, i'll make some tests
[19:02] <qense> thank you Nafai! I didn't know that one. ;)
[19:02] <Nafai> np :)
[19:02] <qense> Nafai: but you can't do things like appindicator.menu.add()?
[19:02] <C10uD> is the menu thing a known issue? 
[19:02] <qense> C10uD: you could assign a new menu to the indicator iirc
[19:02] <C10uD> because currently, we're adding stuff to the gtk.menu directly
[19:03] <C10uD> you mean, readding the menu each time it gets modified
[19:03] <Nafai> C10uD, That is a known issue, I believe, as it is related to the behavior I'm seeing
[19:03] <jpetersen> jcastro, i will look at the rhythmbox patch right now
[19:03] <jcastro> thanks!
[19:03] <jcastro> C10uD, what app are you working on btw?
[19:03] <C10uD> emesene, the crappy im for your wlm needs :p
[19:05] <Nafai> qense: You wouldn't happen to know about the GdkScreen question I posted above, would you?
[19:05] <jcastro> C10uD, oh that's cool dude.
[19:06] <qense> Nafai: I guess it's just looking for the screen the systray is on. Aren't there other ways of getting to know that? I don't know one by heart though.
[19:06] <Nafai> Yeah, that's what I'm unsure of
[19:07] <C10uD> anyway thanks for the quick answers, i'll try your hints asap
[19:07] <qense> I can't help you with that unfortunately.
[19:07] <Nafai> np C10uD
[19:11] <jpetersen> jcastro, and gnome-settings-daemon is done as far as possible with current application-indicator (i added some bugs with required features for further polishing: https://bugs.edge.launchpad.net/ubuntu/+source/indicator-application)
[19:12] <jcastro> jpetersen, ok we'll have Ted check them out tomorrow as soon as he can
[20:22] <jcastro> C10uD, have you also looked at adding message-indicator support to emesene? It's the thing that keeps track of who has IMed you while you're away, etc.
[20:30] <Nafai> question
[20:30] <Nafai> I need help in figuring out how to test vino
[20:30] <Nafai> there is an auto-start option in the desktop file
[20:30] <Nafai> which then gets called when the box to turn on remote desktop is checked in the capplet
[20:30] <Nafai> is there a way to register this desktop file in my local directory?
[20:30] <qense> jcastro: I've stumbled across the bug you've reported. I think it is caused by the patch in GNOME Bugzilla #145278 
[20:31] <Nafai> or should I just try building the .deb and installing a deb of my changes?
[20:34] <jcastro> qense, yeah but that's a totem bug. Wouldn't it be a gstreamer problem?
[20:34] <qense> totem?
[20:35] <qense> jcastro: ah!
[20:35] <qense> pasted the wrong number
[20:35] <qense> meant GNOME Bugzilla #565453
[20:36] <qense> the patch attached to that bug report isn't included in Ubuntu yet iirc
[20:36] <jcastro> qense, feel free to join us in #banshee, the guys are usually around
[20:36] <jcastro> qense, yeah, and I was pulling from git head
[20:37] <seb128> Nafai, I don't understand your issue
[20:39] <Nafai> I figured out a solution
[20:39] <seb128> just running the binary should work
[20:40] <seb128> the server that is
[20:42] <Nafai> that didn't enable the icon
[20:43] <Nafai> but if I run it first and then go to preferences that works :)
[20:43] <seb128> you need to change the preference to display it alltime
[20:45] <C10uD> jcastro, yes, but current codebase is so fucked up i'm not willing to add stuff, we'll see next versions :) i'm just trying to add appindicator in order to have a cleaner desktop, i hope in time for lucid
[20:45] <jcastro> heh
[20:45] <C10uD> btw guys i tried setting icon-theme-path and it's saying i must pass it to the constructor
[20:46] <C10uD> but, seeing the package i installed, it accepts only three args 
[20:46] <C10uD> id, icon_name, app_type
[20:46] <C10uD> :(
[20:49] <Nafai> sounds like a problem with the Python bindings
[20:49] <Nafai> jcastro, Who's responsible for those?
[20:49]  * jcastro goes to see who touched it last
[20:52] <jcastro> Nafai, either ted or ken
[20:52] <Nafai> that's what I thought
[20:53] <jcastro> Nafai, "whichever two are the busiest today" seems to be the answer to everything today, heh
[20:53] <Nafai> heh
[20:53] <Nafai> :)
[20:55] <C10uD> kenvandine, sorry if i ping you, can you take a look? ^ i'm using your ppa
[21:54] <kenvandine> C10uD, weird...  has anytone looked at jockey to see if it is working?
[23:12] <GogglesGuy> notify-osd 0.9.25 doesn't seem to update the text of a notification when sending a new notification with an existing replace-id...