Comment 12 for bug 1290310

I experienced the same problem under Ubuntu 14.04.5 when the system was under heavy computational load for an extended period of time (video encoding) There were no remote GVFS mounts as in atimonin case. I did not experience lagging as Valentis did.

What I tried and the results are as follows:

64bit:~$ killall nautilus
64bit:~$ nautilus -q
Could not register the application: Timeout was reached

64bit:~$ killall nautilus
64bit:~$ nautilus
Could not register the application: Timeout was reached

64bit:~$ nautilus -c
running nautilus_self_check_file_utilities
running nautilus_self_check_file_operations
running nautilus_self_check_directory
running nautilus_self_check_file
running nautilus_self_check_canvas_container
running nautilus_self_check_file_utilities
running nautilus_self_check_file_operations
running nautilus_self_check_directory
running nautilus_self_check_file
running nautilus_self_check_canvas_container

gvfs-mount shows no remote mounts as seen below.

64bit:~$ gvfs-mount -l
Drive(0): TOSHIBA THNSNH128GBST
  Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
  Volume(0): 13 GB Volume
    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
Drive(1): WDC WD2003FZEX-00Z4SA0
  Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
Drive(2): WDC WD3001FAEX-00MJRA0
  Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
Drive(3): Optiarc DVD RW AD-7280S
  Type: GProxyDrive (GProxyVolumeMonitorUDisks2)

64bit:~$ nautilus
Could not register the application: Timeout was reached

I was able to launch successfully via `gksu nautilus`