Public bug reported:
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).
** Affects: nautilus (Ubuntu)
Importance: Medium
Assignee: Ubuntu Desktop Bugs (desktop-bugs)
Status: Incomplete
--
Unable to open Nautilus windows
https://bugs.launchpad.net/bugs/148106
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
