konsave icon indicating copy to clipboard operation
konsave copied to clipboard

[Bug] Konsave 2.2.0 using Python 3.13.3 fails to run on Fedora 42 with Plasma 6.3.4

Open jackemled opened this issue 7 months ago • 5 comments

Describe the bug When trying to run any function of Konsave, the same error message/traceback is produced & the command is not executed. For example, when running konsave -h it does not show the manual.

To reproduce

  1. Install Fedora 42 Plasma Edition.
  2. Run pipx install konsave in your shell.
  3. Try any Konsave command, for example konsave -s MyDesktop.

Expected behavior Konsave should show the help menu when given -h, the profiles list when given -l, or save the current profile when given -s. In my experience it does this fine on other systems, just not Fedora.

Screenshots Image pkg_resources doesn't seem to be something I can install.

System information

  • OS or Linux distribution: Fedora 42 Plasma Edition.
  • How did you install Konsave?: pipx install konsave
  • What version of Konsave are you using? Did you try updating?: Konsave 2.2.0. Tried updating but there are no updates.

Additional context I get a traceback.

Traceback (most recent call last):
  File "/home/jackemled/.local/bin/konsave", line 5, in <module>
    from konsave.__main__ import main
  File "/home/jackemled/.local/share/pipx/venvs/konsave/lib64/python3.13/site-packages/konsave/__init__.py", line 3, in <module>
    from pkg_resources import get_distribution, DistributionNotFound
ModuleNotFoundError: No module named 'pkg_resources'

I'm clueless about anything to do with Python, but if given instructions I can get more information.

jackemled avatar May 02 '25 19:05 jackemled

pip install setuptools

ironhak avatar May 02 '25 23:05 ironhak

if you used pipx then you need to inject setuptools like this: pipx inject konsave setuptools

Kojimboy avatar May 13 '25 11:05 Kojimboy

if you used pipx then you need to inject setuptools like this: pipx inject konsave setuptools

Thank you! That fixed it. I don't remember needing to do this before, & the installation doesn't mention any dependencies. Should a list be added?

jackemled avatar May 13 '25 14:05 jackemled

I'd recommend putting this info into README install section as your recommended way of installing it globally yields a big fat warning about virtual python environments and using pipx being recommended:

error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.
    
    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.
    
    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.
    
    See /usr/share/doc/python3.12/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

Edit: This isn't Debian specific. This happened on my Tuxedo OS and my arch machine.

Sa-Kage avatar Jun 05 '25 11:06 Sa-Kage

For those using uv, the solution is:

uv tool install --with setuptools konsave

Valloric avatar Oct 07 '25 12:10 Valloric