After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 330337 - Symbol lookup error when starting evince and epiphany
Symbol lookup error when starting evince and epiphany
Status: RESOLVED NOTABUG
Product: GARNOME
Classification: Deprecated
Component: general
2.13.x
Other All
: Normal normal
: ---
Assigned To: GARNOME Maintainers
garnome list
: 331505 331506 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-02-08 02:10 UTC by Slobodan D. Sredojevic
Modified: 2006-03-16 02:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Slobodan D. Sredojevic 2006-02-08 02:10:18 UTC
Please describe the problem:
Epiphany and evince modules built fine with garnome 2.13.90 but when I start it
I get these same errors:

bash-3.00$ epiphany
epiphany: symbol lookup error: /opt/gnome-2.14/lib/libgtk-x11-2.0.so.0:
undefined symbol: g_object_compat_control
bash-3.00$ evince
evince: symbol lookup error: /opt/gnome-2.14/lib/libgtk-x11-2.0.so.0: undefined
symbol: g_object_compat_control

We have some bugs (maybe related) on this here:
http://bugzilla.gnome.org/show_bug.cgi?id=327419
http://bugzilla.gnome.org/show_bug.cgi?id=330319



Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Karsten Bräckelmann 2006-02-18 17:25:57 UTC
*** Bug 331506 has been marked as a duplicate of this bug. ***
Comment 2 Karsten Bräckelmann 2006-02-18 22:38:59 UTC
*** Bug 331505 has been marked as a duplicate of this bug. ***
Comment 3 Karsten Bräckelmann 2006-02-18 22:47:02 UTC
quoting 331505 comment 3:
> Yes, this is the libtool bug; the garnome FAQ 3.7 says to file a bug if that
> still happens, so I'm reassigning the bug.

quoting GARNOME FAQ 3.7: [1]
> A workaround for this issue has been included with 2.12.0, however -- if you
> find that the problem still comes up, please report it as a bug to the
> maintainers of your distribution.

Have you done so?


[1] http://gnome.org/projects/garnome/faq.html
Comment 4 Bob Kashani 2006-02-18 23:03:28 UTC
You built gtk against the wrong version of glib. Try rebuilding gtk against the version in garnome.

What distro are you using?
Comment 5 Slobodan D. Sredojevic 2006-02-19 01:41:02 UTC
Karsten: No. I have not reported it upstream. Actually Slackware 10.1 is nowadays pretty obsolete with its software choice, I even didn't want to upgrade it because I thought - that is why, mostly, bootstrap directory exists (libtool is there), so to answer Bob's question too, these are my steps to install Garnome:

cd bootstrap; make install
cd platform; make install
cd desktop; make install

and also steps how I run into the reported bug/problem. If this is wrong, please tell me. Is it normall/possible that some modules link agains libraries that are outside of garnome/bootstrap chroot? Can I use ldd to find it?

I can wipe my /opt/gnome-2.14 and start from scrath and will report results here, day after tomorrow as this is an old/slow compaq armada x86 machine.
Comment 6 Bob Kashani 2006-02-21 19:22:45 UTC
My guess is that something in bootstrap might be causing this. Try building from scratch but do not build anything from bootstrap. You should never build everything in bootstrap, read the README for an explanation as to why.