After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 600029 - nautilus does not show anything while trying to build trumbnails for many figures
nautilus does not show anything while trying to build trumbnails for many fig...
Status: RESOLVED DUPLICATE of bug 599475
Product: nautilus
Classification: Core
Component: Views: All
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-29 13:09 UTC by Leandro Martínez
Modified: 2009-11-08 16:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Leandro Martínez 2009-10-29 13:09:33 UTC
See the video of the bug here:

http://launchpadlibrarian.net/34595036/out.ogv

More information on my machine is available here:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/463234

-------- Description: 


I moved about 10 figures to a folder with nautilus. Now when I try to access this
folder nothing appears, and Nautilus seems to be waiting trumbnails to be built.

The screencast shows the behaviour (the figures never appear). I have 11 figures
on that folder totalling 11Mb. The largest one has 3.8 Mb, so no really big deal.

I think Nautilus should very rapidly quit trying to build a trumbnail and show default
icons, otherwise, if the trumbnail of some figure is problematic, it will not show anything.

- If I remove figure by figure, and even letting a single figure in that folder the problem persits.

- If I move the same files to another folder called "test", it works.

- If I change the name of the "Figures" folder to "test", it works.

- If I change the name back from "test" to "Figures" it stops working again.

- Closing and openning Nautilus does not solve the problem.

- Now I changed the name of the "teste" folder to "Figures" and removed the problematic
"Figures" folder (before) and it works.

So it appears that someway nautilus chosed a "problematic folder", putting the same
content in other folder and renaming it to the name of the problematic one makes
nautilus forget about the problem. Maybe it is related to a cache of trumbnails?


The screencast shows it all. The content of the "teste" folder is the same as
the content of the "Figures" folder.

I'm not sure how to reproduce the problem from scratch. The problem
was happening when I reported it with the "report problem", so some
information may be there.



ProblemType: Bug
Architecture: amd64
Date: Thu Oct 29 09:24:02 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: fglrx
Package: nautilus 1:2.28.1-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: nautilus
Uname: Linux 2.6.31-14-generic x86_64
Comment 1 Leandro Martínez 2009-11-04 18:12:56 UTC
I now have the same problem, but in a folder not having large
files, only a couple pdfs. 

The bug-tracker information of nautilus when having the problem
is here:

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/474518
Comment 2 Leandro Martínez 2009-11-04 18:18:25 UTC
Now I realized the following: on closing nautilus, the process remains background. Opening it again returns the same behaviour. However, if I kill the process in background and open nautilus again, the problem is fixed.
Comment 3 Leandro Martínez 2009-11-04 18:20:59 UTC
Clearly the problem is that the trumbnail generator gets stuck for some reason (in the first case for images, in the second case for pdf files) and then the folder content is not displayed. An alternative icon should be displayed I think, and only updated by trumbnail if it is generated succesfully.
Comment 4 Cosimo Cecchi 2009-11-08 16:19:03 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 599475 ***