Your message dated Wed, 25 Mar 2026 20:10:35 +0100 with message-id <acQzK2bH8h4ShuzI@pegase> and subject line close #1123607 has caused the Debian Bug report #1123607, regarding nanovna-saver fails to start to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1123607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123607 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: nanovna-saver Version: 0.7.3-1.1 Severity: important -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I installed nanovna-saver after seeing it is packaged for Trixie and later. * What exactly did you do (or not do) that was effective (or ineffective)? I tried to start the program from a shell prompt to get terminal output, but apparently no executable is installed in the normal bin path. * What was the outcome of this action? Nothing. * What outcome did you expect instead? A program that runs. Here is the journal output: Dec 18 11:28:15 x1carbon systemd[2168]: Started app-gnome-NanoVNASaver-3608.scope - Application launched by gnome-shell. Dec 18 11:28:15 x1carbon NanoVNASaver.desktop[3608]: Traceback (most recent call last): Dec 18 11:28:15 x1carbon NanoVNASaver.desktop[3608]: File "/usr/bin/NanoVNASaver", line 5, in <module> Dec 18 11:28:15 x1carbon NanoVNASaver.desktop[3608]: from NanoVNASaver.__main__ import main Dec 18 11:28:15 x1carbon NanoVNASaver.desktop[3608]: File "/usr/lib/python3/dist-packages/NanoVNASaver/__init__.py", line 1, in <module> Dec 18 11:28:15 x1carbon NanoVNASaver.desktop[3608]: from .NanoVNASaver import NanoVNASaver Dec 18 11:28:15 x1carbon NanoVNASaver.desktop[3608]: File "/usr/lib/python3/dist-packages/NanoVNASaver/NanoVNASaver.py", line 24, in <module> Dec 18 11:28:15 x1carbon NanoVNASaver.desktop[3608]: from PySide6 import QtCore, QtGui, QtWidgets Dec 18 11:28:15 x1carbon NanoVNASaver.desktop[3608]: ModuleNotFoundError: No module named 'PySide6' I then manually installed the pyside6-tools package (which seemed reasonable, but could be wrong) which pulled in a lot of dependencies but trying to start the app still fails: Dec 18 11:38:05 x1carbon systemd[2168]: Started app-gnome-NanoVNASaver-4998.scope - Application launched by gnome-shell. Dec 18 11:38:06 x1carbon NanoVNASaver.desktop[4998]: Traceback (most recent call last): Dec 18 11:38:06 x1carbon NanoVNASaver.desktop[4998]: File "/usr/bin/NanoVNASaver", line 5, in <module> Dec 18 11:38:06 x1carbon NanoVNASaver.desktop[4998]: from NanoVNASaver.__main__ import main Dec 18 11:38:06 x1carbon NanoVNASaver.desktop[4998]: File "/usr/lib/python3/dist-packages/NanoVNASaver/__init__.py", line 1, in <module> Dec 18 11:38:06 x1carbon NanoVNASaver.desktop[4998]: from .NanoVNASaver import NanoVNASaver Dec 18 11:38:06 x1carbon NanoVNASaver.desktop[4998]: File "/usr/lib/python3/dist-packages/NanoVNASaver/NanoVNASaver.py", line 24, in <module> Dec 18 11:38:06 x1carbon NanoVNASaver.desktop[4998]: from PySide6 import QtCore, QtGui, QtWidgets Dec 18 11:38:06 x1carbon NanoVNASaver.desktop[4998]: ImportError: cannot import name 'QtGui' from 'PySide6' (/usr/lib/python3/dist-packages/PySide6/__init__.py) Using trusty Aptitude, I see that pyside-6tools reverse depends on the python3-qtpy-pyside6 package. After installing it, the program now opens. As I understand it, no assumption should be made about installed packages and thus I think that nanovna-saver should depend on the python3-qtpy-pyside6 package to ensure that all UI dependencies are in place. 73, Nate - -- System Information: Debian Release: 13.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.12.57+deb13-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nanovna-saver depends on: ii libjs-sphinxdoc 8.1.3-5 ii python3 3.13.5-1 ii python3-numpy 1:2.2.4+ds-1 ii python3-scipy 1.15.3-1 ii python3-serial 3.5-2 ii python3-setuptools-scm 8.2.1-1 nanovna-saver recommends no packages. nanovna-saver suggests no packages. - -- no debconf information -----BEGIN PGP SIGNATURE----- iGsEARECACsWIQSC1k9rDmfNQfaJu6b7LFEw1VqIGQUCaUQ+5w0cbjBuYkBuMG5i LnVzAAoJEPssUTDVWogZtEIAn2cQ48od8TpaQ6DRiM/84b00UAwYAKCaXouxS1Wj dU9tzy9Ldi9r8kmfCg== =GK17 -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---Package: nanovna-saver Version: 0.7.4~pre1-1 As far as I know this bug is fixed in testing. Feel free to reopen if necessary.
--- End Message ---
