Bug 28605 - nanovna-saver fails to start
Summary: nanovna-saver fails to start
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: QA Team
QA Contact:
Whiteboard: MGA8-64-OK
Keywords: advisory, validated_update
Depends on:
Reported: 2021-03-16 01:06 CET by Barry Jackson
Modified: 2021-04-12 22:02 CEST (History)
4 users (show)

See Also:
Source RPM: nanovna-saver-0.3.9-0.pre.1.mga8.src.rpm
Status comment:


Description Barry Jackson 2021-03-16 01:06:31 CET
Description of problem:
nanovna-saver fails to start with the following error:

[baz@jackodesktop ~]$ nanovna-saver
Traceback (most recent call last):
  File "/usr/bin/nanovna-saver", line 33, in <module>
    sys.exit(load_entry_point('NanoVNASaver==0.3.9rc0', 'console_scripts', 'NanoVNASaver')())
  File "/usr/bin/nanovna-saver", line 25, in importlib_load_entry_point
    return next(matches).load()
  File "/usr/lib64/python3.8/importlib/metadata.py", line 77, in load
    module = import_module(match.group('module'))
  File "/usr/lib64/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 783, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/usr/lib/python3.8/site-packages/NanoVNASaver/__main__.py", line 33, in <module>
    from PyQt5 import QtWidgets, QtCore
ImportError: cannot import name 'QtWidgets' from 'PyQt5' (/usr/lib64/python3.8/site-packages/PyQt5/__init__.py)

It did run at some point before Mga8 version freeze, so I have no idea what changed.

Re-building it makes no difference.

Building and running this version for/in Mga7 runs fine.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Barry Jackson 2021-03-16 01:07:35 CET

Status comment: (none) => assigned

Comment 1 Barry Jackson 2021-03-17 01:29:59 CET
nanovna-saver-0.3.9-0.pre.1.1.mga8 has been submitted to 8/core-updates_testing


This update adds missing dependencies which if not
previously installed by another package caused this
package to fail to run.

Files affected:




Full testing requires special hardware, but for this update simply checking that it pulls in the required packages and actually runs to a GUI.
Barry Jackson 2021-03-17 01:34:49 CET

Assignee: zen25000 => qa-bugs

Comment 2 Guillaume Royer 2021-03-28 21:06:23 CEST

I've installed NanoVna Saver and reproduced bug. NanoVna Saver freeze.

Updated NanoVan Saver with QA repo and :


No problem at installation. NanoVna Saver launch without error code.
I have'nt no VNA to test all function of software

OK for me

CC: (none) => guillaume.royer

Comment 3 Thomas Andrews 2021-04-11 04:46:33 CEST
That's all we needed for this one, Guillaume. Next time, add "MGA8-64-OK" to the whiteboard for a 64-bit test, and "MGA8-32-OK" for a 32-bit test. Since this bug is a "noarch" package, 64 or 32 doesn't really matter, but we need at least one.

On bugs like this, where one test is sufficient, you can go ahead and edit the Whiteboard yourself once you are satisfied. Once you have posted an OK, someone will come along and look things over, and let you know if another test is warranted after all, or, if it was sufficient, the update will be validated and sent on its way.

Updates that require tests on as wide a range of hardware as we can get, like kernels, just report your test results, and others will take care of the OKs when enough tests have come in.

Giving this an OK based on Guillaume's test, and validating. Advisory in Comment 1.

CC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => validated_update
Whiteboard: (none) => MGA8-64-OK

Comment 4 Guillaume Royer 2021-04-11 14:23:11 CEST
Thank you Thomas for the advisories.
Like I'm newcomer in QA Team, Ididn't want to write in white Board.
I'll know it for other the bugs.
Comment 5 Thomas Andrews 2021-04-11 15:58:21 CEST
No worries. You are as much a part of the team as any of us.

And don't be concerned about mistakes. I've made more than a few, and others have always had my back. When you do make one, and all of us do, all we ask is that you learn from them when they are pointed out.
Aurelien Oudelet 2021-04-12 16:43:08 CEST

Keywords: (none) => advisory
Status comment: assigned => (none)
CC: (none) => ouaurelien

Comment 6 Mageia Robot 2021-04-12 22:02:05 CEST
An update for this issue has been pushed to the Mageia Updates repository.


Resolution: (none) => FIXED

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