Hello Bill,

Am Sonntag 05 August 2018 schrieb William Morder:
> (EE) Fatal server error
> Could not create lock file in /tmp/.tXO-lock
>
> and
>
> tdm [2692] error: X server died during startup
> X server for display :0 can't be started, session disabled
>
> I tried removing the lock file via command-line, and got this;
>
> rm: cannot remove 'XO-lock' Read-only file system
>

I lost track about the original problem, but this error does not seem to have 
any relation to pulse. Look at the messages. The X server died because of 
read-only mounted file system. This seems to be the root of the actual problem. 
I only ever have encountered read-only mounted file systems during boot mostly 
because missing file systems or errors of which.

> This seems to be caused by some conflict between Debian and Devuan
> packages. 

Why would you ever mix Devuan and Debian? Devuan basically *is* Debian exept a 
few packages without dependencies to systemd stuff. Devuan explicitly says not 
to mix with Debian.

If you want to get rid of systemd choose a straight upgrade path from Debian to 
Devuan like described on their website and enjoy.

> I tried removing everything systemd, but that caused problems. I 
> installed Devuan packages, and made init my PID 1. I removed systemd-sysv,
> but didn't do a total purge of systemd stuff, and it ran great, "purring
> like a kitten" (as I said too quickly), and then this crap.

See from the outside this is far too vague (for me at least) to guess what you 
actually did and if or how you broke something. If you're running Debian there 
are ways to use sysvinit as init system, but you shouldn't install Devuan 
packages in a Debian, I think. Run either Debian or Devuan. There lies no 
advantage in mixing them, I'm quite certain.

HTH,

kind regards,
Stefan