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
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 self_check_ file_utilities self_check_ file_operations self_check_ directory self_check_ file self_check_ canvas_ container self_check_ file_utilities self_check_ file_operations self_check_ directory self_check_ file self_check_ canvas_ container
running nautilus_
running nautilus_
running nautilus_
running nautilus_
running nautilus_
running nautilus_
running nautilus_
running nautilus_
running nautilus_
running nautilus_
gvfs-mount shows no remote mounts as seen below.
64bit:~$ gvfs-mount -l nitorUDisks2) nitorUDisks2) nitorUDisks2) nitorUDisks2) nitorUDisks2)
Drive(0): TOSHIBA THNSNH128GBST
Type: GProxyDrive (GProxyVolumeMo
Volume(0): 13 GB Volume
Type: GProxyVolume (GProxyVolumeMo
Drive(1): WDC WD2003FZEX-00Z4SA0
Type: GProxyDrive (GProxyVolumeMo
Drive(2): WDC WD3001FAEX-00MJRA0
Type: GProxyDrive (GProxyVolumeMo
Drive(3): Optiarc DVD RW AD-7280S
Type: GProxyDrive (GProxyVolumeMo
64bit:~$ nautilus
Could not register the application: Timeout was reached
I was able to launch successfully via `gksu nautilus`