I have used Audacity for many years successfully, almost always using Linux. I currently use OpenSuSE on my computers, and Audacity is playing up on one of the machines when I attempt to get input from its Mic connection. There is no problem with output; sound is produced without problem. There is also no problem with recording sound that is coming from other running programs like Firefox and web pages which are sound sources. It is only when I connect a cable to the Mic port that Audacity does not detect a signal.
I have two machines running Audacity 2.1.1 and OpenSuSE Leap 42.1. The other machine, the older one, is able to handle Mic input fine, so the problem is specific to the hardware on my newer machine. When I have pavucontrol running, I can see that signal is detected by it. I can also record Mic input using the Audio Recorder program on this machine. It is only Audacity that cannot detect Mic input.
I have done these tests in the hope that they will give you a bit more information about my hardware and setup:
The output from “arecord -l” is
**** List of CAPTURE Hardware Devices ****
card 1: Generic [HD-Audio Generic], device 0: 92HD99BXX Analog [92HD99BXX Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
The output from “cat /etc/modprobe.d/50-sound.conf” is
options snd slots=snd-hda-intel
# 5Dex.mtR84bFRyqF:FCH Azalia Controller
alias snd-card-0 snd-hda-intel
The output from /usr/sbin/alsa-info.sh can be seen at http://www.alsa-project.org/db/?f=9ac811d945434a235c56769be9d07200d2d132a6
The output from “lspci -vnn | grep -A 1 -i audio” is
00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI Audio Controller [1002:9902]
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI Audio Controller [1002:9902]
Flags: bus master, fast devsel, latency 0, IRQ 32
--
00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller [1022:780d] (rev 01)
Subsystem: Toshiba America Info Systems Device [1179:fa91]
The command “arecord -d 4 /tmp/test.wav” causes a good recording of the Mic input.
The problem is not urgent for me because I can use Audio Recorder instead of Audacity, but it would be able to use Audacity uniformly across the machines for audio work if you are able to identify the problem.
I have this software installed on the machine:
> rpm -qa | grep alsa
alsa-oss-1.0.28-5.2.x86_64
alsa-1.0.29-10.1.x86_64
alsa-utils-1.0.29-9.1.x86_64
alsa-firmware-1.0.29-3.2.noarch
alsa-plugins-32bit-1.0.29-10.1.x86_64
alsa-plugins-pulse-1.0.29-10.1.x86_64
alsa-oss-32bit-1.0.28-5.2.x86_64
alsa-plugins-1.0.29-10.1.x86_64
alsa-plugins-pulse-32bit-1.0.29-10.1.x86_64
> rpm -qa | grep pulse
libpulse0-7.0-3.1.x86_64
pulseaudio-7.0-3.1.x86_64
libxine2-pulse-1.2.6-3.2.x86_64
pulseaudio-utils-7.0-3.1.x86_64
libpulse-mainloop-glib0-7.0-3.1.x86_64
pulseaudio-lang-7.0-3.1.noarch
alsa-plugins-pulse-1.0.29-10.1.x86_64
libpulse0-32bit-7.0-3.1.x86_64
pulseaudio-bash-completion-7.0-3.1.x86_64
alsa-plugins-pulse-32bit-1.0.29-10.1.x86_64
> rpm -q libasound2
libasound2-1.0.29-10.1.x86_64
The output of “uname -a” is
Linux t2 4.1.15-8-default #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab) x86_64 x86_64 x86_64 GNU/Linux