Bug 876 - SlimServer crashes when changing groupdiscs option, which does not work
: SlimServer crashes when changing groupdiscs option, which does not work
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Tagging
: 6.0.0
: PC Debian Linux
: P2 normal (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-02-26 14:35 UTC by Christian Pernegger
Modified: 2008-09-15 14:37 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 Christian Pernegger 2005-02-26 14:35:33 UTC
SlimServer version: 6.0a1 dated 25-02-2005
Perl version: 5.8.4 built for i386-linux-thread-multi (Debian testing)

Whenever I change the groupdiscs option via the web interface the server exits
on this log entry: "Can't use string ("") as an ARRAY ref while "strict refs" in
use at /opt/slimserver/Slim/DataStores/DBI/DBIStore.pm line 1140".
When I change the option manually in the .conf file the change is not reflected
on the web interface (i. e. "treat as multiple" is always selected) but
nevertheless taken into account.
Behaviour with two sets of files (what I consider the standard scenario):
A: TRACKNUM filled, DISC=1, ALBUM consistent
B: TRACKNUM filled, DISC=2, ALBUM consistent and identical to A

groupdiscs=0 --> two albums are spawned, with (Disc x of 2) appended. Disc
number precedes Track number. The respective track detail pages show Disc number
correctly. OK

groupdiscs=1 --> one album containing all tracks is spawned, but Disc number is
always 2. That means that all track numbers are prefixed with 2, and all detail
pages show 2 for the disc number. Accordingly the sort order goes foobar and one
is no longer able to tell which track x belongs to which disc. ERROR
Comment 1 Dan Sully 2005-02-27 16:02:06 UTC
Christian - I've checked in a fix for this as of Subversion change 2253.

It will trigger a rescan if the group discs option is changed. And there will be
an initial rescan upon install beacuse of a schema change.
Comment 2 Chris Owens 2006-06-16 14:40:58 UTC
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.