Nautilus won't start up and the desktop icons are frozen (can't be clicked)

Bug #749776 reported by Stephen Rees-Carter
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: nautilus

Fully updated system, after a fresh boot, Nautilus is pretty unresponsive. It doesn't load when run, and the desktop icons are basically frozen (they can't be clicked).

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu11.1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Mon Apr 4 08:41:59 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta 1 i386 (20110329.1)
ProcEnviron:
 LANGUAGE=en_AU:en
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Stephen Rees-Carter (valorin) wrote :
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
Stephen Rees-Carter (valorin) wrote :

Ok, I think this is what you are after.

Revision history for this message
Jay Mac (jmac939) wrote :

I have the same problem. Error messages are:

(nautilus:4729): 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:4729): 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.

Reboot doesn't help.

Revision history for this message
Mike M (mkmacdonagh) wrote :

Same here.

Also, trying to start it in Ubuntu classic leads to an endless loop of "Starting file manager" windows in the taskbar but the main windows never comes up.

Revision history for this message
Mike M (mkmacdonagh) wrote :

For me the importance is pretty high as I can't browse my files at all since upgrading :(

Revision history for this message
Stephen Rees-Carter (valorin) wrote :

I agree that it's a pretty important bug - I can't mount any drives/network shares, which makes it impossible to do my development work.

A work around I can use occasionally is:

1) Click on the nautilus launcher icon a couple of times
2) Wait until the grayed out windows appear
3) Right click on the launcher icon and select "Quit"
4) Confirm the Force Close and wait for all windows to disappear
5) Click on the launcher icon again, it should load a usable window

It only works occasionally, and relies upon the grayed out windows to appear - which only appear some times.

Revision history for this message
Markus Lutz (markus-gmlutz) wrote :

This bug also is very annoying for me to.
It's a problem even in beta !

Revision history for this message
Dylan Bartlett (dylan-bartlett) wrote :

Getting the same bug too. My only workaround is using KDE which im not very keen on. Low seems like an understatement for a bug which breaks GUI file navigation.

Revision history for this message
Greg Fordyce (greg.fordyce) wrote :

I have the same bug after a recent update with 10.10. I have to right click folders and Open with > Dolphin to use them. Also right clicking folders and selecting properties won't work on the desktop but will in dolphin. Opening a terminal and typing nautilus makes the desktop blink.

Revision history for this message
daniel (danielprietog) wrote :

A careful obsevation of TOP processes, and the error information made me think that the root of the bug may be not Nautilus itself, but the ubuntuone-syncdaemon. I uninstalled all of the Ubuntu One stuff and the windows I tried to open an hour ago popped open, and the machine became noticeably faster.

Revision history for this message
Mike M (mkmacdonagh) wrote :

An update has fixed this for me

Revision history for this message
Pedro Villavicencio (pedro) wrote :

we still need the backtrace, can somebody provide that? Thanks.

Revision history for this message
Greg Fordyce (greg.fordyce) wrote :

Update on comment #10. Found that my machine had some faulty ram, as other problems started to appear. Replaced ram, but still had this fault. I have now done a distro upgrade and all seems fine.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello
Can you update about this issue?
is still reproducible with the latest updates?
thanks
Fabio

Changed in nautilus (Ubuntu):
status: Incomplete → Confirmed
status: Confirmed → Incomplete
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

Changed in nautilus (Ubuntu):
status: Incomplete → Expired
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.