nautilus/bonobo problem after X server restart in feisty

Bug #104521 reported by DaveAbrahams
4
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

After failing to enable desktop-effects, I had to restart my X server. Upon logging in, I got:

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.

Revision history for this message
Rapolas K. (casselas) wrote :

The same for me. Just sometimes my xserver crashes for couple times, and then starts with showing this error.

Revision history for this message
duffernix (robras) wrote :

I receive the same error in a message box while trying to copy a 4 GB dvd.iso file to a network file (mounted via samba). It happens each time when 2 GB of the file has been copied. I'm running 64 bit Feisty beta with all updates applied

Revision history for this message
Dee (dee24) wrote :

I just received this error a few minutes ago when Xserver crashed, leaving no icons on the desktop and causing all my programs to disappear from the taskbar.

Revision history for this message
Dee (dee24) wrote :

Man, after Xserver crashed, "Applications" from Start Menu no longer works. "Main menu" from "System" also does not work.
Does not work as in: I click on them and nothing shows up.
When I try to launch "Main menu" also known as Alacarte from Terminal, I receive the error messages as listed below.

Shortly before the Xserver crashed, I was working within Terminal and trying to compile and install the latest version of Gimp. However, I simply ignored it and restarted X, then carried on installing Gimp. Sudo make install, etc., etc. The only packages I'd installed within the last 12 hours were: gimp-print, gimp 2.2.14.

Since then I've also tried reinstalling python2.5 and python-xml and python-lxml

Nothing happened.

Below are the error messages for Alacarte in Terminal:

lucifiel@lucifiel:~$ alacarte

Traceback (most recent call last):
File "/usr/bin/alacarte", line 36, in <module>
main()
File "/usr/bin/alacarte", line 32, in main
app = MainWindow(datadir, version, sys.argv)
File "/usr/lib/python2.5/site-packages/Alacarte/MainWindow.py", line 49, in __init__
self.editor = MenuEditor()
File "/usr/lib/python2.5/site-packages/Alacarte/MenuEditor.py", line 36, in __init__
self.__loadMenus()
File "/usr/lib/python2.5/site-packages/Alacarte/MenuEditor.py", line 46, in __loadMenus
self.applications.dom = xml.dom.minidom.parse(self.applications.path)
File "/usr/lib/python2.5/site-packages/_xmlplus/dom/minidom.py", line 1915, in parse
return expatbuilder.parse(file)
File "/usr/lib/python2.5/site-packages/_xmlplus/dom/expatbuilder.py", line 926, in parse
result = builder.parseFile(fp)
File "/usr/lib/python2.5/site-packages/_xmlplus/dom/expatbuilder.py", line 211, in parseFile
parser.Parse("", True)
xml.parsers.expat.ExpatError: no element found: line 1, column 0
__________________

Revision history for this message
Dee (dee24) wrote :

Oops forgot to mention that I'm running Feisty Final(patched from beta to final).

Revision history for this message
Dee (dee24) wrote :

All right, I managed to resolve the issue by creating a new user(gave the user full admin permissions) and by doing chown + chmod.

A big thanks goes to the fine folks at #ubuntuforums-beginners for helping me pull through.

According to Shirish, a friend of mine, attaching my ./gnome and ./gnome2 directories might prove useful so here they are in .tar.bz2 format.

Revision history for this message
Dee (dee24) wrote :

Commands run on my home/user directories:
sudo chown -Rvf <your_user_name> <dir>

Example: sudo chown -Rvf lily

sudo - chmod 755 -R /home/whatevernameis

Example: sudo - chmod 755 -Rvf /home/chicken

Revision history for this message
Dee (dee24) wrote :
Revision history for this message
Dee (dee24) wrote :
Revision history for this message
oskar (oskar669) wrote :

I get the exact same error... also after I had to kill the xserver.
I'm running feisty since herd3, since Yuri Aoki.Hidan.Lucifiel said he also upgraded from beta, maybe that's part of the problem.
I got nautilus crashes on startup before, without this error message. killing/restarting nautilus helps.

Revision history for this message
Lars Vopicka (lars+vopicka-deactivatedaccount) wrote :

My problem was the application menu which would not open.
With alacarte i got the above mentioned error as well.

I have found that renaming ~/.config solved both issues.

(I am running edgy on this machine.)

Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

may be related to bug #114428

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.