=== funkyHat is now known as funkyGit
=== funkyGit is now known as funkyHat
[08:24] <jpetersen> Good morning
[08:26] <seb128> hello there
[08:26] <seb128> hey jpetersen
[08:26] <jpetersen> hey seb128
[11:11] <seb128> jpetersen, do you know what the status is about icons being displayed in the indicator for stock items without respecting show_icon?
[11:11] <seb128> jpetersen, is that a known bug? being worked?
[11:11] <seb128> jpetersen, ie the exit one in rhythmbox or the gnome-bluetooth ones
[11:15] <jpetersen> seb128, I think we should respect the GtkImageMenuItem::"always-show-image" property so we do not have to fix all applications
[11:15] <seb128> jpetersen, right, me too
[11:15] <seb128> jpetersen, do you think it's something you could fix?
[11:16] <jpetersen> seb128, yes I can do it
[11:16] <seb128> jpetersen, excellent, please add it to your todolist then ;-)
[11:16] <seb128> thanks!
[11:16] <jpetersen> seb128, ok :)
[11:25] <seb128> jpetersen, do you know what source needs to be changed for that? just to have a bug tracking that issue
[11:25] <jpetersen> seb128, indicator-application
[11:29] <seb128> jpetersen, how is tasklist looking right now?
[11:29] <seb128> jpetersen, I'm checking to see if I can reasonably put some extra bugs on your plates or not ;-)
[11:30] <jpetersen> i am now working on "always-show-image" support and the "leave messages" dialog for gnome-screensaver
[11:31] <jpetersen> there are no other bugs currently assigned
[11:34] <seb128> jpetersen, ok, I'm adding bug #530138 to your list then ;-)
[11:34] <ubot4> Launchpad bug 530138 in indicator-application (Ubuntu Lucid) (and 2 other projects) "Using .append() on a gtkmenu doesn't update the indicator's menu (affects: 1)" [High,Triaged] https://launchpad.net/bugs/530138
[11:36] <jpetersen> seb128, ok
[11:36] <seb128> jpetersen, please consider the gnome-screensaver bug has lower priority than the fixes though
[11:36] <jpetersen> seb128, yes of course :)
[11:36] <seb128> jpetersen, ie default back on that if you have free time and no other bug waiting
[11:36] <seb128> jpetersen, thanks a lot!
[11:37] <seb128> jpetersen, btw you do great work, that's really appreciate ;-)
[11:37] <seb128> jpetersen, lucid will rock ;-)
[11:37] <jpetersen> thanks :)
=== MacSlow is now known as MacSlow|lunch
=== MacSlow|lunch is now known as MacSlow
[14:14] <Nafai> Good morning
[14:15] <seb128> hey Nafai
[14:15] <seb128> how are you?
[14:15] <Nafai> Doing well, and you?
[14:16] <seb128> Nafai, I'm good thanks, almost weekend!
[14:16] <Nafai> Indeed.  Yay.
[14:16] <seb128> Nafai, did you have any luck on this gnome-bluetooth bug?
[14:17] <Nafai> I'm about to test with the update to app indicators that is installing now and then see what is left of the filed bugs on g-b
[14:17] <seb128> Nafai, ok good, did you work on any bug yesterday?
[14:18] <seb128> Nafai, ie any news about the rhythmbox artwork update?
[14:18] <seb128> or the empathy append for notify-osd,
[14:18] <seb128> ?
[14:19] <Nafai> I was reading the code for the rhythmbox bug and have some testing to do to figure out what is going on there
[14:21] <Nafai> I plan on finishing gnome-bluetooth bugs and rhythmbox today and then I'm working a bit tomorrow because I was out a day this week
[14:21] <Nafai> brb, getting breakfast
[14:24] <seb128> Nafai, ok, good, no worry I was just checking if you were done with those or not
[14:25] <seb128> Nafai, seems I don't need to look for new bugs to add to your list today ;-)
[14:27] <Nafai> Yeah, I've got plenty right now :)
[14:40] <jcastro> seb128: I have a workflow question
[14:40] <seb128> jcastro, sure
[14:40] <jcastro> seb128: since we're now frozen, assuming they start fixing up the bugs, how do you deal with that? Do you just queue them up locally and land them after freeze? Use a PPA?
[14:41] <seb128> jcastro, queue them in the lucid queue
[14:41] <seb128> it will be flushed in after beta1
[14:41] <jcastro> is there a url to watch the queue?
=== Pici` is now known as Pici
[15:01] <seb128> jcastro, sorry I didn't see you reply
[15:01] <seb128> https://edge.launchpad.net/ubuntu/lucid/+queue
[15:01] <seb128> jcastro, ^
[15:01] <jcastro> ah duh, that makes sense, thanks
[15:37] <qense> tedg: Do you have time to take a look at <https://code.launchpad.net/~qense/indicator-application/fix-mono-bindings/+merge/20813> please?
[15:39] <qense> jcastro: Do you know if someone is working on bug #529052?
[15:39] <ubot4> Launchpad bug 529052 in indicator-application (Ubuntu) "battery applet comes and goes in notification area (affects: 38) (dups: 9)" [Medium,Confirmed] https://launchpad.net/bugs/529052
[15:42] <qense> tedg: There are a number of users complaining about bug #526041 not being fixed by the fix you pushed to the 0.0.14 release of indicator-application. Would you mind taking a look at it?
[15:42] <ubot4> Launchpad bug 526041 in indicator-application (Ubuntu) (and 2 other projects) "gnome-power-manager crashes all 5-10 minutes again (affects: 5) (dups: 1)" [Low,Confirmed] https://launchpad.net/bugs/526041
[15:44] <qense> jcastro: Transmission is showing all the menu icons in its AppInd menu. Is that a bug in Indicator Application or in my Transmission patch?
[15:47] <jcastro> qense: I believe it's an a-i bug, seb assigned it to someone today
[15:47] <jpetersen> https://bugs.edge.launchpad.net/bugs/528527
[15:47] <ubot4> Launchpad bug 528527 in indicator-application (Ubuntu Lucid) (and 2 other projects) "should respect the gtk "always-show-image" property (affects: 1)" [Low,Triaged]
[15:47] <jpetersen> to me
[15:47] <tedg> qense: So do you think it should be closed for bug 538078 like the reporter suggested?
[15:47] <ubot4> Launchpad bug 538078 in indicator-application "Application Indicator causes Gnome Power fallback icon to show/hide on each refresh (affects: 1)" [Undecided,New] https://launchpad.net/bugs/538078
[15:47] <tedg> qense: Minus reporter, last commentor.
[15:48] <tedg> qense: I haven't looked through the whole patch, but it's really important that notification-item.xml doesn't change.
[15:48] <qense> tedg: In that case you'd probably want to reject the merge request since it does.
[15:48] <qense> jcastro, jpetersen: thanks, I'll have a look at that bug report.
[15:48] <tedg> qense: Well, it doesn't need to be rejected... you can update the branch and the merge request will update.
[15:50] <qense> tedg: I'll revert some changes, but I doubt I'll be able to commit a new revision today. Please also keep in mind that the Mono bindings won't support overriding the Fallback and Unfallback methods until the new version of GAPI is released into GTK#.
[15:51] <qense> Last September support for the virtual methods that are used for fallback and unfallback was added and it is most likely to be released with GTK# 3.0, if everything goes according to plan and 3.0 isn't delayed.
[15:51] <tedg> qense: That's a shame.  Do you know what the ETA is there?
[15:52] <tedg> qense: Ah, I guess that makes some sense.  I wonder if they'll use GObject introspection at that point.
[15:52] <qense> If there will be a GTK# 3.0 release it will most likely be released together with GTK+ 3.0 in September. But it could be that the new GAPI features get delayed, or that 3.0 gets delayed.
[15:52] <qense> tedg: Isn't it already possible to use GObject introspection in C#?
[15:53] <tedg> qense: Honestly, I don't know.  bratsche, DBO ? ^
[15:56] <qense> tedg: Regarding the bugs, I think the last commenter is right indeed. You'd agree with closing the bug you marked as fixed in the changelog of 0.0.14 and point everyone to the newly opened bug report?
[15:57] <bratsche> qense: I don't think there is any C# support for gobject-introspection yet.
[15:58] <bratsche> Also, I'll be surprised if gtk# 3.0 comes out at the same time as gtk+ 3.0.
[15:58] <bratsche> Pleasantly surprised though. :)
[15:59] <qense> bratsche: There are a lot of things unclear and uncertain with regard to GTK#. I heard more developers than just me complain about the fact that almost all attention goes to trunk, leaving the 2.x.x releases to be not much more than just maintenance releases.
[16:00] <jcastro> qense: yeah it's kind of painful right now
[16:00] <bratsche> I haven't really been paying as much attention to what's happening in gtk# land since I don't write a gtk# app anymore.
[16:00] <jcastro> qense: so in a nutshell how does say, banshee act different with an app indicator in this case?
[16:01] <tedg> qense: Yes, I'd agree.
[16:01] <bratsche> Back when I was using gtk#, it always lagged quite a bit behind gtk+ releases.
[16:02] <Nafai> So I'm dealing with some gnome-bluetooth bugs in that menu items aren't getting updated
[16:02] <Nafai> And in all of the functions where things aren't getting updated in the app indicator, they end like this:
[16:02] <Nafai> gtk_ui_manager_ensure_update (GTK_UI_MANAGER (object));
[16:03] <qense> jcastro: It doesn't act really differently, it means I can't add proper fallback support; i.e. the original status icon isn't used when the icon falls back, but the generic fallback implementation. This means that the tray icon has less features. It is something I can live with, personally, especially since I've added a preference for disabling the Application Indicator and using the defaul status icon instead.
[16:03] <jcastro> qense: ah so that basically means it would have to be a distro patch, not something upstream could take, since they need to support the old thing.
[16:03] <Nafai> Would that call somehow not update things so the app indicator would see it?
[16:03] <qense> jcastro: It's just frustrating that all the time I spent on making the fallback mechanism work in C# feels a bit wasted now; I could have submitted a proper patch much earlier if I'd chosen to not work on it.
[16:04] <qense> jcastro: That's not the case, when you don't built the application with --enable-appindicator the default icon is used.
[16:05] <qense> jcastro: However, I'm not sure what the behaviour of the application is when the indicator applet is removed from the panel.
[16:05] <jcastro> ah
[16:05] <qense> jcastro: Something more important is that the patch missed the 1.5.5 release, the last one before 1.6.0.
[16:06] <jono> kenvandine, you seen http://people.ubuntu.com/~alanbell/gwibberfall.png ?
[16:06]  * kenvandine looks
[16:06] <jcastro> qense: I talked to gabriel a bit yesterday, might want to ping him again about it
[16:07] <kenvandine> jono, so what's the fail there?
[16:07] <kenvandine> and how did he do that with the backgrounds :)
[16:08] <Nafai> tedg: Sorry, I meant to address my above questions to you
[16:08] <qense> jcastro: the only issue with the current patch there is, is that the tray menu isn't properly reset when you toggle the preference; the menu gets longer and longer.
[16:08] <qense> jcastro: I'll talk to him when I've got some more time, I have to go now.
[16:08] <jcastro> qense: ok
[16:08] <jcastro> qense: also, I got a new icon for it
[16:08] <qense> jcastro: great!
[16:08] <jcastro> qense: I've sent it to kwwii to scale it, etc.
[16:08] <jcastro> it will look awesome
[16:09] <qense> good
[16:09] <tedg> Nafai: Is this with indicator-application 0.0.16?  I think that is what jpetersen fixed with his patch.
[16:09] <qense> I'm off now, bye everyone!
[16:09] <jono> kenvandine, fail?
[16:10] <Nafai> tedg: Hrm, I thought I had the latest installed, let me double check
[16:10] <kenvandine> jono, the image name is gwibberfail.png
[16:10] <jono> ahhh
[16:11] <jono> no idea
[16:11] <jono> I think it meant to be gwibberfall
[16:11] <kenvandine> looks like a win to me :)
[16:11] <kenvandine> ah
[16:11] <kenvandine> oh
[16:11] <kenvandine> it is fall
[16:11] <kenvandine> miss read
[16:13]  * hyperair read it as gwibberfail
[16:14] <Nafai> tedg: I guess I have 0.0.15, is 0.0.16 in the repos?
[16:14] <tedg> Nafai: Should be getting there.... the buildds seem far behind :(
[16:15] <tedg> Nafai: You can grab the branch... though that's harder.
[16:15] <hyperair> by the way, regarding the move of the window controls from the right to the left, that change is controlled by gconf, right? not the theme? meaning that no matter what theme used in lucid, the controls are now all on the left?
[16:15] <Nafai> tedg: ok, thanks.
[16:16] <Nafai> Is there any way to look at the buildd queue?
[16:16]  * tedg tries to remember....
[16:17] <tedg> Nafai: https://launchpad.net/builders/
[16:17] <Nafai> Thanks
[16:24] <tgpraveen12> jcastro: what is the irc channel for gwibber?
[16:24] <tgpraveen12> i am having a bad bug with it
[16:24] <jcastro> #gwibber on irc.arstechnica.com
[16:24] <jcastro> tgpraveen12: seg|ars is in here btw.
[16:25] <tgpraveen12> seg|ars: hey since the last few weeks(months maybe even) in gwibber with my twitter account set up all it shows are the messages directly addressed to me but does not
[16:25] <tgpraveen12> show anything for the other msgs. ie msgs of ppl i follow
[16:25] <tgpraveen12> few months ago it used to work. am on a fully upgraded lucid btw
[16:25] <tgpraveen12> and jcastro thx
[16:26] <jcastro> oh I think jono hit that bug too
[16:27] <tgpraveen12> jcastro: any known workaround reinstalling didnt help
[16:28] <jcastro> not afaik
[16:42] <AlanBell> hi jono
[16:42] <jono> hey AlanBell
[16:42] <jono> kenvandine, AlanBell did the gwibberfall thing
[16:43] <jono> figured you should both talk :)
[16:43] <AlanBell> hi kenvandine 
[16:43] <kenvandine> hey AlanBell
[16:44] <AlanBell> so yes, the gwibberfall thing is my fault :-)
[16:44] <kenvandine> :)
[16:45] <AlanBell> the idea was just to hack something together for a side-screen at oggcamp
[16:56] <AlanBell> is gwibber an ayatana project?
[16:58] <jcastro> no
[17:04]  * AlanBell finds the questions in the logs
[17:04] <kenvandine> but we love gwibber :)
[17:04] <AlanBell> so certainly fall, and not fail :-)
[17:05] <kenvandine> AlanBell, so have a branch that lets you set the background image?
[17:05] <AlanBell> and I have been talking to the #gwibber crowd on irc.arstechnica
[17:05] <AlanBell> I have a branch with a fullscreen mode
[17:06] <AlanBell> what you are looking at is a single theme running 5 times
[17:07] <AlanBell> and the search string goes into the css class of the body tag, so it might end up processed as <body class="hashubuntu"> (# isn't allowed in class names)
[17:08] <AlanBell> and I have a single css file that styles body.hashshotofjaq and body.hashoggcamp etc in different ways
=== MacSlow is now known as MacSlow|capoeira
=== MacSlow|capoeira is now known as MacSlow