From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1
Description of problem:
I have a large number of photos in a directory tree. A lot of these are .jpeg files, from "Photo CDs" (from film developing) and from a number of digital cameras. When in "icon" view, Nautilus typically displays icons that show thumbnails of the images. However, for some valid jpeg files, it won't display a thumbnail, but instead displays the system's default "jpeg" icon instead.
Note that switching to "catalog" view *does* display a valid thumbnail, and switching back to icon view "forgets" that thumbnail again. Catalog view is not a useful work-around, since files can't be selected/cut/paste/right-clicked/dragged, thus making that view quite useless (btw, what *is* it's purpose?)
When I double-click the file to view the problem images in an image viewer, they are displayed correctly.
Note that I think I'm only seeing this problem on jpeg files from a "Canon Powershot Pro1", and even then, only on a seemingly arbitrary subset of the files (*but* a precisely reproducable subset - i.e. it's always the same set of file no matter whether I log out and back in, or delete files from ~/.thumbnails or ~/.nautilus/metafiles)
None of these fix the problem: F5, CTRL-R, the "Refresh" graphical button, nor View/Reload menu.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run Nautilus
2. Browse to a directory containing jpeg files
3. Put Nautilus into icon mode
Actual Results: Only some icons are thumbnails of the images - others display the system's default "jpeg" icon.
Expected Results: All icons should be image thumbnails.
Created attachment 112897 [details]
A sample jpeg file that nautilus won't display a thumbnail for.
That picture is pretty big so you are probably hitting the preview limit
(nautilus won't create previews for files over a certain size).
In a nautilus window go to Edit -> Preferences then Preview to see what I mean.
Indeed, as pointed out in comment 2, this is a feature, not a bug.