What I did find was that I could capture sound using KRecord. But that does not help me with the above problem and I’ve also found out that Audacious has been affected too. When I try to play music, it gives me the following message: “No suitable mixer element found. snd_pcm-open failed: connection refused”
When I click on a song to be played from within the Dolphin file manger, I get this message that the Audio playback device (and it names the device) does not work and then it says it is falling back on… and the device named has the exact same name.
Is there any chance that an underlying application has crashed ? Is this behaviour still present after a reboot (that re-initializes the applications and underlying processes ? )
The first post with ‘hwinfo --sound’ is meaningless to me in terms of its relevance. Maybe someone who understands the reason for your posting that ‘hwinfo --sound’ info can reply. I always recommend running the alsa-info script to provide information on the hardware and software configuration of one’s audio. Or perhaps you could teach me as to ‘hwinfo --sound’ relevance ? As I have always scratched my head when looking at it. Note I am not saying it is not useful. I am just saying it has never helped me sort someone’s audio problems.
I see you posted some kde menu’s but I have no idea as to the kde version - and that could be important. Myself I am still using openSUSE-12.1 on KDE. Can’t say I have ever seen such a problem.
Reference your ignoring that error message. I note the software assessment is it should be deleted " … KDE thinks could be removed … ". Why do you think you will not be able to get sound back after deleting it ?
Have you tried running the script to obtain more information ?
/usr/sbin/alsa-info.sh
It has a LOT of useful information, from information on the running status of pulse audio, to one’s kernel version, openSUSE version, mixer settings, hardware … etc … so as to provide a more complete picture. It does not , thou, have desktop related information.
sorry I could not reply eariler. Hurricane Sandy had other plans for my area.
I posted the hwinfo --sound because it tells you the sound card brand and driver info.
well now i can’t even get into the computer anymore. when we finally got the power back after 4 1/2 days, I got this code of beeps from the mother board, 1 long and 3 short and my husband looked it up and found that it means that the graphics card is busted. So now, I probably will be forced (by circumstances) to upgrade the system because I probably won’t be able to get a driver for a new card for Suse 11.4.
One thing you can try though, before going out and getting a new system, is to completely unplug the current one from power for a while and let the capacitance drain … I don’t know, try, 24 hours … then test it again. Another quick test, if you can do the swap, is to try a different PSU in the system instead.
