No module named 'LXST._version'

[memo-567]

Sideband v1.8.2 doesn't start

$ sideband
Traceback (most recent call last):
  File "/home/user/.local/bin/sideband", line 5, in <module>
    from sbapp import main
  File "/home/user/.local/lib/python3.11/site-packages/sbapp/main.py", line 30, in <module>
    from LXST._version import __version__ as lxst_version
ModuleNotFoundError: No module named 'LXST._version'

Debian 12 (bookworm) on Raspberry

[markqvist]

What LXST version is installed on the system? Have you tried running pip install -U lxst?

[memo-567]

It's lxst v0.4.5 and yes - tried pip install lxst -U --no-cache-dir --break-system-packages too.

$ pip install sbapp -U --no-cache-dir --break-system-packages
Defaulting to user installation because normal site-packages is not writeable
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: sbapp in ./.local/lib/python3.11/site-packages (1.8.2)
Requirement already satisfied: rns>=1.0.4 in ./.local/lib/python3.11/site-packages (from sbapp) (1.0.4)
Requirement already satisfied: lxmf>=0.9.3 in ./.local/lib/python3.11/site-packages (from sbapp) (0.9.3)
Requirement already satisfied: lxst>=0.4.5 in ./.local/lib/python3.11/site-packages (from sbapp) (0.4.5)
Requirement already satisfied: kivy>=2.3.0 in ./.local/lib/python3.11/site-packages (from sbapp) (2.3.1)
Requirement already satisfied: numpy>=2.0.0 in ./.local/lib/python3.11/site-packages (from sbapp) (2.3.4)
Requirement already satisfied: pillow>=10.2.0 in ./.local/lib/python3.11/site-packages (from sbapp) (12.0.0)
Requirement already satisfied: mistune>=3.0.2 in ./.local/lib/python3.11/site-packages (from sbapp) (3.1.4)
Requirement already satisfied: qrcode in ./.local/lib/python3.11/site-packages (from sbapp) (8.2)
Requirement already satisfied: materialyoucolor>=2.0.7 in ./.local/lib/python3.11/site-packages (from sbapp) (2.0.10)
Requirement already satisfied: beautifulsoup4 in /usr/lib/python3/dist-packages (from sbapp) (4.11.2)
Requirement already satisfied: pycodec2>=4.1.0 in ./.local/lib/python3.11/site-packages (from sbapp) (4.1.0)
Requirement already satisfied: Kivy-Garden>=0.1.4 in ./.local/lib/python3.11/site-packages (from kivy>=2.3.0->sbapp) (0.1.5)
Requirement already satisfied: docutils in /usr/lib/python3/dist-packages (from kivy>=2.3.0->sbapp) (0.19)
Requirement already satisfied: pygments in /usr/lib/python3/dist-packages (from kivy>=2.3.0->sbapp) (2.14.0)
Requirement already satisfied: requests in /usr/lib/python3/dist-packages (from kivy>=2.3.0->sbapp) (2.28.1)
Requirement already satisfied: filetype in ./.local/lib/python3.11/site-packages (from kivy>=2.3.0->sbapp) (1.2.0)
Requirement already satisfied: cffi>=2.0.0 in ./.local/lib/python3.11/site-packages (from lxst>=0.4.5->sbapp) (2.0.0)
Requirement already satisfied: cryptography>=3.4.7 in ./.local/lib/python3.11/site-packages (from rns>=1.0.4->sbapp) (46.0.3)
Requirement already satisfied: pyserial>=3.5 in /usr/lib/python3/dist-packages (from rns>=1.0.4->sbapp) (3.5)
Requirement already satisfied: pycparser in ./.local/lib/python3.11/site-packages (from cffi>=2.0.0->lxst>=0.4.5->sbapp) (2.23)

[markqvist]

Hmm, that's weird. This might be some files hanging from an earlier version, because some of the module names were moved around or something. Because in the 0.4.5 whl file, the _version.py module is definitely there, I just checked by downloading it manually from pip and inspecting + intsalling it.

Try this:

# First, uninstall lxst
pip uninstall lxst

# Remove any remnants of the package
rm ~/.local/lib/python3.11/site-packages/LXST
rm ~/.local/lib/python3.11/site-packages/lxst*.dist-info

# Re-install with cache disabled
pip install lxst --no-cache-dir

Then try running a python console and try importing LXST and looking at the version:

❯ python
>>> from LXST._version import __version__ as lxst_version
>>> lxst_version
'0.4.5'

Hopefully, that should fix it.

[memo-567]

Had to do the same procedure with LXMF afterward, but yeah - that works. 🎉

Thanks 👍👍👍

[memo-567]

FYI: Same issue with another Raspberry ¯\_(ツ)_/¯
However - both are working properly after these procedures.