Bug 521735
Summary: | 9/7 PulseAudo Update; now bork on alsa-sink.c | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bob Agel <cragel> |
Component: | pulseaudio | Assignee: | Lennart Poettering <lpoetter> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 11 | CC: | lkundrak, lpoetter, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-10-14 22:05:32 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bob Agel
2009-09-08 01:37:13 UTC
Very interesting! Today, the only update was kmod-nvidia, yet now pulseaudio is working perfectly: Sep 8 19:26:50 localhost dbus-daemon: Rejected send message, 2 matched rules; type="method_call", sender=":1.33" (uid=42 pid=1995 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="org.bluez.Manager" member="ListAdapters" error name="(unset)" requested_reply=0 destination="org.bluez" (uid=0 pid=1590 comm="/usr/sbin/bluetoothd ")) Sep 8 19:26:50 localhost pulseaudio[1995]: bluetooth-util.c: Error from ListAdapters reply: org.freedesktop.DBus.Error.AccessDenied Sep 8 19:26:54 localhost gnome-session[2013]: WARNING: Could not parse desktop file /home/bob/.config/autostart/xfconf-migration-4.6.desktop: Key file does not have key 'Name' Sep 8 19:26:54 localhost gnome-session[2013]: WARNING: could not read /home/bob/.config/autostart/xfconf-migration-4.6.desktop Sep 8 19:26:56 localhost kernel: fuse init (API version 7.11) Sep 8 19:26:57 localhost pulseaudio[2188]: pid.c: Daemon already running. Yesterday, without corresponding kmod-nvidia to the new kernel, akmod-nvidia was providing 3D. Doubt this could have a bearing, but it's the only change. Ooops! Sorry; it's not fixed. My volume slider was reset to 50% which resulted in 'normal' sound from Streamtuner, but no sound at all in games/online music. Once slider was increased to audible level (100%) to hear other sounds, the static returned and the adjustment (reducing to 95% and then increasing to 100%) was necessary to return to 'normal' sounds. Uh, percent base volumes don't really have any meaning. And what PA understands under "50%" is very different from what ALSA understands under it. Is it possible that you have some kind of alsa-based mixer tool running that interferes with pa's volume handling? Which tools did you use to look at the volume settings? Just alsamixer -c0 No, there's nothing else involved. I haven't added anything except for running much of what's included in http://www.dnmouse.org/autoten.html (codecs) Now, I don't know what Dangermouse has included in "most codecs" so I suppose there's a chance that something there has interfered. So you only ever looked and changed alsamixer -c0? Didn't use gnome-volume-control or its applet, or the Gnome hotkeys? Most likely this is just a misunderstanding how the new mixer handling works: PA exposes a single slider that controls all mixer elements that are in the pipeline from the PCM stream to your speakers. For that we multiply the actual volume factors of each element. When setting the volume we go from the "outermost" (usually "Speaker" or "Master") to the "innermost" (usually "PCM") and try to configure exactly what the user asked for. That means the biggest volume change wil be done with the outermost slider while the inner sliders are usually fixed to something near 0dB. Unless the dB scales on the various elements are incorrect this means that you get the best quality possible, with the largest range and finest granularity the hw can provide. Then, on top of that we extend the range and granularity further in sw if the hw is too limited. Now, the effect is that if you touch any of the volume tools that use PA the entire pipeline of elements in the alsa mixer will be changed. Could that explain what you are experiencing? Certainly it's possible, although prior to the update everything was working correctly with the settings that I've shown. Unfortunately for further testing, I'm headed out this morning for a 2 week vacation and won't be back until 10/5 at the earliest. So, thanks for your time and efforts to date and I'll see if anything new occurs when I return. Closing due to lack of response. Feel free to reopen if you can provide more data. I must apologize for not following-up on this after vacation. However, I've found that the problem seems to be related to Streamtuner and using Xmms. When changing streams, any new stream comes in at max volume, while the rest of the system is behaving properly now. So, since Xmms is not the default app for Streamtuner, I'll do some modifications on my own. Again, apologies and thanks for your efforts. |