nautilus failed to start on natty with the latest updates

Bug #732114 reported by Rus F Adrian
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Binary package hint: nautilus

nautilus wont start (no error given in a terminal) and when shut down my sistem its keep saying 'nautilus wont respond'

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
Date: Wed Mar 9 18:50:40 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110305)
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Rus F Adrian (tue-deactivatedaccount) wrote :
Revision history for this message
Rus F Adrian (tue-deactivatedaccount) wrote :

adi@deb:~$ nautilus

(nautilus:4820): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(nautilus:4820): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(nautilus:4820): GLib-GIO-CRITICAL **: g_bus_unwatch_name: assertion `watcher_id > 0' failed

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Rus F Adrian (tue-deactivatedaccount) wrote :
Revision history for this message
Rus F Adrian (tue-deactivatedaccount) wrote :
Revision history for this message
Rus F Adrian (tue-deactivatedaccount) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

is an instance of nautilus running? is it handling the destkop and icons?

Revision history for this message
Rus F Adrian (tue-deactivatedaccount) wrote :

yes, nautilus is running in the background, and is handling the desktops and the icons.

Revision history for this message
Sebastien Bacher (seb128) wrote :

seems similar to bug #724285, well if nautilus is running why do you say it fails to start?

Revision history for this message
tekstr1der (tekstr1der) wrote :

I just experienced this on an up-to-date natty. After applying updates, I restarted and was informed nautilus was not responding. Upon reboot/login nautilus was not running/responding and launching from terminal resulted in

(nautilus:4110): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(nautilus:4110): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

It looked like a nautilus process was running/hung, but would not launch the gui, nor provide context menu on right-click of desktop.

Also...

sudo kill -9 4110

...appeared to do nothing. Never experienced that before!

Changed in nautilus (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
tekstr1der (tekstr1der) wrote :

This continues to affect me. I can no longer run the nautilus file manager in a useable state. Whether launching from the command line or using the unity launcher for Home Folder, nautilus is hung, not responding and 100% CPU between all 4 cores is being used. I am able to view this behavior under gnome-system-monitor tab "resources", however the "processes" tab does not show what's eating CPU, nor does top, nor htop. Also, htop correlates the four cores totaling 100% constantly. When nautilus does "run" (show its gui), it grays-out during any actions (since the CPU is pegged, I'd assume).

I created an additional user account to test this. Nautilus appears to work correctly under a unity session with the new user.

Logging back in with my normal user results in this same behavior, even using the classic session w/o effects. Only by logging in to a safe-mode session does nautilus work properly and CPU usage is normal.

What could possibly have become corrupted suddenly? The .nautilus folder in ~/ is empty. I removed all gvfs-metadata. I cleared the zeitgeist cache and recently-used.

Killing the nautilus process immediately spawns another, so this is negatively affecting my entire experience w/natty since the CPU is constantly running at 100%

Revision history for this message
tekstr1der (tekstr1der) wrote :

Update: I found the culprit...even though there was no indication of what process was consuming all CPU cycles.

Disabling the ubuntuone-daemon from starting automatically allows everything to function correctly.

There's already a bug filed for this issue, bug # 776386.

Revision history for this message
Victor Vargas (kamus) wrote :

Marked as duplicated then, thank you.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.