Thanks for the info. Is there a simple way to kill off the gdm pulseaduio when the user logs in? Some sort of hook I can tie into? Thanks, Bill On Thu, Dec 31, 2009 at 11:26 AM, Colin Guthrie <gmane at colin.guthr.ie> wrote: > 'Twas brillig, and Bill Cox at 31/12/09 16:07 did gyre and gimble: >> The problem is that there is no audio at the console until I log in. >> There is also no audio at the gnome login. ?Grr... > > AFAIK, the GDM login relies on autospawning, so turing off auto spawning > will result in no sound at gdm login. > > As for speechd-up I'd recommend running it as the gdm user, not as a > system user, then when the real user logs in, the gdm user's PA and > speechd-up processes should die and a version for the user who is > logging in should be run in it's place. > > I think this configuration has been discussed quite thoroughly over the > last couple weeks. > > I'm not familiar with it, so speechd-up may require modification to work > this way but it certainly seems like the most logical and secure way to > run the system (the same would be true of timidity too I believe). > > Col > > -- > > Colin Guthrie > gmane(at)colin.guthr.ie > http://colin.guthr.ie/ > > Day Job: > ?Tribalogic Limited [http://www.tribalogic.net/] > Open Source: > ?Mandriva Linux Contributor [http://www.mandriva.com/] > ?PulseAudio Hacker [http://www.pulseaudio.org/] > ?Trac Hacker [http://trac.edgewall.org/] > > _______________________________________________ > pulseaudio-discuss mailing list > pulseaudio-discuss at mail.0pointer.de > https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss >
