I am also getting Nautilus crashes, but it doesn't come up in the Bug Reporting proggy... Below is what comes up in a box:
"Nautilus can't be used now, due to an unexpected error." "Nautilus can't be used now, due to an unexpected error from Bonobo when attempting to locate the factory.Killing bonobo-activation-server and restarting Nautilus may help fix the problem." When this crash occurred, what I was doing was looking through some things I had downloaded with Azureus and was going to copy them and put them in the directory I use for ebooks. All the sudden the file manager closed and up pops the error on my other monitor. I run dual 19" flat panel monitors and have it set up as if I have two totally separate puters, (two sep desktops). It doesn't seem to matter which monitor I am working with File Manager on, it does it on both 'sides' If you need any further info or I can help in any way, please let me know.... Bill Sebastien Bacher wrote: > Thanks for your bug report. The crash looks like a memory corruption. > Could you try to get a valgrind log for it? (you can follow the > instructions from https://wiki.ubuntu.com/Valgrind for that) > > ** Changed in: gnome-panel (Ubuntu) > Importance: Undecided => Medium > Assignee: (unassigned) => Ubuntu Desktop Bugs > Status: Unconfirmed => Needs Info > > -- [apport] gnome-panel crashed with SIGSEGV in _int_malloc() https://launchpad.net/bugs/90383 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
