streamrip icon indicating copy to clipboard operation
streamrip copied to clipboard

[BUG] <title>Can't launch Streamrip after Linux Mint 22.1 upgrade

Open Jodel-D18 opened this issue 11 months ago • 8 comments

Describe the bug

I have recently moved from Linux Mint 21.3 to 22.1. Streamrip has been working perfectly with my Qobuz streaming service, but since my Linux upgrade, I can’t launch it. I’m far from a Linux / Python expert so any pointers would be appreciated. I don’t think this is really a ‘bug’ rather a configuration issue on my PC since I installed Mint 22.1.

Image

The file in local/bin/rip shows the following:

Image

Command Used

rip

Debug Traceback

Unable to complete this section as 'rip' command no longer works - sorry.

Config File

I couldn't copy this file with all the colour coding / formatting, so have tried to show in screenshots in the section below:

Operating System

Linux Mint Cinnamon 22.1

streamrip version

Unable to confirm, but I believe I had Version 2.0.2 installed

Screenshots and recordings

Image

Image

Image

I tried to upgrade / reload streamrip but got the following message:

Image

Additional context

I don’t know how to proceed with this issue, so any guidance would be very much appreciated.

Jodel-D18 avatar Feb 19 '25 15:02 Jodel-D18

You'll may need to do a bit of reading on pipx and how to manage its virtual environments (venv).

AllKind avatar Feb 19 '25 15:02 AllKind

Thanks for the response - I'll try to get my head around this pipx stuff! I had a quick read and it doesn't seem like I could 'break' anything on my system with this approach. I do want to get Streamrip working again as it is a great utility.

Jodel-D18 avatar Feb 19 '25 17:02 Jodel-D18

I've now installed pipx and tried to reinstall streamrip, which all seemed to go smoothly. I think I now have the latest version of streamrip (2.0.5) loaded in the virtual environment (venvs).

Image

I'm still missing something though as the command 'rip' returns the same error message :(

Image

I must be missing some critical step in the process, but I'm not sure what this is. It feels like I'm 95% there, just missing a step or two. I really don't know what to try next, so any comments would be gratefully received!

Jodel-D18 avatar Feb 20 '25 11:02 Jodel-D18

I just started getting this after upgrading to Fedora 43. Exact same error.

Did you ever get this resolved?

unraidcitadel avatar Oct 31 '25 16:10 unraidcitadel

Unfortunately not. I did persevere and tried to understand what was happening, but I just couldn't get it to work / install after updating Linux. I'm sure someone a bit more knowledgeable would not have any trouble, but it is beyond my limited Linux capabilities.

Jodel-D18 avatar Oct 31 '25 16:10 Jodel-D18

Dang. I'm just as at a loss as you.

Worked great yesterday lol

unraidcitadel avatar Oct 31 '25 16:10 unraidcitadel

Solution:

I am ashamed to say I needed to battle with Gemini for most of the day for this but here we go.

AI Response output that fixed it for me: "Your analysis is correct: python3-pillow is already installed, but pip is stubbornly trying (and failing) to build its own version from a cached source file.

This is happening because pip isn't "seeing" your DNF-installed package as a valid option to satisfy streamrip's dependency, so it tries to build its own.


The Solution (The "Hack")

We will manually work around this. The plan is:

  1. Force-install streamrip without any of its dependencies.
  2. Manually install all of its other Python-based dependencies, skipping Pillow.

This way, streamrip will be installed, its (non-Pillow) dependencies will be met, and when you run rip, it will find and use the system-wide python3-pillow that dnf installed.

Step 1: Install streamrip with no dependencies

This command tells pip to install the package but to ignore its dependency list.

python3 -m pip install --user --upgrade streamrip --no-dependencies

Step 2: Manually install the other dependencies

This command installs all the other packages streamrip needs, which pip was trying to download in your log.

python3 -m pip install --user aiofiles==0.7.0 aiolimiter==1.2.1 appdirs==1.4.4 click-help-colors==0.9.4 deezer-py==1.3.6 m3u8==0.9.0 pathvalidate==2.5.2 pytest-asyncio==0.21.2 pytest-mock==3.15.1 rich==13.9.4 simple-term-menu==1.6.6 tomlkit==0.7.2

(Note: I've pinned the versions to match the ones pip was trying to use, just to be safe).

After both steps are complete, the original ModuleNotFoundError should be gone, and the Pillow build error is bypassed. Your rip command should work now."

unraidcitadel avatar Oct 31 '25 22:10 unraidcitadel

unraidcitadel, thanks for responding to this thread.

I tried your suggested method / commands and whilst not successful for me, I think I've moved forward a bit!

I installed streamrip with no dependencies and that seemed fine.

When I then tried to install the other packages, I had to install: aiodns mutagen Pillow (but only a version earlier than 10.9) pycryptodomex

Now when I try to run rip, the ModuleNotFoundError has gone, but I now get another error message: "Segmentation fault (core dumped)"

I'll try something like Gemini AI to see if I can move forward .... don't hold your breath!

Jodel-D18 avatar Nov 02 '25 15:11 Jodel-D18