No, other users on my PC doesn't have such problem when opening any folder.
This problem persist for my user since Ubuntu 12.04. Before update to Ubuntu 12.10 I remove all hidden files. But problem appear anyway. Removing configuration folders (when Unity not running) ".gnome .gnome2 .gconf .gconfd .metacity .cache .dbus .dmrc .mission-control .thumbnails" doesn't help to solve this issue.
Seems, disabling thumbnailing fix this freeze at starting Nautilus after "killall nautlius" (when I tried disable thumbnailing in nautilus setting - it's freeze for ~20sec). Further more, set option "Count number of items" for folders to "Never" (but thumbnailing for files enabled "Show thumbnails" = "Local files only") help to fix Nautilus start after "killall nautlius" but, when I try to run Nautilus just after I login my user - it's run on background with high CPU usage and not responding for ~30 sec. This seems is not a solution for me.
Below, in attachment, You can find log of command "ls -al" to see if there is any file or folder than can cause such troubles
No, other users on my PC doesn't have such problem when opening any folder.
This problem persist for my user since Ubuntu 12.04. Before update to Ubuntu 12.10 I remove all hidden files. But problem appear anyway. Removing configuration folders (when Unity not running) ".gnome .gnome2 .gconf .gconfd .metacity .cache .dbus .dmrc .mission-control .thumbnails" doesn't help to solve this issue.
Seems, disabling thumbnailing fix this freeze at starting Nautilus after "killall nautlius" (when I tried disable thumbnailing in nautilus setting - it's freeze for ~20sec). Further more, set option "Count number of items" for folders to "Never" (but thumbnailing for files enabled "Show thumbnails" = "Local files only") help to fix Nautilus start after "killall nautlius" but, when I try to run Nautilus just after I login my user - it's run on background with high CPU usage and not responding for ~30 sec. This seems is not a solution for me.
Below, in attachment, You can find log of command "ls -al" to see if there is any file or folder than can cause such troubles