> By default, pulseaudio only runs as the user, and not system wide.

Yes.  What does that have to do with my bug report?

> Unless you have a specific reason, pulseaudio should not be run system
wide as it is a possible security risk.

I have a specific reason (the reason being I am not a moron -- I know
what I am doing) so that's why I enabled it in /etc/default/pulseaudio.
Again, what does that have to do with my bug report?

> Added to that, pulseaudio will only use the hal module if its
available and hal is running.

Not true, if HAL is not available, PA refuses to start.  This is FACT.

> Perhaps the hal module loading needs to prevent pulseaudio from
failing etc

No, what needs to be fixed is the initscript's ordering and
dependencies.  If you "fix" the hal module loading by loading the old
"detect" module, you get only one sound output in stereo, not several
outputs.

> but people who set up pulseaudio system wide, do so for a good reason,
and I'd suspect they would know what they are doing.

I know what I am doing and I know why I submitted the bug.

In summary:

- there is a bug in the Ubuntu initscript that triggers in a certain scenario 
which is not the default but it is a supported scenario by the original 
developers.
- fixing this bug with the fix that I have researched and tested introduces no 
regressions or changes in behavior to default-configured systems
- fixing this bug with the fix that I have researched and tested fixes the 
needs of us who use PA system-wide

On the other hand, if you would like to cut your nose to spite your
face, you could theoretically remove the initscript altogether in the
next update, right?  I mean, it's not like PA defaults to systemwide,
right?  You even said it yourself: "people who set up pulseaudio system
wide, do so for a good reason, and I'd suspect they would know what they
are doing".  So that means *I* know what I am doing and I could very
well write my own initscript, right?

News for you: I did.  I fixed the initscript and generously contributed
that fix back to the community.  It took me quite a while to figure the
bug out and fix it.  Did you even give this bug a longer-than-cursory
look?

This excuse of a triage is shameful.  So, tell me again: why did you
triage this bug as WONTFIX?

** Changed in: pulseaudio (Ubuntu)
       Status: Won't Fix => Confirmed

-- 
fails to start on boot due to hal not running
https://bugs.launchpad.net/bugs/244679
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to