Have you tried with just the following?
startBristol -jack -b3
It looks like the engine has failed to start due to the midi selection (the
default midi options are the ALSA seq so I would advise not changing that).
This causes the GUI to fail as well since the engine is not available. What
version of bristol is this? I am surprised by the error message regarding
'suid root' as I thought this was dropped in the -69 release on sourceforge
- it should now rely on PAM RT permissions or be started as root, so the
message is superfluous and you only need suid permissions if you want to use
bristol dedicated to the audio device with RT scheduling.
>From: Larry Troxler
Express yourself instantly with MSN Messenger! Download today it's FREE!