assigning to Michael for comment. I can try tackling the fix, but not today.

There is a white-on-transparent html/images/cover.png in Default/ now, and a gray-on-transparent html/images/cover.png in EN/

The EN image is necessary for any skin that employs a white background (Handheld, Classic, Touch, Nokia770), because the white-on-transparent appears blank in these skins.

If a resized request is sent for cover.png, for example

http://localhost:9000/Classic/html/images/cover_50x50.png

I would expect it to look in Classic/html/images followed by EN/html/images, but that's not how it works. Instead it looks through all skin folders until it finds a match, and uses the first match it finds. It's finding Default first, and we're getting the "blank" image in the skin.

The data for cover.png is grabbed by Slim::Web::HTTP::getStaticContent('html/images/cover.png');, which in turn calls Slim::Web::HTTP::fixHtttpPath.

fixHttpPath grabs all of the skindirs with 

my $skindirs = $template->context()->{'CONFIG'}->{'INCLUDE_PATH'};
       
what isn't clear to me here is how to sort $skindirs appropriately. Throw in the added complexity that some skins (e.g., Touch) are supposed to have an inheritance from other skins first. So, in the case of Touch, getStaticContent should try to find Touch/html/images/cover.png first, then Nokia770/html/images/cover.png, then EN/html/images/cover.png (and then, IMHO, give up and maybe return some kind of uber-default 1x1 image).