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 628172 - Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported
Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the sam...
Status: RESOLVED DUPLICATE of bug 627916
Product: empathy
Classification: Core
Component: General
2.31.x
Other Linux
: Normal critical
: ---
Assigned To: empathy-maint
empathy-maint
Depends on:
Blocks:
 
 
Reported: 2010-08-28 01:39 UTC by Cleiton Lima
Modified: 2010-08-28 07:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Cleiton Lima 2010-08-28 01:39:16 UTC


Thread 1 (Thread 0xb7fd2880 (LWP 1987))

  • #0 g_logv
    at gmessages.c line 554
  • #1 g_log
    at gmessages.c line 568
  • #2 ??
    from /usr/lib/libgtk-x11-3.0.so.0

I'm using Fedora 14 Alpha.
Comment 1 Cleiton Lima 2010-08-28 01:40:31 UTC


Thread 1 (Thread 0xb7fd2880 (LWP 1987))

  • #0 g_logv
    at gmessages.c line 554
  • #1 g_log
    at gmessages.c line 568
  • #2 ??
    from /usr/lib/libgtk-x11-3.0.so.0

Comment 2 Felipe Besoaín Pino 2010-08-28 02:07:11 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.
Comment 3 Frederic Peters 2010-08-28 07:20:10 UTC
Thanks Felipe for triaging, this is actually known, and reported as bug 627916.

Cleiton, thanks for your report, this is because Empathy introduced libgcr as a dependency, which doesn't exist (yet) for GTK+ 3, and the bug is that configure gets completed nevertheless...

For the time being, you'd be better building Empathy against GTK+.

*** This bug has been marked as a duplicate of bug 627916 ***