-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FISSURE install on newly created Ubuntu 22.04 on WSL on Windows 10 #45
Comments
I haven't tried that exact setup yet, but Ubuntu 22.04 should have the python3-pyqt5. Try doing a |
Thanks for your comment. Here is the result peterd@DESKTOP-MGMJK4K: |
tried on different Ubuntu versions peterd@DESKTOP-MGMJK4K: peterd@DESKTOP-MGMJK4K: |
after installing Python2 on 18.04 peterd@DESKTOP-MGMJK4K: |
It errors for those too when you select yes? Choosing no exits out. |
I did sudo apt install qt4-default then did ./install and selected yes and it is installing now. Got to a GUI where I see a list of software such as LTE |
There could be a conflict with some other software or you might be missing the universe ppa which is normally a default ppa for Ubuntu. You could check with:
To add it:
To see if some other program is influencing it, you might be able to get something from a reverse search:
Then purge and reinstall the offending program. |
The installation completed. Then on the GUI I accidentally hit install instead of close. I interrupted it quickly as shown below. Thanks [100%] Built target wavingz-test Install Complete |
You may have to open a new terminal for the fissure command to work. You should be ok if you canceled it immediately. There are only a couple things that can’t be run twice and I don’t think it would be that bad if they did. You can see what commands get run if you are concerned and try to fix anything being written twice. |
Can you see from the commands that were after "Install Complete" if the system was corrupted? I have a new "stupid" problem, I can't open a new terminal in Ubuntu-18.04. I can open terminals for 20.04 and 22.04 no issue. PS C:\Users\peter> wsl -d Ubuntu-18.04 |
I ignored the error message and typed fissure and the FISSURE dashboard came up. |
I’ll try WSL in the next few weeks and provide an update here if it is working. There may be factors that make the install more difficult. You can search for instances of .bashrc in the installer file and see what was added. Chances are it has to be modified if errors are produced or terminals won’t open. |
I am a new user of fissure but have worked with GNUradio. I am considering to use fissure as part of teaching communications theory at my university, since it can illustrate basic concepts using real signals. I have run teaching labs using GNUradio and USRPs for over a decade. . Is there a beginners guide to help sort out basic startup problems. For example, my RTL runs fine on SDRsharp in Windows 10, but the GNURadio flowgraph using the RTL source says "no supported devices found". Also, I find that the dashboard is often unresponsive which may be user error. Busy students quickly get frustrated. |
We are in the process of filling out the documentation in the Read the Docs user manual. It is mostly empty now with only a few tidbits, but it will get there eventually. Similarly, more lessons will be constructed towards demonstrating concepts for beginners. Anyone who wants to develop their own lessons is encouraged to do so and we offer the option to integrate those lessons to help others or we can do things to make it easier for them to maintain it themselves. Your situation is what we are trying to achieve with FISSURE, although you would certainly be a pioneer at this stage. Once the Phase I roadmap items are completed this summer, we will be doing more to actively reach out to academia for those looking to demonstrate principles in signals, cybersecurity, programming, and open source software in general. We can make a discussion post outside this issue in which to elaborate further. Depending on the FISSURE branch, different GNU Radio mechanisms and software packages are used by default. For the RTL with the maint-3.10 branch, I would check to see if only the soapy blocks are implemented in FISSURE flow graphs (Inspection Flow Graphs would be a good place to check). If the RTL is not working for certain tools or functions, we can work together to remedy it by creating a new issue and coming up with suggestions to fix it. Chances are some version of a software package was unable to be installed or conflicted with existing software and we moved on waiting for the day when someone would speak up. However if the problem happens to be attributed to a specific virtual environment, we would have to test it out sometime to confirm which steps need to be taken to ensure it works every time. If there are certain actions that cause the Dashboard to lock up, we would be very interested in seeing the steps to reproduce the behavior in a new issue so we can try to fix it. There are plenty of optimizations that still need to be done. |
installation on newly created Ubuntu 22.04 on WSL on Windows 10
can anyone help?
Thanks
Peter
eterd@DESKTOP-MGMJK4K:~/FISSURE$ ./install
Ubuntu 22.04 detected
./install: line 55: qmake: command not found
No Qt5 found.
Qt5 is required to open the installer. Do you want to proceed? [y]/n: y
[sudo] password for peterd:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package python3-pyqt5 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Unable to locate package qtcreator
E: Unable to locate package qtbase5-dev
E: Unable to locate package qtchooser
E: Unable to locate package qt5-qmake
E: Unable to locate package qtbase5-dev-tools
E: Package 'python3-pyqt5' has no installation candidate
Traceback (most recent call last):
File "/home/peterd/FISSURE/Installer/installer", line 2, in
from PyQt5 import QtCore, QtGui, uic, QtWidgets
ModuleNotFoundError: No module named 'PyQt5'
peterd@DESKTOP-MGMJK4K:~/FISSURE$ pwd
/home/peterd/FISSURE
The text was updated successfully, but these errors were encountered: