** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1884455
Title:
pulseaudio creates /root/.config/p
That is a very good observation about not having to be on startup!!
After I disabled both vmware.service and virtualbox.service, I cleaned-up:
delete the '/root' and then make sure to mount it from the zfs dataset.
Then I shutdown the system yesterday evening (2020-06-25).
When I started the syst
Thanks. Although they occur after zfs-mount.service, the two best
explanations I can think of for what uses PulseAudio and might run as
root are vmware.service and virtualbox.service.
Also it's possible the unwanted directory is created after /root is
unmounted. Not necessarily on startup.
--
Yo
I can share the output of "systemd-analyze plot": please see attached file
'systemd_startup_04.svg'.
If needed I can provide output of some other commands: just let me know what
else might be useful.
** Attachment added: "svg plot of system startup"
https://bugs.launchpad.net/ubuntu/+source/
If you can provide a full list of processes running before 'zfs-
mount.service' then I might recognise something that could cause it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad
I *never* logged in graphically as root. I also do not use the root account: at
most some 'sudo' commands from time to time. In the previous comments I had the
root shell because I wanted to show as easy as possible that the whole content
of the '/root' is only one symbolic link
(fe1417537ae045
OK, if not the PulseAudio daemon then maybe a PulseAudio client did it.
That might happen if you log in graphically as root. Or it might be
something more obscure you have running as root.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
I checked and the option is not activated:
-
root@minighost:~# grep daemonize /etc/pulse/daemon.conf
; daemonize = no
root@minighost:~#
-
In fact, the only option that is activated in the /etc/pulse/daemon.conf is the
following:
-
root@minighost:~
The existence of a file in /root and also:
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1:
No PulseAudio daemon running, or not running as session daemon.
both suggest that your pulseaudio daemon is running in system-wide mode
when it shouldn't.
Please look in /etc/pulse/d
9 matches
Mail list logo