On Sat, Aug 16, 2014 at 11:10 PM, 张敬强 <godfrey.pub...@gmail.com> wrote: > 在 2014年8月16日 星期六 13:07:39，Felipe Sateler 写道： >> > 8月 16 11:53:23 SUN pulseaudio[10094]: [pulseaudio] main.c: Failed to >> > acquire >> > autospawn lock >> >> This seems fishy: these two are from different PID's. What does `ps >> -fea | grep pulseaudio` say? >> > > If set autospawn = no in .config/pulse/client.conf, there is no "Daemon > already running" message > the ps result: > g0dfrey 1206 1 0 10:38 ? 00:00:00 /usr/bin/pulseaudio --start > g0dfrey 1223 1 0 10:38 ? 00:00:00 /bin/sh > /usr/bin/start-pulseaudio-kde > > If I delete .config/pulse/client.conf, then "Daemon already running" message > come back > the ps result: > g0dfrey 1296 1 0 11:01 ? 00:00:00 /usr/bin/pulseaudio --start > --log-target=syslog > g0dfrey 1309 1 0 11:01 ? 00:00:00 /bin/sh > /usr/bin/start-pulseaudio-kde > the journald message: > 8月 17 11:01:29 SUN pulseaudio[1306]: Daemon already running.
Do you see the problem if you disable autospawn? That is, disabling autospawn and after rebooting, do you still see the problem of the secure directory? -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
