[Touch-packages] [Bug 1884455] Re: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset

2020-06-25 Thread Dumitru Sipos
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

[Touch-packages] [Bug 1884455] Re: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset

2020-06-24 Thread Dumitru Sipos
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"

[Touch-packages] [Bug 1884455] Re: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset

2020-06-23 Thread Dumitru Sipos
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

[Touch-packages] [Bug 1884455] Re: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset

2020-06-22 Thread Dumitru Sipos
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: -

[Touch-packages] [Bug 1884455] [NEW] pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset

2020-06-21 Thread Dumitru Sipos
Public bug reported: I use 'zfs' and have /root as its own dataset which is mounted during startup by 'zfs-mount.service'. At one of the latest upgrades, the 'zfsutils-linux' package failed to update because the service 'zfs-mount' service had an issue and could not mount the '/root' dataset