Mixer issues: please file a report if you are affected

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have just sent the following instructions to everyone who sent an
email to this list, or to -test-list, indicating they are suffering from
a manifestation of the bug whereby the simple PulseAudio-implemented
'Volume' control in gnome-volume-control cannot properly control their
volume. I'm also sending it to the lists to catch anyone I missed, or
who didn't post about it but nevertheless is suffering. If you are
suffering from this issue - if g-v-c does not properly control your
volume and you have to use alsamixer to get output at a usable level
(*not* if you need alsamixer to switch input devices or set input
volumes, at least not for now) - please file a report according to these
instructions. Thanks.

We're trying to get these kinds of bugs fixed. It would be very helpful
if you could file a bug at http://bugzilla.redhat.com , on the
pulseaudio package in Rawhide. Please include the following information.

1. Attach the file /tmp/alsa-info.txt, after running 'alsa-info.sh
--no-upload'

2. To find out exactly what you had to change to control your volume,
please do this, as root:

alsactl init
amixer -c0 > amixer_before.txt

Now verify that your problem exists again. Then run a mixer and make the
changes you have to make to 'resolve' your problem. Then go back to
running commands:

amixer -c0 > amixer_after.txt
diff -u amixer_before.txt amixer_after.txt > amixer_diff.txt

Then attach the file 'amixer_diff.txt' to the bug report. The commands
above assume the important sound device is card #0 in the output of
'cat /proc/asound/cards' . If this is not the case, change -c0 in each
of the above commands to -cN, where N is the actual number of the
important device in 'cat /proc/asound/cards' - for instance, if it's
card number 2 in that list, change all -c0 to -c2 .

3. Also please include an exact description of the problem, including
how your card behaves before the problem is fixed, how it behaves after
the problem is fixed, and information on your actual sound output device
- are you using a simple pair of computer speakers? Internal speakers on
a laptop? Headphones? A digital S/PDIF connection to an external
decoder?

Once you have done this, please let me know the number of your bug
report. We will then work to make sure as many of these bugs are
resolved as possible. You may be contacted for further information, or a
confirmation of the fix, on the bug report, so please keep an eye on it
after filing. Thanks very much for your help!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net

-- 
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux