Description of problem: gnuradio-companion does not work on Fedora 35. Version-Release number of selected component (if applicable): gnuradio-3.9.2.0-6.fc35.x86_64 How reproducible: Always. Steps to Reproduce: 1. Try to start gnuradio-companion on Fedora 35. Actual results: $ gnuradio-companion Traceback (most recent call last): File "/usr/bin/gnuradio-companion", line 53, in check_gtk from gi.repository import Gtk File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 671, in _load_unlocked ImportWarning: DynamicImporter.exec_module() not found; falling back to load_module() During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/gnuradio-companion", line 90, in <module> check_gtk() File "/usr/bin/gnuradio-companion", line 57, in check_gtk die(err, "Failed to initialize GTK. If you are running over ssh, " File "/usr/bin/gnuradio-companion", line 32, in die from gi.repository import Gtk File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 671, in _load_unlocked ImportWarning: DynamicImporter.exec_module() not found; falling back to load_module() Expected results: It should start. Additional info: N/A
It's warning, interesting that it tracebacks. On the affected line there is: > from gi.repository import Gtk I.e. no idea why it tracebacks, something wrong with the gtk?
Potentially related upstream issue, so far only reported once. https://github.com/gnuradio/gnuradio/issues/4891#issuecomment-881699070 > I.e. no idea why it tracebacks, something wrong with the gtk? yes :( whether or not importing fails **seems to** depend on the warnings settings, even if there's no difference in emitted warnings. Haven't tried running from F35 yet, will have to do. Might or might not be triggerable in a container, seeing that GTK/Gdk might interact with X more intimately than I can facilitate with sharing of sockets and files into a podman container :/
Upstream issue for this particular bug report: https://github.com/gnuradio/gnuradio/issues/5216
OK, as a workaround I will patch out the 'warnings.filterwarnings("error")' downstream until better fix is available.
FEDORA-2021-9f50b3b3b9 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2021-9f50b3b3b9
FEDORA-2021-9f50b3b3b9 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-160f1cfd85 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-160f1cfd85
FEDORA-2021-160f1cfd85 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-160f1cfd85` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-160f1cfd85 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
*** Bug 2016400 has been marked as a duplicate of this bug. ***
(In reply to Fedora Update System from comment #8) > FEDORA-2021-160f1cfd85 has been pushed to the Fedora 35 testing repository. > Soon you'll be able to install the update with the following command: > `sudo dnf upgrade --enablerepo=updates-testing > --advisory=FEDORA-2021-160f1cfd85` > You can provide feedback for this update here: > https://bodhi.fedoraproject.org/updates/FEDORA-2021-160f1cfd85 > > See also https://fedoraproject.org/wiki/QA:Updates_Testing for more > information on how to test updates. Followed this instruction and now it works on Fedora 35. The version that did not work was 3.9.2.0-6 and the updated one is 3.9.2.0-7. Thanks. Harish
FEDORA-2021-160f1cfd85 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.