[pulseaudio-discuss] First start by gnome-session doesn't honour default.pa?

[Ng Oon-Ee]

On Wed, 2010-09-29 at 16:00 +0100, Colin Guthrie wrote:
> 'Twas brillig, and Ng Oon-Ee at 29/09/10 15:13 did gyre and gimble:
> > Hi all,
> > 
> > I've enabled the virtual simultaneous output option in paprefs, and also
> > the line 'set-default-sink combined' to /etc/pulse/default.pa
> > 
> > I do not have ~/.pulse/default.pa or any user-specific configuration.
> > 
> > Whenever I first start Gnome, the simultaneous output is not loaded, and
> > thus is not set to default. When I 'killall pulseaudio' the next
> > instance works as I expect (simultaneous output exists and is default).
> > 
> > Could this have something to do with esdcompat? My gnome-media,
> > gnome-settings-daemon, and libcanberra are all compiled with pulseaudio
> > enabled.
> > 
> > I could of course workaround this by running killall pulseaudio
> > everytime I boot, but that's not exactly optimal =)
> 
> I suspect this is something to do with gconf.
> 
> paprefs just sets some keys in gconf and it's up to module-gconf to
> actually read and process them.
> 
> I believe (tho' have not checked) that module-gconf will not wait for
> gconf itself to be loaded before being considered "loaded" therefore,
> the set-default-sink combined in default.pa may not work, even if the
> gconf is available and working.
> 
> Out of curiosity, does unloading/reloading just module-gconf make the
> simultaneous output appear? (as opposed to killing the whole of the PA
> daemon) It's not any more elegant a solution but it does narrow down
> where the problem lies :D
> 
> Col
> 
Isn't it always this way... now that I want to test that it starts
working properly every single boot. The next time I see this issue I'll
be sure to try unloading/reloading module-gconf. Probably a race
condition of some sort.