Bristol crashes on startup

From Arnout Engelen

        You may want to make bristolengine a suid-root executable

Strange message: it is suid-root.

spawning midi thread
Could not reschedule thread to 2
parent going into idle loop
connected to :0.0 (80f82f0)
display is 2960 by 1050 pixels
Window is w 2960, h 1050, d 24, 0 0 0
Using DirectColor display
masks are ff0000 ff0000 ff0000
INIT: 80f8008
Initialise the mini link to bristol: 80fe810
        flags are 8a000000
midi sequencer
Returning socket 3
Opened listening control socket: 5028
Client ID = 132
Queue ID = 0
Device name did not parse, defaults 128.0
Cannot subscribe port 0 from client 128: Operation not permitted

Not sure what that means.

Error opening midi device /dev/midi, exiting midi thread

Indeed that device doesn't exist, I used to be able to use vkeybd with bristol though.

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)

...?

[edit] And now it works

For some reason it started working. Beats me as to why. JACK is not running, it started running when I ran it with '-v'. The hammond module still crashes when used, though that worked before also.

arnouten@bird:~$ bristol
        You may want to make bristolengine a suid-root executable
spawning midi thread
Could not reschedule thread to 2
parent going into idle loop
connected to :0.0 (80f82f0)
display is 2960 by 1050 pixels
Window is w 2960, h 1050, d 24, 0 0 0
Using DirectColor display
masks are ff0000 ff0000 ff0000
INIT: 80f8008
Initialise the mini link to bristol: 80fe810
        flags are 8a000000
midi sequencer
Problem with bind

This is where it starts to go different. Maybe the bristolengine was still running? Wonder how i started it...

Could not open control listening socket: 0
No controlling socket available: anticipating MIDI
Error opening control device, exiting midi thread
hostname is localhost, bristol
port is 5028
Connected to the bristol control socket: 5
bristolengine already active
80d4e80 80000000 0
acceptConnection(0)
Accepted connection from 0 (3) onto 2 (5)
bristolSystem(127, 0, 64) 10
        flags are 2010
getsid(80d6a48, 0): 0
getsid(81b5d68, 0): 1
getsid(81c8918, 0): 2
configured 16 voices
message from 2, 81c8918
bristolSystem(127, 0, 14) 0
        flags are 700
2:      2 2
configuring midi channel to 0
bristolSystem(127, 0, 2) 0
        flags are 100
bristolSystem(127, 0, 12) 0
        flags are 600
1:      2 2
initialising one bristolmini
CID: 3
createDisplay()
createDisplay()
done create interface: 80f80c0, 80fe810
brightonWorldChanged(748 400 10 10)
parent exiting
Allocated 24 colors (48)
        going operational: 80f8008, 80fe810
Allocated 48 colors (72)

[edit] Running without MIDI in

Pretty useless (playing with the mouse is silly), but:

• run the engine with 'bristolengine -mididev /dev/snd/seq'
• run bristol with 'bristol'