Paper UI: Hang on specific control tab

[rapiertg]

Hi,

When I choose some specific (actually two of six cause this behavior) tab in Control menu in paper ui the whole website hangs with log spammed by messages:

angular.min.js:107 TypeError: [sprintf] expecting number but found string
    at b.format (sprintf.min.js:3)
    at b (sprintf.min.js:3)
    at Object.getItemStateText (utility.js:1)
    at r.$scope.getItem (controllers.min.js:3)
    at controllers.min.js:3
    at Object.n [as forEach] (angular.min.js:7)
    at r.$scope.getItems (controllers.min.js:3)
    at fn (eval at compile (angular.min.js:213), <anonymous>:4:345)
    at Object.<anonymous> (angular.min.js:116)
    at r.$digest (angular.min.js:131)
(anonymous) @ angular.min.js:107
(anonymous) @ angular.min.js:81
$digest @ angular.min.js:131
$apply @ angular.min.js:134
g @ angular.min.js:87
T @ angular.min.js:92
w.onload @ angular.min.js:93
angular.min.js:107 TypeError: [sprintf] expecting number but found string
    at b.format (sprintf.min.js:3)
    at b (sprintf.min.js:3)
    at Object.getItemStateText (utility.js:1)
    at r.$scope.getItem (controllers.min.js:3)
    at controllers.min.js:3
    at Object.n [as forEach] (angular.min.js:7)
    at r.$scope.getItems (controllers.min.js:3)
    at fn (eval at compile (angular.min.js:213), <anonymous>:4:345)
    at Object.<anonymous> (angular.min.js:116)
    at r.$digest (angular.min.js:131)

[lolodomo]

Maybe you have %d in a label while you should have %s.

[rapiertg]

Not using labels at all. Now I noticed that I probably dont have channel's names at all:

[rapiertg]

As to the hanging of specific control tab - thru elimination I know which things cause this - every tab with squeezebox thing. Rest of tabs works.

[lolodomo]

Have you channels linked to image for this thing ?
What happens if you unlink these channels ?

[rapiertg]

Yes, I had cover_art linked. After I unlinked It, the tab works fine now.

[lolodomo]

Lioking at the code of the squeezebox 2.x binding, the channel name is coverartdata and is an image.

[kaikreuzer]

Does this problem still exist after #3731 had been merged?

[rapiertg]

Don't have test environment, so sorry, until next stable release I can't check it.

[rapiertg]

Sorry for late reply after last stable. Had little time to update. This seems to be fixed.