Difference between revisions of "ModuleNotFoundError"

From GNU Radio
Jump to: navigation, search
(Add instructions for when gnuradio can be started from the terminal but not from the gui)
(Edit wrong advice. `source` doesnt work)
 
Line 62: Line 62:
 
If you get the ModuleNotFoundError error while starting GNU Radio from GUI, but can start GNU Radio using the terminal, it is because the environment variables are set for the terminal, but not for your graphical environment. Try one of the listed solutions below.
 
If you get the ModuleNotFoundError error while starting GNU Radio from GUI, but can start GNU Radio using the terminal, it is because the environment variables are set for the terminal, but not for your graphical environment. Try one of the listed solutions below.
  
1. Store the export commands stated in Part E in <code>~/.profile</code>. Then run <code>source ~/.profile</code>.<br>
+
1. Store the export commands stated in Part E in <code>~/.profile</code>. Log out and back in for the changes to take effect.<br>
2. Store the export commands stated in Part E in a new shell script in <code>/etc/profile.d/</code>. Restart your computer thereafter.<br>
+
2. Store the export commands stated in Part E in a new shell script (with any name of your choice) in <code>/etc/profile.d/</code>. Restart your computer thereafter.<br>

Latest revision as of 00:33, 17 May 2021

When you start gnuradio-companion or execute grcc, if the system isn't configured properly for GRC to find the GNU Radio Python scripts and/or libraries, then you will see an error message similar to this one:

ModNotFound.png

If you get this error message and you're running Linux, try the instructions on this page to see if any of them fix the issue. For issues and settings for OSX, see the MacInstall guide.

A. Determine the GNU Radio install prefix[edit]

If you don't know or remember your installation prefix, perform the following step:

  • on a terminal screen, enter gnuradio-config-info --prefix

then use that prefix in place of {your-prefix} in the following commands.

B. Finding the Python library[edit]

Using a terminal, enter the following command, substituting the prefix you found above in place of {your-prefix}:

find {your-prefix} -name gnuradio | grep "packages"

Put the appropriate paths it found into the export commands below. Note that the paths are separated by colons :

C. Setting PYTHONPATH[edit]

- For almost all Debian / Ubuntu (and derivative) systems, and most other 32-bit Unix/Linux systems, the paths will look like this:

export PYTHONPATH={your-prefix}/lib/{Py-version}/dist-packages:{your-prefix}/lib/{Py-version}/site-packages:$PYTHONPATH

- For other 64-bit systems, the paths will look like this:

export PYTHONPATH={your-prefix}/lib64/{Py-version}/site-packages:$PYTHONPATH

D. Setting LD_LIBRARY_PATH[edit]

- For almost all Debian / Ubuntu (and derivative) systems, and most other 32-bit Unix/Linux systems, use:

export LD_LIBRARY_PATH={your-prefix}/lib:$LD_LIBRARY_PATH

- For other 64-bit systems, use:

export LD_LIBRARY_PATH={your-prefix}/lib64:$LD_LIBRARY_PATH

E. Store the commands in a Bash start-up file[edit]

Once you have determined the correct two export commands to use, open your text editor and put them in your ~/.bash_aliases or ~/.bashrc or ~/.profile file. Save the file. There are three ways for for these changes to take effect.
1. On your terminal enter exit. Then start a new terminal.
2. Type source NAME_OF_FILE_EDITED (e.g. source ~/.profile ).
3. Reboot your computer.

As an example, your entries might be:

export PYTHONPATH=/usr/local/lib/python3/dist-packages:/usr/local/lib/python3.6/dist-packages:$PYTHONPATH
export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH

F. Starting GNU Radio from GUI[edit]

If you get the ModuleNotFoundError error while starting GNU Radio from GUI, but can start GNU Radio using the terminal, it is because the environment variables are set for the terminal, but not for your graphical environment. Try one of the listed solutions below.

1. Store the export commands stated in Part E in ~/.profile. Log out and back in for the changes to take effect.
2. Store the export commands stated in Part E in a new shell script (with any name of your choice) in /etc/profile.d/. Restart your computer thereafter.