Headless problems: 'cannot connect to X server' and the like
Posted: Mon Jul 30, 2012 12:38 pm
Hi there!
Finally got my hands on my rpi...set it up with raspbian, like it so far.
Besides the current state of the alsa drivers (no mmap/jackd, underruns, etc...) I'm tinkering with software instruments on my pi. However I am running into problems with several applications I am trying out. In order to keep system load low I want to run it headless (=without starting X).
For example 'ams': From the man page of ams: „--nogui Start without GUI“.
For some reason, ams is not responding to that switch:
Similar problem with bristol: man startBristol: „-gui Do not start the GUI, only the engine.“
So I'm left wondering, what else I could to, to get those applications working without X. Anyone able to shed some light on those issues?
Thanks in advance,
Konrad
Btw, I'm running latest raspbian:
Finally got my hands on my rpi...set it up with raspbian, like it so far.
Besides the current state of the alsa drivers (no mmap/jackd, underruns, etc...) I'm tinkering with software instruments on my pi. However I am running into problems with several applications I am trying out. In order to keep system load low I want to run it headless (=without starting X).
For example 'ams': From the man page of ams: „--nogui Start without GUI“.
For some reason, ams is not responding to that switch:
Code: Select all
pi@raspberrypi ~ $ ams --nogui
ams.real: cannot connect to X server
pi@raspberrypi ~ $ ams -nogui
ams.real: cannot connect to X serverCode: Select all
pi@raspberrypi ~ $ startBristol -audio alsa -gui
checking availability of TCP port 16174
using port 16174
starting logging thread [@1343651643.409969]
Copyright (c) by Nick Copeland <nickycopeland@hotmail.com> 1996,2012
This program comes with ABSOLUTELY NO WARRANTY; for details type `<Ctrl> w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `<Ctrl> g' for details of GPL terms.
emulation defaults:
-voices 32
-detune 0
-gain 2
-pwd 2
-glide 5
-curve 175
brighton version 0.60.10
Jul 30 12:34:03 bristol [0.084618] starting console logging [@1343651643.409969]
Jul 30 12:34:03 bristol [0.093622] Copyright (c) by Nick Copeland <nickycopeland@hotmail.com> 1996,2012
Jul 30 12:34:03 bristol [0.104279] This program comes with ABSOLUTELY NO WARRANTY; for details type
Jul 30 12:34:03 bristol [0.107380] `bristol warranty'. This is free software, and you are welcome to redistribute it
Jul 30 12:34:03 bristol [0.110696] under certain conditions; type `bristol conditions' for details of terms.
Jul 30 12:34:03 bristol [0.111726] bristol version 0.60.10
Jul 30 12:34:03 bristol [0.113629] bristol
Jul 30 12:34:03 bristol [0.114254] -rate 44100
Jul 30 12:34:03 bristol [0.116326] -count 256
Jul 30 12:34:03 bristol [0.117278] -audio alsa
Jul 30 12:34:03 bristol [0.119076] -gui
Jul 30 12:34:03 bristol [0.121033] -port 16174
Jul 30 12:34:03 bristol [0.122056] jsm will use 'startBristol -audio alsa -gui'
Jul 30 12:34:03 bristol [0.127018] generate bandlimited waveforms(31, 12, 84, 1.50, 0.80, 44100)
Jul 30 12:34:03 bristol [0.132399] Fixing samplerate at 44100
Jul 30 12:34:03 bristol [0.196329] rescheduled thread: 40
Jul 30 12:34:03 bristol [0.199037] midi jack: 128.1
Jul 30 12:34:03 bristol [0.201123] Opened listening control socket: 16174
Jul 30 12:34:03 bristol [0.201768] returning handle 0, flags 80000020, fd 4
Jul 30 12:34:03 bristol [0.203178] opened control socket
Jul 30 12:34:03 bristol [0.205750] midiOpen: 16174(100)
Jul 30 12:34:03 bristol [0.206696] opened midi device 128.1
brighton
-audio alsa
-gui
-port 16174
starting event management thread
cannot connect to :0.0
brightonOpenDisplay(): cannot open :0.0
brightonInterface() failed
could not create window
Jul 30 12:34:33 bristol [30.331587] init watchdog exception
Jul 30 12:34:33 bristol [30.335699] terminate MIDI signalling
Jul 30 12:34:33 bristol [30.339064] audio thread failed: exiting.
Jul 30 12:34:34 bristol [31.200596] midiThread exiting
Jul 30 12:34:34 bristol [31.203228] midithread exited
Jul 30 12:34:34 bristol [31.205442] bristol parent exiting
Jul 30 12:34:34 bristol [31.207478] terminating logging thread
pi@raspberrypi ~ $Thanks in advance,
Konrad
Btw, I'm running latest raspbian:
Code: Select all
pi@raspberrypi ~ $ uname -a
Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux