Bug 10409 - Errors from List.pm: Use of uninitialized value in array element
: Errors from List.pm: Use of uninitialized value in array element
Status: RESOLVED WONTFIX
Product: Logitech Media Server
Classification: Unclassified
Component: Windows Service
: 7.3.1
: PC Windows XP
: -- normal (vote)
: Future
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-12-20 13:31 UTC by Tim Bessie
Modified: 2019-01-25 12:11 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Bessie 2008-12-20 13:31:30 UTC
I did a clean install of SqueezeCenter 7.3.1-24367.  After installing it, scanning my library, and then playing a few tracks, I foundthe below in the server.log file.  I do not know if this had any impact on any component's functioning:

[08-12-19 01:08:34.8718] Slim::Utils::Misc::msg (1126) Warning: [01:08:34.8716] Use of uninitialized value in array element at /<C:\Software\MULTIM~1\SQUEEZ~1\server\SQUEEZ~1.EXE >Slim/Buttons/Input/List.pm line 250.
[08-12-19 01:08:34.8721] Slim::Utils::Misc::msg (1126) Warning: [01:08:34.8720] Use of uninitialized value in array element at /<C:\Software\MULTIM~1\SQUEEZ~1\server\SQUEEZ~1.EXE >Slim/Buttons/Input/List.pm line 261.
[08-12-19 01:08:34.8723] Slim::Utils::Misc::msg (1126) Warning: [01:08:34.8722] Use of uninitialized value in array element at /<C:\Software\MULTIM~1\SQUEEZ~1\server\SQUEEZ~1.EXE >Slim/Buttons/Input/List.pm line 268.
Comment 1 KDF 2008-12-21 00:37:13 UTC
mostly harmless, but changing line 240 of Slim/Buttons/Input/List.pm to:

my $listIndex = $client->modeParam('listIndex') || 0;

should avoid the warning, whatever the player ui navigation that was causing it.  
Comment 2 James Richardson 2008-12-21 18:08:07 UTC
KDF: Should we make that change permanent?  I.E. check it into SVN for 7.3.2
Comment 3 KDF 2008-12-21 18:32:12 UTC
It would help if we have more details on the reproduceable case in question. It would be best to make sure the cause is known and that we don't create any undesired consequences for something that may be deliberately avoiding providing the undefined value.
Comment 4 Chris Owens 2008-12-22 09:55:20 UTC
We need to know in what menu this occurred before we fix this issue.