Ubuntu
pulseaudio package

Init script is needlessly noisy

Bug #656426 reported by Mario Limonciello
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pulseaudio (Ubuntu)
Fix Released
Wishlist
Daniel T Chen

Bug Description

Binary package hint: pulseaudio

The default installation of pulseaudio is configured for per-user sessions. On every boot that means that the init script emits this warning message:

 log_warning_msg "PulseAudio configured for per-user sessions"

I don't see any value in this, and it is one of the items that detracts from the experience when plymouth is failing to come up in a timely fashion and the VT shows any text hat was left there.

Revision history for this message
Daniel T Chen (crimsun) wrote :

The larger issue is why we even bother providing an initscript at all for desktop environments; clearly there is no value in spamming a desktop user. For server environments - the non-trivial number of those that act as network PA servers - we need a way to denote that the system-wide PA daemon *is* active.

Changed in pulseaudio (Ubuntu):
assignee: nobody → Daniel T Chen (crimsun)
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Delan Azabani (azabani) wrote :
Revision history for this message
Daniel T Chen (crimsun) wrote :

Delan, that patch doesn't address the requirement that I outlined in comment #1.

tags: added: patch-needswork
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pulseaudio - 1:1.1-0ubuntu9

---------------
pulseaudio (1:1.1-0ubuntu9) precise; urgency=low

  * debian/pulseaudio.init: Don't tell the user pulseaudio daemon isn't
    starting when in per-user mode. This is the most common case in Ubuntu
    and causing needless distracting text on the screen. (LP: #656426)
 -- Mario Limonciello <email address hidden> Fri, 17 Feb 2012 16:32:52 -0600

Changed in pulseaudio (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Mario Limonciello (superm1) wrote :

I think that whatever work would be necessary to get the init script only installed on servers will be outside that which will happen after feature freeze in precise. I'd rather the immediate bug that was reported be fixed in precise (hence the upload). If you want to rework where the init script is located at a future time, I think that's still fine.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.