[02:34] <ethana2> I installed the app-menu and applet, but it doesn't work with Kmines
[02:34] <ethana2> i have the qt thing for it installed..  the Kmines menu is removed from its window but doesn't show up in the panel
=== klattimer1 is now known as klattimer
=== MacSlow is now known as MacSlow|lunch
=== MacSlow|lunch is now known as MacSlow
[13:52] <kenvandine> davidbarth, can you look at that indicator-me merge request today? for the libgwibber port
[13:54] <davidbarth> kenvandine: yup, but need to finish some administrative stuff first
[13:54] <kenvandine> ok
[13:54] <kenvandine> davidbarth, thx
[14:01] <davidbarth> kenvandine: the branch works fine here so far
[14:06] <kenvandine> davidbarth, good :)
[14:07] <davidbarth> kenvandine: i have a strange behavior with the text entry though, it's only displaying 1 char at a time as i type
[14:07] <davidbarth> kenvandine: can you reproduce that on your system? i haven't seen any update that could create that issue in my apt-get update this morning
[14:11] <kenvandine> humm
[14:11]  * kenvandine tries
[14:13] <kenvandine> davidbarth, nope... can't reproduce that here
[14:13] <kenvandine> davidbarth, maybe a dbusmenu problem? slowness on the bus?
[14:13] <kenvandine> can't be related to my branch though
[14:14] <davidbarth> kenvandine: yeah, i don't think that's due to the changes
[14:14] <kenvandine> although, with the new theme the text is very light in that input box
[14:14] <davidbarth> kenvandine: so more of an ido/gtk regression
[14:14] <davidbarth> indeed
[14:15] <dutchie> There are currently no bugs filed against popey.
[14:15] <dutchie> whoops
=== npmccallum_ is now known as npmccallum
[15:10] <davidbarth> kenvandine: https://code.edge.launchpad.net/~ken-vandine/indicator-me/libgwibber-port/+merge/32775 a few things to see, nothing big
[15:11] <davidbarth> kenvandine: some of them are discutable, you can ping me here
[15:12] <kenvandine> humm
[15:12] <kenvandine> ok
[15:12] <kenvandine> so your saying we should check for configured accounts once, and display the text entry
[15:13] <kenvandine> and then if the service goes away leave the text entry?
[15:13] <kenvandine> it would start the service again, sure... i was just keeping the behavior the same as before
[15:16] <kenvandine> davidbarth, ^^
[15:19] <davidbarth> kenvandine: right, i think that's the principle of least surprise, "why did the entry disappear suddenly" vs "oh i don't have configured accounts, that's why it's not there"
[15:21] <kenvandine> sure, that actually simplifies the code quite a bit
[15:21] <kenvandine> we only need to the signal so we we know when to display the entry
[15:21] <kenvandine> and then we can just forget it
[15:31] <jcastro> hi klattimer
[15:31] <jcastro> klattimer: I am back!
[15:31] <jcastro> klattimer: I see ibus has been giving you a hard time, heh
[15:32] <klattimer> hard time isn't the word
[15:33] <klattimer> :/
[15:33] <klattimer> since the 1.3.7 update it's been kicking my ass
[15:33] <jcastro> klattimer: hey just to follow up, did the notify-osd fixes you did get reviewed and merged? I haven't seen them do a release or an upload into maverick
[15:34] <klattimer> I haven't done anything to notify OSD yet
[15:35] <klattimer> g-s-d's indicator took priority and then ibus reared up again
[15:35] <klattimer> the things i have done wrt notify osd is clear up some of the bug backlog
[15:40] <jcastro> ok
[15:46] <kenvandine> davidbarth, ok I think I addressed all your comments
[15:54] <davidbarth> kenvandine: super, let me see
[15:55] <kenvandine> davidbarth, thx
[15:59] <davidbarth> kenvandine: sweet, approved!
[16:00] <kenvandine> davidbarth, great, thx
[16:02] <davidbarth> kenvandine: i'll roll a release around thursday
[16:03] <kenvandine> great