[PROBLEM] 8.1 32bit and Spotify.

[the_bertrum]

Hello folks,

The in-place upgrade to 8.1 has failed on all three of my devices.  A fresh installation, followed by a restored from backup also failed.  The start up log in each failed case ends in the section of available components after Airplay.  Spotify would normally come next.  I started afresh and configured up manually and the UI went unresponsive as soon as I hit "set" after turning on the Spotify renderer and giving it a new name.  I suspect the new librespot might not be happy?  Is anyone else running 32bit 8.1 with Spotify turned on?

Robert

[the_bertrum]

Additional evidence. I edited the backup file to turn off the Spotify renderer, then restored a fresh 32bit image from it. All working nicely.

[TookaFace]

I can confirm for Spotify with 64 bits img.

Fresh install, set Spotify on, and the system hang. I can run librespot from cmdline without issues.

[the_bertrum]

I can confirm for Spotify with 64 bits img.

Fresh install, set Spotify on, and the system hang. I can run librespot from cmdline without issues.

OK, I'll abort my plan to try with the 64bit image then

[bitlab]

Can also confirm the issue on both 32 and 64 bit.
On both the libresport runs fine from the cmdline.

To be sure on the 32 bits downgraded librespot to the prev version and the issue remains.
So it looks a problem om the moode side itself.

Reproduce:

• Enable spotify
  

How notice the issue:

• Run moodeutl -l
  
• The last output line shows (not show the output of the next step):
  

20220624 090948 worker: Airplay renderer (available)

[the_bertrum]

Can also confirm the issue on both 32 and 64 bit.
On both the libresport runs fine from the cmdline.

To be sure on the 32 bits downgraded librespot to the prev version and the issue remains.
So it looks a problem om the moode side itself.

Reproduce:

• Enable spotify
  

How notice the issue:

• Run moodeutl -l
  
• The last output line shows (not show the output of the next step):
  

20220624 090948 worker: Airplay renderer (available)

Yup, that's exactly what I see.

[bitlab]

workarround to get the rest of moode backup again (without spotify):

• Go to the audio config and disable spotify
  
• Reboot (to reset hanging server)
  

[the_bertrum]

workarround to get the rest of moode backup again (without spotify):

• Go to the audio config and disable spotify
  
• Reboot (to reset hanging server)
  

My systems were hung so badly I couldn't get to the config pages to turn it off sadly.  I resorted to a rebuild and restore from backup, after switching off the Spotify renderer in the moodecfg.ini in the backup file.

[bitlab]

workarround to get the rest of moode backup again (without spotify):

• Go to the audio config and disable spotify
  
• Reboot (to reset hanging server)
  

My systems were hung so badly I couldn't get to the config pages to turn it off sadly.  I resorted to a rebuild and restore from backup, after switching off the Spotify renderer in the moodecfg.ini in the backup file.

If you have ssh session available to the Pi you can also use the following commands to disable it:

Code:

sqlite3 /var/local/www/db/moode-sqlite3.db "update cfg_system set value=0 where param='spotifysvc'"
moodeutl -r

btw using a configuration /boot/moodecfg.ini file with only to disable spotify, will not work because the importer is only executed after the spotify start :-(

Code:

[Renderers]
spotifysvc = "0"

[the_bertrum]

btw using a configuration /boot/moodecfg.ini file with only to disable spotify, will not work because the importer is only executed after the spotify start :-(

Code:

[Renderers]
spotifysvc = "0"

I didn't use it to fix an already broken system where Spotify had already been turned on, that was to set up a clean installation and restore a backup without turning on Spotify which would break it again.