Bug 389681
Summary: | pulseaudio does not play (nice) with isa sb16 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adam Pribyl <covex> |
Component: | hal | Assignee: | David Zeuthen <davidz> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | mclasen, pierre-bugzilla |
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: | 2007-11-30 18:03:26 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
Adam Pribyl
2007-11-18 19:46:09 UTC
The problem seems to come from hal. Because lshal does not lists all appropriate components: lshal | grep alsa udi = '/org/freedesktop/Hal/devices/computer_alsa_timer' alsa.device_file = '/dev/snd/timer' (string) alsa.type = 'timer' (string) info.capabilities = {'alsa', 'access_control'} (string list) info.category = 'alsa' (string) info.udi = '/org/freedesktop/Hal/devices/computer_alsa_timer' (string) udi = '/org/freedesktop/Hal/devices/computer_alsa_sequencer' alsa.device_file = '/dev/snd/seq' (string) alsa.type = 'sequencer' (string) info.capabilities = {'alsa', 'access_control'} (string list) info.category = 'alsa' (string) info.udi = '/org/freedesktop/Hal/devices/computer_alsa_sequencer' (string) For that reason it also does not change the device permissions and users do not have access to them. This was revealed when I removed alsa-plugins-pulseaudio. However the pavucontrol still sigsegvs, so there is still some problem with pulseaudio too. pavucontrol has a bug which causes it to segfault when no sound card has been identified. See http://pulseaudio.org/ticket/172 This will be fixed shortly upstream. You say the device is properly identified by the kernel but HAL doesn't find it? This is most likely an issue in the kernel driver, and probably similar to the issue described in #370821. I am reassigning this issue to HAL now. David will probably be able to tell you quickly if this issue is the same as #370821. Please paste the outputs of "tree" here, similar to those posted in that bug report. I will ping the guys on the ALSA ML about this, too. |