..and absent a prefs file, is the code really trying to muckle with /imgproxy.db in the root directory? Or is that just a debugging output artifact?
Thanks for the report. It was indeed a race condition. The cache initialization was being called before the prefs-init, while depending on one of the prefs. Should be fixed in the next build (or in git - if you run from the source).
-- Michael _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
