*** This bug is a duplicate of bug 1228759 ***
https://bugs.launchpad.net/bugs/1228759
** This bug is no longer a duplicate of bug 1217036
pulseaudio crashed with SIGABRT in output_free()
** This bug has been marked a duplicate of bug 1228759
pulseaudio crashed with SIGABRT in
*** This bug is a duplicate of bug 1228759 ***
https://bugs.launchpad.net/bugs/1228759
** Information type changed from Private to Public
** This bug has been marked a duplicate of bug 1228759
pulseaudio crashed with SIGABRT in output_free()
--
You received this bug notification because
** Information type changed from Private to Public
--
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/1216703
Title:
pulseaudio crashed with SIGSEGV in pa_thread_mq_done()
Status in
This will probably be fixed if we cherry-pick:
commit 0e9baa429ea2620dbb11f4b3a26eaa46620a9124
Author: Tanu Kaskinen tanu.kaski...@linux.intel.com
Date: Tue Jun 18 21:21:08 2013 +0300
combine: Fix crash in output freeing
** Changed in: pulseaudio (Ubuntu)
Status: New = Triaged
--
Okay, so it appears module-dbus-protocol wasn't completely fixed, as I
thought. It is still crashy.
(In this case it crashes on removal of the card, but while doing so, it
references the card's name, which has already been freed.)
So maybe I need to remove module-dbus-protocol again...
**
** Summary changed:
- pulseaudio crashed with SIGABRT in output_free()
+ [module-combine-sink] pulseaudio crashed with SIGABRT in output_free()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
This crash will likely be fixed by:
commit 1470fc325a0f583813e625b2cfb53fb3907ccd72
Author: Tanu Kaskinen tanu.kaski...@linux.intel.com
Date: Wed Jul 10 21:48:40 2013 +0300
resampler: Fix peaks resampler's channel handling
** Changed in: pulseaudio (Ubuntu)
Status: New = Triaged
Yeah, I can see why this is happening. Because we now have some policy
handling in telepathy-ofono (turn on/off speakerphone mode) and some
policy in pulseaudio (react to headphone plug/unplug), these end up
colliding.
To come around this, I think we need to monitor headphone plug/unplug in
I don't think there is a need to change PulseAudio, because the required
API is already available.
I think indicator-sound is currently using the API to monitor playback,
but not to monitor recording.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Hmm, maybe indicator-sound is already using that API for recording too,
because I remember at some point that the drop-down menu would show the
recording gain only when recording was active. If so, it's just a matter
of transforming that information to an icon, too.
--
You received this bug
Hi Liis,
I'm not sure how this could have happened - there shouldn't have been
any updates to 10.10 that could have caused this. But I think your best
bet at this point is to install this package:
https://code.launchpad.net/~ubuntu-audio-dev/+archive/alsa-daily/+files
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pulseaudio (Ubuntu Saucy)
Assignee: (unassigned) = David Henningsson (diwic)
** Changed in: pulseaudio (Ubuntu Saucy)
Status: New = Fix Committed
--
You received this bug notification
I believe a fix is here:
http://bazaar.launchpad.net/~ubuntu-audio-dev/pulseaudio/ubuntu/revision/603
You're encouraged to test and make sure it works for you.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Sep 24 11:57:56 ubuntu-phablet kernel: [ 180.498000] tabla_codec_enable_chmask:
Slim close tx/rx wait timeout
Sep 24 11:57:56 ubuntu-phablet kernel: [ 180.498641] tabla_codec_enable_slimrx:
Disconnect RX port ret = 0
Sep 24 11:57:56 ubuntu-phablet kernel: [ 180.501449] overflow error on port a,
Hi and thanks for the research,
It looks like this is fixed in Ubuntu 13.10 (I verified by looking at
the source), so I'm closing this bug as fix released.
(If you would like this to be pushed into 13.04, you need to follow the
procedures for stable release updates, but the question is how much
Hi Strelok,
Thanks for finding the patch, I've submitted a merge proposal which I hope will
be reviewed soon.
** Branch linked: lp:~diwic/rhythmbox/lp1155575
** Changed in: rhythmbox (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member
** Summary changed:
- No audio in the headphones with a two pins jack unless plugged in after the
call
+ [mako] No audio in the headphones with a two pins jack unless plugged in
after the call
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) = David Henningsson (diwic)
** Changed in: linux-manta (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: linux-manta (Ubuntu)
Assignee
This is new territory for me, so forgive me if this is a goofy question, but
how are these dmic dependent gain parameters
typically provided? Is this something that should be provided in, say, the
ACPI tables, or is this typically hard-coded in the drivers?
How is this handled in the
Hi,
@Raymond, the jacks are not created as phantom because VT1708 uses jack
polling instead of unsol events. See function vt1708_build_controls in
patch_via.c
@Emil, are you having problems with both headphones and speaker, or is
one of them working okay?
--
You received this bug notification
@bfiller, something is wrong on the Android side, inside the proprietary
blob somehow. rsalveti to investigate further.
** Also affects: touch-preview-images
Importance: Undecided
Status: New
** Changed in: touch-preview-images
Assignee: (unassigned) = Ricardo Salveti (rsalveti)
There is already possibilities for indicator-sound to get notification
when a recording starts/stops.
** Changed in: pulseaudio (Ubuntu Saucy)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio
This should now be fixed on Mako (Nexus 4) - you can use the sound
indicator to change the volume while you're on a call. Anybody wants to
verify?
Still not working on Maguro (Galaxy Nexus), I don't know why. It looks
like the relevant call to Android is working as expected.
** Changed in:
Closing as invalid due to the lack of responses to the last comment.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
That's a little weird - I have tested Nexus 4 today (with an image from a few
days ago), and I think the call volume is quite ok.
(But it's difficult to verify when you're calling yourself for the testing.)
--
You received this bug notification because you are a member of Desktop
Packages,
I think there are two bugs here. The current code sets the voice volume
to maximum.
I'm currently looking into how to change that volume from PulseAudio.
However, if your problem is that it's difficult to hear the receiver,
it sounds like the volume needs to be higher than it is today. Can you
If you just set pin 0x15 to 0xc5 (OUT + HP), chances are that you can
have working headphone output by retasking pin 0x15 as a headphone - but
as raymond says, not easy to know without alsa-info (
https://wiki.ubuntu.com/Audio/AlsaInfo )
--
You received this bug notification because you are a
Change /usr/share/pulseaudio/alsa-mixer/paths/analog-output-
headphones.conf from:
[Jack Front Headphone]
required-any = any
[Jack Headphone]
required-any = any
to :
# [Jack Front Headphone]
# required-any = any
# [Jack Headphone]
# required-any = any
...restart pulseaudio (or the computer)
Side note: There might actually a better solution in newer kernels: if
you install the daily DKMS package (
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS ) you will get this
too.
Then edit /etc/modprobe.d/alsa-base.conf and add this line:
options snd-hda-intel jackpoll_ms=250
..then reboot
** Summary changed:
- [dailer app] During a live call, there's no volume adjustment available
+ [dialer app] During a live call, there's no volume adjustment available
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
After talking to YK, I'm closing this due to lack of responses. Feel
free to reopen if you would like to take this up again, and also have
the time to run kernel bisects etc.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because
A year later; Tanu is working on this upstream (from time to time) as
part of a bigger routing system change, but it's a complicated story and
progress is slow.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Hi,
So far there have been no responses to comment #30. If anybody wants to
work with me - and have the time necessary to run tests etc - feel free
to start there. If not, I'm closing this bug, because there isn't more I
can do at this point.
Thanks.
** Summary changed:
- [soundnua]: hdmi
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided = Low
--
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/1210083
Title:
volume control does not work on Galaxy S2 and
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) = David Henningsson (diwic)
--
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/843587
Title:
Default sink/source
Hi, I'm closing this bug now, because nobody ever showed any screenshot
or similar (of the sound settings GUI) where IEC958 was showing. Feel
free to reopen if you provide such screenshot, preferrably under the
latest release of Ubuntu.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete
Hi Aditya2204,
The audio customisation done on this platform (on the preload install)
is to add a daily DKMS package - see
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS for how to do the same.
I can also confirm that we never enabled the subwoofer on Ubuntu for
this machine. Whether this is
@Adam, yeah, I noticed a while ago and reported it to operators at
Canonical, but it seems to be down still.
http://voices.canonical.com/user/128/ seems to be up though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in
Okay, how does PulseAudio determine if a client is confined or not?
--
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/1211380
Title:
pulseaudio socket needs confined app restrictions
The question is if this is worth spending time on right now, given that
we're trying to get rid of audioflinger, and then all this logic will
change anyway.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
But the first one is probably relatively easy - libandroid-audiosystem-
asound2 (or some other package) already changes /etc/pulse/default.pa I
believe, so we should probably comment out the load-module module-udev-
detect line on all images that use audioflinger.
--
You received this bug
Hi Jono,
I can't reproduce the failure here, using skype from the partner repo.
Did you try that version, and if so, what was the result?
** Changed in: pulseaudio (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which
Looking at the latest logs, I think we actually have two different bugs
to deal with.
One being the long system delays, which might or might not be related to
the graphics driver.
The other one being the audio driver. The regular underruns at 194 ms,
and the high interrupt count, both seem to
Public bug reported:
Looking at PulseAudio logs, it seems speech-dispatcher requests a total latency
of 1 ms, which in turn gives sub-ms latency inside the PulseAudio engine.
This causes unnecessary CPU consumption, or underruns. I understand that you
would want immediate feedback, but wouldn't
Hi Luke,
Could you test this patch and sponsor/upstream it if you find it not
causing any regression on your side?
** Patch added: debdiff.patch
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1208826/+attachment/3762472/+files/debdiff.patch
--
You received this bug
** Summary changed:
- Skype audio in Saucy broken
+ [Thinkpad T520] Skype audio in Saucy broken
--
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/1208485
Title:
[Thinkpad T520]
, and ARM. This resulted in various odd sounds, such as
indicated in the original bug report below, and other comments in this report.
This SRU fixes the code to correctly deal with the above number of channels, 6
channels being common for 5.1 audio output. Thanks to David Henningsson for the
patch
I did a small test on two machines I have here, one ALC888 + front mic
and one IDT92xx + internal mic. I tested recording with Capture at +30
dB and Mic Boost at 0 dB, then I tested recording with Capture at 0 dB
and Mic Boost at +30 dB.
For both machines, there was no significant difference in
potentially regress quality on those machines. Hopefully those are fewer, so
this is what we should default to.)
BugLink: https://bugs.launchpad.net/1085402
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
.../alsa/mixer/paths/analog-input-dock-mic.conf| 12 ++--
.../alsa
On 08/02/2013 03:34 PM, Arun Raghavan wrote:
On Fri, 2013-08-02 at 15:19 +0200, David Henningsson wrote:
Some HD-audio codecs (at least ALC269VB and ALC283) become quite noisy on
high Mic Boost levels. So e g, if there is a Mic Boost and a Capture
control, both ranging from 0 dB to +30 dB, you
@Andrew, hi, the skype developers are working on it, and provided the
below workaround. Start skype from a terminal, like this:
PULSE_LATENCY_MSEC=50 skype
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Hmm, actually, if you use the latest version from the partner archive,
4.2.0.11-0ubuntu0.12.04.2, that now includes the workaround above.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Pushed upstream:
http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=e6051cdf8db554c0bbd4257959c37a7ecc9c10c5
** Changed in: pulseaudio (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is
So it's started correctly as my user but the directory has the wrong
permissions. Could this be a bug in lightdm?
At least it can't be a bug in PulseAudio, because PulseAudio shouldn't
have the permission to create that directory with those permissions,
right?
--
You received this bug
This patch set went into PulseAudio 4.0, which is now in Saucy.
** Changed in: pulseaudio (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
This bug fix went into PulseAudio 4.0, which is now released into Saucy.
** Changed in: pulseaudio (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
** Description changed:
+ [SRU Justification]
+ Several new hardware has either headset jacks or headphone-or-mic jacks,
where the system cannot detect what has been plugged in. E g, for such a
headset jack you can either plug in a headphone or a headset, but since the
system cannot tell which
SRU uploaded to precise-proposed, waiting for ubuntu-sru approval.
--
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/1169143
Title:
Headset support on some Dell machines
Status in
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) = David Henningsson (diwic)
** Changed in: pulseaudio (Ubuntu Precise)
Assignee: (unassigned) = David Henningsson (diwic)
** Changed in: pulseaudio (Ubuntu Precise)
Status: New = In Progress
--
You received this bug
I believe this is fixed in the latest version of Ubuntu (both 13.04 and
13.10). Please reopen the bug if it isn't. Thanks!
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is
Looking at the latest logs, there are terrible delays, probably for
which we cannot blame the graphics driver.
( 61.711| 0.007) D: [alsa-sink-ALC889 Analog] alsa-sink.c: Expected sleep:
9.27ms, real sleep: 7.91ms (diff -1.36 ms)
( 61.920| 0.204) D: [alsa-sink-ALC889 Analog] alsa-sink.c:
To sum up our IRC discussions, a few things to try are:
- Install precise, verify it's still working correctly
- Upgrade to a raring kernel in precise (install
linux-generic-lts-raring-eol-upgrade and reboot) and see if this causes the
problem to appear
- If not, also upgrade to raring X
dmesg output before reproducing the issue has the following line that looks
suspicious to me:
[13828.248950] hrtimer: interrupt took 15288 ns
It seems a bit suspicious to me too, but 15288 ns = 0.015 ms, which
should not be enough to disturb the overall system latency.
[27622.091908]
While it would be interesting to see if jack detection works differently
if Legacy Front Panel Audio was disabled, it is unrelated to this
issue.
This issue is about when sound suddenly stops to work, and does so for
all output jacks.
--
You received this bug notification because you are a
One thing to check is what's causing the 10 ms system latencies here.
In a root shell, execute this command:
cd /sys/kernel/debug/tracing
echo wakeup_rt current_tracer
echo 1 tracing_on
Run for a minute or two, then
cat trace /tmp/trace.txt
echo 0 tracing on
Then attach /tmp/trace.txt
Hi,
I've made a special build in this PPA:
https://launchpad.net/~diwic/+archive/pulse-timing-test
Once it has finished building, could you try to give me a pulseaudio
verbose log? Try to reproduce the hangout/mumble/skype bug with the
pulseaudio package in this ppa, and the log enabled.
After some debugging on IRC, I'm still not sure what's causing the
problem. We should try a build with DEBUG_TIMING (in module-alsa-sink.c)
on for even more verbose logging in PulseAudio.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
It looks like a transient error. Please try running sudo apt-get update
and then try again. Thanks.
** Changed in: pulseaudio (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Fixed in 3.10
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pulseaudio (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a
The relevant PulseAudio changes are in PulseAudio 4.0 - once we have
released that into Saucy, we should probably SRU those files into 12.04
too.
** Changed in: pulseaudio (Ubuntu)
Status: In Progress = Fix Committed
** Also affects: pulseaudio (Ubuntu Precise)
Importance: Undecided
** Description changed:
Using the phone I've had very few issues till today when I nearly missed
a really import text from my Mom.
The reason I missed it was because the phone didn't ping when the
message arrived as it was in sleep mode.
- This is as far as I can tell a fairly
** Summary changed:
- pulseaudio sets certain input volumes too low
+ [Logitech H800 Headset] pulseaudio sets certain input volumes too low
** Package changed: pulseaudio (Ubuntu) = alsa-driver (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which
Hi Susan,
It looks like you disconnected your headset before filing this bug, so hardware
information about your headset was not included in the bug report. Could you
1) connect your headset
2) turn the microphone gain up and test it and confirm the bug
3) with this configuration, follow
Ok, I can't reproduce it either.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/664061
Title:
Wrong spacing between characters in form fields
Status in “evince” package in Ubuntu:
If it's skype notification sound specific, it's probably bug 1173073.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1190700
Title:
Crackling audio on Ubuntu 13.04 on Lenovo
Marking as fix released as two independent people reported the problem
as fixed.
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Thanks for your report. I don't think this is PulseAudio related. Could
you check your file system for corruption, out of disk space, or
similar?
** Changed in: pulseaudio (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Desktop
** Information type changed from Private to Public
--
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/1074903
Title:
pulseaudio crashed with SIGSEGV in pa_atomic_load()
Status in
Well, was there some error causing pulseaudio to be left unconfigured?
Could you look in e g
/var/log/dpkg.log
/var/log/apt/term.log
/var/log/apt/history.log
...for error messages or anything else that could help us understand why
it was left unconfigured?
--
You received this bug
From windows 7 I found out that realtec ALC662 codec is located at
location 0 on HD Audio bus.
Is there any more information here that could be relevant, such as the
PCI bus address of the ALC662 codec as well as the HDMI codec?
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1169984 ***
https://bugs.launchpad.net/bugs/1169984
** This bug has been marked a duplicate of bug 1169984
3.8.0-18 HDMI/DisplayPort audio regression: Either oops or opening device
fails with -ENODEV
--
You received this bug notification because you
Is the problem that the recording is extremely noisy, or that it is
completely silent? Or do you get error messages when trying to record?
In case it's noisy, maybe you can try going into alsamixer and reducing
Internal Mic one or two steps and see if it makes a difference?
--
You received this
The analog audio does not show up at all, it's not being probed
correctly.
First try the latest drivers:
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS
If this does not help, with the drivers installed also try add the
following to /etc/modprobe.d/alsa-base.conf :
options snd_hda_intel
I tried the latest alsa but no luck. It still does not work.
Perhaps the hardware is broken? Have you tried it under Windows (and if
so, it could be good to know if it required extra drivers to work)?
--
You received this bug notification because you are a member of Desktop
Packages, which is
@Raymond, please don't pollute this bug with other bugs. Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/978370
Title:
[soundnua]: S/PDIF and IEC958 are used
** Summary changed:
- No sound on laptop
+ [Asus W7J] No sound on laptop
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1178897
Title:
[Asus W7J] No sound on laptop
Status in
(bug
#299578), as it seems it should be reported upstream, specifically to
David Henningsson.
Using a Gigabyte z77x-ud5h motherboard, you can only hear sound when plugging
a jack cable in rear, c/sub or side jack, but not if it's in the usual green
out one.
Having tried all the output
Thanks Marcelo,
When looking at the output from 13.04, you seem to have forgotten to
turn up the microphone gain. Also you seem not to have done any
recording test before running alsa-info on 13.04.
('Capture' and 'Internal Mic' gain are both at minimum values.)
Anyway, assuming you've tried
Hi daniele,
Is it both internal mic and external mic (plugged into the jack) that is
not working? If it's only internal, try the Inverted internal mic
suggestion here:
http://voices.canonical.com/david.henningsson/2012/05/22/three-audio-
bugs-in-12-04/
--
You received this bug notification
Hi,
Could any of you affected by this bug do the following:
1) Boot 12.10, e g from a live-CD if you don't have it installed any more,
confirm that the internal mic is working, then run alsa-info (
https://wiki.ubuntu.com/Audio/AlsaInfo ).
2) Boot 13.04, confirm that the internal mic is no
Hi, I've backported a fix which might or might not help this problem,
I'm not sure. I've put it up at https://launchpad.net/~diwic/+archive
/pulseaudio-testing where it's currently waiting to build. Can you
please try it (ensure that you're running pulseaudio version
1:3.0-0ubuntu6.1~diwicppa )
** Description changed:
[Impact]
jackd (jackd2) is unable to start when trying to acquire the same audio
device used by pulseaudio. (jackd1 is currently not able to acquire the
card through dbus).
Users are often unable to use jack at all, without disabling pulseaudio.
[Test
Good question. I guess it would be good to have dmesg output from the
instant when this is connected and you try to record, but I'm not sure
if that will lead anywhere.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
Seems to be a kernel/driver related problem:
[43751.609481] xhci_hcd :02:00.0: ERROR: unexpected command completion code
0x11.
[43751.609483] usb 3-2: Not enough bandwidth for altsetting 1
[43751.609484] 4:2:1: usb_set_interface failed (-22)
Unfortunately one cannot tell from the dmesg if
Thanks, have you also tested the final built branches so you know that
this is what is required to fix the problem?
--
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/1163638
Title:
Fixed in raring/saucy, right?
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: pulseaudio (Ubuntu Precise)
Status: New = Incomplete
** Changed in: pulseaudio (Ubuntu Quantal)
Status: New = Incomplete
--
You received this bug notification
Public bug reported:
As you can see on the attached screenshot, there are two identical
checkboxes both saying Use your mobile phone as a network device
(PAN/NAP). I expected either just one checkbox, or some additional
description telling what the difference between them are.
This happened
** Attachment added: Screenshot from 2013-05-21 15:20:49.png
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1182469/+attachment/3682924/+files/Screenshot%20from%202013-05-21%2015%3A20%3A49.png
** Description changed:
As you can see on the attached screenshot, there are
Merged, but not yet uploaded.
** Changed in: pulseaudio (Ubuntu Precise)
Status: Incomplete = Fix Committed
** Changed in: pulseaudio (Ubuntu Quantal)
Status: Incomplete = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is
I've already added Enable=Socket in /etc/bluetooth/audio.conf,
without that I can't pair my headset.
I can confirm that PulseAudio as of 13.04 does not work with
Enable=Socket. This is IMO a bug on the bluez side.
From what I've been told by the bluez people, the socket interface is
deprecated
401 - 500 of 888 matches
Mail list logo
