Bugzilla – Bug 3474
AutoLoader scanning errors
Last modified: 2008-09-15 14:39:24 UTC
When performing a rescan with the nightly from 31/5 I get the following messages and the scanning doesn't find any tracks. I have started without a slimserver configuration file once before and then entered the music directoy path in web interface and directly performed a full rescan when I got this. Use of uninitialized value in pattern match (m//) at /usr/share/perl/5.8/AutoLoader.pm line 39 during global destruction. Use of uninitialized value in substitution (s///) at /usr/share/perl/5.8/AutoLoader.pm line 40 during global destruction. Use of uninitialized value in concatenation (.) or string at /usr/share/perl/5.8/AutoLoader.pm line 41 during global destruction. Use of uninitialized value in concatenation (.) or string at /usr/share/perl/5.8/AutoLoader.pm line 86 during global destruction. Use of uninitialized value in substr at /usr/share/perl/5.8/AutoLoader.pm line 94 during global destruction. (in cleanup) Can't locate auto/.al in @INC (@INC contains: /usr/local/SlimServer_v2006-05-31/Plugins /usr/local/SlimServer_v2006-05-31/CPAN/arch/5.8.7/i486-linux-gnu-thread-multi /usr/local/SlimServer_v2006-05-31/CPAN/arch/5.8.7/i486-linux-gnu-thread-multi/auto /usr/local/SlimServer_v2006-05-31/CPAN/arch/5.8/i486-linux-gnu-thread-multi /usr/local/SlimServer_v2006-05-31/CPAN/arch/5.8/i486-linux-gnu-thread-multi/auto /usr/local/SlimServer_v2006-05-31/CPAN/arch/i486-linux-gnu-thread-multi /usr/local/SlimServer_v2006-05-31/lib /usr/local/SlimServer_v2006-05-31/CPAN /usr/local/SlimServer_v2006-05-31 /etc/perl /usr/local/lib/perl/5.8.7 /usr/local/share/perl/5.8.7 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /usr/local/SlimServer_v2006-05-31/scanner.pl line 0
When performing the scanning the second time I get the same messages again but this time the scanning actually finds the tracks and they are also shown in the slimserver.
If you run with --d_scan, what files does this happen around? Thanks
Erland - I'm unable to reproduce this on Ubuntu 5.10 There have also been a lot of fixes since the original bug report. Please reopen if you can reproduce still. Thanks