Comment 3 for bug 1167102

Two additional bits of information that might be useful.

1. This problem still exists in 13.10
2. Switching to another image and then back again can actually allow the failed image to display correctly. If I switch to an adjacent image in the file list, it will not work but if I switch to an image that is 5 or 6 or more entries away, it will usually display the original image when I select it again. This makes me think it has something to do with the caching and that selecting an entry far enough away will clear the blank image from the cache and cause it to be rendered again.