The bug is old and Ubuntu changed quite a lot since, there has also been
no activity here nor similar reports. Closing since we believe the issue
as described is deprecated but feel free to file a new report if you
still have problems in recent Ubuntu versions.
** Changed in: nautilus (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/230273
Title:
(very) strange fix for slow change directory performance some people
experience (could help find a fix?)
Status in Nautilus:
New
Status in nautilus package in Ubuntu:
Invalid
Bug description:
Binary package hint: nautilus
Hi
I have been using Ubuntu at least since Dapper, and always experienced
varying degrees of slowness in nautilus, be it right after a reboot
like with Hardy for me, or only after a few hours of somewhat
intensive file browsing/management. Perhaps Feisty was the fastest for
me in this regard, and the only one which I had as fresh install
(excepting user files), even Dapper I dist-upgraded it straight from a
fresh ubuntu 5.10 install to one of the later Dapper betas. Hardy has
been the one with the worst performance from nautilus, for me at
least.
OK, so I am aware most people have no performance problems with
nautilus, but if you search ubuntuforums.org for post titles
mentioning nautilus you will see a lot of them are about poor
performance/slowness in nautilus.
Steps to reproduce this 'fix':
'Normal' behaviour:
- Nautilus takes more than a few seconds to start responding (while
freezing all open nautilus windows) when the user changes directories,
regardless if the user is changing to an empty directory, one full of pictures
or directories. (This has nothing to do with reading and displaying cached
thumbnails, that comes *after* the nautilus had stopped responding.)
Reproducing the fix:
- For best results, find a folder that doesn't take to long after the
'normal' nautilus change dir freeze to stop loading, i.e., the red stop button
in nautilus turns gray instantly. A directory which contains only a few dozen
folders and nothing else is ideal.
- Change into a sub folder that as at least one file renamable by you,
or create a file yourself
- Now, create a file, or rename an existing one from the context menu
-> 'Rename', you don't need to actually change anything in the name, but just
leave the inline editable lable as if you were just trying to come up with a
name for the file, but don't touch it!
- With name lable for that file still in edit mode, click on the up
directory button in nautilus
Result:
- Nautilus changes to the parent directory and finishes loading it,
instantly! Impossible! :)
Expected Result:
- It would take more than a couple of seconds to change directories.
Would it possible please to find out how to reproduce this 'erroneous'
behaviour with regular usage? :)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/230273/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
