On Tue, 16.09.08 15:12, Matthias Clasen (mclasen@xxxxxxxxxx) wrote: > > 3.) Logging in I hear first the GDM "audio logo," think I'll call it > > an earcon from now on. But, Orca launches in my secondary audio device. > > That's inappropriate, but I have no way to control that except to unplug > > my secondary and tertiary audio devices and start over. > > Hardly pulseaudios fault if orca picks the wrong device. I have no idea > how orca decides which device to use. Actually, nowadays I prefer seeing PA as black box, where only PA decides what device clients should be connecting to, not the clients themselves. Policy decisions should be up to the sound server, not the client. That said, in some situations (like probably this one) it does make sense to have device selection in the clients themsevles. Unfortunately ALSA device enumeratin is rather flaky and we don't support it in the PA backend for libasound. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
