On Fri, Jun 1, 2012 at 3:23 AM, Easior <eas...@tom.com> wrote: [ snip ] > Thanks again. My result is as follows: > > $ ps aux | grep pulse > easior 2989 0.0 0.6 100052 5472 ? Sl 15:47 0:00 > /usr/bin/pulseaudio --start --log-target=syslog > easior 2993 0.0 0.3 12636 2708 ? S 15:47 0:00 > /usr/libexec/pulse/gconf-helper [ snip ] > I think that the runtime files should be in the /var/somewhere or /root/ even > if the > pulseaudio is been running as the superuser. Do you?
I suppose, but your system is doing really weird stuff: running pulseaudio as user and writing to / should be, at least theoretically, impossible. PulseAudio is not setuid'. You could check proc to see if it's actually PA writing to /; for example, I have $ ps aux | grep pulse canek 752 0.0 0.1 320356 5624 ? Sl May27 2:52 /usr/bin/pulseaudio --start --log-target=syslog canek 755 0.0 0.0 190328 20 ? Sl May27 0:00 /usr/libexec/pulse/gconf-helper So I do $ ls -l /proc/752/fd/ total 0 lr-x------ 1 canek canek 64 May 30 20:39 0 -> /dev/null l-wx------ 1 canek canek 64 May 30 20:39 1 -> /dev/null lrwx------ 1 canek canek 64 May 30 20:39 10 -> /home/canek/.pulse/a8880ec371495fe2255463514a0d14e8-device-volumes.x86_64-pc-linux-gnu.gdbm lrwx------ 1 canek canek 64 May 30 20:39 11 -> /home/canek/.pulse/a8880ec371495fe2255463514a0d14e8-stream-volumes.x86_64-pc-linux-gnu.gdbm lrwx------ 1 canek canek 64 May 30 20:39 12 -> /home/canek/.pulse/a8880ec371495fe2255463514a0d14e8-card-database.x86_64-pc-linux-gnu.gdbm So I can see that my PA process has opened files on /home/canek/.pulse/. However, I guess that will only confirm that your PA process is opening files in /. So this I would do (as root): 1. Backup any pulse file in /etc: $ tar zcvf /root/pulse-conf-bak.tar.gz $(find /etc -iname "*pulse*") In my system, there are only 4 PulseAudio files in /etc: $ find /etc -iname "*pulse*" /etc/pulse /etc/xdg/autostart/pulseaudio-kde.desktop /etc/xdg/autostart/pulseaudio.desktop /etc/dbus-1/system.d/pulseaudio-system.conf 2. Uninstall pulse: $ emerge -C pulseaudio 3. Remove every single file in /etc that looks related to pulse (check before that nothing else is getting in the list): $ find /etc -iname "*pulse*" # If everything seems safe to delete, then $ rm -rf $(find /etc -iname "*pulse*") 4. Emerge PA again: $ emerge -1v pulseaudio 5. Delete /.pulse and all its files. 6. Reboot. If after all this you are still getting the .pulse directory in /, then I have no idea how is getting in there. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
