FS#37987 - [pulseaudio] pid.c: Daemon already running.

Attached to Project: Arch Linux
Opened by Robert Orzanna (orschiro) - Tuesday, 03 December 2013, 06:47 GMT
Last edited by Jan Alexander Steffens (heftig) - Wednesday, 12 February 2014, 09:35 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

On each boot I get the following message.

Dec 03 07:22:38 thinkpad rtkit-daemon[1450]: Successfully made thread 1449 of process 1449 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Dec 03 07:22:38 thinkpad rtkit-daemon[1450]: Supervising 1 threads of 1 processes of 1 users.
Dec 03 07:22:50 thinkpad rtkit-daemon[1450]: Successfully made thread 1599 of process 1599 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Dec 03 07:22:50 thinkpad rtkit-daemon[1450]: Supervising 2 threads of 2 processes of 1 users.

Dec 03 07:22:50 thinkpad pulseaudio[1599]: [pulseaudio] pid.c: Daemon already running.

Additional info:

I don't use any DE but Openbox only which I run from .xinitrc.

I left pulseaudio completely unmodified and do not start it explicitly, at least not that I am aware of.

To me it seems that something is starting the daemon multiple times.

Steps to reproduce:

Install lib32-libcanberra-pulse 0.30-4, lib32-libpulse 4.0-6, libpulse 4.0-6, pulseaudio 4.0-6, pulseaudio-alsa 2-2

Leave all default and start your system.

This is when I get this message.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Wednesday, 12 February 2014, 09:35 GMT
Reason for closing:  Fixed
Additional comments about closing:  4.99.3-1, in [testing]
Comment by Jelle van der Waa (jelly) - Thursday, 05 December 2013, 18:45 GMT
Attach your .xinitrc maybe you start it there, or in your openbox config
Comment by Robert Orzanna (orschiro) - Thursday, 05 December 2013, 18:48 GMT
Not that I am aware of.
   .xinitrc (1.4 KiB)
   autostart (0.6 KiB)
Comment by Robert Orzanna (orschiro) - Saturday, 07 December 2013, 12:16 GMT
Could it be caused by having the following two files in /etc/xdg/autostart?

pulseaudio-kde.desktop
pulseaudio.desktop
Comment by Robert Orzanna (orschiro) - Sunday, 08 December 2013, 10:28 GMT
I moved both files to {.bak} to test whether pulseaudio will still successfully start and indeed it does. However, I have no idea what is starting up pulseaudio then. Any idea what is starting pulse?

~ $ ps aux | grep pulse
orschiro 1134 2.6 0.1 353932 12252 ? S<l 10:05 2:07 /usr/bin/pulseaudio --start
orschiro 1304 0.0 0.0 69216 2380 ? S 10:05 0:00 /usr/lib/pulse/gconf-helper
orschiro 31666 0.0 0.0 12620 1068 pts/2 S+ 11:27 0:00 grep pulse

Are the .desktop entries in /etc/xdg/autostart really necessary?
Comment by Colin Keenan (colinkeenan) - Sunday, 05 January 2014, 19:00 GMT
I can confirm this happens to me in Xfce as well. It is clearly a widespread bug, but nearly nobody notices it. The point is, there does not seem to be any need to have .desktop files in the xdg folder relating to pulseaudio. Even the script in X11/xinit isn't needed. As long as pulseaudio is installed, it seems to start at boot even though nobody seems to be able to explain what is starting it. Please also see my discussion of this: https://bbs.archlinux.org/viewtopic.php?id=175241
Comment by Colin Keenan (colinkeenan) - Tuesday, 07 January 2014, 00:45 GMT
I've discovered why pulseaudio is starting even without any pulseaudio files in /etc/xdg or in /etc/X11/xinit/xinitrc.d/. The Display Manager is starting it If you disable the Display manager (and also remove all the pulseaudio files from /etc/xdg and /etc/X11/xinit/xinitrc.d) then pulseaudio won't run at all. If you leave all the pulseaudio files alone, but just disable the DM, then pulseaudio will run and you won't get any errors about it trying to run twice. I want the DM though, so for now, my solution is to delete all those pulseaudio files from the xdg and X11 directories. Really, those files need to be modified to account for the possibility that the DM already started pulseaudio.
Comment by Colin Keenan (colinkeenan) - Tuesday, 07 January 2014, 23:45 GMT
Please see  FS#38412  - [pulseaudio] pid.c: Daemon already running, Prevent by modifying ...xinitrc.d/pulseadio & PKGBUILD (https://bugs.archlinux.org/task/38412) that I have reported.
Comment by Jan Alexander Steffens (heftig) - Thursday, 06 February 2014, 20:23 GMT
Fixing this properly would require revamping PulseAudio's lifecycle management to use, e.g., the systemd user manager in order to be launched reliably and early enough. Ideally using socket activation.

Right now it's a mess of libpulse's own autospawn and various startup methods (XDG, xinit.rc), potentially racing with each other and then aborting with "daemon already running."

I'm not going to invest loads of time fixing this downstream just to avoid a warning.
Comment by Jan Alexander Steffens (heftig) - Thursday, 06 February 2014, 21:12 GMT
I forgot the xinit stuff was our downstream patch.

In the interest of keeping the package vanilla, would removing the xinit script and reactivating autospawn be a solution?