Re: [Scrollkeeper-devel] too much probs :-(

[Dan M. <mu...@al...>]

On Mon, 20 Jan 2003, [ISO-8859-15] Camille B=E9gnis wrote:

> Hello,
>=20
> I am experimenting too much stability problems with=20
> scrollkeeper/yelp/khelpcenter
>=20
> I have problems registering my OMF files, which do not appear on help=20
> browsers even if the OMF file is valid and teh category OK. :-(

Do any of the documents from the ScrollKeeper system appear?  Is it just =
a=20
problem with recently added documents, or with all of them?

> As the scrollkeeper-{install,update,uninstall} messages are always the=20
> same, I have no clue on what's going wrong.

Try using verbose mode on these commands if you want more information on=20
what is working and what isn't working.  Also, ScrollKeeper keeps a log=20
(typically /var/log/scrollkeeper.log) so you can always look in there to=20
see what is happening and any errors.

> After playing a little with those scripts, scrollkeeper is all screwed=20
> up. When I try to launch khelpcenter for example:
>=20
> [...]
> khelpcenter (kdebase): Requested plugin documents for ID konqueror
> khelpcenter (kdebase): Eeek, our group pointer is NULL!
> khelpcenter (kdebase): Scrollkeeper contents file '' does not exist.
> [...]
>=20
> And yelp looks empty. If I reinstall yelp, it works again...

When you reinstall yelp, do the documents for the new OMF files appear? =20
If so, it would seem that the problem is not with=20
scrollkeeper-{install,update,uninstall}.

If you find it helpful to poke around in ScrollKeeper a bit, keep an eye
on /var/lib/scrollkeeper/scrollkeeper_docs to see if new documents get
added to the bottom of the file (or removed).  To see what is in a given
contents list, look in /var/lib/scrollkeeper/<locale>/*.  Overall, it
should be pretty simple to identify whether ScrollKeeper is generally
working or not.

If you need to find out what paths ScrollKeeper is using, use=20
scrollkeeper-config.  And don't forget that the OMF file path is stored i=
n=20
/etc/scrollkeeper.conf.

At any rate, the fact that reinstalling Yelp influences whether things
works suggests that this particular problem is probably not with
ScrollKeeper.  It may have something to do with how paths are set up when=
=20
packages (perhaps Yelp) are built.

-Dan