[KLUG Members] View www.espn.com with Konqueror (KDE v3.0)

[members@kalamazoolinux.org]

>>I decided to try it again recently.  I'm running an up to date Ximian on
>>Redhat 7.2, making sure I had the latest Galeon & Mozilla.  I blew away
>>my ~/.galeon directory to start fresh.  The first day Galeon worked
>>great.  The very next day I logged on, and when I now try to start
>>Galeon I get a ERROR popup that says:  "Cannot find a schema for galeon
>>preferences.  Check your gconf setup, look at galeon FAQ for more info".
>>Is there some trick to make Galeon work?
>That's a Gnome-Bonobo error.  It will affect more than just Galeon.  Are
>you running your home directory over NFS?  If so, you've got a locking
>issue.

One of the problems posed by a component based architecture is configuration and
syncronization.  Components (quasi-stand-alone entities) need to know when a
config change occurs,  or possibly just some event.  The "best" way for them to
do this is to not truly manage such information themselves but depend upon some
central respository.  Lots of app specifc .whatever files simply don't cut it
any more.  This repository is managed by the gconfd daemon,  one runs for every
session.  Only gconfd and it's companion oaf components have some very real
syncronization problems (bugs) in GNOME 1.x.  Just plain flawed design. 
Workarounds have made these pretty stable,  but the real answer is GNOME 2.0.  I
have a script that runs on logout that uses at to schedule gconftool --shutdown
 and an oaf-slay to run in two minutes.  This avoids any hangers-on that might
befoul things.


-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/