I would re-zip the packages in question and reupload them just to see if something fishy happened while compressing them.

You could also just send them file by file over ftp since the number of files in the packages seldom are of any significant amount.

There is a bug in unzip that still lingers in some linux/unix versions, where all paths and filenames are erroneously lowercased by the unzipper.

After creating a new zip as @adajad suggests, browse it to check the paths/files to the problem addons have the correct case. Then, after uploading and unzipping on the host, check again. The bug I mentioned is with unzip, not zip, so that is where you may see the difference.

There are usually several unzip programs available. If it turns out to be the issue I describe you could try deflating with gzip.

Hi,

Thanks for the replies. I've just uninstalled and FTP all the packages and it has the same result. The icon.jpg doesn't even display for the troublesome addons.

The unzip issue doesn't just affect packages. So you could spot-check a few other files (many of the Zend files in the core have mixed case paths). However, as icon.png is all lower case, it seems unlikely that zip/unzip could be the issue.

It is a png file? (I assume icon.jpg is a typo?)

How do the 'troublesome' addons appear on the install page? Do you see their names and descriptions? Is it just the icons that are missing?

Could it be the browser cache?

I've just done a clean install of C5 and uploaded the same Packages with the same outcome. I then added some ones I've just freshly downloaded and they work fine

These original Packages were downloaded then Dropboxed to me by my client, so I'm thinking something might have happened during the original download or transfer to me. They work fine in my local environment though which makes it confusing.

I've requested he re-downloads and sends them again.

Still thinking it may be case sensitivity, if your local environment is windows, it won't care about the case of filenames. But Linux will. So a previously corrupted filename case may continue to work in windows, but fail to work if copied to linux.