Bugzilla – Bug 2929
Problem: Can't open file for (song title) in 6.2.1, works in 6.2.0
Last modified: 2011-03-16 04:24:58 UTC
I just downloaded SlimServer 6.2.2 from the public download page at slimdevices.com. I'm upgrading from a working version of 6.2.1. I copied both *.conf files from the 6.2.1 directory to the 6.2.2 directory and ran 6.2.2. I was asked to run the build-perl-modules script. Then 6.2.2 started up with no complaints. But when it came up, and I tried to play a song, the SB2 displayed the message PROBLEM: Can't open file for (song title) I rescanned the music library with the "clear all" option. I got the same message for any song I tried to play. I switched back to 6.2.1, and incidentally was asked to run the build-perl-modules script again (even though 6.2.1 had already been up and running!). Songs played just fine. I'm running Slackware Linux 8.1 with a 2.4 kernel and perl 5.8.7. One thing that I have noticed on my system is that when I try to install DBD::SQLite using CPAN, it will compile but fails one test. CPAN won't install it.
a log with d_source enabled will provide more details on why the player reported a problem.
Created attachment 1127 [details] Log with d_source when 6.2.1 won't play songs Looks like a problem in the convert.conf file, but I'm using the same file for 6.2.1 and 6.2.2. Did the format change?
the format did not change, but you should never have to copy the conf files over from an older install. Please try reinstalling and leaving the conf files as default for 6.2.2. This looks more like a support issue than a bug. you should contact support@slimdevices.com
Yes, running with the original .conf files fixed it. I've been bringing my .conf files forward because that's the easiest way to add AAC/faad2 support when I upgrade. It's worked so far, but it looks like the convert.conf file has changed significantly. I have some related questions that I'll ask tech support. Note: I had the minor revision numbers off by one, now fixed in the bug report.
use custom-convert.conf for adding custom conversion lines. Marking as closed. New issues can be handled as new bugs it tech support doesn't resolve them for you.