4 msgpsmouse.c lost sync at byte 1
24 msgcups problem
5 msgNew hibernate modules in 2.6.23-gentoo-r3
13 msgEmerging virtual/editor installs nano - why?
9 msgFirefox mplayerplug-in problem
6 msgservices not starting since move to amd64
8 msgBe careful when using dhcp with a LiveCD
5 msgNew kernel broken nvidia-drivers
3 msgexaile
3 msgbookmarks invisible in Firefox fullscreen
1 msgsynce-engine
6 msgMake errors with new kernel-gentoo-2.6.23-r3
3 msgunlink ACCESS VIOLATIONs
4 msggnome emerge gives blocked packages
1 msgwxPython - cannot import wx
9 msgApache loading mod_php?
6 msgMoving LVMs around

bonobo, nautilus and mplayer
\ Thufir (5 Dec 2007)

2 msgQusetion: amd64 + apache2 + mod_extract_forwarded
2 msgHelp applying a qt patch
Subject:bonobo, nautilus and mplayer
Group:Gentoo-user
From:Thufir
Date:5 Dec 2007


 
I've only done the most cursory search on the following error:

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
factor.Killing bonobo-activation-server and
restarting Nautilus may help fix the problem.



But I did want to throw it out there. Ever since installing mplayer I'll
sometimes get screen freezes in GNOME after using mplayer. I did
eventually get the above error, and, as suggested, killing bonobo-
activation-server and restarting Nautilus (I logged out) seems have fixed
this instance of this annoyance.

In Windows there's the event viewer, I haven't found a similar thing in
Linux. I looked in .nautilus but didn't see an error log to shed more
light on this.



-Thufir

--
gentoo-user mailing list



© 2004-2008 readlist.com