[regression] No sound on ThinkPad T530 until activity at headphone jack(in or out/in) after about 14Feb19

That's more likely to be a kernel or pulseaudio issue (though that component didn't change recently)

another user's comments:
 Re: Broken output sound

    Your screenshots are the same as mines when i've got that issue.
    How it had happened on my system:
    - a couple days ago, made the usual daily upgrades from 'proposed', including gvfs, pulseaudio, alsa and the likes. Sound was working before and after the upgrades.
    - with the next cold boot, i first upgrade some other releases (bionic, cosmic, bulleyes), the sound was was ok on each ones.
    - next cold boot on Disco, kernel 13, and that sound issue appeared; i've closed and reopened the session, but that did not solved the problem.
    - rebooting with the kernel 12 and there the sound was ok; in fact i should say that the system had found and well identified the mobo sound chipset.
    - since, i have made many cold boots and sound is now always working.

    So it looks like the upgrade process has disturbed, at boot time, the sound chipset discovery; is it the gcc8/9 switch to blame ?

please note - there has been at least 1 pulseaudio update and many alsa updates since the 10th Feb.

We seem to be missing details about your sound chip. Can you please run this command on the laptop:

  apport-collect 1816271

so that it might automatically upload the missing information?

apport information

apport information

apport information

apport information

apport information

Tried.

DID:
kris@kris-ThinkPad-T530:~$ apport-collect 1816271
The authorization page:
 (https://launchpad.net/+authorize-token?oauth_token=K44nhP8rLb86KwxBJ2rd&allow_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
kris@kris-ThinkPad-T530:~$

-I then allowed it for 1HR. Then refreshed page and :

GOT:

Authorize application to access Launchpad on your behalf
Unable to identify application

The information provided by the remote application was incorrect or incomplete. Because of that we were unable to identify the application which would access Launchpad on your behalf.

You may have already authorized this application.

See all applications authorized to access Launchpad on your behalf.

some info manually copied:
pulseaudio 1:12.2-2ubuntu1

ALSA version
Driver version: k4.19.0-13-generic
library version 1.1.8
utilities version 1.1.7

loaded ALSA modules
snd_hda_intel

Pulseaudio
installed - yes
running - yes

soundcards recognized by alsa
0[PCH ]:HDA-intel - HDA Intel PCH
HDA Intel PCH at 0xf2530000 irq 32

pci soundcards installed on system
00:1b.0 audeo device : intel corp 7 series/C216chipset family

1200 line text file attached:
(boot)
pactl list
aplay -l
-unplug headphones, replug headphones
pactl list
aplay -l

Thanks.

Can you please also run this command:

  dpkg -l > allpackages.txt

and then send us the resulting file 'allpackages.txt'?

dpkg -l > allpackages.txt

Sounds like the same issue as bug 1815384 so making this one a duplicate of that.

note - I get no sound after boot whether or not headphones are plugged in.

That's fine. So long as they work after replugging as mentioned in the description:

> Now if I unplug headphones and plug back in, it wakes up and recognizes it and works fine.

Then we can treat them as the same bug, for now.

Ok. Thanks for ack. :)

This bug is reopened.

While bug 1583801 is about not getting sound when booting with the headphones plugged in, you say you experience a secondary problem of no sound even without headphones plugged in during boot.

So let's make this bug about that second part. Please reword the bug title/description to be about that.

Kris M says in comment #44 of bug 1583801:

1816271 I get no sound after boot whether or not headphones are plugged in.
If headphones not plugged in, after boot, plugging them in wakes sound.
If headphones ARE plugged in at boot, must unplug and plug in headphones to wake sound.
It's just not waking alsa or pulseaudio. Worked fine until about 14th or 15th.Feb

to clarify title:
After about 14Feb19 :

When boot, there is no sound: settings/sound does not show any soundcard.

If I then plug in a headphones to headphone jack, Immediately soundcard and sound are present.

If I booted with the headphones already plugged in, I must unplug AND then replug the headphones to get immediately soundcard and sound are present.

I saw a single pulseaudio update go in at or around 14Feb19.

I can go back to 10Feb and redo updates, but I have also found that sometimes, even when I don't have something checked in update, it will update it anyway, so hard to get a system without that specific update while I am taking other updates. Yes that in itself is a bug but not for this bug.

hardware: Sony Vaio computer speakers, or Razer headphones. Result same.

Hardware spec sheet as well as Win7 claim the Realtek codec is ALC3202. Apparently Ubuntu is seeing it as ALC269VC.

Steve,

The reporter says the problem started on the same day as the last update:

https://launchpad.net/ubuntu/+source/pulseaudio/1:12.2-2ubuntu1

So it is a regression that occurred in an update. Or are you suggesting that tag is only for stable releases?

Hmm, actually the sound control panel for disco got redesigned and released about the same day. So it's possible this is a configuration problem from that.

Yes, indeed, I think that may be it(new alsa config panel). They added boxes and the way it works and it seems NOW that if I unplug headphones, and boot, then go to settings/sound:
set system vol to full
set output device to "speakers-builtin audio"
set configuration to "analog stereo output"
Then the speakers appear in the test box and all works as it should.
Plug in headphones and the selection changes as it should. And back and forth.

Before, those settings would not hold through a boot, NOW they do.

I did see some more alsa library stuff going in yesterday and today.
Don't know what fixed it but it seems to be fixed.
At the moment, I might guess an error in the new alsa config layout, and not pulseaudio.

I did do alsamixer and changed automute (right arrow way over) ena to disa to ena, with tests interspersed, but that seemed to make no difference.

Requires that you go to settings/sound and set stuff up correctly the first time.(I think)

I am guessing that that would be the case after a clean install, but I will not test that.

I think this should be closed/as solved, but I would like to be able to re-open it if the problem re-appears. Many thanks for all your time.

I don't completely follow, but if you are happy then yes we can close this.

Feel free to reopen it (change the status) if you feel something is still wrong.

Issue still reproducible on ubuntu 18.04 LTS

This bug is closed so if you still experience problems then please open a new bug by running:

  ubuntu-bug pulseaudio