Bug 735908
| Summary: | Audio device doesn't work in KDE | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Slawomir Czarko <slawomir.czarko> |
| Component: | kdemultimedia | Assignee: | Than Ngo <than> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | jreznik, kevin, ltinkl, rdieter, rnovacek, smparrish, than |
| 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: | 2012-08-07 19:02:47 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
Slawomir Czarko
2011-09-06 06:44:13 UTC
Are you using PulseAudio? If you aren't, there's the problem. (Only one application can access the sound device at a time without PulseAudio, so if any other application is using it, the KDE notification system cannot use it.) If you are using PulseAudio, then you probably have some other application trying to talk directly to the hardware device instead of using PulseAudio, thereby not allowing PulseAudio to access it. Make sure alsa-plugins-pulseaudio is installed. maybe there's a pulse autostart race. Does doing a: pulseaudio --kill in the case where things don't work, help any? alsa-plugins-pulseaudio is installed How can I find out if I'm using PulseAudio? In case it matters, when I login KDE starts these programs: - skype - pidgin - konsole - VMplayer - chrome - dropbox - kwallet I'll try "pulseaudio --kill" next time it happens. (In reply to comment #2) > maybe there's a pulse autostart race. > > Does doing a: > > pulseaudio --kill > > in the case where things don't work, help any? Autostart race could be what's happening. I noticed that the problem happens usually when I login first time after reboot. If I then log out and login again usually it doesn't happen. pulseaudio --kill doesn't help Today I actually got a different situation: - I reboot the machine and log in - the message about not working playback device appears - BUT the login sound plays normally - additionally I got a new message: KDE detected that one or more internal sound devices were removed. Do you want KDE to permanently forget about these devices? This is the list of devices KDE thinks can be removed: * Capture: Default * Output: Default Yes No Manage devices If I select "Manage devices" I can see that Default device doesn't appear any more under "Audio Output" categories but it's still under "Audio Capture" categories (although it's greyed out like it was before). Sound seems to work OK. I added a NetworkManager dispatcher script to start a VPN connection automatically when eth0 gets connected. This runs before I log in. It looks like the additional delay reduces significantly the probability that this problem will occur. Now I get it only about 20% of the time. This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |