Ubuntu
nautilus-actions package

Unable to open Nautilus windows

Bug #148106 reported by Mark Crutch on 2007-10-02

This bug report is a duplicate of: Bug #182345: nautilus crashed with SIGSEGV in gconf_client_remove_dir(). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	nautilus-actions (Ubuntu)	Triaged	Medium	Unassigned

Bug Description

Binary package hint: nautilus

I have upgraded a machine from Feisty to Gutsy and now have issues opening any Nautilus windows.

When I get the first window to open, I am then able to open other Nautilus windows with no problems. However once I close the last of the windows, I can't open any others. The process list shows a single remaining Nautilus instance with a high CPU usage. If I "killall nautilus" then I am subsequently able to open Nautilus windows again - until I close the last of them and end up in the same situation.

When this happens a "nautilus-debug-log.txt" file is produced containing many thousands of entries, all identical apart from the timestamp:

"0x8177880 2007/10/02 14:33:45.7653 (USER): debug log dumped due to signal 11"

I think this could be related to (or a dupe of) issue #27109 ("nautilus uses 100% cpu after closing a ssh session") - although in my case the problem occurs even if I'm trying to open my home directory rather than an SSH connection: I do have some SSH bookmarks defined, but I get this problem even if I'm not using them.

The machine in question is actually a virtual machine running on the latest version of VMWare Server (1.0.4).

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2007-10-02:

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in nautilus:
assignee:	nobody → desktop-bugs
importance:	Undecided → Medium
status:	New → Incomplete

Revision history for this message

Mark Crutch (markc-qsiuk) wrote on 2007-10-02:

Backtrace Edit (17.4 KiB, text/plain)

Backtrace attached, but I had a quick look through it and noticed a mention of "nautilus-actions". I tried removing the nautilus-actions package, and that seems to have cured the problem.

I am happy for this issue to be closed, as there was nothing in the nautilus-actions package that I really need to use, however if you wish to reassign it or send it onto the nautilus-actions maintainer then please do so.

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2007-10-02:

will do it, thanks for your quick response.