[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: how is pulseaudio supposed to work?



On Tue, 18.12.07 11:58, Kevin Fenzi (kevin scrye com) wrote:

> > There are many reasons why I chose to make PA a session daemon: 
> ...snipp...
> 
> This brings me to the following question: 
> 
> Why not have a /etc/xdg/autostart/pulseaudio.desktop 
> to start pulseaudio for user sessions? 

Actually, if you look closely you'll see that we do ship an XDG
autostart file. However, not really because of the reasons you are
suggesting here and it's a different story.

Basically, the problem is that XDG autostart doesn't define any order
in which those files are executed. However, PA needs to be started
before any login sound is played, or any event sound is cached in the
server.

 KDE extended the XDG spec a bit, and thus on KDE PA is started that
way. However, on GNOME gnome-session starts PA sychronously and waits
for it and then uploads event samples to it. And thus we cannot really
move the point where we start PA out of there.

What I am planning to do is make PA a normal XSM client like any other
app, and rip out the esd-specific code in gsm. But that's not done
yet. So for now the PA as esd-dropin works great and is good
enough. It's not a top priority on my list to change this. But it's
right next to the top of my list.

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net         ICQ# 11060553
http://0pointer.net/lennart/           GnuPG 0x1A015CC4


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]