On 6/29/23 18:28, Abhimanyu Sethia wrote:
> Hi
>
> I am trying to run a GNU Radio Companion Flowgraph. I instantiated a
> POWDER O-RAN Profile
> <
https://www.powderwireless.net/show-profile.php?project=PowderProfiles&profile=O-RAN> with these <
https://www.powderwireless.net/p/PowderProfiles/O-RAN&rerun_paramset=8b225f4d-16af-11ee-9f39-e4434b2381fc>parameters. Then, I successfully installed gnu-radio using `sudo apt-get install gnuradio` (version installed- 3.10.5.1). After this, when I try to launch GNU Radio Companion using command `gnuradio-companion`, it throws the following error:
> While trying to display an error message, another error occurred
> Namespace Gtk not available The original error message follows.
> ValueError Failed to initialize GTK. If you are running over ssh, did
> you enable X forwarding and start ssh with -X? (Namespace Gtk not
> available)
> *Additional Information that might be useful*
>
> * I have tried the same steps on local terminal (ssh-ed using -X flag
> and with Xming app installed on Windows) as well as on the VNC
> window. Both give the same error message.
> * I tried to implement the solution suggested here
> <
https://stackoverflow.com/questions/56823857/valueerror-namespace-gtk-not-available> and ran /sudo apt-get install libgtk-3-dev /and /sudo apt install python3-gi gobject-introspection gir1.2-gtk-3.0 . /After installing the apps, /gnuradio-companion/ still did not work but the error message changed to this-
https://pastebin.com/5e9qQzsp <
https://pastebin.com/5e9qQzsp>.
>
> Any help on how do I run gnuradio-companion would be appreciated.
Hi Abhimanyu. I'm not sure why gnuradio-companion doesn't pull in these
deps (gobject-introspection python3-gi gir1.2-gtk-3.0) by default on
Ubuntu 22, but that is indeed the first step. As for the second issue,
that is an X forwarding thing. If you try running `xterm` or similar,
you will get a more meaningful error (likely that DISPLAY is not set).
Some Linux distros do not build xorg-server with XC-SECURITY, so when
ssh runs its xauth generate command, that fails; so those users might
need to use both `ssh -X -Y` (man ssh) to forward. I wonder if that is
the case for you, or maybe some other problem when ssh runs xauth (e.g.,
a bug where xauth is not in the expected place). You can check by
adding `-vv` to your ssh command and look for errors running xauth. Try
running the xauth command manually yourself with a different path (ssh
uses a tmpdir that won't exist if you just copy what it ran from the
log), and see if there is an error.
David