Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54772 readers

222 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others

Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):

💰 Please help cover server costs.


Ko-fi	Liberapay

founded 1 year ago

MODERATORS

[email protected]

Since I implemeted SpotX on my computer I need to shut down it twice (lemmy.dbzer0.com)

submitted 7 months ago by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

I don't know if it's SpotX the problem, but around the time I implemented (a few days ago) when I shut down my PC it says an app is still running and I need to cancel it and shut down again.

The app running has no icon and name too. What could be the problem and solution?

top 6 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 7 months ago (1 children)

Just to confirm, you're using the full installation from here right? It works perfectly for me since a long time.

[–] [email protected] 1 points 7 months ago

yes exactly, it may not be a SpotX issue then

[–] [email protected] 2 points 7 months ago* (last edited 7 months ago)

I have SpotX and I shutdown normally.

However I do get ads with it, so SpotX either doesn't work for me or it's deprecated.

oh, also an OS would be nice. I'm on Arch.

[–] [email protected] 5 points 7 months ago (1 children)

Have you tried reinstalling Spotify without cracking it with SpotX and seeing if you still encounter the issue?

[–] [email protected] 2 points 7 months ago (1 children)

I'll try

[–] [email protected] 1 points 7 months ago

If the issue isn't there after that, we can determine that a fresh install of Spotify is not the problem.

You can then try running SpotX and checking for the issue again; if the issue reappears, SpotX is the problem, or at least the version of SpotX that you're using.