nautilus crash on error when locating bonobo factory

Bug #128776 reported by Francesco Fumanti
4
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

Nautilus crashes when I change from list view to icon view; and viceversa. It also crashes when I try to open a folder in the nautilus window.

I get an error dialog telling me that it could not locate the bonobo factory. As my dist-upgrade from feisty to gutsy went not completely smooth, I reinstalled with Synaptic Package Manager everything that was found by doing a bonobo search and that was marked as installed. But it did not solve the problem.

Unfortunately, the crash does not launch apport; however it dumps a core and a nautilus error-log in my home directory.

Revision history for this message
Francesco Fumanti (frafu) wrote :
Revision history for this message
Francesco Fumanti (frafu) wrote :
Revision history for this message
Francesco Fumanti (frafu) wrote :

Despite the updates, it continues to crash systematically, so that it that it is not possible to navigate through folders. (For the moment I am using Thunar, but it does not seem to work well either as it seems to hang sometimes.)

Revision history for this message
Francesco Fumanti (frafu) wrote :

I tried to produce a backtrace with gdb, but the nautilus window hangs when I try to open a subfolder until I quit gdb. I will attach the file pruduced by gdb:

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. Your trace looks like the same to bug 127826, are you still facing the problem?

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Francesco Fumanti (frafu) wrote :

Yes, it is still occurring in my uptodate gutsy. I first told about it still happening in bug 127826,and I was told to file a new bug. (So I filed this one.)

By the way, I want to point out that when I do a trace with gdb, the crash hangs before the nautilus window disappears and I have to "force quit" it

Revision history for this message
Francesco Fumanti (frafu) wrote :

The crashes do still happen if I try to open a folder so that it opens in the same window. However, if I open a folder by choosing "open in a new window" from the contextual menu (right click), it opens in another window without anything crashing.

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

what version of the nautilus package is installed?

Revision history for this message
Francesco Fumanti (frafu) wrote :

Synaptic Package Manager tells me that nautilus 1:2.19.6-0ubuntu2 is installed on my ubuntu gutsy installation and that it is also the latest version.

Revision history for this message
Francesco Fumanti (frafu) wrote :

I made another backtrace today. Nautilus hangs at the point where the crash occurs when it is attached to gdb. I assumed that the problem has occurred at that point and called the backtrace command of gdb. After quitting gdb, nautilus was again responsive.

Revision history for this message
Francesco Fumanti (frafu) wrote :
Revision history for this message
Francesco Fumanti (frafu) wrote :

I wonder whether I should not remove the bonobo indication in the title as it does not appear anymore on my system.

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

"Reading symbols from /usr/local/bin/nautilus...done."

Looks like you run a local copy and not the Ubuntu package, closing the bug

Changed in nautilus:
status: Incomplete → New
status: New → Invalid
Revision history for this message
Francesco Fumanti (frafu) wrote :

You were right; after uninstalling the local copy, the bug does not occur anymore.

Sorry: I thought that the copy that I installed manually had been overwritten by the update from the repository.

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

the packaging system doesn't use the local directory, it's made for sysadmin who want to install a custom version to use before the distribution one

Revision history for this message
oxi (oxiroxt) wrote :

Hi, I'm experiencing this problem after messing with the gutsy and backports repositories, but I have version 1:2.18.1-0ubuntu1 installed instead. Also, I don't have any files in /usr/local/bin.

I used Gutsy repos once to install kernel2.6.22 and nvidia-glx module for that kernel. I used backports repos to try to install kde4 but didn't succeed. Then I upgraded hal(don't ask me why, I don't recall :D), which was being held. Then downgraded hal and played with apt pinning to try to remove all upgraded/installed packages from backports repos. Ended up with Gutsy packages removed too :D. Installed Gutsy packages again, and I think that's all.

I'm new to Ubuntu and come from over 2 years experience with Gentoo. I got tired of compiling and since a friend of mine told me debian-based distributions have safe ways to install both stable and unstable packages, well I thought I'd give it a try,... I just haven't found out how yet. I'm very happy with Feisty for the moment, except now I'm starting to recall why I leaved debian in the first place. I feel apt is a little bit too complicated to maintain if you want to do things out-of-the-mold. Weird and scary apt...

Changed in nautilus:
status: Invalid → New
Revision history for this message
oxi (oxiroxt) wrote :

Sorry in case I shouldn't have re-opened it.

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

you might want to use http://launchpad.net/support for questions rather than commenting on a closed bug

Changed in nautilus:
status: New → Invalid
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.