Spotify no longer works. #1976
Replies: 16 comments 14 replies
-
|
For all intents and purposes, I have the exact same issue with Spotifyd, and I can't find a solution either. |
Beta Was this translation helpful? Give feedback.
-
|
Just to be clear this is the latest build below, installed from scratch. No previous settings imported, no Pacman -Syu. Only thing done after the install is to attempt Spotify setup which as said seems to setup fine according to the GUI, but it doesnt actually make itself discoverable. rAudio 20250627 Works fine on a previously saved older image, wiped spotify settings and it setup fine and is dicoverable. |
Beta Was this translation helpful? Give feedback.
-
Please explain the "rubbish". |
Beta Was this translation helpful? Give feedback.
-
Sure. The link you provided to look at leads to another link which is dead (404). So looks like the advice has changed your pointing us towards.. "rubbish" could have been worded better I guess... Maybe outdated would have been better? |
Beta Was this translation helpful? Give feedback.
-
|
Plain and simple "The link you provided to look at leads to another link which is dead (404)." would be even better. In case you haven't read it, the link Comment out username and password, with discussions in the thread - without the broken link, provides a possible solution for the |
Beta Was this translation helpful? Give feedback.
-
|
@rern There is no username or password there to remove. Registration of Spotify on your latest build is broken. Works fine on previous build. |
Beta Was this translation helpful? Give feedback.
-
|
Fix for it to show as available is to remove "ipv6.disable=1" from \boot\cmdline.txt, then reboot. Set as disabled by defaullt on build image, I guess is now required for Spotifyd to work unlike previous versions... only issue is doesnt seem to output to my USB DAC. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks man, good info!RPLe 6 août 2025 à 19:00, RolandB ***@***.***> a écrit :
Fix is to remove "ipv6.disable=1" from \boot\cmdline.txt which is set by defaullt on build image.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
@rern Going by a previously working build where ipv6 is disabled in cmdline.txt it complains but still works... Older build with ipv6 disabled in cmdline - WorkingAug 06 19:13:34 rAudio systemd[1]: Started A spotify playing daemon. On latest build with ipv6 disabled - Not advertisedrAudio:~ # sudo journalctl -u spotifyd -f Latest build with ipv6 enabled in cmdline.etc - Advertised > No Sound > Tracks say unavailablesudo journalctl -u spotifyd -f Hope the ouput helps. Can run other tests if required and given input. Roland. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I haven't tested with the latest build yet, but it does work with my 2 older builds: 20250309 (one before last) and 20210820, both with IPV6 disabled. Dump below: cat /etc/spotifyd.conf[global] systemctl status spotifyd
Aug 07 09:18:40 rAudio spotifyd[1076315]: (218400 ms) loaded There's one error that I don't like although it does work somehow, it's "Couldn't read volume from alsa device with name "hw:0". I also do have weird errors with the UpNP client though (and different ones for each build), although it does work on both. RP |
Beta Was this translation helpful? Give feedback.
-
|
Try downgrading wget http://tardis.tiny-vps.com/aarm/repos/2025/03/08/aarch64/extra/spotifyd-0.3.5-1-aarch64.pkg.tar.xz
pacman -U spotifyd-0.3.5-1-aarch64.pkg.tar.xz
systemctl restart spotifyd |
Beta Was this translation helpful? Give feedback.
-
|
@rern Downgraded as per your suggestion, now crashes soon as try and connect (Latest build, no changes just registered spotify and downgraded Spotifyd) sudo journalctl -u spotifyd -f cat /etc/spotifyd.conf Roland |
Beta Was this translation helpful? Give feedback.
-
|
@rern Maybe could be to with this? https://lists.freebsd.org/archives/freebsd-ports-bugs/2025-March/070857.html Roland. |
Beta Was this translation helpful? Give feedback.
-
|
I looked it up carefully. Unfortunately it’s a bit above my skill level, as I’m in no way a Linux expert. I’ve no idea how (and on what) to apply the patch, for instance. RPLe 8 août 2025 à 19:00, RolandB ***@***.***> a écrit :
@rern Maybe could be to with this?
https://lists.freebsd.org/archives/freebsd-ports-bugs/2025-March/070857.html
Roland.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
@rern librespot-org/librespot#1527 .. this may be the problem. |
Beta Was this translation helpful? Give feedback.
-
|
@rern @erpol Fixed for myself by doing the following : Enabled ipv6 in /boot/cmdline.txt so from cat /etc/spotifyd.conf to [global] rAudio1 doesn't return to mpd after stopping Spotify connect and you have to manually go and click "stop" to get the mpd or play something from library. Roland. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the info! I’ll try that and get back to you. I have hifiberry DAC+ / Lite audio boards, any idea how (in which config file) I could find what to put after device = ? Thanks,RPLe 12 août 2025 à 01:30, RolandB ***@***.***> a écrit :
@rern @erpol Fixed for myself by doing the following :
Enabled ipv6 in /boot/cmdline.txt
put entry into host file /etc/hosts > 127.0.0.1 apresolve.spotify.com
and changed spotifyd.conf to use "device = "plughw:2,0" instead of device = "hw:2,0" for my USB DAC.
Roland.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Apparently both 0.0.0.0 and your 127… do work. I’m trying it in a couple of hours on my broken build. RPLe 12 août 2025 à 00:46, RolandB ***@***.***> a écrit :
@rern librespot-org/librespot#1527 .. this may be the problem.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, I just tested this and it works:
*
Installed raudio build 20250627, with spotifyd build 0.4.1-1
*
Checked that spotifyd generates multiple errors on start. The ***@***.*** "external speaker" appears in the IOs Spotify app, but it can't get a stable connection to it or stream any music.
*
Enabled ipv6 in the file /boot/cmdline.txt (change ipv6.disable=1 to ipv6.disable=0)
* Added the line: '127.0.0.1 apresolve.spotify.com' in the file /etc/hosts
*
After reboot, the spotifyd daemon starts without errors, the mobile and PC apps can see the ***@***.*** external speaker, stably connect to it and play music with metadata (cover image, etc).
It would be nice to be able to change these settings directly in the raudio image file now !
I also saw that there's a new source build posted in Github from 3 days ago (no images yet), but no mention of spotifyd in the changelog.
I'll make sure to test it when the images are available.
RP
…________________________________
De : RolandB ***@***.***>
Envoyé : mardi 12 août 2025 00:30
À : rern/rAudio ***@***.***>
Cc : erpol ***@***.***>; Mention ***@***.***>
Objet : Re: [rern/rAudio] Spotify no longer works. (Discussion #1976)
@rern<https://github.com/rern> @erpol<https://github.com/erpol> Fixed for myself by doing the following :
Enabled ipv6 in /boot/cmdline.txt
put entry into host file /etc/hosts > 127.0.0.1 apresolve.spotify.com
and changed spotifyd.conf to use "device = "plughw:2,0" instead of device = "hw:2,0" for my USB DAC.
Roland.
—
Reply to this email directly, view it on GitHub<#1976 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADDV4UZGISWJUGVVI5USYFL3NEKOZAVCNFSM6AAAAACBNH6PPWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMBXGY2TGMI>.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
|
@rern Spotify is now discoverable but does not play on my USB DAC (Topping E30) as current spotifyd build now opens ALSA with a format the E30’s USB interface doesn’t expose (commonly FLOAT_LE), the hw device will refuse it. device = "plughw:0,0" works because ALSA’s plug plugin converts the stream to something the DAC accepts. Is there a way to fix this in the build for myself and others like me? RolandB |
Beta Was this translation helpful? Give feedback.
-
|
@rern Even though the version has been reverted to 0.3.5, it’s now built against a newer librespot backend. In that newer backend, the ALSA output code tries to open devices in FLOAT_LE format first. My Topping E30’s USB interface doesn’t advertise FLOAT_LE in hardware mode — only S32_LE, SPECIAL, and DSD. When using hw:…, ALSA requires the app to open the device with an exact supported format. So spotifyd now fails to open the E30 in raw hw: mode and I get silence. Switching to plughw:… works because ALSA’s plug layer converts FLOAT_LE → S32_LE transparently before sending it to the DAC. Hopefully this is something that can be worked around or way to detect issues and change spotifyd to PLUGHW ? RolandB |
Beta Was this translation helpful? Give feedback.
-
|
Soooo, I also wanted to use spotify + bluetooth. To get things working for me on the 20250822 release I did the following, as above :
Which, as others have said allows the spotifyd to be workably discoverable. I then made tmy /etc/asound.conf file look like this at the bottom (renamed the pcm bit and added the ctl bit): And then modified my /etc/spotifyd.conf to look like: With these changes I could hear my spotify working again. I don't really know what I'm doing other than hacking my way through life, so this may not be (probably is not) correct, but it may help someone, beware though these changes do not survive a restart of the device, or contact with the settings :) |
Beta Was this translation helpful? Give feedback.
-
|
Ok, thanks for the heads up, but I don't think any of this applies to me - I installed the 20250822 build, and with the downgraded Spotify version (0.3.5-1), it works out of the box even with ipv6 disabled and no specific entry in hosts. The settings in /etc/spotifyd.conf are consistent with my system: [global] Now though, Spotifyd starts every time with the volume at 87, in spite of any UI settings (it's set to start at 30). If any of you guys has a fix for this ... 😂 RP |
Beta Was this translation helpful? Give feedback.
-
|
I too was able to get build 20250822 spotify to connect and play out-of-the-box without ipv6 and the additional entry in /etc/hosts. However, it stopped playing and disconnected midstream and would not reconnect. |
Beta Was this translation helpful? Give feedback.
-
|
I tested it yesterday, it disconnected once after 5 minutes, then when reconnected it played continuously for hours without mishaps. I’ll try the 2 tweaks to see if it changes anything. I’d certainly like a fix for the volume starting at 87 though. I have to be very cautious or else I’ll blow my speakers!RPLe 10 sept. 2025 à 02:51, digixmax ***@***.***> a écrit :
I too was able to get build 20250822 spotify to connect and play out-of-the-box without ipv6 and the additional entry in /etc/hosts.
However, it stopped playing and disconnected midstream and would not reconnect.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
There is a new breakage and a new fix in librespot. |
Beta Was this translation helpful? Give feedback.
-
|
Guys, Please try the UPDATE:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Re-registered again just in case on delveloper site and all seems to go through but raudio never shows up and eventually the service stops. used to get similar errors in past on prev versions of raudio and spotifyd but worked anyhow.. now just refuses to work.
Jul 13 17:39:15 rAudio systemd[1]: Started A spotify playing daemon.
Jul 13 17:39:16 rAudio spotifyd[1929]: [INFO] Loading config from "/etc/spotifyd.conf"
Jul 13 17:39:16 rAudio spotifyd[1929]: [INFO] Using alsa volume controller.
Jul 13 17:39:16 rAudio spotifyd[1929]: [INFO] Starting zeroconf server to advertise on local network.
Jul 13 17:39:16 rAudio spotifyd[1929]: [WARN] Discovery server failed to start: Address family not supported by protocol (os e>
Jul 13 17:39:16 rAudio spotifyd[1929]: [ERROR] failed to enable discovery: Unknown error { Address family not supported by pro>
Jul 13 17:39:16 rAudio spotifyd[1929]: [INFO] retrying discovery in 5 seconds
Jul 13 17:39:21 rAudio spotifyd[1929]: [INFO] trying to enable discovery (retry 1/4)
Jul 13 17:39:21 rAudio spotifyd[1929]: [WARN] Discovery server failed to start: Address family not supported by protocol (os e>
Jul 13 17:39:21 rAudio spotifyd[1929]: [ERROR] failed to enable discovery: Unknown error { Address family not supported by pro>
Jul 13 17:39:21 rAudio spotifyd[1929]: [INFO] retrying discovery in 10 seconds
Jul 13 17:39:31 rAudio spotifyd[1929]: [INFO] trying to enable discovery (retry 2/4)
Jul 13 17:39:31 rAudio spotifyd[1929]: [WARN] Discovery server failed to start: Address family not supported by protocol (os e>
Jul 13 17:39:31 rAudio spotifyd[1929]: [ERROR] failed to enable discovery: Unknown error { Address family not supported by pro>
Jul 13 17:39:31 rAudio spotifyd[1929]: [INFO] retrying discovery in 20 seconds
Jul 13 17:39:51 rAudio spotifyd[1929]: [INFO] trying to enable discovery (retry 3/4)
Jul 13 17:39:51 rAudio spotifyd[1929]: [WARN] Discovery server failed to start: Address family not supported by protocol (os e>
Jul 13 17:39:51 rAudio spotifyd[1929]: [ERROR] failed to enable discovery: Unknown error { Address family not supported by pro>
Jul 13 17:39:51 rAudio spotifyd[1929]: [INFO] retrying discovery in 40 seconds
Jul 13 17:40:31 rAudio spotifyd[1929]: [INFO] trying to enable discovery (retry 4/4)
Jul 13 17:40:31 rAudio spotifyd[1929]: [WARN] Discovery server failed to start: Address family not supported by protocol (os e>
Jul 13 17:40:31 rAudio spotifyd[1929]: [ERROR] failed to enable discovery: Unknown error { Address family not supported by pro>
Jul 13 17:40:31 rAudio spotifyd[1929]: [ERROR] maximum amount of retries exceeded
Jul 13 17:40:31 rAudio spotifyd[1929]: Error:
Jul 13 17:40:31 rAudio spotifyd[1929]: 0: Discovery unavailable and no credentials found.
Jul 13 17:40:31 rAudio spotifyd[1929]: Location:
Jul 13 17:40:31 rAudio spotifyd[1929]: src/setup.rs:119
Jul 13 17:40:31 rAudio spotifyd[1929]: Suggestion: Try enabling discovery or logging in first with
spotifyd authenticate.Jul 13 17:40:31 rAudio spotifyd[1929]: Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Jul 13 17:40:31 rAudio spotifyd[1929]: Run with RUST_BACKTRACE=full to include source snippets.
Jul 13 17:40:31 rAudio systemd[1]: spotifyd.service: Main process exited, code=exited, status=1/FAILURE
Jul 13 17:40:31 rAudio systemd[1]: spotifyd.service: Failed with result 'exit-code'.
just keeps doing this and restarting. Can anyone help?
Beta Was this translation helpful? Give feedback.
All reactions