# Re: Question about gnuradio-companion

**URL:** <https://www.ruby-forum.com/t/re-question-about-gnuradio-companion/230482>\
**Category:** GNU Radio\
**Created:** [June 19, 2014, 5:27pm UTC](https://www.ruby-forum.com/t/re-question-about-gnuradio-companion/230482 "2014-06-19T17:27:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jason\_sam](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/7993a0/32.png) [@jason\_sam](https://www.ruby-forum.com/u/jason_sam)\
**Post date:** [June 19, 2014, 5:27pm UTC](https://www.ruby-forum.com/t/re-question-about-gnuradio-companion/230482/1 "2014-06-19T17:27:47Z")

</div>

> > > But with this info, I’m not sure. That’s not an error that GNU Radio is  
> > > gnuradio companion. But as before if I execute the python script companion
> 
> and that could be annoying. May also be a problem if trying to  
> remotely log in and run the app.
> 
> Tom

I just ran into Scott’s problem.

The problem is not that gnuradio-companion’s popen() of …/top\_block.py  
is failing, it’s that the popen() of the xterm executable, xterm, is  
failing.

gnuradio-companion tries to open an xterm when you have a “No GUI” top  
block.

$ sudo yum install xterm

solved the problem for me.

Regards,  
Andy