I get this on the terminal every time I open a Nautilus window:

** WARNING **: Unable to parse ScrollKeeper TOC XML file:
	/gnome/var/lib/scrollkeeper/TOC/49

Dan figured out that this was caused by the fact that I do not have this file on
my system:

/gnome/share/gnome/help/nautilus/C/nautilus.sgml

But I do have this file on my system:

/gnome/share/omf/nautilus/nautilus-C.omf

Apparently both of these are obsolete, and it is somewhat mysterious why I have
the omf (some kind of metadata) file, but not the file to which it refers. Since
these are both installed in /gnome, they should both have been installed
together and deleted together.

We might want to try to figure out why I ended up with one and not the other. Or
we might want to just suppress the WARNING since there is nothing actually wrong
(just an extra file that doesn't get used). Or we might want to not care.



------- Additional Comments From don@eazel.com 2001-03-01 18:49:54 ----

I suspect that if you did a clobber build you wouldn't be seeing this problem. 
If that's the case, then this bug can quickly move to 1.2.




------- Additional Comments From sullivan@eazel.com 2001-03-01 18:54:27 ----

Well, that might be true, but on the other hand I managed to somehow get 
into this situation after my last clobber build, which was recently. Since the 
clobber build wipes out all of /gnome, it should have clobbered both of 
these files, which means one of them came back afterwards and the 
other didn't.



------- Additional Comments From dan@eazel.com 2001-03-01 21:01:57 ----

This is just a warning message in components/help/hyperbola-filefmt.c.  We
really don't want this kind of thing spewed to the terminal.  We have a few
options here:
1) Have scrollkeeper not generate a TOC for the file.  This is what happens with
HTML files.
2) Just kill the error message
3) Send the error message to some log file or have it only displayed when
Nautilus is run in certain modes (eg, --verbose)

It looks like Nautilus doesn't do #3, so perhaps we should do #2 in the short
term, and eventually do #1.

I don't think this is so much a bug, because ScrollKeeper and Nautilus seem to
be robust against missing documents.  However we should suppress this ugly
warning I think.

Assigning to Laszlo, since this is his code so he should get to decide how it is
handled.  Laszlo, if you don't get this done, please reassign to me and I'll
just comment out the line which issues the warning.

Don - This can be a P3.  The easy fix is to comment out one line.



------- Additional Comments From don@eazel.com 2001-03-01 21:21:29 ----

Laszlo, this is approved for 1.0.




------- Additional Comments From laszlo.kovacs@sun.com 2001-03-02 05:57:47 ----

I commented out the warning for the moment. I also commented out another one
related to not finding the topleveldocs.xml file. It is easier to find them if
we decide to implement a log file.

There are a variety of reasons why you could have that obosolete OMF file
installed. The most common is that during a previous build it gets into
omf-install and then you update your Nautilus CVS and the source OMF file is
deleted as it was taken out. But it is still in your omf-install directory so it
gets installed. I also noticed that it got installed and manually removed it
from omf-install. 



------- Additional Comments From jfleck@inkstain.net 2001-03-03 18:16:19 ----

Verifying based on code examination, and by duplicating sullivan's original
case: I've got the omf file, but I blew away the sgml file, and was not able to
get an error message.



------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 21:06 -------