[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
h
Ursula,
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any
(attaching alsamixer card-views, per last comment)
** Attachment added: "card-0_vs_card-1_top-vs-bottom.png"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1223592/+attachment/4748140/+files/card-0_vs_card-1_top-vs-bottom.png
--
You received this bug notification because you are a
Sorry, I failed to mention in comment #9 that the actual *problem* is I
no longer hear any audio, and no longer have microphone access. Another
screenshot attached (of sound settings UI - upon initial installation,
this was non-empty).
Here's my current output for `grep "Codec:" /proc/asound/card*
disclaimer: I'm trying to confirm if this affects me (so, please chime
in if someone reading this can point me elsewhere or confirm)...
I found on initial install - of Ubuntu 16.04, on Samsung ATIV 9, 12inch
laptop - that audio/mic. worked perfectly without issue. Now, since
multiple boots and upd
This is still an issue that affects me. Right now I have no audio
despite a power cycle. Pulse audio seems to think the HDMI is still
plugged in and no amount of futzing seems to change the state. Is there
a better place to submit this bug? I'm relatively new to Ubuntu /
Linux.
--
You receive
6 matches
Mail list logo
