Re: oaf/orb is being rather screwy... evolution/nautilus troubles
Perhaps your using some package that is to old. Im not using evolution but
I am using Nautilus and I havent noticed such problems that you are
reporting. I hacked up a python script (using code from reportbug) that
prints out the versions of depending packages installed on your system.
When Im doing an "getdependencies nautilus" I get this:
Versions of packages nautilus depends on:
ii bonobo 1.0.14-1 The GNOME Bonobo System.
ii gconf 1.0.7-3 GNOME configuration database syste
ii gdk-imlib1 1.9.11-3 Gdk-Imlib is an imaging library fo
ii libart2 1.4.1.4-1 The Gnome canvas widget - runtime
ii libaudiofile0 0.2.3-2 The Audiofile Library
ii libbonobo2 1.0.14-1 The GNOME Bonobo library.
ii libc6 2.2.5-2 GNU C Library: Shared libraries an
ii libcdparanoia0 3a9.8-4 Shared libraries for cdparanoia (r
ii libdb3 3.2.9-14 Berkeley v3 Database Libraries [ru
ii libeel0 1.0.2-5 Eazel Extensions Library
ii libesd0 0.2.23-2 Enlightened Sound Daemon - Shared
ii libfam0 2.6.6.1-4 client library to control the FAM
ii libfreetype6 2.0.6-1 FreeType 2 font engine, shared lib
ii libgconf11 1.0.7-3 GNOME configuration database syste
ii libgdk-pixbuf-gnome2 0.15.0-2 The GNOME Canvas pixbuf library
ii libgdk-pixbuf2 0.15.0-2 The GdkPixBuf library.
ii libglib1.2 1.2.10-3 The GLib library of C routines
ii libgnome-vfs0 1.0.4-3 The GNOME virtual file-system libr
ii libgnome32 1.4.1.4-1 The Gnome libraries
ii libgnomeprint15 0.34-2 The GNOME Print architecture - run
ii libgnomesupport0 1.4.1.4-1 The Gnome libraries (Support libra
ii libgnomeui32 1.4.1.4-1 The Gnome libraries (User Interfac
ii libgnorba27 1.4.1.4-1 Gnome CORBA services
ii libgtk1.2 1.2.10-4 The GIMP Toolkit set of widgets fo
ii libjpeg62 6b-5 The Independent JPEG Group's JPEG
ii libmedusa0 0.5.1-1 The GNOME search/indexing package
ii libnautilus0 1.0.6-1 Shared libraries that part of Naut
ii liboaf0 0.6.7-4 The GNOME Object Activation Framew
ii liborbit0 0.5.13-2 Libraries for ORBit - a CORBA ORB
ii libpanel-applet0 1.4.0.6-1 Library for Gnome Panel applets
ii libpng2 1.0.12-2 PNG library - runtime
ii libpopt0 1.6.2-6 lib for parsing cmdline parameters
ii librsvg1 1.0.3-1 SAX-based renderer library for SVG
ii libwrap0 7.6-9 Wietse Venema's TCP wrappers libra
ii libxml1 1:1.8.17-1 GNOME XML library
ii oaf 0.6.7-4 The GNOME Object Activation Framew
ii scrollkeeper 0.2-6 A free electronic cataloging syste
ii xlibs 4.1.0-14 X Window System client libraries
ii zlib1g 1:1.1.3-19 compression library - runtime
You might want to compare that with your system. I attached the script to
this mail.
On Feb 26 20:04, Sanchez theSkiingCommunistCact wrote:
>
>
> in more attempted testing since my last post, i've come across the following
> nautilus error printed out to terminal:
>
> ** WARNING **: Throbber Activation exception 'Unknown CORBA exception id:
> 'IDL:CORBA/COMM_FAILURE:1.0''
>
> and the following popping up as error messages in nautilus itself:
>
> Nautilus can't be used now, due to an unexpected error from OAF when attepting
> to register the file manager view server.
>
> The icons view encountered an error when starting up
>
>
>
> --- Sanchez theSkiingCommunistCact <sanchezthecactus@yahoo.com> wrote:
> > recently, I've been having trouble with evolution and
> > nautilus (both from SID).
> >
> > In Evolution, I occasionally (actually, rather
> > regularly, but not 100% of the time) get the following
> > error when i try creating a new email
> >
> > <<
> > Could not create composer window:
> > Unable to activate HTML editor component.
> >
> > The error from the component system is:
> > Unknown CORBA exception id:
> > 'IDL:CORBA/COMM_FAILURE:1.0'
> > >>
> > (though sometimes the bottom line just says something
> > to the effect of "An Unknown Error Occurred"). If i
> > try new mail again, it works flawlessly (though i
> > occasionally have 2 or 3 errors right in a row, i
> > eventually do get a composer window), however, so this
> > is more annoyance than anything else, but it is a
> > rather large annoyance.
> >
> > With nautilus, i have a slightly different trouble:
> > at least once during every nautilus session, when i
> > try opening a nautilus window, the nautilus desktop
> > dissappears, then it reappears and 3 - 5 new nautilus
> > windows open up. closing them kills the desktop once
> > again, though nautilus and nautilus-throbber processes
> > linger on. if i kill all those processes and restart
> > nautilus, i get 'proper' behavior for a varying amount
> > of time, but then the desktop kill/multpile window
> > open thing happens again.
> >
> > i was finally able to get some terminal output when
> > this error happened by runinng 'nautilus' from a
> > terminal ('run-nautilus' gave no output at all), and
> > it said something similar to the evolution problem i
> > have stated above:
> > nautilus-throbber: something wrong with
> > OAF/ORBIT/something like that... it was another
> > COMM_FAILURE, i beleive, but the terminal overwrote
> > (CTRL-L'ed) itself when the nautilus desktop died (the
> > process exited, i was back in shell, and nautilus no
> > longer spit any information out to the terminal), and
> > i did not get the chance to copy the exact error down
> > before it was overwriten with CTRL-L :-(... all i know
> > for sure is that the error claimed to be with
> > nautilus-throbber, and either OAF or CORBA or ORBIT...
> > (i dont understand much about these components, so
> > its rather difficult to straighten them out ;) )
> >
> > appologies if this is not the correct list (is this
> > striclty a developer list?) to issue these questions
> > to, but i've found that obscure problems such as these
> > that i tend to find somewhat regularly get overlooked
> > on debian-user or #debian support channel, so i
> > thought that a more specific list, which i know
> > developers read would perhaps be helpful.
> >
--
* John Ericson john@john.pp.se
* ICQ: 7325429 JID: high@jabber.org
* web: http://john.pp.se
#!/usr/bin/python
#
# Needs reportbug.py that exists in package reportbug
import sys, reportbug
argc = len(sys.argv)
if argc < 2:
print "Usage: "+sys.argv[0]+" <package>"
sys.exit(1)
package = sys.argv[1]
status = reportbug.get_package_status(package)
(pkgversion, pkgavail, depends, conffiles, maintainer, installed, origin,
vendor, reportinfo, priority, desc) = status
#print "Getting dependency information for "+package+"..."
depinfo = reportbug.get_dependency_info(package, depends)
print depinfo
Reply to: