After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 777613 - Nautilus file manager stopped opening suddenly after closing-opening a few times. It doesn't open even after waiting a lot.After that it never opens. Not opening even from terminal.
Nautilus file manager stopped opening suddenly after closing-opening a few ti...
Status: RESOLVED DUPLICATE of bug 749207
Product: nautilus
Classification: Core
Component: general
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-01-22 17:18 UTC by Pradeep Kumar
Modified: 2017-04-08 13:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Pradeep Kumar 2017-01-22 17:18:11 UTC 
Running on Ubuntu 16.04.1LTS .
When I tried to open it from terminal , it finally shows some error:
Output of "nautilus" in default terminal of ubuntu:

"(nautilus:24456): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed

(nautilus:24456): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Could not register the application: Timeout was reached

(nautilus:24456): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(nautilus:24456): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(nautilus:24456): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed ".
Comment 1 Pradeep Kumar 2017-01-22 17:20:04 UTC 
Even clicks on desktop files,folders not working.
Comment 2 Pradeep Kumar 2017-01-22 17:21:59 UTC 
Works fine after running "killall nautilus".
Comment 3 Ernestas Kulik 2017-04-08 13:52:13 UTC 

*** This bug has been marked as a duplicate of bug 749207 ***