Volume Slider Jumps, due to rapidly changing hardware jack sense state

Additional Data point. The volume slider will stay put if it is set at 100%. I'm seeing the output source on the sound menu flicker between sources still.

I cannot reproduce this here. Do you have any other volume controlling application running like ear candy ?

No. Just checked ps. I've closed everything. Btnx service stopped.
It's been rebooted several times. Banshee is the only music player

It acts like it's getting random dbus events. This system was fine
under Natty.

On 10/21/2011 03:29 PM, Conor Curran wrote:
> I cannot reproduce this here. Do you have any other volume controlling
> application running like ear candy ?
>
>
> ** Changed in: indicator-sound
> Assignee: (unassigned) => Conor Curran (cjcurran)
>

Does sound settings's volume slider behave in a similar way ?

Identical.

Also, under the "output" tab, the "connector:" dropdown switches between options. If I select "Analog Output" (Option 2) it will switch back to "Analog Headphones" (Option 1) at the same time the slider jumps.
If I select "Analog Headphones"(option 1), it will stay with that option, but I can see it flash "Analog Output" when the slider jumps, but remains at option 1.

Sorry, more data, hopefully helpful.

Under Output, When the GF106 High Def controller is selected, the slider DOES NOT jump. When the Internal Audio Analog Stereo is is selected, the slider DOES jump.

The more data the better Jim :)
Firstly I just want to eliminate i-sound as a culprit here.

1. find the pid of indicator-sound-service
ps ax | grep indicator-sound-service

2. Attach gdb to block the service
sudo gdb -p $PID

3. Once it's attached you should type 'continue'. This will allow the service to operate as normal. Then hit ctlr + c. This will stop the service so this should block the sound service ensuring it is not interacting with the pulse server. Can you do this and then reproduce the bug and see if you still see symptoms ?

When I ^C, the volume slider didn't move and sound settings menu was inaccessible.

If you open the control center and go to the sound settings icon this will open the same application.
Could you do this again and see if the slider on the sound settings is moving ?

Ah. Ok.

It is still jumping after the above is performed.

From the information you've provided, it seems like a component of the GNOME stack is at fault, not indicator-sound. So, I'm adding a task for gnome-settings-daemon, though I'm not sure if its to blame here (could be gnome-control-center or gnome-media)

Please run "apport-collect 874535" in a terminal, so we can get some information about your hardware. Please also consider getting a log form PulseAudio, as per the instructions found here: https://wiki.ubuntu.com/PulseAudio/Log.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Pulseaudio

Noticed that the volume slider wasn't jumping, but the output device selection box was during this procedure.

As seen in the PulseAudio log, this is the jack sensing being flaky. The first time I saw it I thought it was just faulty hardware, but I think we need to start filter out short changes in the jack sensing.

There is a work around. You need to work around it on two levels:

PulseAudio level: edit /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf and comment out the entire section that starts with [Jack_InputDevice].

This will stop the box from jumping. If audio is still crackling, also try:

ALSA level: start alsamixer in a terminal and change "Automute mode" to "disabled"

FYI, the Pulseaudio change made no difference in the jumping.

Disabling Automute in alsa did stop it along with the associated volume changes, however

Hi David!

Could you post an exact line to edit in PulseAudio config files for Ubuntu 12.04 (pulseaudio 1:1.1-0ubuntu15.3)?

File /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf have no [Jack_InputDevice] string, and file 'analog-output-headphones-2.conf' exists in same dir.

Change /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf from:

[Jack Front Headphone]
required-any = any

[Jack Headphone]
required-any = any

to :

# [Jack Front Headphone]
# required-any = any

# [Jack Headphone]
# required-any = any

...restart pulseaudio (or the computer) for changes to take effect.

Side note: There might actually a better solution in newer kernels: if you install the daily DKMS package ( https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS ) you will get this too.

Then edit /etc/modprobe.d/alsa-base.conf and add this line:

options snd-hda-intel jackpoll_ms=250

..then reboot and test. In case the sound card is not the first hda intel sound card, you might need to add more, like this:

options snd-hda-intel jackpoll_ms=0,250

or

options snd-hda-intel jackpoll_ms=0,0,250

...depending on which card you want to change.

Thank you so much to: Jim for submitting this bug report; Luke for pointing out the PulseAudio logging wiki; and David for providing the workaround details for PulseAudio and snd-hda-intel. I've had the volume pop-up problem (easily 50+ times a day) since I built my system in late 2012 and only bummed that I finally found this bug report today instead of a long time ago.

