[System76 Oryx Pro] no sound after 18.10 upgrade

Bug #1799007 reported by Tessa on 2018-10-20
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pulseaudio (Ubuntu)
Medium
Unassigned

Bug Description

After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows.

Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: tessa 11703 F.... pulseaudio
 /dev/snd/controlC0: tessa 11703 F.... pulseaudio
 /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio
 /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio
CurrentDesktop: pop:GNOME
DistroRelease: Pop!_OS 18.10
InstallationDate: Installed on 2018-03-05 (230 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
Tags: third-party-packages cosmic
Uname: Linux 4.18.0-10-generic x86_64
UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again.
UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/20/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.02dRSA2
dmi.board.asset.tag: Tag 12345
dmi.board.name: Oryx Pro
dmi.board.vendor: System76
dmi.board.version: oryp3-ess
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Oryx Pro
dmi.product.sku: Not Applicable
dmi.product.version: oryp3-ess
dmi.sys.vendor: System76

Tessa (unit3) wrote :

other report in the wild: https://askubuntu.com/questions/1085176/sound-device-lost-after-update-to-18-10

note that their debugging steps don't even work for me, running pacmd just gets a complaint that the pulse daemon isn't running, even though it looks like systemd intentionally started it in non-daemon mode:

```
$ pacmd list-cards
No PulseAudio daemon running, or not running as session daemon.
$ pstree
[...]
        |-systemd-+-(sd-pam)
        | |-at-spi-bus-laun-+-dbus-daemon
        | | `-3*[{at-spi-bus-laun}]
        | |-dbus-daemon
        | |-dconf-service---2*[{dconf-service}]
        | |-evolution-addre---5*[{evolution-addre}]
        | |-evolution-calen---9*[{evolution-calen}]
        | |-evolution-sourc---3*[{evolution-sourc}]
        | |-gnome-screensav---3*[{gnome-screensav}]
        | |-gnome-shell-cal---5*[{gnome-shell-cal}]
        | |-goa-daemon---3*[{goa-daemon}]
        | |-goa-identity-se---3*[{goa-identity-se}]
        | |-gvfs-afc-volume---3*[{gvfs-afc-volume}]
        | |-gvfs-goa-volume---2*[{gvfs-goa-volume}]
        | |-gvfs-gphoto2-vo---2*[{gvfs-gphoto2-vo}]
        | |-gvfs-mtp-volume---2*[{gvfs-mtp-volume}]
        | |-gvfs-udisks2-vo---2*[{gvfs-udisks2-vo}]
        | |-gvfsd-+-gvfsd-trash---2*[{gvfsd-trash}]
        | | `-2*[{gvfsd}]
        | |-gvfsd-fuse---5*[{gvfsd-fuse}]
        | |-gvfsd-metadata---2*[{gvfsd-metadata}]
        | |-pulseaudio---{pulseaudio}
[...]
```

Victor Perin (victorperin) wrote :

Same problem here.
Upgraded ubuntu from 18.04.

$ pacmd list-cards
No PulseAudio daemon running, or not running as session daemon.

Does anyone know a way to fix it?

Victor Perin (victorperin) wrote :

I've manage to get sound working again running:

```
$ sudo apt install --reinstall pulseaudio
$ pulseaudio
```

And at every boot I need to open a terminal for pulseaudio. (It still doesn't start with the system).

Tessa (unit3) wrote :

hmmm. I tried that, but no dice for me. pulse starts in a terminal, but nothing in my session sees a sound device still. for the one started in a terminal, it doesn't respond to kill signals, and needs to be kill -9d.

I suspect the "/usr/bin/pulseaudio --daemonize=no" process is just grabbing the soundcard and so running the second one does nothing useful. running the X11 wrapper script errors out:

$ start-pulseaudio-x11
Connection failure: Connection refused
pa_context_connect() failed: Connection refused

Given that pacmd explicitly complains about there being no daemon running, the fact that systemd is running pulseaudio with --daemonize=no is probably a bad thing.

Tessa (unit3) wrote :

Digging into the pulse config on 18.10, it looks like instead of using the daemon mode it's trying to setup up some sort of IPC socket, but this isn't getting run correctly:

tessa@viper:~$ systemctl start pulseaudio.socket
tessa@viper:~$ systemctl status pulseaudio.socket
● pulseaudio.socket - Sound System
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.socket; enabled; vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Sun 2018-10-21 10:37:45 PDT; 4s ago
           └─ ConditionUser=!root was not met
   Listen: /run/pulse/native (Stream)

note that it requires a non-root user, but running as more normal user for some reason evaluates to root and fails.

Daniel van Vugt (vanvugt) wrote :

Please run this command to send us more information about the system:

  apport-collect 1799007

tags: added: cosmic
Changed in pulseaudio (Ubuntu):
status: New → Incomplete
Pirouette Cacahuète (lissyx) wrote :

I'm also facing the same issue, and "apport-collect 1799007" does not accept to run for me, stating I'm not on the bug :/

Pirouette Cacahuète (lissyx) wrote :

Ok, in my case, |fuser -v| reveals that it's being blocked by timidity.

Tessa (unit3) wrote :

@lissyx: so you're probably just experiencing #1797714. can you give the exact fuser command you ran and the output you saw though, so others can repeat that test on this bug?

tags: added: apport-collected third-party-packages
description: updated
Tessa (unit3) wrote : AlsaInfo.txt

apport information

apport information

apport information

apport information

apport information

```
tessa@viper:~$ fuser -v /dev/snd/pcmC*
                     USER PID ACCESS COMMAND
/dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio
/dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio
tessa@viper:~$ pacmd list
Daemon not responding.
```

Daniel van Vugt (vanvugt) wrote :

Tessa,

Thanks. Can you please also attach a full system log from the machine by running this?

  journalctl -b > journal.txt

and attach it here.

Everyone else, please log your own new bug by running:

  ubuntu-bug pulseaudio

summary: - no sound after 18.10 upgrade
+ [System76 Oryx Pro] no sound after 18.10 upgrade
tags: added: system76
Daniel van Vugt (vanvugt) wrote :

Per the bug description, this is not related to Timidity.

Tessa (unit3) wrote :
Daniel van Vugt (vanvugt) wrote :

I think the main hint is in comment #15:

  tessa@viper:~$ pacmd list
  Daemon not responding.

This means pulseaudio has either hung, crashed or been killed. Please follow these instructions to see if you can find any evidence of a crash:

  https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

If not, and if the pulseaudio daemon is still running and not responding to 'pacmd list' then please try forcing a crash report with:

  killall -ABRT pulseaudio

Tessa (unit3) wrote :

@vanvugt: there's nothing in /var/crash from pulseaudio, and as noted above, pulse is started in non-daemon mode by Ubuntu. so it's running, but apps can't seem to talk to it. probably because of the failure to start the socket service, as noted above. without the socket, and without it being a daemon, I don't think there's any way for apps to actually reach pulse.

Killing pulse works fine, but it just respawns in the same broken state:

$ ps axf | grep pulse
20761 pts/0 S+ 0:00 | | \_ grep --color=auto pulse
15659 ? S<sl 0:00 \_ /usr/bin/pulseaudio --daemonize=no
$ pacmd list
No PulseAudio daemon running, or not running as session daemon.
$ killall -ABRT pulseaudio
$ ps axf | grep pulse
22402 pts/0 S+ 0:00 | | \_ grep --color=auto pulse
22248 ? S<sl 0:00 \_ /usr/bin/pulseaudio --daemonize=no
$ pacmd list
No PulseAudio daemon running, or not running as session daemon.

Daniel van Vugt (vanvugt) wrote :

OK, the wording is confusing but we still call it a "daemon" even though it has "--daemonize=no".

The command "pacmd list" should work so indeed there's a bug in pulseaudio here.

Next, please follow ALL the steps in comment #19 and in the link it mentions.

Daniel van Vugt (vanvugt) wrote :

I mean please run:

  killall -ABRT pulseaudio

and then repeat all these steps:

  https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

Please also run:

  dpkg -l > allpackages.txt

and send us the file 'allpackages.txt'.

franck (franck-du35) wrote :

for me the problem is solved with :
sudo apt remove pulseaudio
reboot

Daniel van Vugt (vanvugt) wrote :

Franck, that's very strange. If you would like to keep discussing your issue then please log a new bug.

Tessa (unit3) wrote :

@vanvugt: alright, it's been uploaded, it says it's at this URL but I don't have permissions to view that and verify:
https://errors.ubuntu.com/oops/ffc53e0c-dba2-11e8-9fcf-fa163e6cac46

packages list is attached

Daniel van Vugt (vanvugt) wrote :

Tessa,

I think these two things might be related...

1. Pop!OS doesn't like pulseaudio:

UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again.

2. You have two sound servers and should only have one:

Pulseaudio:
      Installed - Yes (/usr/bin/pulseaudio)
      Running - Yes

Jack:
      Installed - Yes (/usr/bin/jackd)
      Running - No

It sounds like System76's Pop!OS ships with jackd and they don't want you using pulseaudio. Certainly having both installed I would expect one of them might fail to access the sound hardware. This also means I am not sure the correct way to fix this other than it sounds like pulseaudio shouldn't be installed at all in Pop!OS.

Suggested quick fix: Uninstall either your jackd packages, OR your pulseaudio packages.

Fully clean fix: Reinstall Ubuntu from scratch, downloading it from here:
http://releases.ubuntu.com/18.10/

Changed in pulseaudio (Ubuntu):
status: Incomplete → Opinion
Daniel van Vugt (vanvugt) wrote :

More simply, please try this command and then reboot:

sudo apt remove jackd jackd2 jackd2-firewire

Changed in pulseaudio (Ubuntu):
status: Opinion → Incomplete
Tessa (unit3) wrote :

@vanvugt: actually, PoP! is just a light themeing a driver PPA on top of Ubuntu, it doesn't really change a lot. it also uses pulseaudio, I installed jackd after I started having issues just in an attempt to get usable sound on my system, but it didn't improve the situation. but pulseaudio was definitely broken before I installed jack.

in any case, I'll uninstall jack and re-run the crash dump settings and we'll see where we stand.

Daniel van Vugt (vanvugt) wrote :

OK, that makes sense. In that case I was misled by apport automatically writing this in the bug report:

UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again.

Tessa (unit3) wrote :

Repeated the crash report after purging the jack audio packages: https://errors.ubuntu.com/oops/831e65ae-dd64-11e8-959d-fa163ee63de6

Daniel van Vugt (vanvugt) wrote :

There is no need to send more crash reports right now. Just uninstall the jack packages and see if that solves the problem.

Tessa (unit3) wrote :

ahhh well like I said that crash dump was from after uninstalling the jack packages. things are still broken without jack installed. no sound in any app.

Daniel van Vugt (vanvugt) wrote :

1. Can you please confirm where you are looking when you say "it no longer shows any of the audio output devices"? Are you looking in Settings > Sound > Output ?

2. Can you please try booting Ubuntu from USB:
   http://releases.ubuntu.com/18.10/
   and tell us if the problem still occurs in the live USB session?

Tessa (unit3) wrote :

yes, that's where I've been looking. nothing listed for input or output in the sound control panel.

Tessa (unit3) wrote :

note that the sound devices seem to be correctly detected by the kernel:

[ 28.963298] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=2 (0x14/0x1b/0x0/0x0/0x0)
[ 28.963299] snd_hda_codec_realtek hdaudioC0D0: hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 28.963300] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 28.963302] snd_hda_codec_realtek hdaudioC0D0: dig-out=0x1e/0x0
[ 28.963302] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 28.963304] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18
[ 28.963306] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12
[ 28.975012] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16
[ 28.975048] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
[ 28.975079] input: HDA Intel PCH Speaker Surround as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18

