pulseaudio is started twice - effectively making device management impossible.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
alsa-plugins (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Trusty |
Invalid
|
Undecided
|
Unassigned | ||
ubuntu-drivers-common (Ubuntu) |
Fix Released
|
Undecided
|
Martin Pitt | ||
Trusty |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
On the current kubuntu 14.04 live-image (and for a 13.10 upgraded system) pulseaudio is running twice. This makes attaching/
The fix is https:/
[Test Case]
To reproduce just boot up the current image and do a "ps -ef | grep pulseaudio"
[Regression Potential]
Low. This fix has been out for many months in 14.10, and only changes the environment that "aplay -l" gets called with. In the absolutely worst case if this goes totally wrong, ubuntu-drivers would stop to detect sl-modem capable soft-modems.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu10
ProcVersionSign
Uname: Linux 3.13.0-
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CurrentDesktop: KDE
Date: Sun Mar 23 22:36:50 2014
InstallationDate: Installed on 2013-12-24 (89 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G7ET31WW (1.13 )
dmi.board.
dmi.board.name: 2356GCG
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 2356GCG
dmi.product.
dmi.sys.vendor: LENOVO
Changed in alsa-plugins (Ubuntu Trusty): | |
status: | New → Invalid |
Changed in ubuntu-drivers-common (Ubuntu Trusty): | |
status: | New → Triaged |
importance: | Undecided → High |
description: | updated |
Changed in ubuntu-drivers-common (Ubuntu Trusty): | |
status: | In Progress → Fix Committed |
tags: | added: verification-done |
I can add that it is the first instance started that is the correct one. Shutting that doesn will make it respawn. That is not the case for the second instance.