Bug 295691
Summary: | KDE Sound server (artsd), signal 11, SIGSEGV | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James Cooper <jmichc> |
Component: | arts | Assignee: | Than Ngo <than> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | jks, rdieter, twegener |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-04-25 04:37:56 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
James Cooper
2007-09-19 01:38:31 UTC
rpm -q arts please I can't start arts either. I don't know if it is the same problem the OP had. [jks@jks-desktop ~]$ artsd *** PULSEAUDIO: Unable to connect: Connection refused Error while initializing the sound driver: device: default can't be opened for playback (Connection refused) [jks@jks-desktop ~]$ rpm -q arts arts-1.5.8-4.fc8 arts-1.5.8-4.fc8 Joseph, you're having a separate problem (arts not crashing but pulseaudio not being able to open/initialize the audio device). Do you have kde-settings-pulseaudio installed? If not, you need it. Thanks, installing kde-settings-pulseaudio solved my problem. It should probably be required for all kde installs. fwiw, it's the default (ie, included if you 'yum groupinstall kde-desktop'), but not required so that it's optional (ie, folks can opt-out of pulseaudio support if they so choose). The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there have not been any updates to the report since thirty (30) days or more since we requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance. Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9. |