[csw-users] Evolution 2.2 on Solaris 10

[Mats Larsson]

On 2005-04-12 20:59, Ian Baines wrote:
> I have a recently installed Solaris 10 (Sparc) system with Sun's
> Gnome 2.6 and with it Evolution 1.4.6, all running happily.
> 
> I would like to upgrade Evolution to version 2.2 using the
> Blastwave.org version but don't yet wish to upgrade Gnome to the
> Blastwave Gnome 2.8.
> 
> I have previously used Blastwave's Evolution 2.0 and Gnome 2.8 under
> Solaris 9 with success. I have currently got a number of non
> graphical blastwave packages installed under Solaris 10 without
> problems.
> 
> I shutdown Sun's Evolution using "evolution --force-shutdown" and
> backed up the ~/evolution and ~/.gconf/apps directories. I installed
> Evolution 2.2 using "pkg-get -i evolution" and the installation ran
> OK. I have no LD_LIBRARY_PATH at all and /opt/csw/bin is in my path
> (but after /usr/bin). I have not uninstalled Sun's Evolution 1.4.6.
> 
> I started Evolution 2.2 in a shell using "/opt/csw/bin/evolution" and
> I get the following:-
> 
> * - * - * - *
> 
> [ian at amazon ~]$ /opt/csw/bin/evolution
> 
> es menu class init

Before the "es menu class init" thing I get:

(evolution:8278): Gtk-WARNING **: Could not find the icon 'stock_mail'.
The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
         http://freedesktop.org/Software/icon-theme/releases

I do have these installed:

application CSWgnomeicontheme                gnome_icon_theme - GNOME
icon theme
application CSWhicoloricontheme              hicolor_icon_theme -
freedesktop.org base icon theme

Anybody who knows hat's wrong?

> /opt/csw/lib/evolution/2.2/plugins/org-gnome-save-calendar.eplug:18:
> parser error : Premature end of data in tag e-plugin-list line 2
> 
> /opt/csw/lib/evolution/2.2/plugins/org-gnome-select-one-source.eplug:18:
> parser error : Premature end of data in tag e-plugin-list line 2
> 
> /opt/csw/lib/evolution/2.2/plugins/org-gnome-subject-thread.eplug:14:
> parser error : Premature end of data in tag e-plugin-list line 2

Same for me. Should be reported as a bug I believe. But easily fixed by
adding this line at the end of each file:

</e-plugin-list>

> evolution-shell-Message: Killing old version of
> evolution-data-server...
> 
> (evolution:14143): e-error.c-WARNING **: No parent set, or default
> parent available for error dialog [ian at amazon ~]$
> 
> I also get a pop up warning box saying the following:-
> 
> Evolution can not start Your system configuration does not match your
> evolution configuration. Click Help for details (With a Help and Quit
> button.)
> 
> (Clicking Help brings up Mozilla with a blank page at
> support.ximian.com. Quit does have the desired effect.)

Not experiencing this. For me Evo finally comes up after several
warnings like:

(evolution:8278): camel-WARNING **: Invalid root:
'/home/uabmol/.evolution/mail/local/Drafts.ibex.index'

(evolution:8278): camel-WARNING **: version: TEXT.000 (TEXT.000)

(evolution:8278): camel-WARNING **: block size: 1024 (1024) OK

(evolution:8278): camel-WARNING **: free: 0 (0 add size < 1024) OK

(evolution:8278): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD

(evolution:8278): camel-WARNING **: flags: unSYNC

(evolution:8278): camel-WARNING **: Invalid root:
'/home/uabmol/.evolution/mail/local/Outbox.ibex.index'

(evolution:8278): camel-WARNING **: version: TEXT.000 (TEXT.000)

(evolution:8278): camel-WARNING **: block size: 1024 (1024) OK

(evolution:8278): camel-WARNING **: free: 0 (0 add size < 1024) OK

(evolution:8278): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD

(evolution:8278): camel-WARNING **: flags: unSYNC

(evolution:8278): camel-WARNING **: Invalid root:
'/home/uabmol/.evolution/mail/local/Sent.ibex.index'

(evolution:8278): camel-WARNING **: version: TEXT.000 (TEXT.000)

(evolution:8278): camel-WARNING **: block size: 1024 (1024) OK

(evolution:8278): camel-WARNING **: free: 0 (0 add size < 1024) OK

(evolution:8278): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD

(evolution:8278): camel-WARNING **: flags: unSYNC

Sure would be nice to know why?

/MOL