You had me worried with this bug problem, but I think the problem
is not there:

ldd /usr/bin/gnome_segv:

libdb.so.2 => /usr/lib/libdb.so.2 (0x4012b000)

ls -l  /usr/lib/libdb.so.2
/usr/lib/libdb.so.2 -> libdb1.so.2

Please reopen the bug if I am wrong.

We can't change what gnome-libs uses, because users have
~/.gnome/metadata.db in their home directory, and event
if we write a migration tool, we'd then be broken for
mixed 6.2, 7.0 installations at a single site.

Our decision on this, as I recall is to stick with db1
format until gnome2, which will be getting rid of 
metadata.db anyways.

I think I got misunderstood --

what I wanted to propose was that  the build of gnome-libs gets
changed in a way that programs compiled with some `gnome-config
--libs gnomeui` are linked in the same way as the packaged programs
(it looks like a discrepancy between the build system -- which links
against libdb -- and /usr/lib/gnomeConf.sh from gnome-libs-devel
which causes subsequent compilations to link against libdb1.

If anything is still unclear (or I'm just talking rubbish), please contact me.

Nils

I still don't understand. gnome-config includes -ldb1.
The soname for -ldb1 is libdb.so.2.  This is the library that
the packaged programs are linked against. Thus, I assume they
were built against -ldb1...

I just checked it on a beta5 system and there
-ldb1 resolves to libdb.so.2 (as you said).

The problem occurred on an older beta, it
was probably triggered by something else --
I could think of a libdb1.so pointing to a
libdb1.so.xxx instead of libdb.so.2 -- which
obviously has been fixed in the meantime.

We found this as we packaged something
using the GNOME libs and it definitely
needed a libdb1.so to be installed instead
the GNOME stuff shipped with the beta
which needed libdb.so.

Thanks anyway!

Nils