Bug 92061

Summary: Pulseaudio daemon cannot start at all after update from 6.0 to 6.99
Product: PulseAudio Reporter: ngoonee
Component: daemonAssignee: pulseaudio-bugs
Status: RESOLVED FIXED QA Contact: pulseaudio-bugs
Severity: major    
Priority: medium CC: lennart
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description ngoonee 2015-09-21 01:56:39 UTC
Not able to start pulseaudio daemon when upgrading to 6.99.

Am using Arch Linux 64-bit.

Here's pulseaudio -vvvv for working[1] and not working[2]

[1] - http://pastebin.com/QNgjBFvG
[2] - http://pastebin.com/ijp4mbFw

It's 1.4k++ lines each, but the difference between both logs that I observe is that [2] just hangs after loading module-esound-protocol-unix, while [1] continues to load module-native-protocol-unix.

And by 'hang', I really mean 'hang'. Control-C does not work in that terminal, nor does a normal kill, I need kill -9 to terminate that process.

Using the basic default.pa and daemon.conf that ships with Arch, not sure whether many changes have been made there but I doubt it. Will provide if its relevant, on request.
Comment 1 ngoonee 2015-09-21 02:29:49 UTC
If I comment out load-module module-native-protocol-unix then the daemon starts, but of course its not usable.
Comment 2 Jan Alexander Steffens (heftig) 2015-09-21 02:33:16 UTC
strace might be useful, as well as a stacktrace while it hangs.
Comment 3 Jan Alexander Steffens (heftig) 2015-09-21 02:36:00 UTC
This reminds me - pulseaudio 6.99 in Arch now uses systemd socket activation (pulseaudio.socket and pulseaudio.service).

Does it work after you use "systemctl --user stop pulseaudio.{socket,service}"?
Comment 4 ngoonee 2015-09-21 02:52:19 UTC
Ah, when did systemctl --user become a thing again? I thought it was dead? I still had an old pulseaudio.service in my home directory from using systemctl --user before it was dropped/deprecated a year or so back.

Deleting my pulseaudio.service solves things. PEBKAC, sorry.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.