@Colum, thanks - from the log we can see that module-bluetooth-discover
is unloaded manually. The program unloading it is python2.7 which
unfortunately does not tell us exactly from where this comes, just that
it is some software written in python...
May 13 19:58:09 gaynor-F1-22PTV1
@Colum, thanks. Could you try the following:
edit /etc/pulse/default.pa and above the line that says ### Automatically load
driver modules for Bluetooth hardware, add a line with this text:
set-log-level 4
Reboot your computer and confirm that the bug is still present. Then do a
grep pulseaudio
Do you have updated packages to try?
Good point. I won't have time to update them today. Please remind me in
a few weeks if I haven't done it by then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Today's status:
- alsa-lib patches for adding the surround21:x name is upstream. There has not
been an upstream release of alsa-lib since.
- pulseaudio patches are not yet upstream. But I found that the problem might
be more complex than first expected.
1) It's easy just to add another
Could you please consider to reverse the status back from
'INCOMPLETE' to 'CONFIRMED' (again).
I will do so for PulseAudio if I get the requested information, which
is:
if you can verify that module-bluetooth-discover is indeed *not* loaded (i e
does not show up in pactl list modules),
Ok, I first did a quick test here and my BT headset paired, showed up in
sound settings, worked as usual, and profile was selectable. So at least
the problem is not *that* generic.
Anyway, module-bluetooth-discover is loaded from /etc/pulse/default.pa,
which is run every time pulseaudio starts.
Ok, so this is several bugs in one then...
pulseaudio[1928]: [pulseaudio] module-bluetooth-device.c: Failed to
acquire transport /org/bluez/716/hci0/dev_00_0C_55_D1_91_ED/fd0
For this error, if it appears when you're trying to switch to the
headset, it looks like something on the bluez side.
Apr 29 09:06:52 Voyager kernel: [ 2013.010319] Bluetooth: re-auth of legacy
device is not possible.
Apr 29 09:06:55 Voyager bluetoothd[716]: Protocol not supported (93)
This indeed looks like the kernel is at fault. I don't know much
bluetooth (I'm more into the audio side of things), so
Crash is fixed upstream:
commit ada83601f04f73177ea5f8bda01f02a38ba55409
Author: Tanu Kaskinen tanu.kaski...@linux.intel.com
Date: Thu Jul 11 13:35:24 2013 +0300
module: Fix crash in pa_module_unload_all()
If this bug hits many people, we should consider cherrypicking it and
make an SRU
I can confirm the workaround in comment #2 works for me.
Also, I have a hard time reproducing this. It seems to happen every now
and then but not when you try to reproduce it.
Anyway, I noticed something else. This also happened on the lock screen,
and when I logged in I noticed my login
I've now committed the patch to PulseAudio git - thanks for testing!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256511
Title:
Sounds settings lost after reboot
To manage notifications about
** Changed in: alsa-lib (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1286021
Title:
2.1 surround support (userspace)
To manage notifications
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254745
Title:
[Z35HL, Realtek ALC660, Green Line Out, Rear] No sound at
Public bug reported:
Steps to reproduce:
Execute gnome-session-quit --reboot and notice a Log out dialog.
Expected a Reboot dialog.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-session-bin 3.9.90-0ubuntu12
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1285179
Title:
pulseaudio does not remember the audio level for usb audio
Yup, got that too. It's fixed in systemd 204-5ubuntu17.
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed = Fix Released
** Package changed: pulseaudio (Ubuntu) = systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
;
}
but it has stopped working on startup. The reason is this commit:
commit 0b83787d4e844f47affbc903d97b0ca69e234570
Author: David Henningsson david.hennings...@canonical.com
Date: Tue Apr 16 15:17:37 2013 +0200
alsa: Initialize ports before sinks/sources
...this causes the current profile
Okay, I wrote a patch, but haven't tested it myself, anybody who wants
to test it?
http://lists.freedesktop.org/archives/pulseaudio-
discuss/2014-March/020294.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With all due respect, I want to report a bug in ALSA, and I don't understand
how joining a developers mailing list will further
that goal.
Well, if you want the bug fixed (and not only reported), go where the
developers are.
The initial link I was given
** Summary changed:
- pulse audio
+ pulse audio crashed in pa_thread_mq_get
** Summary changed:
- pulse audio crashed in pa_thread_mq_get
+ pulseaudio crashed in pa_thread_mq_get
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Setting to incomplete while waiting for someone to test the patch.
** Changed in: pulseaudio (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1227769
Title:
Hi,
You have filed this bug in the Ubuntu bugtracker, but you don't seem to
be running Ubuntu. Is this a problem in Ubuntu 14.04 as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296017
Title:
I was sent here by people who know WAY more than I about Linux. They stated
my issue was occurring at the driver level, and so
get thee to the ALSA people was my instruction.
The ALSA people are here: http://mailman.alsa-
project.org/mailman/listinfo/alsa-devel
--
You received this bug
Hi,
This is a feature, not a bug. Regardless of your phone's capabilities,
your computer cannot distinguish between headphones and headsets, which
is why we ask you.
You might be helped by this article:
http://voices.canonical.com/david.henningsson/2014/03/07/headset-jacks-
on-newer-laptops/
**
It's most definitely a kernel bug. Also, I looked at both 1294729,
1293828 and 1286866 and all of them refer to the ICE1712 driver.
A recent commit that affects ICE1712 is this one:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
trusty.git;a=commit;h=25cb36334e92312684f5cc18bfcf1eb96eb00485
Public bug reported:
If indicator-sound is not installed, the command unity-control-center
sound will crash with Settings schema 'com.canonical.indicator.sound'
is not installed and then a SIGTRAP.
Either unity-control-center should hard depend on indicator-sound or
unity-control-center needs
FWIW, I agree with UserError that it is bloat, but as Luke points out, we
should probably fix this in Debian rather than to introduce a delta.
I'm not sure if 200k bloat even counts as a bug, so setting to Wishlist
priority.
** Changed in: alsa-lib (Ubuntu)
Importance: Undecided = Wishlist
** Patch added:
0001-sink-source-Initialize-port-before-fixate-hook-fixes.patch
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1289515/+attachment/4035418/+files/0001-sink-source-Initialize-port-before-fixate-hook-fixes.patch
--
You received this bug notification because you are
read volume/mute for the correct port.
BugLink: https://bugs.launchpad.net/bugs/1289515
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
src/pulsecore/sink.c | 11 +++
src/pulsecore/source.c | 11 +++
2 files changed, 22 insertions(+)
diff --git a/src
I was able to see something similar on the desktop, and came up with a
patch to fix it. Can you test it and see if it resolves your problem as
well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
u-c-c, I think, but it's not that high priority since PulseAudio usually
does not restart itself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1286084
Title:
unity-control-center crashed with
Setting to incomplete while waiting for answer to comment #2
** Changed in: unity-control-center (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289917
Title:
Thanks for the patch!
With this version, the problem has changed.
No longer do we wait indefinitely for the erasing button do become
clear, but when it is finished, the amount of free space is reported as
0.0 B, and you still can't continue to the next step (i e create the
USB disk), because the
Hi Martin / Dominik,
Just moving /usr/sbin/alsactl to /sbin/alsactl probably won't work, as
alsactl uses stuff from /usr/share/alsa/init/* , and as already pointed
out, there is also /var/run/* stuff that gets stored.
But can somebody point me to the set of rules here? I mean, what rule
says
Btw. There was something tricky about this. Like, if the sound card gets
discovered before /usr, then alsactl would run as an upstart or systemd
job. But if /usr gets mounted before the sound card (e g on hotplugging
a USB headset), then the udev rule would run alsactl instead.
Does this make
Public bug reported:
I first successfully burned two big files to a DVD. I then removed one
of the files and added a third file in its place. When trying to burn
the second DVD, I noticed that the four options were suddenly gone (see
screenshot).
ProblemType: Bug
DistroRelease: Ubuntu 14.04
** Attachment added: brasero.png
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1290065/+attachment/4015204/+files/brasero.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290065
Title:
Public bug reported:
When first booting this machine with daily 14.04, keyboard does not
work. You can't enter password or select a different user.
However, you can work around this by using the mouse to start a guest
session. After logging out the guest session, keyboard works as
expected.
From what I can tell (looking at the source code), this is fixed in
Ubuntu 14.04.
** Changed in: libav (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
See screenshot - I was about to erase a disk so I could make a new live
USB disk, and I've been waiting a few minutes now (it ususally finished
in a few seconds). The erasing button is grayed out and the animation
is running constantly.
ProblemType: Bug
DistroRelease: Ubuntu
** Attachment added: usbcreator.png
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1289269/+attachment/4011499/+files/usbcreator.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After restarting usb-creator, the disk shows having correct amount of
free space. However trying to create a startup disk immediately fails
with Installationen misslyckades (means installation failed).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Trying to start usb-creator with this command: LC_ALL=C usb-creator-
gtk fails with the following error message:
An unhandled exception occurred:
'ascii' codec can't encode character '\xe4' in position 13: ordinal not in
range(128)
ProblemType: Bug
DistroRelease: Ubuntu
Public bug reported:
When trying to create a usb startup disk, it immediately fails with an error
message translating to 'Installation failed' (in both window caption and text).
Btw, I notice that a /dev/loop device is created (and not cleaned up) every
time this happens.
ProblemType: Bug
Volumes for music and phone calls are stored independently. Volume
returns to what it was before the phone call, regardless of how you
adjusted the volume during the phone call. Is this not the case?
** Changed in: pulseaudio (Ubuntu)
Status: New = Incomplete
--
You received this bug
Sound volume, and the primary sound output, should be global settings.
Other settings should be specific to individual user accounts.
Assuming other settings mean all other sound related settings, does
this mean that the primary sound *input* should be handled differently
than the primary sound
Public bug reported:
If another window is on screen, sometimes the what-did-you-plug-in
dialog is popped up *behind* this window, causing the user not to see
the dialog.
** Affects: unity-settings-daemon (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status
** Branch linked: lp:~diwic/unity-settings-daemon/lp1287584
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287584
Title:
what-did-you-plug-in dialog pops up behind other windows
To manage
Note: as of Ubuntu 13.10, hda-jack-retask is part of alsa-tools. Just
install the alsa-tools-gui package from the regular archive and start
hdajackretask. (Note: if you don't have a .pulse directory, try
symlinking .pulse to .config/pulse - and remove the symlink again when
you have closed
** Changed in: pulseaudio (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1159687
Title:
[USB-Audio - Logitech B530 USB Headset, recording]
Public bug reported:
2.1 surround should work as seamlessly as other surround options, such
as 4.0, 5.1 and 7.1 work today.
** Affects: alsa-lib (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status: In Progress
** Affects: pulseaudio (Ubuntu
** Summary changed:
- 2.1 surround support in userspace
+ 2.1 surround support (userspace)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1286021
Title:
2.1 surround support (userspace)
To manage
** Description changed:
2.1 surround should work as seamlessly as other surround options, such
as 4.0, 5.1 and 7.1 work today.
+
+ Alsa-lib and pulseaudio patches for 14.04 can be tested here:
+
+ https://launchpad.net/~diwic/+archive/surround21
** Changed in: pulseaudio (Ubuntu)
Thanks for the log - it looks like the error is with the channel matrix:
Here's where it does not work, i e, no sound sent to O02 and O03:
( 39.718| 0.000) D: [pulseaudio] resampler.c:I00 I01
( 39.718| 0.000) D: [pulseaudio] resampler.c: +
( 39.718| 0.000) D:
A small but (I hope) helpful tip to compile pulse
To install current build dependencies do:
sudo apt-get build-dep pulseaudio --no-install-recommends
When I use the upstream git version of PulseAudio I follow this guide
for how to set it up: http://colin.guthr.ie/2010/09/compiling-and-
Okay, found it. So, to enable the subwoofer for non-subwoofer source material
(such as a stereo source), you need to set
enable-lfe-remixing = yes
in /etc/pulse/daemon.conf
And the fact that LFE remixing was suddenly enabled by switching profiles was a
bug, sent a patch here:
Just a heads up that the userspace improvements to 2.1 surround can now be
tested in 14.04 by adding this ppa:
https://launchpad.net/~diwic/+archive/surround21
(and rebooting afterwards).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi,
Just a heads up that the userspace improvements to 2.1 surround can now be
tested in 14.04 by adding this ppa:
https://launchpad.net/~diwic/+archive/surround21
(and rebooting afterwards).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
If a stream is started corked and remains corked, the sink/source
remained idle without being properly suspended. This patch fixes
that issue.
BugLink: https://bugs.launchpad.net/bugs/1284415
Tested-by: Ricardo Salveti ricardo.salv...@canonical.com
Signed-off-by: David Henningsson david.hennings
The functionality has been merged now, although I'm not sure when 14.04
will switch from gnome-settings-daemon to unity-settings-daemon.
** Changed in: unity-settings-daemon (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of
Actually, as of today ( version 14.04.0+14.04.20140219-0ubuntu1 of
unity-settings-daemon ) this functionality is released into 14.04
(ubuntu-desktop depends on unity-settings-daemon ).
** Changed in: unity-settings-daemon (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this
Note that for 12.04 based preinstalls, the functionality is shipped in
the separate what-did-you-plug-in package instead of together with
unity-settings-daemon.
Support for stock 12.04 is not planned. Source for OSP2 is here:
https://code.launchpad.net/~diwic/+junk/what-did-you-plug-in
**
- [quite annoying] when I use rhythmbox or banshee, I ALWAYS have to resetup
mode in the sound settings panel or the
subwoofer won't work. When I say always, I mean between each song! So I have
to set mode to anything else than Analog
surround 2.1 and then back to Analog surround 2.1...
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1131220
Title:
[soundnua]: gnome-control-center crashed with
pulseaudio[2048]: [pulseaudio] alsa-mixer.c: Assertion 'eb = p2-elements'
failed at modules/alsa/alsa-mixer.c:3191, function
path_set_condense(). Aborting.
This bug is fixed in later PulseAudio versions (4.0+). I think you can
work around it for now by only specifying one path on the
Hi, while going through old bugs I forgot about (sorry!) I noticed that
alsa-info has been supplied for UX51VZH and N55SF, so I sent these
upstream. If you want me (or someone else) to send your quirk upstream
as well, please submit alsa-info (
https://wiki.ubuntu.com/Audio/AlsaInfo ).
Well, upstream now has a subwoofer quirk for your machine, so this
should fix the alsa level if you install the latest drivers (
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS ).
Then the PulseAudio stuff remains, where my recommendation is to add the
stuff as suggested here:
So it's just a matter of backporting
http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=83b26046fcce5f497042fd7c5d7ae6904d7b76e1;hp=0ca4414d0f3eeb39bbad504eaaae76d40b7189cc
(and possibly
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1040873
Title:
[N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at
I mean, what application are you using that appears to be benefiting
from an echo canceler? Some VOIP software I assume? Is the application
using an echo canceler by default, or do you have to load it manually
somehow?
--
You received this bug notification because you are a member of Ubuntu
Pushed to branch, waiting for upload...
http://bazaar.launchpad.net/~ubuntu-audio-dev/alsa-tools/ubuntu/revision/34
** Changed in: alsa-tools (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@Po-Hsu Lin: if outputs show up even when they are not connected, I'd
say it could be a bug, but not a serious one.
- Line out jacks do not have jack detection in 12.04, because it is not
enabled in PulseAudio. This should be fixed/improved in 14.04.
- Some hardware does not support jack
** Changed in: hwe-next
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169143
Title:
Headset support on some Dell machines
To manage notifications about
https://code.launchpad.net/~diwic/gnome-settings-daemon/what-did-you-
plug-in/+merge/204680
** Changed in: pulseaudio (Ubuntu Precise)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For jack detection issues, there are a few levels of checking:
1) Ask a direct verb using hda-verb or hda-jack-sense-test
2) Check the mixer control (amixer contents)
3) Check the availability status in pulseaudio (pactl list cards)
Depending on where the jack event gets lost the cause is
Please note that if you don't have any input device actually connected,
there shouldn't be any device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1264964
Title:
[Dell Optiplex 9020SFF] No audio
From: Niraj kulkarnini...@rediffmail.com
Apparently this board seems to need some extra initialization before a proper
codec probe value can be read.
BugLink: https://bugs.launchpad.net/bugs/1155202
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/hda_intel.c
On 01/22/2014 12:40 PM, Takashi Iwai wrote:
At Wed, 22 Jan 2014 12:32:28 +0100,
David Henningsson wrote:
From: Niraj kulkarnini...@rediffmail.com
Apparently this board seems to need some extra initialization before a proper
codec probe value can be read.
BugLink: https
how do I apply this patch on PC?
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211920
Title:
Low audio output / missing subwoofer on Vostro
Anyway. Any of those things sound like a good plan?
Answered in private
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1131220
Title:
[soundnua]: gnome-control-center crashed with SIGSEGV in
Quantal is quite old by today's standards. That said, it does seem to be
a bug in PulseAudio, as there is a Speaker Phantom Jack on ALSA level
but no analog-output-speaker port on PulseAudio level. A PulseAudio
verbose log might help to figure out what the cause is:
Ok. So to try to get this into upstream, you need to test this with the
latest upstream driver, and I need to know *where* this code was added,
too.
So, the patch needs to apply to:
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/sound/pci/hda/hda_intel.c
This code is the same
There seem to be more than one problem with the a52 plugin. See also bug
1241439
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242390
Title:
ac-53 (a52 plugin) core dumps
To manage notifications
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248116
Title:
[Gigabyte Z87X-UD3H] PulseAudio switch rapidly port making the
** Changed in: alsa-driver (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168736
Title:
Crash in Firefox P5L-MX, Analog Devices AD1986A, Green Line Out,
I was able to reproduce this one today. The port switch (to headphones)
is failing on kernel level with the following message: Slim close tx/rx
wait timeout (and subsequent follow-up errors).
I suspect another 'feature' of Qualcomm's kernel driver is that you
can't switch ports while PCMs are
Added a completely untested patch here:
http://bazaar.launchpad.net/~diwic/pulseaudio/lp1227769/revision/610
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1227769
Title:
[mako] No audio in the
Hi.
Due to the security concerns (and disk space) of bringing a new package
into main, and due to low demand, I've skipped the webrtc echo canceller
so far. But I don't mind adding it if someone has a practical use case
for it?
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed =
** Summary changed:
- PulseAudio switch rapidly port making the sound horrible
+ [Gigabyte Z87X-UD3H] PulseAudio switch rapidly port making the sound horrible
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
: (unassigned) = David Henningsson (diwic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248116
Title:
[Gigabyte Z87X-UD3H] PulseAudio switch rapidly port making the sound
horrible
To manage
Why is this marked Incomplete ?
Is there anything you need from me ?
It sounds like it could be hardware failure, could you rule this out by
e g booting a live-CD and see if speakers work there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Summary changed:
- valgrind aplay -L prints scary warnings
+ segfault in namehint API (valgrind aplay -L prints scary warnings)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008600
Title:
Cool stuff. I've never looked at PCI IOMMU traces before.
I don't see anything obvious when looking at those traces though, so
we're probably looking at some type of chipset bug here.
I guess we're down to trial and error then? I e, try random changes to
stuff that win7 does but we don't (or the
** Changed in: linux-lts-raring (Ubuntu Precise)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1249956
Title:
External microphone cannot be detected
To manage
** Changed in: linux (Ubuntu)
Assignee: David Henningsson (diwic) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132562
Title:
[Acer AO751h] choppy sounds, lots of rewinds
Lowering severity due to
- not many machines/people affected
- workaround available (comment #5)
** Changed in: alsa-driver (Ubuntu)
Importance: Undecided = Low
** Changed in: pulseaudio (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member
** Summary changed:
- no sound/audio, traps: pulseaudio[25921] trap divide error ip:7fe46a303a57
sp:7fff825b91d0 error:0 in libavutil.so.51.22.1
+ [a52 plugin] no sound/audio, traps: pulseaudio[25921] trap divide error
ip:7fe46a303a57 sp:7fff825b91d0 error:0 in libavutil.so.51.22.1
**
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231496
Title:
pulseaudio crashed with SIGABRT in output_free()
To manage notifications about this
** Changed in: alsa-driver (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211920
Title:
Low audio output / missing subwoofer on Vostro 5460/5470
So, I installed the stuff from my own ppa, in the hope that it would
also crash and so I could track the problem down. Unfortunately, it
didn't, it ran as good as always.
In addition, the pactl list command does not show anything really out of
the ordinary. I was expecting it to show a
401 - 500 of 4719 matches
Mail list logo
