On 03/25/2016 09:20 AM, Richard Ibbotson wrote: What avcs are you seeing ausearch -m avc -ts recent

On 03/25/2016 06:58 AM, Richard Ibbotson wrote: Well, that just about proves that SELinux isn't involved, doesn't it?

On Fri, 25 Mar 2016 13:20:46 +0000 Richard Ibbotson wrote: I don't know if this is the same problem I had or not, but for several weeks, the gnome-control-panel "sound" settings would not work for me to change default devices and wot-not, they were completely frozen as though it thought there was only one sound device and it only had one output mode. The command line pactl interface, however, worked flawlessly and I was able to change setting that way (after figuring out the obscure syntax). After a few week, the gnome control panel started working again (no idea why it stopped or started :-).

On 03/25/2016 01:21 PM, Richard Ibbotson wrote: <snip/> The entire audio subsystem is a grand mystery to me; however (afaik), with regard to pulseaudio, *outputs* are *sinks* and *inputs* are *sources*.

On Fri, 25 Mar 2016 13:20:46 +0000 Richard Ibbotson <richard.ibbotson(a)gmail.com&gt; wrote: That's so 5 years ago. ;-) Do you have a wav file available. If not, just grab one off the web. Then run the command aplay [wav file name]. Is there sound? While you're at it run aplay -lL Do you see lots of entries? How many sound cards do you have? Is it possible your video card is being mistaken for a sound card, and because of random ordering of sound devices, now your default sound card? Look for the default setting in the output. Is it pulse? If you haven't got pavucontrol installed, install it. It's a lot easier to deal with this using the graphical interface. Open it, under sound -> mixers, and look at your cards and their settings. Are they correct? Could it be that the sound card is disabled in alsa for some reason? Pulse runs on top of alsa, so if this is the case, pulse wont work. Run alsamixer -c0 and check whether everything is alsa is working properly. 0 is the first sound device, and usually is default sound device. If you have more than one sound device, check all of them. That should get you started. There's also an alsa-user mailing list you can access at gmane.org. Reading that should give you troubleshooting ideas if none of the above does.

On 03/28/2016 02:02 PM, Richard Ibbotson wrote: Ok, so either you haven't loaded the necessary kernel module for your sound card (the modules typically have the text "snd" in their name) or your sound card went bye-bye. Try "lspci | grep -i audio" and see what you get. On my desktop (with several physical sound devices): [root@prophead ~]# lspci | grep -i audio 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller 01:00.1 Audio device: NVIDIA Corporation GF110 High Definition Audio Controller (rev a1) [root@prophead ~]# lsmod | grep -i snd snd_usb_audio 176128 4 snd_usbmidi_lib 36864 1 snd_usb_audio snd_rawmidi 32768 1 snd_usbmidi_lib snd_hda_codec_realtek 81920 1 snd_soc_rt5640 114688 0 snd_hda_codec_generic 69632 1 snd_hda_codec_realtek snd_hda_codec_hdmi 49152 5 snd_hda_intel 36864 12 snd_soc_rl6231 16384 1 snd_soc_rt5640 snd_hda_codec 126976 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel snd_soc_core 204800 1 snd_soc_rt5640 snd_hda_core 61440 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel snd_compress 20480 1 snd_soc_core snd_pcm_dmaengine 16384 1 snd_soc_core ac97_bus 16384 1 snd_soc_core snd_soc_sst_acpi 16384 0 snd_seq 69632 0 snd_hwdep 16384 2 snd_usb_audio,snd_hda_codec snd_seq_device 16384 2 snd_seq,snd_rawmidi snd_pcm 114688 8 snd_soc_rt5640,snd_usb_audio,snd_soc_core,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_pcm_dmaengine,snd_hda_core snd_timer 32768 2 snd_pcm,snd_seq snd 73728 47 snd_hda_codec_realtek,snd_usb_audio,snd_soc_core,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec_generic,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device,snd_compress soundcore 16384 1 snd And on my laptop (with just the built-in sound devices): [root@golem4 ~]# lspci | grep -i audio 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) [root@golem4 ~]# lsmod | grep -i snd snd_hda_codec_hdmi 49152 1 snd_hda_codec_realtek 81920 1 snd_hda_codec_generic 69632 1 snd_hda_codec_realtek snd_hda_intel 36864 5 snd_hda_codec 126976 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel snd_hda_core 61440 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel snd_hwdep 16384 1 snd_hda_codec snd_seq 69632 0 snd_seq_device 16384 1 snd_seq snd_pcm 114688 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core snd_timer 32768 2 snd_pcm,snd_seq snd 73728 20 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_seq_device soundcore 16384 1 snd ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - "You think that's tough? Try herding cats!" - ----------------------------------------------------------------------

https://ask.fedoraproject.org/en/question/45118/sound-suddenly-stopped-wo... Finally found this. Which might or might not give some clues. The bit at the bottom of the page might be worth trying. Remove wine- pulseaudio. Trouble is it also takes out Wine which I would like to keep. <sigh> Tried to remove pavucontrol and reinstall. Still nothing. Tried modprobe snd-hda-intel and modprobe pulseaudio but obviously that's not going to work. Result was ... Module pulseaudio not found in directory /lib/modules/4.3.5-300.fc23.x86_64. But that could be me trying the wrong modprobe command. Also tried... https://bbs.archlinux.org/viewtopic.php?id=154002 I did pactl list. It said... XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) Connection failure: Connection refused pa_context_connect() failed: Connection refused Killed pulseaudio and restarted as a user with service pulseaudio restart. Might have to reinstall the whole system. Was hoping to stay away from that one. -- Richard

On Mon, 28 Mar 2016 22:02:32 +0100 Richard Ibbotson <richard.ibbotson(a)gmail.com&gt; wrote: The aplay -lL is run by itself just to list devices alsa knows about. Anyway, it gave you the answer you needed - null, no soundcards found. As Rick pointed out. You can buy a simple USB sound device on Ebay for about a dollar. Good enough for mic in and sound out, if that's all you need.