You are not logged in.
Hi All,
I have decided to take the Gnome challenge, having been an Xfce user since I first started using Linux about 10 years ago. Anyway, Gnome is all installed (vanilla, no extensions etc until I resolve all issues I have) and everything seems ok, except with Nautilus.
Upon opening Nautilus, the window appears immediately and my home directory is populated, but the window is unresponsive, or slower than a snail in reverse, for about 5 minutes. Looking at my system monitor, it is sitting at about 12% CPU for those 5 mins and then it returns to a useable state (unless I perform certain actions - changing view from grid to list triggers another 5 minute wait for example).
Opening Nautilus as root does not suffer this issue at all. It behaves completely as expected.
Using this, I thought it may be something to do with user config or cached data, so I uninstalled Nautilus and removed all traces of config files and cleared my caches. After a reboot and re-installing Nautilus, tried again, and the same issue occurs. I cannot figure out why it is doing this.
I haven't been able to find anything remotely similar on a Google search, in the wiki or in the forums so have decided to post to ask for help.
Now, I have never used strace before, but installed it and gave it a go. I simply did a comparison between root and user just by doing strace -o /path/to/output/file nautilus both as user and root, so if I need to enable other options to help solve this, please let me know.
Below are the links to the output generated by strace. Bear in mind, this is simply from running nautilus as both user and root. No other actions were performed. In the case of the launch as user, I simply waited until all activity had stopped and the CPU usage had dropped to 0%. As you can see, there is vastly much more going on as user than root.
http://www.filedropper.com/usernautilustrace
http://www.filedropper.com/rootnautilustrace
Please let me know if any other info is needed.
Cheers.
llinux 3.16.2-1
nautilus 3.12.2-1
PS: I do have a NAS that is mounted to /mnt on boot and then the main subfolders on the NAS are bind mounted to directories in /home - could this be the cause, as in the root home folder, there are only empty directories?
[SOLVED]It was my xdg user dirs. I have always customised that so instead of a folder named Templates (which I never used) I changed it to Themes.
It would seem Nautilus uses the xdg templates directory to populate it's New Document Menu, so Nautilus would hang trying to populate that menu with the thousands of icons and wallpapers and other themes I had stored in that directory.
Now I have Themes separated from Templates, all works perfectly.[/SOLVED]
Last edited by Padfoot (2014-09-21 06:11:07)
Offline
PS: I do have a NAS that is mounted to /mnt on boot and then the main subfolders on the NAS are bind mounted to directories in /home - could this be the cause, as in the root home folder, there are only empty directories?
This should be simple enough to test, simply unmount your NAS and try if nautilus works any better.
Offline
Padfoot wrote:PS: I do have a NAS that is mounted to /mnt on boot and then the main subfolders on the NAS are bind mounted to directories in /home - could this be the cause, as in the root home folder, there are only empty directories?
This should be simple enough to test, simply unmount your NAS and try if nautilus works any better.
Have tried that, and it makes no difference I'm afraid. Thanks though.
Offline
I couldn't make anything of those traces, but did you check journal for any errors that could be related?
which process is using your cpu when nautilus is unresponsive?
Offline
No journal errors or terminal errors shown. nautilus is the process hogging the cpu, as you can see from the trace, it pretty obvious how (as opposed to why). root launch strace is 10K lines, user is 450k lines.
Offline