Bugzilla – Bug 2659
Crash in Slim/Formats/MP3.pm due to possible module conflict
Last modified: 2008-09-15 14:39:24 UTC
The following error occurs during a library scan: Can't use string ("image/jpg $") as a HASH ref while "strict refs" in use at C:/Program Files/SlimServer/server/Slim/Formats/MP3.pm line 184. The line number is from SlimServer_v2005-11-29.exe release. This problem did not exist in 6.2.1 and prior.
Created attachment 1058 [details] Sample file to duplicate the bug.
And this occurs on any scan? I'm unable to reproduce so far..
Yes. It occurs every time, even when I have just this one file in the music library.
Additionally, I consistently receive the similar errors on line 194 when I click on an album link and it goes through to read the cover art: Can't use string (" $.' ",#(") as a HASH ref while "strict refs" in use at C:/Program Files/SlimServer/server/Slim/Formats/MP3.pm line 194 This appears to exist for any mp3 file (album collection) which has a cover art embedded in it.
Do you need additional information for debugging?
We've had this recently reported and it is cleared up by a fresh install. I suspect this is an ols copy of MP3::Info that has been moved from CPAN to the lib tree since it is customised. Please try uninstalling and reinstalling to be rid of this error. most recent dupe of this was bug2767 we'll probably need to make sure this module move is handled by the installer before official realese of 6.5 tho.
*** Bug 2635 has been marked as a duplicate of this bug. ***
After trying the SlimServer_v2006-01-03.exe cut, the following error is displayed instead: Slim::DataStores::DBI::Track Slim::DataStores::DBI::Track=HASH(0x4023298) destroyed without saving changes to cover at slimserver.pl line 0 Can't locate object method "id" via package "Path::Class::File" at /PerlApp/Slim/DataStores/DBI/DataModel.pm line 941. closing dbh with active statement handles
that problem should be alleviated with the jan 4 build, or the jan 5 build due out in a couple hours
I'm closing this one, as I believe it is fixed. Please reopen if you can reproduce with the latest 6.5 nightly. Thanks.