oryx pro - sleep no longer works after Pop! 18.10 upgrade

[nergdron]

Distribution (run cat /etc/os-release):

NAME="Pop!_OS" VERSION="18.10" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 18.10" VERSION_ID="18.10" HOME_URL="https://system76.com/pop" SUPPORT_URL="http://support.system76.com" BUG_REPORT_URL="https://github.com/pop-os/pop/issues" PRIVACY_POLICY_URL="https://system76.com/privacy" VERSION_CODENAME=cosmic UBUNTU_CODENAME=cosmic

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

not really sure what package sleep issues fall under. the kernel? linux-image-4.18.0-10-generic: Installed: 4.18.0-10.11 Candidate: 4.18.0-10.11 Version table: *** 4.18.0-10.11 500 500 http://ubuntu.ca-west.mirror.fullhost.io/ubuntu cosmic/main amd64 Packages 500 http://mirror.enzu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status

Issue/Bug Description:

after upgrading my oryx pro to Pop! OS 18.10, sleep mode has stopped working correctly. the computer goes to sleep for somewhere under 30s, and then wakes up again.

Steps to reproduce (if you know):

put computer to sleep. watch it wake up again on its own.

Expected behavior:

stays asleep.

Other Notes:

[brs17]

@nergdron For the quickest response, I would recommend you contact System76 support via a support ticket (or give them a call).

[brs17]

Which Oryx pro do you have?

[nergdron]

I'm not sure how I tell which revision I have, lshw doesn't show anything useful. where do I find that?

[brs17]

The graphical System76-driver tool should show you, as would the the output of sudo dmidecode | grep Version

[nergdron]

Version: 1.05.02dRSA2 Version: oryp3-ess

[nergdron]

working through this issue with system76 support, and I've discovered a bit of a workaround that helps figure out where this problem is happening. it looks like in 18.10 pulseaudio is started by systemd as a user process, not a daemon, but all the user apps complained they couldn't find a daemon. after disabling the systemd init and starting pulse manually, my devices appear and pulse works fine!

tessa@viper:~$ systemctl --user disable pulseaudio.service
tessa@viper:~$ systemctl --user disable pulseaudio.socket
tessa@viper:~$ systemctl --user stop pulseaudio.*
tessa@viper:~$ pulseaudio --start

further investigation reveals that the user pulseaudio.socket systemd job seems to be responsible:

$ systemctl --user start pulseaudio.socket
$ pulseaudio --daemonize=no
W: [pulseaudio] authkey.c: Failed to open cookie file '/home/tessa/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key '/home/tessa/.config/pulse/cookie': No such file or directory
E: [pulseaudio] socket-server.c: bind(): Address already in use
E: [pulseaudio] module.c: Failed to load module "module-native-protocol-unix" (argument: ""): initialization failed.
W: [pulseaudio] module.c: module-combine is deprecated: Please use module-combine-sink instead of module-combine!
W: [pulseaudio] module-combine.c: We will now load module-combine-sink. Please make sure to remove module-combine from your configuration.
E: [pulseaudio] main.c: D-Bus name org.PulseAudio1 already taken.
$

however, if I comment out the references to pulseaudio.socket from the systemd config (/usr/lib/systemd/user/pulseaudio.service) and try to start pulseaudio.service on its own, it still fails to work correctly.

so. is systemd to blame? something else? I'm not sure, but I can hopefully just disable these supplied services and start pulseaudio in my session autostart.

[brs17]

I attempted to recreate this issue with a fresh 18.10 install. The issue did not happen. Going to try an upgrade from 18.04->18.10 next.

[brs17]

Upgrading a fresh install did not lead to this issue either.