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 331505 - Can't start epiphany, g_object_compat_control error
Can't start epiphany, g_object_compat_control error
Status: RESOLVED DUPLICATE of bug 330337
Product: GARNOME
Classification: Deprecated
Component: general
2.12.x
Other Linux
: Normal major
: ---
Assigned To: GARNOME Maintainers
garnome list
Depends on:
Blocks:
 
 
Reported: 2006-02-17 05:24 UTC by Slobodan D. Sredojevic
Modified: 2006-02-19 01:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Slobodan D. Sredojevic 2006-02-17 05:24:53 UTC 
I am using Garnome 2.13.91 (GNOME 2.14 beta2). If I open gnome-terminal and start epiphany from it, I get this error:

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

This error happens with epiphany shiped with GNOME beta1 too.
Comment 1 Crispin Flowerday (not receiving bugmail) 2006-02-17 09:41:46 UTC 
What gtk version do you have installed in /opt/gnome-2.14, and what platform are you running on ? (i.e. linux/freebsd, 32bit/64bit?)
Comment 2 Slobodan D. Sredojevic 2006-02-17 15:07:50 UTC 
GNU/Linux, Slackware 10.1. It is gtk+ shiped with GNOME 2.14 beta2 - that is gtk+-2.8.12, glib is 2.9.6. This is a 32-bit machine. This error was present in gtk+-2.8.10/glib from beta1 too, at least for me. 

I can login into GARNOME, I am using standard garnome-session script, almost all GNOME-2.14beta2 software works except epiphany and evince (same error, I have filled the bug too). I see only two unusual things with this install:

- huge performance regressions starting from gdm spreading all over the desktop, mostly startup times

- somehow I triggered problem/bug explained in the link following that is an very old problem some users have from time to time and I workaround it by starting:

exec $GARNOME/libexec/gnome-settings-daemon &
before 
exec $GARNOME/bin/gnome-session

http://gnomesupport.org/forums/viewtopic.php?t=454
Comment 3 Christian Persch 2006-02-18 18:50:33 UTC 
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.
Comment 4 Karsten Bräckelmann 2006-02-18 22:38:59 UTC 
I guess, one bug would have been sufficient...

*** This bug has been marked as a duplicate of 330337 ***
Comment 5 Slobodan D. Sredojevic 2006-02-19 01:07:12 UTC 
Karsten: Note that first bug report was assigned to garnome module, I was left ten days without developer input on that bug before opening the same one for epiphany/evince module. Sorry for the bugzilla mess and additional work you had to do (how can I help you?) but also understand that just a month before release every bug report is important and at the end can reveal serious problem. I see GNOME through Garnome, many do and would like that this distro is fully ready when 2.14 is out.