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 738546 - Nautilus couldn't start
Nautilus couldn't start
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-10-14 18:54 UTC by Mikhail
Modified: 2017-08-29 06:57 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
backtraces of nautilus (4.12 KB, application/x-gzip)
2014-10-14 18:54 UTC, Mikhail 		Details

Description Mikhail 2014-10-14 18:54:41 UTC 
Created attachment 288544 [details]
backtraces of nautilus

Nautilus couldn't start

[mikhail@localhost ~]$ nautilus

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

(nautilus:5520): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Could not register the application: Timeout was reached
[mikhail@localhost ~]$ nautilus

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

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



Demonstration:
https://drive.google.com/file/d/0B0nwzlfiB4aQMllsLS1RZmlIQ2M/view?usp=sharing


$ rpm -q nautilus
nautilus-3.14.0-2.fc21.x86_64
Comment 1 Alexandre Franke 2016-12-04 22:39:11 UTC 
Do you still experience the issue with a recent version of GNOME?
Comment 2 Alexandre Franke 2017-08-29 06:57:45 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!