(x-www-browser:12505): dconf-CRITICAL **: unable to create directory xsession-errors file indicates that dconf is also having the Pulseaudio starts normally, at some point itĬrashes and refuses to restart complaining it can't create a directory in This does not look like pulseaudio-specific.
Pulse secure debian 4.13 free#
Feel free to close this as not a bug.ĭate: Thu, 11:22:58 +0100 Package: pulseaudio
Thus, the pulseaudio daemon was already running. I: main.c: Running in system mode: noĮ: pid.c: Daemon already running.Į: main.c: pa_pid_file_create() failed. I: main.c: Using modules directory /usr/lib/pulse-4.0/modules. I: main.c: Using state directory /home/trey/.pulse. I: main.c: Using runtime directory /run/user/1000/pulse. I: core-util.c: Failed to acquire high-priority I: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: I: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Pulseaudio -log-level=info -log-target=stderr Versions of packages pulseaudio suggests:ĭate: Wed, 21:15:57 -0600 I rebooted my machine at least once. Versions of packages pulseaudio recommends: Versions of packages pulseaudio depends on: Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) My attempt to build from source (as suggested by #576769) failed because IĪpparently built the pulseaudio_4.0-6 source, not pulseaudio_4.0-6+b1, and this Same issue, but doesn't report the actual name of the secure directory attempted. I see bug #576769 which seems to report the I have ensured my user is part of the audio, rwxr-xr-x 1 root root 83K Sep 12 05:12 /usr/bin/pulseaudio* Pulseaudio is setuid root, as the following shows: run/user/ directory, not my user (UID 1000). It appears that pulseaudio is trying to open the lock in root's (UID 0's) W: lock-autospawn.c: Cannot access autospawn lock.Į: main.c: Failed to acquire autospawn lock I ran pulseaudio from a zsh console, and I got this result:Į: core-util.c: Failed to create secure directory Pulseaudio wasn't working: I had no sound, and pavucontrol fails to connect to I reinstalled my Debian sid system after a hard drive failure, and noticed that
0 kommentar(er)
