jaunty: nautilus open/save-file window hangs out

[Remy Damour]

Description: Ubuntu 9.04
Release: 9.04

*************************************************
$ apt-cache policy nautilus
nautilus:
  Installed: 1:2.26.2-0ubuntu1
  Candidate: 1:2.26.2-0ubuntu1

*************************************************
DESCRIPTION:

Everything was fine prior to upgrading to jaunty.

Now, when I start my computer, everything is ok.
After some time (a few hours), nautilus looks like having hard-time to open "open file" / "save file" window.

That's extremely annoying. When I am in gedit and do 'ctrl + o', open-file window takes 18 seconds to open up, idem when hitting 'file/save as'.

Please note the following:
 - it's not that I'm running an old computer: core2duo p7350 with 4Gb ddr2
 - it's not depedent on current working directory: it occurs on all folders, incl. empty ones
 - it's not linked to gedit (this problem occurs with all apps, being firefox, opera, gimp...)
 - when I restart the computer, it works fine for a couple of hours, and then takes ages to show up that window
 - it never occured under intrepid
 - I suspect the problem being from nautilus, but I'm not sure at all, just a feeling

Honestly I don't know what to report, I have no error messages, it simply hangs out for 18 seconds or so (quite huge, on each ctrl + o)!
If you need any dmesg or similar, let me know, I will provide it.

Regards, Remy

[Remy Damour (remy-damour)]

I forgot to mention in bug report that the app calling nautilus-window freezes while waiting for it to be displayed (cannot do anything on the app, though system itself does not freeze)

[A. Walton (awalton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 298060, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.