On 11/20/07, Lennart Poettering <lennart at poettering.net> wrote: > On Tue, 20.11.07 16:32, Jon Smirl (jonsmirl at gmail.com) wrote: > > > > > On 11/20/07, Lennart Poettering <lennart at poettering.net> wrote: > > > On Tue, 20.11.07 21:50, Lennart Poettering (lennart at poettering.net) wrote: > > > > > > > > I just have the standard Ubuntu package installed. I would suppose > > > > > that whoever made it knew what they were doing. > > > > > > > > I wouldn't want to speculate about this. > > > > > > > > > > I just spoke to the Ubuntu guys. They have the file > > > /etc/default/pulseaudio which can be used to enable system wide > > > mode. Most likely you modified that file? > > > > Looking at it I must have modified it a while ago and forgotten. If > > you don't turn > > PULSEAUDIO_SYSTEM_START=1 on, you can't start pulse using > > /etc/init.d/pulseaudio and then pulse doesn't start on boot. Editing > > that file is the standard way of turning on services in Ubuntu. > > > > Am I supposed to start it with my Gnome session instead? > > Yes, PA is normally started as a drop-in replacement for esd. I.e. it > provides a compatibility script called "esd" that actually starts > PA. All you have to do is to toggle the "Start ESD" checkbox in g-s-p. This wasn't obvious. I was looking to enable Pulse. Now for the really good news. Running it as a session fixed my volume problem. Does this point to where the bug may be in system mode? > > > What to do is not exactly obvious when installing the package. > > But afaik the file in /etc/default/ tells you that using the > system-wide stuff is not recommended and not what most people would > want to use. But it failed to mention the recommended alternative. -- Jon Smirl jonsmirl at gmail.com
