Here's an interesting bug

GNU Radio
1

That I suspect will be hard to fix.

If you run grcc in something that doesn’t have access to the X display,
it barfs:

Traceback (most recent call last):
File “/usr/local/bin/grcc”, line 27, in
from gnuradio.grc.python.Platform import Platform
File
“/usr/local/lib64/python2.7/site-packages/gnuradio/grc/python/Platform.py”,
line 23, in
from … gui.Platform import Platform as _GUIPlatform
File
“/usr/local/lib64/python2.7/site-packages/gnuradio/grc/gui/Platform.py”,
line 20, in
from Element import Element
File
“/usr/local/lib64/python2.7/site-packages/gnuradio/grc/gui/Element.py”,
line 20, in
from Constants import LINE_SELECT_SENSITIVITY
File
“/usr/local/lib64/python2.7/site-packages/gnuradio/grc/gui/Constants.py”,
line
22, in
import gtk
File “/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/init.py”,
line 64, in
_init()
File “/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/init.py”,
line 52, in _init
_gtk.init_check()
RuntimeError: could not open display

–
Marcus L.
Principal Investigator
Shirleys Bay Radio Astronomy Consortium

2

On 05/30/2013 11:31 PM, Marcus D. Leech wrote:

That I suspect will be hard to fix.

Its kind of random between releases of pygtk, but its basically known
behaviour. You need X to import gtk. Perhaps, the grcc could be modified
to import only the non gui python builder classes. I think the two (gui
and non gui) are not too badly interwoven.

-josh