Bug 25667 - gnuradio-companion fails to run
Summary: gnuradio-companion fails to run
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Barry Jackson
QA Contact:
URL: https://github.com/gnuradio/gnuradio/...
Whiteboard:
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2019-11-07 18:31 CET by Barry Jackson
Modified: 2019-11-18 14:37 CET (History)
0 users

See Also:
Source RPM: gnuradio-3.8.0.0-mga8.src.rpm
CVE:
Status comment:


Attachments

Description Barry Jackson 2019-11-07 18:31:30 CET
Description of problem:
gnuradio-companion fails to run from menu or CLI.

$ gnuradio-companion
Traceback (most recent call last):
  File "/usr/bin/gnuradio-companion", line 102, in <module>
    run_main()
  File "/usr/bin/gnuradio-companion", line 95, in run_main
    exit(main())
  File "/usr/lib/python3.8/site-packages/gnuradio/grc/main.py", line 83, in main
    platform.build_library()
  File "/usr/lib/python3.8/site-packages/gnuradio/grc/core/platform.py", line 197, in build_library
    utils.hide_bokeh_gui_options_if_not_installed(self.blocks['options'])
  File "/usr/lib64/python3.8/collections/__init__.py", line 891, in __getitem__
    return self.__missing__(key)            # support subclasses that define __missing__
  File "/usr/lib64/python3.8/collections/__init__.py", line 883, in __missing__
    raise KeyError(key)
KeyError: 'options'

This has been reported upstream in:
https://github.com/gnuradio/gnuradio/issues/2873

Please assign to me - thanks.
Comment 1 Lewis Smith 2019-11-07 20:32:52 CET
Thanks for the report.

> Please assign to me
Done; and marked as 'upstream'.

Keywords: (none) => UPSTREAM
Assignee: bugsquad => zen25000
URL: (none) => https://github.com/gnuradio/gnuradio/issues/2873

Comment 2 Barry Jackson 2019-11-18 14:37:14 CET
Fixed in svn commit 1461629

Closing

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.