I confirmed I was affected by the same jack sensing issue by using PulseAudio logging this way (based on the wiki; you might want to confirm you don't have an existing client.conf file):

echo autospawn = no > ~/.config/pulse/client.conf
pkill pulseaudio
pulseaudio --daemonize -vv --log-time=1 --log-target=file:/tmp/pulseaudio.log
tail -f /tmp/pulseaudio.log

Searching the logs with:
grep is.now /tmp/pulseaudio.log

showed repeated messages like this:
D (1565.604| 634.163) [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
D (1565.626| 0.020) [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D (1712.599| 146.972) [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
D (1712.621| 0.020) [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged

I was thinking I'd use the snd-hda-intel jackpoll_ms workaround, until I thought about actually checking the hardware setup on my system. First I connected/disconnected headphones to the front panel headphone jack to confirm the jack shown in the debug output above indeed toggled again while tailing the log. Then I disconnected the cable from my case to the motherboard "Front panel audio connector (AAFP)" since I never use those jacks anyway. This simple hardware fix worked for me and so I thought I'd share this information in case anyone else has the issue and wants to go this route so the kernel sound drivers don't have to process any interrupts generated by (phantom) audio jack plug events.

To restore the standard PulseAudio daemon process without debugging, I re-enabled autospawn, killed the debug daemon process and after a few seconds it is restarted automatically:

rm ~/.config/pulse/client.conf
pkill pulseaudio

> Then I disconnected the cable from my case to the motherboard "Front panel audio connector (AAFP)" since I never use those jacks anyway. This simple hardware fix worked for me

did your computer chassis have a HDA front audio panel ?

http://www.intel.com/support/motherboards/desktop/sb/cs-015851.htm

http://en.wikipedia.org/wiki/Intel_High_Definition_Audio

The different signal assignments can cause trouble when AC'97 front-panel dongles are used with HDA motherboards and vice versa. An AC'97 dongle returns audio on pins 6 and 10 rather than a digital plug sensing signals. Consequently, a loud audio passage may make the HDA motherboard with AC'97 dongle believe that headphones and microphones are being plugged and unplugged hundreds of times per second. An AC'97 motherboard with an HDA dongle will route the AC'97 5 V audio supply (pin 7; silence) to the speakers instead of the desired left and right audio signals.

My case has an audio cable with two connectors on it clearly labeled "AZALIA" (codename for HD Audio according to the wiki) and "AC'97". I had AZALIA connected to the motherboard AAFP connector. The ASUS motherboard has a BIOS setting to toggle between the default HD Audio setting (which is what I have set) and legacy AC'97 mode.

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/Documentation/sound/alsa/HD-Audio.txt

do the problem limited to the front panel headphone jack and mic jacks ?

how about the other jacks at rear panel ?

you have to disable jack_detect by early patching if all jacks have this problems

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/Documentation/sound/alsa/HD-Audio.txt

specify hint

jack_detect = 0

The problem only happens with the front panel headphone jack, the debugging did not show any plugged events for the front mic. I do not see the problem with the rear audio jacks.

With debugging still enabled, I plugged in cables to the motherboard rear audio ports and it showed plugged events for 'Rear Mic Jack' and 'Line Jack', but not for the any of the Front/Center/Rear/Side audio out jacks (so I assume either the hardware or the default ALSA/PulseAudio config does not do jack detection for those).

Given removing the front audio connector from the motherboard fixed the problem, I have not changed any Alsa or PulseAudio settings like jack_detect (and don't plan to). I'm guessing the front headphone jack in my chassis is bad, or perhaps there is some sort of electromagnetic interference through the unshielded cable going to the front audio jacks.

>> With debugging still enabled, I plugged in cables to the motherboard rear audio ports and it showed plugged events for 'Rear Mic Jack' and 'Line Jack', but not for the any of the Front/Center/Rear/Side audio out jacks (so I assume either the hardware or the default ALSA/PulseAudio config does not do jack detection for those).

because pulseaudio only check the line out recently , some business desktop and those all-in-one-pc have internal speakers , line out and headphone jacks

http://cgit.freedesktop.org/pulseaudio/pulseaudio/log/src/modules/alsa/mixer/paths/analog-output-lineout.conf

From Bug #1285741 (duplicate)
I'll continue my comments/questions here.

@Raymond
I have a MB with HDA and a case with 2 connectors (HDA and AC97). HDA is plugged.
I even check the wirering in the connector with my ohm-meter, everything is OK.
In the BIOS I can disable the front panel and then the flircks disappear but I don't have headphone output and I need it.

You asked me:
"try disable jack detection of front panel headphone by hdajackretask or early patching"
When I try I get the error message: "Failed to create file '/home/jp/.pulse/client.conf.M5FECX': No such file or directory"
even with sudo.

I don't know what to do. I don't have a client.conf file in the directory.
And no clue how to do early patching.

http://voices.canonical.com/david.henningsson/2011/11/29/turn-your-mic-jack-into-a-headphone-jack/

select alc892 codec

check advanced override to allow you to change the pin default

select headphone node 0x1b

Chang Jack detection from present to not present

This is exactly what I did.

Then I have to click "Apply now" and I get the error message:
"Failed to create file '/home/jp/.pulse/client.conf.M5FECX': No such file or directory"

http://git.alsa-project.org/?p=alsa-tools.git;a=commitdiff;h=772fbde91c00c8f9517e67e2f5401d28e9aa88d4;hp=472c414744dfaa04903f8b5dc2cebbab1b4b93d5

Raymond,

I thing you don't know what is my Linux level, I'd say beginner.
So I went in the page you provided then in this page
http://git.alsa-project.org/?p=alsa-tools.git;a=summary
and I downloaded the first snapshot (2014-01-05)
The I extracted the file. Now I'd guess I have to install but there is no readme/install to follow.
There is no configure, make file to run, so I am stuck.

Do you have a how-to? Please let me know.

you should email the author since the source and ppa are already the latest version if you still got the bug

take a look at the early patching

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/Documentation/sound/alsa/HD-Audio.txt

Node 0x1b [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
  Pincap 0x0001373e: IN OUT HP EAPD Detect Trigger
    Vref caps: HIZ 50 GRD 80 100
  EAPD 0x2: EAPD
  Pin Default 0x02214c20: [Jack] HP Out at Ext Front
    Conn = 1/8, Color = Green
    DefAssociation = 0x2, Sequence = 0x0

you use need to set bit 8 of the pin default of the headphone to indicate that this pin complex has no jack detection circuit by early patching

[pincfg]
0x1b 0x2214d20

the driver create front headphone phantom jack instead of front headphone jack

and won't enable unsolicited event to report the headphone state when the headphone is plugged/unplugged

The hd-audio driver reads the file via request_firmware(). Thus,
a patch file has to be located on the appropriate firmware path,
typically, /lib/firmware. For example, when you pass the option
`patch=hda-init.fw`, the file /lib/firmware/hda-init.fw must be
present.

The patch module option is specific to each card instance, and you
need to give one file name for each instance, separated by commas.
For example, if you have two cards, one for an on-board analog and one
for an HDMI video board, you may pass patch option like below:
------------------------------------------------------------------------
    options snd-hda-intel patch=on-board-patch,hdmi-patch
------------------------------------------------------------------------

Thanks for your answer, Raymond.
However, the only sentence I understand is the first one,
"you should email the author since the source and ppa are already the latest version if you still got the bug"

All the rest is over my small head.
I sent a email to the author and I hope he will get a chance to answer.

Meanwhile, if you know some I could do, I'll do it with pleasure but please explain step by step the same way for a dummy.

Thanks

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248116

https://wiki.ubuntu.com/PulseAudio/Log

the Symptom is the headphone was reported plug and unplugged in the loop in the pulseaudio verbose log

the exact cause of the problem is not known, you have to enable tracepoint to find out why unsolicited event was triggered

or the jack detect is inverted

by using hda-verb GET_PIN_SENSE after you disable the unsolicited event by set the misc bit of headphone or disable jack detect using hint jack_detect = 0

A big step forward.

Following the page
https://wiki.ubuntu.com/PulseAudio/Log:

After running the 3 lines, I waited ~4 seconds then removed the Headphone jack, then waited ~5 seconds then plugged the jack back, then waited ~4 second and stopped the process with Ctrl-c

File is attached.
If you want more, let me know

Now I try to find how to use hda-verb GET_PIN_SENSE and how to set the misc bit of headphone:
Can I use the same process here?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248116/comments/12

Below is my codec:
$ head -n 10 /proc/asound/card0/codec*
Codec: Realtek ALC892
Address: 0
AFG Function Id: 0x1 (unsol 1)
Vendor Id: 0x10ec0892
Subsystem Id: 0x18497892
Revision Id: 0x100302
No Modem Function Group found
Default PCM:
    rates [0x5f0]: 32000 44100 48000 88200 96000 192000
    bits [0xe]: 16 20 24

Let me know what should be the line after [codec]

Sorry, I did a (small) mistake in my previous post.
The file log was done with Linux Mint 16 (Ubuntu 13.10) but I have the same issue.

Now I attach a new log made with UbuntuStudio 13.10 and with the exact same process.

Hope this will help

Note: as of Ubuntu 13.10, hda-jack-retask is part of alsa-tools. Just install the alsa-tools-gui package from the regular archive and start "hdajackretask". (Note: if you don't have a .pulse directory, try symlinking .pulse to .config/pulse - and remove the symlink again when you have closed hda-jack-retask. Otherwise you'll get an error when clicking "Apply now".)

refer to pulseaudio verbose log , your headphone seem quite normal

using hda-emu

> jack 0x1b 1
send: NID=0x1b, VERB=0x709(exec_pin_sense), PARM=0x0
receive: 0x0
send: NID=0x1b, VERB=0xf09(get_pin_sense), PARM=0x0
receive: 0x80000000
send: NID=0x14, VERB=0x707(set_pin_ctl), PARM=0x0
send: NID=0x15, VERB=0x707(set_pin_ctl), PARM=0x0
send: NID=0x16, VERB=0x707(set_pin_ctl), PARM=0x0
send: NID=0x17, VERB=0x707(set_pin_ctl), PARM=0x0

when headphone is plugged , driver set the pin ctls of four line out jacks to zero

CTL Notify: Front Headphone Jack:0, mask=1
JACK report Front Headphone, status 1
JACK report Rear Mic, status 0
JACK report Front Mic, status 0
JACK report Line, status 0
JACK report Line Out Front, status 0
JACK report Line Out Surround, status 0
JACK report Line Out CLFE, status 0
JACK report Line Out Side, status 0

driver update headphone jack status and send ctl notify to user space

when pulseaudio receive the hctl event, pulseaudio mute the four line out playback switches

the only point is your green line out is not pluuged

when the headphone is unplugged,

do module-switch-on-port-available switch to your spdif device ?

hda specification only need GET_PIN_SENSE to get the detection,

do the driver really need to use SET_PIN_SENSE when pincap support trigger ?

you can use the following command when headphone is plug and unplugged to find out whether the driver really need to execute SET_PIN_SENSE

sudo hda-verb /dev/snd/hwC0D0 0x1b GET_PIN_SENSE 0

7.3.4.9 Pin Capabilities
The Pin Capabilities parameter returns a bit field describing the capabilities of the Pin Complex Widget.

Output Capable indicates whether the pin complex supports output. If Output Capable is a 1, the
pin is capable of output.

Headphone Drive Capable indicates that the pin has an amplifier with sufficient current drive to
drive headphones. If Output Capable is a 0, then this bit has no meaning and must be 0.

Presence Detect Capable indicates whether the pin complex can perform presence detect to
determine whether there is anything plugged in. Presence detect does not indicate what is plugged
in, only that something is plugged in.

Trigger Required indicates whether a trigger is required for an impedance measurement (see
Section 7.3.3.15).

Impedance Sense Capable indicates whether the pin complex supports impedance sense on the
attached peripheral to determine what it is. More accurate (possibly sequenced) forms of peripheral
discrimination may be supported independent of this capability; however, if this bit is a 1, then the
codec must support at least the basic impedance test as described in Section 7.3.3.15.

the trigger is required for an impedance measurement but your codec does not support Impsense

you can disable it by hint

trigger_sense=0

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/Documentation/sound/alsa/HD-Audio.txt

- jack_detect (bool): specify whether the jack detection is available
  at all on this machine; default true
- inv_jack_detect (bool): indicates that the jack detection logic is
  inverted
- trigger_sense (bool): indicates that the jack detection needs the
  explicit call of AC_VERB_SET_PIN_SENSE verb
- inv_eapd (bool): indicates that the EAPD is implemented in the
  inverted logic

Node 0x1b [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out
  Control: name="Headphone Playback Switch", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Front Headphone Jack", index=0, device=0
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals: [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x00 0x00]
  Pincap 0x0001373e: IN OUT HP EAPD Detect Trigger
    Vref caps: HIZ 50 GRD 80 100
  EAPD 0x2: EAPD
  Pin Default 0x02214020: [Jack] HP Out at Ext Front
    Conn = 1/8, Color = Green
    DefAssociation = 0x2, Sequence = 0x0
  Pin-ctls: 0xc0: OUT HP VREF_HIZ
  Unsolicited: tag=01, enabled=1
  Power states: D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 5
     0x0c 0x0d 0x0e 0x0f 0x26*

I did what David said in #49

I run alsamixer
Flickers are still there but now Master, Headphone PCM and Front sliders do not change for full level (before they was going at full) and Front mic slider jumps.
Input Front Mic change to Line.

I checked again with hdajackretask, I confirm "Green Headphone, Front side, Jack detection Not present"

@Raymond
I don't have speakers. I have headphone on the green front jack and audio player on the blue line input, rear side. Nothing else.

Headphone is connected, but above still active "Green Headphone, Front side, Jack detection Not present"
~ $ sudo hda-verb /dev/snd/hwC0D0 0x1b GET_PIN_SENSE 0
nid = 0x1b, verb = 0xf09, param = 0x0
value = 0x80000000

Headphone is disconnected, but above still active "Green Headphone, Front side, Jack detection Not present"
 ~ $ sudo hda-verb /dev/snd/hwC0D0 0x1b GET_PIN_SENSE 0
nid = 0x1b, verb = 0xf09, param = 0x0
value = 0x0

Node 0x14 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
  Control: name="Front Playback Switch", index=0, device=0
    ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name="Line Out Front Jack", index=0, device=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals: [0x00 0x00]
  Pincap 0x0001003e: IN OUT HP EAPD Detect Trigger
  EAPD 0x2: EAPD
  Pin Default 0x01014010: [Jack] Line Out at Ext Rear
    Conn = 1/8, Color = Green
    DefAssociation = 0x1, Sequence = 0x0

pulseaudio only check line out Jack but yours are line out front jack

0.240| 0.000) D: [pulseaudio] alsa-mixer.c: Probe of jack 'Line Out Jack' succeeded (not found)
( 0.240| 0.000) D: [pulseaudio] alsa-mixer.c: Probe of jack 'Line Out Phantom Jack' succeeded (not found)

only found four jacks which support Jack detect : headphone, front Mic, rear Mic and line in

seem did not check line out front Jack

http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/src/modules/alsa/mixer/paths/analog-output-lineout.conf?id=ecf3ab2b5788c85c237eeb6429bd1d525b9ac0cc

+[Jack Line Out]
+required-any = any
+
+[Jack Line Out Phantom]
+state.plugged = unknown
+state.unplugged = unknown
+required-any = any
+
+[Jack Line Out Front]
+required-any = any
+

( 0.181| 0.000) D: [pulseaudio] module-alsa-card.c: Found 4 jacks.
( 0.182| 0.000) I: [pulseaudio] alsa-util.c: Successfully attached to mixer 'hw:0'
( 0.182| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
( 0.182| 0.000) D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status yes
( 0.182| 0.000) D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
( 0.182| 0.000) D: [pulseaudio] module-switch-on-port-available.c: finding port analog-output-headphones
( 0.182| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Mic Jack' is now unplugged
( 0.182| 0.000) D: [pulseaudio] device-port.c: Setting port analog-input-microphone-front to status no
( 0.182| 0.000) D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
( 0.182| 0.000) D: [pulseaudio] module-switch-on-port-available.c: finding port analog-input-microphone-front
( 0.182| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Rear Mic Jack' is now unplugged
( 0.182| 0.000) D: [pulseaudio] device-port.c: Setting port analog-input-microphone-rear to status no
( 0.182| 0.000) D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
( 0.182| 0.000) D: [pulseaudio] module-switch-on-port-available.c: finding port analog-input-microphone-rear
( 0.182| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Line Jack' is now plugged in
( 0.182| 0.000) D: [pulseaudio] device-port.c: Setting port analog-input-linein to status yes
( 0.182| 0.000) D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event.
( 0.182| 0.000) D: [pulseaudio] module-switch-on-port-available.c: finding port analog-input-linein

do pulseaudio use line out.conf or desktop-speaker.conf to differentiate the three output path of those business desktop with internal speaker, li...

http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=28&Level=5&Conn=4&ProdID=284

refer to alc892 datasheet

8.2.4 verb execute pin sense (verb id=709h)

payload

bit 0 right(ring) channel select
           1: sense left channel(tip)
            0: sense right channel(ring)

the ALC892 does not support hardware impedance sensing and will ignore this control

don't exec pin sense (verb id=709h) before GET_PIN_SENSE since alc892 does not support ImpSense

The attachment "alc892_no_trigger_sense since alc892 does not support ImpSense" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

Hi Raymond
Any new?
Do you want more test, log?
I can do recording and playing is not pleasant at all.
I hope you will find a fix or a workaround.

it is strange that your headphone is plugged in at 25.567 , unplugged at 25.781 and plugged again 25.855

seem related to [pulseaudio] module-device-restore.c: Restoring mute state for sink alsa_output.pci-0000_00_14.2.analog-stereo.

( 25.567| 16.401) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
( 25.567| 0.000) D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status yes
( 25.568| 0.000) D: [pulseaudio] module-switch-on-port-available.c: finding port analog-output-headphones
( 25.568| 0.000) D: [alsa-sink-ALC892 Analog] alsa-mixer.c: Activating path analog-output-headphones
( 25.568| 0.000) D: [alsa-sink-ALC892 Analog] alsa-mixer.c: Path analog-output-headphones (Headphones), direction=1, priority=90, probed=yes, supported=yes, has_mute=yes, has_volume=yes, has_dB=yes, min_volume=0, max_volume=64, min_dB=-179, max_dB=0
( 25.568| 0.000) D: [alsa-sink-ALC892 Analog] alsa-mixer.c: Element Master, direction=1, switch=1, volume=1, volume_limit=-1, enumeration=0, required=0, required_any=0, required_absent=0, mask=0x7ffffffffffff, n_channels=1, override_map=yes
( 25.568| 0.000) D: [alsa-sink-ALC892 Analog] alsa-mixer.c: Element Headphone, direction=1, switch=1, volume=1, volume_limit=-1, enumeration=0, required=0, required_any=4, required_absent=0, mask=0x3600000000f66, n_channels=2, override_map=yes
( 25.568| 0.000) D: [alsa-sink-ALC892 Analog] alsa-mixer.c: Element Front, direction=1, switch=1, volume=3, volume_limit=-1, enumeration=0, required=0, required_any=0, required_absent=0, mask=0x6, n_channels=2, override_map=no
( 25.568| 0.000) D: [alsa-sink-ALC892 Analog] alsa-mixer.c: Element Surround, direction=1, switch=2, volume=2, volume_limit=-1, enumeration=0, required=0, required_any=0, required_absent=0, mask=0x6, n_channels=2, override_map=no
( 25.568| 0.000) D: [alsa-sink-ALC892 Analog] alsa-mixer.c: Element Side, direction=1, switch=2, volume=2, volume_limit=-1, enumeration=0, required=0, required_any=0, required_absent=0, mask=0x6, n_channels=2, override_map=no
( 25.568| 0.000) D: [alsa-sink-ALC892 Analog] alsa-mixer.c: Element Center, direction=1, switch=2, volume=2, volume_limit=-1, enumeration=0, required=0, required_any=0, required_absent=0, mask=0x7ffffffffffff, n_channels=1, override_map=no
( 25.568| 0.000) D: [alsa-sink-ALC892 Analog] alsa-mixer.c: Element LFE, direction=1, switch=2, volume=2, volume_limit=-1, enumeration=0, required=0, required_any=0, required_absent=0, mask=0x7ffffffffffff, n_channels=1, override_map=no
( 25.568| 0.000) D: [alsa-sink-ALC892 Analog] alsa-mixer.c: Element PCM, direction=1, switch=0, volume=1, volume_limit=-1, enumeration=0, required=0, required_any=0, required_absent=0, mask=0x3600000000f66, n_channels=2, override_map=yes
( 25.568| 0.000) D: [alsa-sink-ALC892 Analog] alsa-mixer.c: Element IEC958, direction=1, switch=2, volume=0, volume_limit=-1, enumeration=0, required=0, required_any=0, required_absent=0, mask=0x0, n_channels=0, override_map=no
( 25.568| 0.000) D: [alsa-sink-ALC892 Analog] alsa-mixer.c: Jack Front Headphone, alsa_name='Front Headphone Jack', detection possible
( 25.568| 0...

If you read again my posts #47 and #48 you will see that I unplugged and re-plugged the headphone during the log.

I stated the log with the headphone plugged then I removed it then I re-plugged it.
I waited around 5-8 seconds between.
I don't know what are the unit for the figure ( 25.567| but you should see that.

If you see a very short time maybe when I unplugged it then re-plugged it some contacts was made temporarily but for a very short time, milliseconds.
But you should see 5-8 seconds between the actions.

I am a bit disappointed.

This bug has been reported by Jim Rorie on 2011-10-14, more than 2 full years ago.

I agree there is not a lot of people impacted
The Importance is Low and nobody is assigned to this bug.
There is no workaround.

I have audio with static every few seconds and I can't listen or record properly. Is it not important?
I want to capture video with this computer but I can't.
To my point of view, this but is hightly important as I can't do my video project.

Do I need to wait another 2 years?

Please could you tell me if you will start to fix it and how long it will take. I'll decide if I need to switch to another distribution.
I already tried Centos but the video tools are in very old version. Ubuntu has recent version and LTS I'd like tu use in April.

Experienced same issue with a Gigabyte 5.1 mother board (2013 vintage), moving the audio jack to another output solved the problem, not other changes were made to the system. OS used Ubuntu 14.04 LTS Trusty. In this case it is definitely due to incorrectly sensing the audio output jack being used.

Today 07 June 2014, I installed Fedora 20 Mate and tested audio.

Audio is perfect no glitch, volume slider jump, no bug !!!!!

So, this is a bug with ubuntu based OS and people here don't care.

So I say good bye to this Ubuntu.

Readers, if you get the same, you know the solution.

My Kubuntu 14.04 also suffered from this problem. But the next seems to solve it:

in /etc/pulse/client.conf
uncomment "Autospawn" line and change it to "Autospawn = no" and save

Then stop pulseaudio by the next command:
killall pulseaudio

And restart kmix to switch it to new configuration.

Also I disabled 'Auto mute mode' for alsa. You can do it by typing alsamixer at your console.

Same started happening to me when I add a device to the headphones jack.

I tried kolobok-not-dead 's suggestion. Flickering disappears, but unfortunately the mixer's volume cannot be changed.
@kolobok-not-dead - did you have that? Does it have to do with the kmix? (trying to find kmix's equivalent in unity)

See also: http://askubuntu.com/questions/490813/audio-flicking-at-back-port with a description of the problem (in that person's case, the back port instead of the headphone jack)

My issue was due to a bad jack detection.

You should try the following:
Install alsa-tools 1.0.28-1 (1.0.28-2 if the previous is not working)
run hdajackretask
Tic Advanced override
Set Jack detection to Not Present for the jock you have the issue.
Clic Apply now
Clic Install boot override and reboot

I had to set headphone and front mic on my box
Hope this will help

Thanks fo the tip, NrNice! I will try it. That will actually disable said jacks, am I right? I.e., it would be a temporary fix rather than a solution?

It will not disable the input/outpout sound but only physical pluggin detection. You will have to select with or alsamixer (CLI), or alsa sound GUI or PulseAudio Volume Control GUI.

IMHO better a manual working setup than a non working automatic.
Temporary or definitive fix it's up to you as it is very easy to change.

you have to report upstream bug

as the driver enable the unsolicited event, the driver should disabled unsolicited event of particular widget whenever the rate of the receving unsol event of the widget is over 10 times per second

if the bug is caused by numerous unsolicited events

I'm seeing this same issue on an EVGA X79 motherboard. I've used NrNice's work around to disable to headphone jack. I'm running Ubuntu 14.04.3 (3.19.0-28-generic #30~14.04.1-Ubuntu).

Hi,

Same bug here on Ubuntu 15.10 (4.2.0-19-generic) with an Asus Z-97-C motherboard.

David Henningsson post (#31) did the trick, but i have spent some times finding the solution for this.

Anyway, thanks David

Problem still exists in Ubuntu 16.04, and the worst is the fix on comment #31 does not work anymore ....

I've also got this problem in 16.04...

Hi,
I have had the same issue after installing Ubuntu 16.04. I have tried the fix from comment #31 and it didn't work for me. However, as soon as I plug my headphone into the front panel headphone plug, the annoying issue disappeared, and the popping up comes back if headphone is unplugged.
Now I unplugged my rear speaker's plug, and no popping up at all.
Additionally, when I adjust the "Sound Setting", I was unable to hear the Test Sound if I try to play sound from Digital Output (S/PDIF). Not sure if this is relevant.
Ubuntu gurus, perhaps the issue links to the audio plug scan or config?
Thanks in advance.

I'm just started experiencing this in 16.04 this evening.

Seems like the bit which shows the status of the jack being present should be debounced. I'm checking the jack sensing with `hdajacksensetest` and only incidentally the status is wrong. A simple debounce of 2 polls with something like 100ms would be fine.

I've also got this problem in 18.04 with a Gigabyte motherboard.

When I use front jack input the problem disappears.

Same here, Gigabyte GA-B250M-DS3H with HDA Intel PCH, ALC887-VD. Ubuntu 18.04.

On my machine, once this starts happening it survives a reboot but goes away for a while after a _cold_ reboot.

Clicks every few seconds and debounce might indeed be a workaround (~20 ms plug/unplug in my case):

$ ./pulseaudio -vvvv --log-time=1 2>&1 | grep -P 'Front Headphone.*is now'
( 0.120| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
( 3.134| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
( 3.155| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
( 5.161| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
( 5.182| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
( 6.324| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
( 6.345| 0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged

I'm yet to see anything other than 21-22 ms. I set jackpoll_ms=40 in snd_hda_intel options but still seeing the same plug/unplug interval.

Similar reports on this pulseaudio bug: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084

Heh, of course jackpoll_ms=40 doesn't work, anything below 50 ms is ignored: https://github.com/torvalds/linux/blob/master/sound/pci/hda/hda_intel.c#L1720

With jackpoll_ms=60 I'm seeing intervals of slightly above 60 ms, so this makes sense.

Hi,

The same on Kubuntu 18.04

Tried kernels:
uname -r
4.20.17-042017-generic

uname -r
5.1.6-050106-generic

Hardware:
Base Board Information
        Manufacturer: Gigabyte Technology Co., Ltd.
        Product Name: AB350M-D3H-CF

Realtek® ALC887 codec

Headphones are connected on the backward.

Log according to https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874535/comments/33:
tail -f /tmp/pulseaudio.log | grep is.now
( 241.947| 0.019) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
( 269.853| 27.904) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
( 269.874| 0.019) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
( 274.694| 4.818) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
( 274.716| 0.018) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
( 276.145| 1.427) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
( 276.166| 0.019) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
( 276.251| 0.083) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
( 276.272| 0.019) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged

In fact I don't have jack in 'Front Headphone Jack', my jack is plugged in 'Line Out Jack':
manual testing by plug/unplug
(1692.464| 35.788) D: [pulseaudio] module-alsa-card.c: Jack 'Line Out Jack' is now unplugged
(1693.627| 1.148) D: [pulseaudio] module-alsa-card.c: Jack 'Line Out Jack' is now plugged in

1) Fix did not help:
> Then edit /etc/modprobe.d/alsa-base.conf and add this line:
> options snd-hda-intel jackpoll_ms=250
However this fix (or maybe together with the second fix) made sound interruptions to appear more rarely (e.g. once in a minute instead of once in several seconds).
Tried jackpoll_ms=250,250 and jackpoll_ms=1000,1000

2) Fix did not help either:
Commenting out the following in the
/usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf

#[Jack Front Headphone]
#required-any = any

#[Jack Headphone]
#required-any = any

3) Fix did not help:
ALSA level: start alsamixer in a terminal and change "Automute mode" to "disabled"
On my system I basically don't have 'Automute mode' option

4) The only solution helped is to physically disconnect front panel audio connector on the motherboard. Only then those sound cracking and popping disappeared completely.

UPDATE:
even after disconnection of the front audio panel, the issue still happens once in a blue moon:
Left pulseaudio in debug mode for several days after fix:

$ tail -f /tmp/pulseaudio.log | grep is.now

(3284.252| 96.036) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
(3285.280| 1.006) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
(4430.108| 136.098) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
(4431.133| 1.003) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
(65064.220| 35.638) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
(65065.244| 1.023) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
(163655.996| 23.995) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
(163657.020| 1.023) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
(166826.748| 0.027) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
(166827.772| 0.712) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
(170071.580| 2.337) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
(170072.605| 0.483) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
(170196.156| 63.020) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
(170197.180| 1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
(173292.956| 110.638) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
(173293.980| 1.023) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
(405426.784| 13.234) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
(405427.804| 0.998) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
(501250.208| 28.079) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
(501251.228| 1.018) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
(508205.532| 1.475) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
(508206.556| 1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
(576198.464| 60.134) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
(576199.484| 1.018) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
(577215.964| 3.252) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
(577216.992| 0.726) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
(577250.780| 26.097) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in
(577251.804| 1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
(577291.740| 0.147) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in...

This worked for me Thank you David Henningsson (diwic)

Sorry if i post wrong, is my first comment

Change /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf from:

[Jack Front Headphone]
required-any = any

[Jack Headphone]
required-any = any

to :

# [Jack Front Headphone]
# required-any = any

# [Jack Headphone]
# required-any = any

...restart pulseaudio (or the computer) for changes to take effect.