Invalid JSON after update to latest version (20240218=>20240212)

[Lubos-V]

Hi rern and the rest of the crowd,

earlier today I applied the 20240218 update which seemed to produce some error message at the end (I missed it unfortunately). Everything but the playback works properly". There is no playback and the "Player" section produces the followingt JSON error. I tried re-applying the update but it's now reporting 20240212 (0218 disappeared). The error remains.

Any ideas what to best do here?

Thanks!

Errors: Unexpected token ',', ..."layname": , "name": "... is not valid JSON Copy<{
  "page"  : "player"
, "login" : false
, "asoundcard"       : false
, "autoupdate"       : true
, "bluetooth"        : false
, "btaplayname"      : ""
, "buffer"           : true
, "bufferconf"       : { "KB": 131072 }
, "camilladsp"       : false
, "counts"           : {
  "album": 801,
  "albumartist": 305,
  "albumyear": 801,
  "artist": 768,
  "composer": 0,
  "conductor": 0,
  "dabradio": 0,
  "date": 66,
  "genre": 29,
  "latest": 2,
  "nas": 1,
  "playlists": 0,
  "sd": 0,
  "song": 10178,
  "usb": 0,
  "webradio": 23
}
, "crossfade"        : false
, "crossfadeconf"    : { "SEC": 0 }
, "custom"           : false
, "dabradio"         : false
, "devicewithbt"     : false
, "dop"              : false
, "equalizer"        : false
, "ffmpeg"           : false
, "lastupdate"       : "2023-11-24 <gr>• 17:42</gr>"
, "lists"            : {
  "albumignore" : false
, "mpdignore"   : false
, "nonutf8"     : false
}
, "listdevice"       : {  "HiFiBerry DAC+ Pro": "hifiberry-dacplus" }
, "listmixer"        : false
, "mixertype"        : false
, "normalization"    : false
, "novolume"         : true
, "output"           : { "aplayname": , "name": "HiFiBerry DAC+ Pro", "card": false, "device": false, "hwmixer": false, "mixertype": "none" }
, "outputbuffer"     : false
, "outputbufferconf" : { "KB": 16384 }
, "player"           : "mpd"
, "pllength"         : 1
, "replaygain"       : false
, "replaygainconf"   : {
  "TYPE"     : "album"
, "HARDWARE" : false
}
, "soxr"             : false
, "soxrconf"         : { "PLUGIN": "soxr", "QUALITY": "very high", "THREADS": 1 }
, "soxrcustomconf"   : { "PLUGIN": "soxr", "QUALITY": "custom", "PRECISION": 20, "PHASE_RESPONSE": 50, "PASSBAND_END": 91.3, "STOPBAND_BEGIN": 100, "ATTENUATION": 0, "FLAGS": 0 }
, "soxrquality"      : ""
, "state"            : "stop"
, "updatetime"       : "(MPD: 27s + Cache: 10s)"
, "updating_db"      : false
, "version"          : "0.23.13-2"
, "volume"           : false
}```

[cmh714]

been testing myself....yeah the latest update and possibly the one prior seem to have messed a few things up. So this is what I did during testing...
flashed 240108; restored a backup I had from 240104; did pacman -Syu ---and all is good to this point, running the update breaks things just not sure where the glitch is.

[ceejayemm]

This very similar to my original report in #1594
Chris

[Lubos-V]

Ah yes @ceejayemm it looks like that.

I think the

Invalid card number 'scontents'.

was the error message I saw at the end of the update log. Need to find a way to merge this with your bugreport...

[rern]

Please try today's update, 20240219.

[Lubos-V]

as reported under #1594 it seems to have worked @rern - thanks!