I upgraded my 7.6 test server to 7.7, and upon starting the app, it decided to auto-rescan. I didn't actually want this rescan, as I wanted to reconfigure my prefs to point at several music source folders, rather than point at a folder that has shortcuts to each music source folder.
So I aborted the scan, changed the music folders prefs, and discovered that the scanner was still running (added note to https://bugs.slimdevices.com/show_bug.cgi?id=15186), and that I couldn't actually abort it. I stopped the server, and the external scanner was still running, so I had to manually terminate that process too. When I restarted LMS, it said it was still scanning (but it wasn't!). I aborted the scan, and then started a clear+scan all. After a few seconds, this reported that the scan had been aborted! I have now started a new clear+scan all, and it seems to be doing something. But my experience here is that this is even worse than previous releases, which have been pretty poor at handling rescan status and abortion. I think this could be a fairly common experience for existing users who are going to upgrade from 7.6 to 7.7. Phil _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
