This bug was fixed in the package ubuntu-drivers-common - 1:0.2.91.9
---
ubuntu-drivers-common (1:0.2.91.9) trusty-proposed; urgency=medium
* sl-modem plugin: Keep environment for aplay, just ensure it's using the C
locale. This avoids staring pulseaudio twice and causing races
** Changed in: ubuntu-drivers-common (Ubuntu Trusty)
Status: In Progress = Fix Committed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
I can confirm that the fix as in proposed works as intended.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively making
** Description changed:
- SRU INFORMATION
- ===
- IMPACT:
- On the current kubuntu 14.04 live-image (and for a 13.10 upgraded system)
pulseaudio is running twice. This makes attaching/deattaching of usb-headset
and other stuff impossible because the two instances fight over the
** Branch linked: lp:ubuntu/trusty-proposed/ubuntu-drivers-common
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively making
This can be accepted once bug 1376966 is verified. Thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively making device
Backported fix uploaded to trusty SRU review queue:
https://launchpad.net/ubuntu/trusty/+queue?queue_state=1
Now the SRU team needs to review and accept this, then testing the
-proposed package would be much appreciated!
** Description changed:
-
- On the current kubuntu 14.04 live-image (and
I tried applying the patch in comment 22 to my 14.04 installation
(3.13.0-39-generic, upgraded from 12.04) and rebooting, but it didn't
solve the problem with my Logitec webcam microphone. I still get the
same error.
ubuntu-drivers-common 1:0.2.91.7 is the currently installed version.
Are they
Forgot to mention I am using Gnome3 shell, not Unity or KDE.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively making
** Also affects: alsa-plugins (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: alsa-plugins (Ubuntu Trusty)
Status: New = Invalid
** Changed in:
Alberto Milone, could you add the updated version of this package to
14.04 backport the fix?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started
Hi,
can this be backported to the 1:0.2.91.x-branch (the one in ubuntu
14.04).
Thanks!
Felix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is
Fix from #22 helped me (Kubuntu 14.04 upgraded from 12.04). Thanks,
guys!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively
Thanks jaunmanuel for finding the fix and sharing the knowledge about how you
found it.
I'll add redirecting 'aplay' temporarily to a script to my list of debugging
techniques :-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Thanks jaunmanuel for finding the fix and sharing the knowledge
about how you found it.
I'll add redirecting 'aplay' temporarily to a script to my list of
debugging techniques :-)
:-) Nice to hear!
Juan Manuel Cabo
--
You received this bug notification because you are a member of Desktop
** Branch linked: lp:ubuntu/utopic-proposed/ubuntu-drivers-common
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively making
This bug was fixed in the package ubuntu-drivers-common - 1:0.2.97
---
ubuntu-drivers-common (1:0.2.97) utopic; urgency=medium
* tests/testarchive.py: Organize debs in pool/ structure, for better
reusability.
* tests/ubuntu_drivers.py: Drop expected failures, they've
To Martin Pitt: Thank you very much for the fix. I manually applied
that commit to my sl_modem.py and it of course works. Restarting the
computer, or running ubuntu-drivers list doesn't result in a second
instance of pulseaudio.
Also, the duplicate bug:
USB microphone inputs not
On Mon, Aug 18, 2014 at 04:26:16PM AEST, Martin Pitt wrote:
I don't know why aplay invokes pulseaudio (that seems wrong, as
pulseaudio usually uses ALSA as a backend), but if passing on the
environment (for DBUS_SESSION_BUS_ADDRESS etc.) helps, I'm fine with
doing that. The main reason for
The aplay call was introduced in http://bazaar.launchpad.net/~jockey-
hackers/jockey/trunk/revision/519 for bug 295158. Apparently some sl-
modem types don't appear in /proc/asound/cards. It's indeed a strange
hack, but so is sl-modem in the first place :) Beyond that bug report
I'm afraid I have
This should help: https://github.com/tseliot/ubuntu-drivers-
common/commit/5fe70ce1
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New = Fix Committed
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug
Also solved the problem here!
Using 'aplay -l' seems like a rather strange hack to detect a software
modem. I think either the Python ALSA bindings or /proc/asound/cards for
that instead only. Right now 'aplay -l' apparently is only called when
no modem is found through /proc/asound/cards as a
@juanmanuel , your solution worked for me. I am running 14.04 upgraded
from 13.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice -
Works on current 14.10 also. Good job juanmanuel !!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively making device
On saturday I made some tests and found the root CAUSE of the issue, and
the SOLUTION.
The reason aplay is called, is because it is used to enumerate sound cards,
(with the -l argument as in aplay -l), by ubuntu-drivers, to find ye-old
software modems.
The ubuntu-drivers-common package scripts
I'm sorry that the previous post was too long.
This is the summary:
1) aplay -l gets called with an empty environment by a script in
ubuntu-drivers-common which Kubuntu runs at startup, through the
DriverManager_DBus.
aplay -l doesn't find a pulseaudio and creates a new one (through libasound),
Pulseaudio and KDE aside.
What is aplay doing the the KDE-startup sequence in the first place?
I know theres a login sound, but should'nt that be played by some application
through pulseaudio directly.?
--
You received this bug notification because you are a member of Desktop
Packages, which
- fix Pulseaudio's self-detection so that it works when the first
instance is still initializing
Yes, this is what should happen.
As for running Pulseaudio as a specific user, I wonder what would happen
when multiple users are logging onto a system at the
same time. Would this not
It seems to be specific to KDE too. It could be related to KDE having a
login sound which Unity does not have (I assume that's what the aplay
does?), but it could also be something in the way KDE sets up
sessions...?
--
You received this bug notification because you are a member of Desktop
Yes, it only seems to happen with KDE. I also found that Pulseaudio
installs one extra start-up script for KDE only in /etc/xdg/autostart.
The man pages of these scripts both mention they will use an already
running Pulseaudio.
I think the proper solution is either:
- run Pulseaudio *once* and
At the end here at least, the pid file points to the lowest PID. Could I
check it during the start-up phase as well? Could it be possible the 2nd
instance is already loading before the 1st has a chance to write its pid
file?
Does it make sense that Pulseaudio's respawn option should be turned on,
Did you see my systemtao log of a KDE login from a cold reboot.
https://launchpadlibrarian.net/172625307/kde-login.stap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
This happens in Kubuntu Utopic too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively making device management
My workaround is disabling Pulseaudio's respawn and starting Pulseaudio
through ~/.profile.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started
Well, the question is why aplay - alsa pulse plugin - libpulse does not
connect to the existing instance but instead starts a new one.
What about the files in /var/run/user/userid/pulse/ - if there are pid files,
to they point to the new-invalid or old-valid pulse instance?
--
You received
Am I the only one that cares for this bug. Unfortunately I'm unable to
figure out why aplau trigger pulseaudio to that more times. And release
is in 48 hours or so.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
Heres a log on a KDE startup and as far as I can see it is a cascade
looking something like this.
DriverManager start python3 which then starts aplay which then again starts
pulseaudio. Parallel to that kmixctl is also starting pulseaudio. Both lines of
events happen 2 or 3 times. They sort of
Another thing. The *first* pulseaudio is the instance that works and
respawns if killed. So kmixctl is from my perspective allowed to start
pulseaudio aplay is not.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
ok - chmod -x /usr/bin/aplay solves it. Now that aplay does not run
pulseaudio no additional instances is run.
Now the question is why aplay runs pulseaudio.
Lokking the the alsa-repositories I found the following
* alsa-utils - nothing interesting.
* alsa-lib - nothing interesting.
*
Is anything happening with this bug. I'll be happy to recompile anything
to help tracking this down.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is
It renders essential functionality of the package (or a dependent one)
broken.
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
The issue is also present when running the latest cd-image in
virtualbox.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
It does not happend in Unity - only KDE.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively making device management
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.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
45 matches
Mail list logo
