startBristol fails trying to connect mini link

giving this command
andrea@ubuntustudio:~$ startBristol -mini
a white screen appears (I guess it should be Bristol) and I get this output (as soon as it's done printing it the white screen disappears)

        You may want to make bristolengine a suid-root executable
spawning midi thread
Could not reschedule thread to 2
parent going into idle loop
        flags are 8a000000
midi sequencer
Returning socket 3
Opened listening control socket: 5028
Client ID = 129
Queue ID = 1
Device name did not parse, defaults 128.0
Cannot subscribe port 0 from client 128: Operation not permitted
Error opening midi device /dev/midi, exiting midi thread
connected to :1.0 (80f82f0)
display is 1280 by 1024 pixels
Window is w 1280, h 1024, d 24, 0 0 0
Using TrueColor display
masks are ff0000 ff0000 ff0000
INIT: 80f8008
Initialise the mini link to bristol: 80fe5a8
hostname is localhost, bristol
port is 5028
Connected to the bristol control socket: 5
bristolengine already active
80d4e80 80000000 0
parent exiting
return - no data in buffer
cleanupBristol(0)

guess it's more or less the same problem (I also tried running jack first but it makes no difference)
my distro is Ubuntu (actually Ubuntu Studio but it's the same thing, right?) and the sound card is a realtek alc882

EDIT:
startBristol -libtest works for me (it doesn't make any sound but if I got it right it's supposed to start the GUI only)

EDIT: I solved compiling the source of bristol 0.10.12. first make sure you have all the other packages you need (I needed to use synaptic for a couple of them...)

This package is still broken on 8.04. Guess nobody has had time to look at it. Probably should be patched or pulled from the distros.

Is this symptom still reproducible in 8.10?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Still broken in 9.04 which shouldn't be a surprise as it's the same version packaged. A new version in 9.10 though so fingers crossed for that.

Although after attempting to install the 9.10 package on 9.04 (since it had no newer dependencies) it still seems broken (and is compiled without jack support). Although obviously there might be something different in 9.10 which causes it to not be broken.

I have changed the status to Confirmed because it has happened to me today.

Please try to reproduce this with the latest release available in Lucid before re-changing the status.

Can't confirm on Lucid, closing.

The same problem persists in Lucid (10.04):

startBristol -mini
checking availability of TCP port 5028
using port 5028
generate bandwidth limited waveforms(31, 12)
spawning midi thread
could not reschedule thread
parent going into idle loop
Init waiting for midi thread OK status
Fixing samplerate at 44100
midi sequencer: bristol
Opened listening control socket: 5028
midiOpen: 5028(100)
Client ID = 128
Queue ID = 0
Registered 128 0
Device name "bristol" did not parse, defaults 128.0
Got midi thread OK status
bristol version 0.40.8
connected to :0.0
display is 1280 by 800 pixels
Window is w 1280, h 800, d 24, 0 0 0
Using DirectColor display
Initialise the mini link to bristol: 84faef8
hostname is localhost, bristol
TCP port: 5028
Accepted connection from 0 (3) onto 2 (5)
Connected to the bristol control socket: 4
bristolengine already active
created 32 voices: allocated 32 to synth
 sid is 0
spawning audio thread
could not reschedule thread
init waiting for audio thread OK status
bristolAudioOpen(plughw:0,0, 44100, 256, 1a00008)
audioOpen(0012d080, 0, 1024): plughw:0,0
opening device plughw:0,0, flags 0000000d
open playback on plughw:0,0, pre 8
Error opening PCM device plughw:0,0
Problem opening audio device plughw:0,0, exiting audio thread
Midi read retry (9136)
audio thread failed: exiting.
parent exiting
return - no data in buffer for 0
cleanupBrighton(0)
cleared sigpipe handler
cleanupBrighton(0)
midi write error, fd 4, size 1
return - no data in buffer for 0
socket closed
request acked: -1

startBristol -libtest does work again (not producing any sound), and gives this output:

bristol version 0.40.8
connected to :0.0
display is 1280 by 800 pixels
Window is w 1280, h 800, d 24, 0 0 0
Using DirectColor display
Initialise the hammondB3 link to bristol: a071ef8
user r 1000/1000, e 1000/1000
Read Configuration: hammondB3
brightonWorldChanged(765 400 10 10)
going operational: a067008, a071ef8
�
��cleared sigpipe handler
cleanupBrighton(0)
socket closed
request acked: -3

Thank you for taking the time to report this bug. This issue has been fixed in newer versions of Ubuntu, and Jaunty/ Karmic are EOL. Thus, I am closing this bugtask.

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".