gedit and scrollkeeper problems on 4.11 system

Kevin Oberman oberman at es.net
Mon Feb 14 12:58:10 PST 2005


> Date: Mon, 14 Feb 2005 15:25:02 -0500
> From: Joe Marcus Clarke <marcus at FreeBSD.org>
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Kevin Oberman wrote:
> |>Date: Mon, 14 Feb 2005 15:16:16 -0500
> |>From: Joe Marcus Clarke <marcus at FreeBSD.org>
> |>
> |>-----BEGIN PGP SIGNED MESSAGE-----
> |>Hash: SHA1
> |>
> |>Kevin Oberman wrote:
> |>|>Date: Mon, 14 Feb 2005 13:08:10 -0500
> |>|>From: Joe Marcus Clarke <marcus at FreeBSD.org>
> |>|>
> |>|>-----BEGIN PGP SIGNED MESSAGE-----
> |>|>Hash: SHA1
> |>|>
> |>|>Kevin Oberman wrote:
> |>|>| I am unable to update gedit and seem to have messed up scrollkeeper.
> |>|>|
> |>|>| The system is running 4.11-stable and all ports are updated
> regularly. I
> |>|>| have tried updating to gedit-2.8.2_1 to 2.8.3 and failed to get it to
> |>|>| install properly.
> |>|>|
> |>|>| The first issue is that in help/C has:
> |>|>| for file in gedit-C.omf; do \
> |>|>|         install -c -o root -g wheel -m 444 $file.out
> |>|>/usr/X11R6/share/gnome/omf/gedit/$file; \
> |>|>| done
> |>|>|
> |>|>| While gedit-C.omf is there, I don't have a gedit-C.omf.out, so the
> |>|>| script fails. portupgrade then starts re-installing the old
> |>|>| version. Then the REALLY scarry thing happens:
> |>|>| --->  Restoring the old version
> |>|>| update-desktop-database: not found
> |>|>| Segmentation fault (core dumped)
> |>|>| Segmentation fault (core dumped)
> |>|>| Segmentation fault (core dumped)
> |>|>| Segmentation fault (core dumped)
> |>|>| Segmentation fault (core dumped)
> |>|>| Segmentation fault (core dumped)
> |>|>| Segmentation fault (core dumped)
> |>|>| Segmentation fault (core dumped)
> |>|>| Segmentation fault (core dumped)
> |>|>| Segmentation fault (core dumped)
> |>|>| Segmentation fault (core dumped)
> |>|>| Segmentation fault (core dumped)
> |>|>| Segmentation fault (core dumped)
> |>|>| Segmentation fault (core dumped)
> |>|>|
> |>|>| All of the segmentation faults are in scrollkeeper. This is where I
> |>|>| really get worried. I really don't want to re-install all of Gnome,
> |>|>| especially when 2.10 is so close and that will force a complete Gnome
> |>|>| rebuild.
> |>|>|
> |>|>| Any ideas what went wrong here?
> |>|>
> |>|>Good be a problem with your libxslt installation.  IT may also be a
> |>|>problem with scrollkeeper itself.  What happens if you rebuild both of
> |>|>those ports?
> |>|
> |>|
> |>| Well, it's a bit deeper down the tree than that. I re-installed libxslt,
> |>| but scrollkeeper fails to configure as it can't find its DTD. I'm still
> |>| trying to figure out what I need to install to fix that. I've tried all
> |>| of the docbook ports as well as sdocbook-xml, p5-XML-Parse, and
> |>| xmlcatmgr. Still no joy. :-(
> |>|
> |>| Any idea how to get the DTD back or am I facing a major re-install of
> |>| the whole thing?
> |>
> |>Which DTD is missing?
> |
> |
> | Joe,
> | Sorry. I need to learn to read. It was not missing a DTD, but xmlcatmgr
> | was segfaulting when attempting to get the DTD.
> | checking for DocBook XML DTD... Segmentation fault (core dumped)
> | Segmentation fault (core dumped)
> | configure: error: not found. Make sure you have the DocBook DTD
> installed and ensure that it is registered in /usr/local/share/xml/catalog.
> | ===>  Script "configure" failed unexpectedly.
> | Please direct the output of the failure of the make command to a file, and
> | then feed that file to the gnomelogalyzer, available from
> | http://www.freebsd.org/gnome/gnomelogalyzer.sh, which will diagnose
> the problem
> | and suggest a solution.  If - and only if - the gnomelogalyzer cannot
> solve
> | the problem, report the problem to the FreeBSD GNOME team at
> gnome at FreeBSD.org,
> | and attach
> | "/usr/ports/textproc/scrollkeeper/work/scrollkeeper-0.3.14/config.log" and
> | the output of the failure of the make command.  Also, it might be a
> good idea
> | to provide an overview of all packages installed on your system (e.g.
> an `ls
> | /var/db/pkg`).
> |
> | But why the heck s it failing? I'm baffled, but  suspect it's something
> | in some library. Maybe I need to rebuild expat? (I really don't
> | understand what is going on and am probably flailing away more than
> | anything else.)
> 
> The command use to check for the DTD is xmlcatalog which is installed by
> libxml2.  You could try reinstalling that as well reinstalling docbook-sk.

Bingo! libxml2 is the culprit.

I'd love to know what happened to it, but it is scrollkeeper configures
fine, now, but I am still afraid something is wrong. I got the following
on the install of scrollkeeper, which bothers me:
/local/sbin:/usr/local/bin:/usr/X11R6/bin:/root/bin:/usr/X11R6/bin" ; \
        /usr/X11R6/bin/scrollkeeper-rebuilddb -q -p /var/db/scrollkeeper
I/O error : Attempt to load network entity http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd
/usr/X11R6/share/gnome/help/gnotime/C/gnotime.xml:344: parser error : Entity 'mdash' not defined
                   &mdash; New Project
                          ^
/usr/X11R6/share/gnome/help/gnotime/C/gnotime.xml:357: parser error : Entity 'mdash' not defined
                    <guimenuitem> &mdash; Reload Configuration File</guimenuitem                                         ^

These continue, mostly for &emdash, but also for &percent, so I suspect
something is still wrong. :-( I think I'm going to punt and do
"portupgrade -Rfx xorg-libraries" on scrollkeeper. Not too long a list
of dependencies. :-(
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634


More information about the freebsd-gnome mailing list