Bug 2924 - Attempting to edit a radio stream entry in a playlist causes slimserver to crash
: Attempting to edit a radio stream entry in a playlist causes slimserver to crash
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Playlists
: 6.2.2
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-02-03 14:24 UTC by Philip Meyer
Modified: 2006-02-06 15:20 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Meyer 2006-02-03 14:24:01 UTC
I have a playlist "Radio Playlist" that I have added several radio stations to.  Some of these have names, such as "WDIY", others only have a stream url (the name is the same as the stream url).

When I click to edit an entry so that I can put a nice name to the stream, I get the following error:

Slim::DataStores::DBI::Track->retrieve() parameters don't include defined values for all primary key columns (id) at P:/Music/SlimServer/trunk/server/Slim/DataStores/DBI/DBIStore.pm line 244

Note that in the past, I am sure I have edited the entries so all have nice names, but it seems that SlimServer hasn't written the name data to the playlist file on disk, so upon a full rescan the names were lost.  I have looked at the playlist file on disk "Radio Stations.m3u", and it currently contains the following:

http://www.digitallyimported.com/mp3/chillout96k.pls
http://www.digitallyimported.com/mp3/djmixes96k.pls
http://www.digitallyimported.com/mp3/progressive96k.pls
http://www.digitallyimported.com/mp3/trance96k.pls
rtsp://helix.muhlenberg.edu:554/broadcast/live.rm
http://www.sky.fm/mp3/newage.pls
http://wxpnsc.streamguys.com:80/
mms://ms2.capitalinteractive.co.uk/xfm_high
http://rm1.refugemedia.com/ramgen/encoder/wdiy.rm

i.e. the file doesn't contain #EXTM3U and #EXTINF instructions.
Comment 1 KDF 2006-02-03 23:57:12 UTC
sorry, my fault.  should be fixed at change 6070
Comment 2 Philip Meyer 2006-02-06 15:20:15 UTC
Just in case anyone else is having this problem, I was still seeing this error until I updated to 6.2.2 SVN6097 - it seems to be working now.