[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Thank you for reporting this bug to Ubuntu.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: pulseaudio (Ubuntu)
Status: Ne
Sorry for the confusion - but please forget about my comment #10. I
actually missed that manipulating settings in ~/.pulse/default.pa had
silently changed the output device without giving me notice. With the
correct device, control=PCM does the trick and restores proper function
of the volume contr
Well, actually I've just tested linux-backports-modules-alsa-lucid-
generic, but to no effect - neither media keys nor the volume panel
applet change any channel at all. Installing the package also had a
strange side-effect; seems it removed the network manager applet from
the panel and replaced it
Please test linux-backports-modules-alsa-lucid-generic.
--
Only first 20% of the volume slider works
https://bugs.launchpad.net/bugs/571987
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Same problem here (VT1708S); both suggestions from the Ubuntu Wiki
mentioned above don't work. After deleting ~/.pulse/default.pa (i.e.,
resetting everything to default), trying to change the volume by media
keys or the panel applet has no effect at all anymore. Seems there is
something severely br
(Clarification: when pavucontrol causes everything to mute, above, it's
not actually muting the alsa channels: it just causes no sound to come
out, and no amount of playing with the volume gets it back.)
--
Only first 20% of the volume slider works
https://bugs.launchpad.net/bugs/571987
You recei
I can't, in alsamixer with pulseaudio, I can't modify PCM. It jitters
between 100 and 97, whenever it flicks from 97 to 100, 'front' goes down
a notch. Note that changing front from 0 to 100 is a good range, but
that only corresponds to about 20% in the pulseaudio slider.
A combination that almost
Hmm. How about this:
1) First, change all levels at alsamixer (i e alsamixer -c0 in a terminal) to a
setting that you like.
2) Figure out which one of the alsamixer controls you would like to have
pulseaudio control for you.
3) Add that control (PCM, Master Front, Headphones etc) to the pulseaudi
Oh, by 'volume to be fixed' I mean 'unchangable', not 'repaired'.
--
Only first 20% of the volume slider works
https://bugs.launchpad.net/bugs/571987
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Adding 'ignore_dB=1' caused the volume to be fixed, and pa couldn't
change it at all. Adding control=PCM caused there to be no sound
produced. So, neither were fixes.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => New
--
Only first 20% of the volume slider works
https://bugs.lau
Please check this:
https://wiki.ubuntu.com/DebuggingSoundProblems/KarmicCaveats#Volume%20range%20anomalies
(that section applies to Lucid as well) and report back whether it
worked or not.
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
** Tags added: regression-release
--
O
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/46436367/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/46436368/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/46436369/BootDmesg.txt
** Att
13 matches
Mail list logo
