[05:54] <elfy> sound indicator seems to be working again
[05:57] <Unit193> Really?  Recent updates, scroll wheel?
[05:58] <elfy> just updated
[05:58] <elfy> yep - scoll wheel
[05:58] <Unit193> Yes! \o/
[05:58] <elfy> also I noticed yesterday that tbird new mails get indicated
[05:58] <elfy> I'd forgotten all about those 
[15:25] <elfy> and a reboot stops the sound thing working 
[16:02] <ali1234> elfy: i just upgraded, it doesn't work in gtk3 indicators
[16:03] <ali1234> tbird mail indications working/not working is probably the same bug as with pidgin, which i think is bug 1203888
[16:04] <elfy> using the default indicators here
[16:04] <ali1234> appindicator is same whether you use gtk2/3
[16:04] <ali1234> because it's on dbus
[16:04] <ali1234> i suppose the problem could be in gtk
[16:04] <elfy> maybe so - no idea :)
[16:04] <elfy> not usre why the thing was working this morning 
[16:05] <ali1234> if you run killall blueman-applet and then blueman-applet in terminal, do you see that gtk error?
[16:05] <ali1234> "signal 'child-added' is invalid for instance '0x193d0b0' of type 'GtkMenu'"
[16:05] <elfy> I disable blueman
[16:05] <elfy> I Can check though
[16:06] <ali1234> anything that uses appindicator really
[16:06] <ali1234> indicator-cpufreq, glipper
[16:06] <ali1234> or even the example code i put on the bug (the second one)
[16:06] <ali1234> what it seems like is because the signal is invalid, the indicator doesn't update when the client changes it's menus
[16:07] <ali1234> eg because there's a new message from tbird or whatever
[16:07] <brainwash_> appindicator is not an requirement, it's just an enhancement, right?
[16:07] <ali1234> (child-added refers to adding/updating a menu item)
[16:07] <ali1234> appindicator is how many apps make indicators
[16:08] <elfy> I know that if I edit the service to Exec=/usr/lib/indicator-sound-gtk2/indicator-sound-service
[16:08] <elfy> it works 
[16:08] <brainwash_> like nm-applet?
[16:08] <ali1234> yeah, nm-applet uses it
[16:08] <ali1234> though i haven't see any problems with it
[16:08] <ali1234> but it might be the case if a new wireless access point comes online it might not get added to the menu
[16:08] <brainwash_> but nm-applet would still show up, if appindicator is missing, right?
[16:08] <elfy> ali1234: also - I think the reason I started noticing tbird notifications is this is a new install and I'd not set notifications to 1 second from 10
[16:09] <ali1234> brainwash_: if appindicator is missing it won't show up, but that isn't the bug
[16:09] <ali1234> the bug is that the menus can't be changed once the indicator is created
[16:09] <brainwash_> I know, just wanted to understand what appindicator actually does
[16:09] <ali1234> and some indicators create a empty menu and then try to add items after
[16:09] <ali1234> others just update them when some event happens and that is also broken
[16:10] <ali1234> well, to see what appindicator does, just check the minimal test case on the bug ^
[16:10] <ali1234> it's also the simplest way to create an indicator in python
[16:10] <elfy> is that what's causing the sound indicator to fail? 
[16:10] <ali1234> if you run that code it makes an indicator with "One" menu item and then adds a second menu item "Two" - in saucy you never see "Two"
[16:11] <ali1234> elfy: no sound indicator is a different bug afaik
[16:11] <ali1234> sound indicator works ok with gtk3 except for the scroll wheel on the icon bug
[16:11] <elfy> ok - well I'd not notice a blueman one - even if I had it enabled as I don't have any bluetooth things to notice it with :p
[16:12] <elfy> ali1234: well that kind of makes that as bad as not working at all lol 
[16:12] <ali1234> why?
[16:12] <elfy> because that's what people use it for :)
[16:12] <ali1234> you can still change the volume by clcking on it, it still shows the current sound status and all the menu items work
[16:13] <ali1234> and you can see eg rhythmbox current song and skip tracks
[16:13] <ali1234> mouse wheel over the menu even works, only over the icon doesn't work
[16:13] <ali1234> and it is broken exactly the same in unity anyway
[16:13] <elfy> it might well be - I'm not pointing fingers 
[16:13] <ali1234> every bug remaining with gtk3 indicators also affects unity
[16:14] <ali1234> so there's nothing we can do with our side
[16:14] <elfy> are we going to actually definitely going to gtk3 by release of 13.10?
[16:14] <elfy> indicators
[16:14] <ali1234> i think the plan is to put it in backports
[16:15] <ali1234> and then include it in 14.04
[16:15] <ali1234> but it's not up to me
[16:15] <elfy> so we need to have gtk2 working as well then I assume
[16:15] <ali1234> well
[16:15] <ali1234> there's only like two gtk2 indicators left, sound is one of them
[16:15] <ali1234> the other is appindicator
[16:15] <elfy> I know 
[16:16] <ali1234> if appindicator is broken on gtk2 i suggest to start with the example test code
[16:16] <elfy> the fix is easy enough to get sound one working
[16:18] <elfy> ali1234: anyway thanks for the info
[18:14] <Unit193> ali1234: Oooh!  Using grml-rescueboot now too? :D