Re: oaf/orb is being rather screwy... evolution/nautilus troubles
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.
>
> -thanks.
> joe
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Greetings - Send FREE e-cards for every occasion!
> http://greetings.yahoo.com
>
__________________________________________________
Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com
Reply to: