Bug 13354 - Can't get TrackInfo for Current Track
: Can't get TrackInfo for Current Track
Status: RESOLVED DUPLICATE of bug 13068
Product: Logitech Media Server
Classification: Unclassified
Component: CLI
: 7.4.0
: PC Other
: -- normal with 1 vote (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-12 07:21 UTC by Joerg Schwieder
Modified: 2009-08-17 09:34 UTC (History)
4 users (show)

See Also:
Category: Bug


Attachments
error log (25.30 KB, text/plain)
2009-08-12 07:22 UTC, Joerg Schwieder
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joerg Schwieder 2009-08-12 07:21:43 UTC
If I try to get TrackInfo for the currently playing track, it doesn't get sent, but logs an error:
[09-08-12 16:11:06.2259] Slim::Web::Cometd::sendHTTPResponse (669) Sending Cometd chunk:
[{"error":"encountered CODE(0xb08eb68), but JSON can only represent references to arrays or hashes at /usr/share/perl5/Slim/Web/Cometd.pm line 638.\n","successful":false}]

This works fine if I request any other track from the current playlist, just not the current one.

My request is:
 {
    channel => "/slim/request",
    data => {
          request  => [
                        "00:04:20:12:3b:42",
                        [
                          "trackinfo",
                          "items",
                          0,
                          100,
                          "menu:menu",
                          "context:playlist",
                          "track_id:7953",
                        ],
                      ],
          response => "/051a4a96/slim/request",
        },
    id => 46,
  },

And the full log entry is attached (this looks like the menu gets built but not sent).

r28114 (I don't believe this, I updated this morning to 2814xx, I believe the reported revision is wrong)
Comment 1 Joerg Schwieder 2009-08-12 07:22:22 UTC
Created attachment 5603 [details]
error log
Comment 2 James Richardson 2009-08-12 07:51:48 UTC
Possible dupe of bug 13301?
Comment 3 Joerg Schwieder 2009-08-12 07:57:37 UTC
Sounds like it.
This bug should cause the symptoms seen on 13301, it's similar in iPeng.
Here you've got the debugging data :-)
Comment 4 James Richardson 2009-08-12 08:34:55 UTC
*** Bug 13301 has been marked as a duplicate of this bug. ***
Comment 5 Joerg Schwieder 2009-08-14 06:44:08 UTC
While debugging for #13157 I noticed that this only fails if I use a track_id, it works when I use a url to identify the track
Comment 6 Chris Owens 2009-08-17 09:17:34 UTC
Ben says this is a duplicate of a bug assigned to him.

*** This bug has been marked as a duplicate of bug 13068 ***