but I can't find any devices for them under /dev:

root@viper:~# find /dev | grep sound
root@viper:~# find /dev | grep card

Daniel van Vugt (vanvugt) wrote :

Try looking in /dev/snd/ :)

Also, please try booting Ubuntu from USB:
   http://releases.ubuntu.com/18.10/
and tell us if the problem still occurs in the live USB session?

Tessa (unit3) wrote :

Ahh yes, there everything is in /dev/snd, so really starting to feel like a pulseaudio bug.

$ ls /dev/snd
by-path controlC1 hwC1D0 pcmC0D0p pcmC1D3p pcmC1D8p timer
controlC0 hwC0D0 pcmC0D0c pcmC0D1p pcmC1D7p seq

I'll try the USB boot thing this aft and get back to you.

Tessa (unit3) wrote :

Booting off USB, sound works fine, soundcards show up correctly. So... it's something that got messed up in the upgrade from 18.04, I guess?

Daniel van Vugt (vanvugt) wrote :

Yes, I suspected as much. System76 wouldn't ship a laptop without working audio on Ubuntu.

It sounds like that machine has gone through a couple of upgrades:

  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)

I can't tell what has been broken in the process, but it does look like pulseaudio since 'pacmd' isn't working for you.

I suggest:

 (a) Try to reinstall pulseaudio packages, like:
     sudo apt install --reinstall pulseaudio

or

 (b) Back up your data and then reinstall fresh from http://releases.ubuntu.com/18.10/

We may never know what went wrong on the machine before 18.10 reaches end of life in July 2019.

Changed in pulseaudio (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
Tessa (unit3) wrote :

I've already tried reinstalling pulseaudio, and it doesn't do anything. I can't really afford to reinstall my work laptop right now, I really need it to just, you know, work. ;)

but I also need working sound so I'm not really sure what to do. is there really no way to debug pulseaudio and why it's broken? if not, are there supported alternate audio servers for ubuntu which will work with everything?

Daniel van Vugt (vanvugt) wrote :

The PulseAudio developers should be able to help you with more advanced debugging. You can log a bug to get help from them at:

  https://gitlab.freedesktop.org/groups/pulseaudio/-/issues

Tessa (unit3) wrote :

ok, I've figured some more out with the help of system76 support:

https://github.com/pop-os/pop/issues/389

the TL&DR is that the issue seems to be caused by the systemd init scripts, and that stopping them all and running pulseaudio manually works fine. so this isn't really even a pulse issue, but perhaps a systemd or ubuntu packaging issue.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.