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 543234 - vmware crashes while loading libgio-2.0.so.0
vmware crashes while loading libgio-2.0.so.0
Status: RESOLVED NOTABUG
Product: GARNOME
Classification: Deprecated
Component: general
2.23.x
Other Linux
: Normal normal
: ---
Assigned To: GARNOME Maintainers
garnome list
Depends on:
Blocks:
 
 
Reported: 2008-07-16 07:34 UTC by Dieter Kadelka
Modified: 2008-07-22 13:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
simple script to break out of the GARNOME env (400 bytes, text/plain)
2008-07-22 13:05 UTC, Karsten Bräckelmann
Details

Description Dieter Kadelka 2008-07-16 07:34:00 UTC
/usr/lib/vmware/bin/vmware: error while loading shared libraries: /home/ad08/garnome/lib/libgio-2.0.so.0: undefined symbol: g_thread_gettime

Here are my files with g_thread_gettime:

bindings/glibmm/work/main.d/glibmm-2.17.0/glib/src/glib_functions.defs
desktop/nautilus/work/main.d/nautilus-2.23.4/libnautilus-private/nautilus-icon-i
nfo.c
desktop/nautilus/work/main.d/nautilus-2.23.4/libnautilus-private/nautilus-file-o
perations.c
platform/glib/work/main.d/glib-2.17.2/gio/.libs/libgio-2.0.so.0
platform/glib/work/main.d/glib-2.17.2/gio/.libs/libgio-2.0.a
platform/glib/work/main.d/glib-2.17.2/gio/.libs/libgio-2.0.so.0.1702.0T
platform/glib/work/main.d/glib-2.17.2/gio/.libs/libgio-2.0.so
platform/glib/work/main.d/glib-2.17.2/gio/.libs/gfilemonitor.o
platform/glib/work/main.d/glib-2.17.2/gio/.libs/libgio-2.0.so.0.1702.0
platform/glib/work/main.d/glib-2.17.2/gio/gfilemonitor.c
platform/glib/work/main.d/glib-2.17.2/gio/gfilemonitor.o
platform/glib/work/main.d/glib-2.17.2/glib/.libs/libglib-2.0.so.0.1702.0
platform/glib/work/main.d/glib-2.17.2/glib/.libs/libglib-2.0.so.0
platform/glib/work/main.d/glib-2.17.2/glib/.libs/libglib-2.0.exp
platform/glib/work/main.d/glib-2.17.2/glib/.libs/libglib-2.0.ver
platform/glib/work/main.d/glib-2.17.2/glib/.libs/libglib-2.0.so
platform/glib/work/main.d/glib-2.17.2/glib/.libs/gtimer.o
platform/glib/work/main.d/glib-2.17.2/glib/.libs/libglib-2.0.a
platform/glib/work/main.d/glib-2.17.2/glib/.libs/gthread.o
platform/glib/work/main.d/glib-2.17.2/glib/glib.symbols
platform/glib/work/main.d/glib-2.17.2/glib/gtimer.c
platform/glib/work/main.d/glib-2.17.2/glib/gtimer.o
platform/glib/work/main.d/glib-2.17.2/glib/gthread.c
platform/glib/work/main.d/glib-2.17.2/glib/gthread.h
platform/glib/work/main.d/glib-2.17.2/glib/gthread.o
platform/glib/work/main.d/glib-2.17.2/gthread/.libs/libgthread-2.0.so.0.1702.0
platform/glib/work/main.d/glib-2.17.2/gthread/.libs/libgthread-2.0.a
platform/glib/work/main.d/glib-2.17.2/gthread/.libs/gthread-impl.o
platform/glib/work/main.d/glib-2.17.2/gthread/.libs/libgthread-2.0.so
platform/glib/work/main.d/glib-2.17.2/gthread/.libs/libgthread-2.0.so.0
platform/glib/work/main.d/glib-2.17.2/gthread/.libs/libgthread-2.0.so.0.1702.0T
platform/glib/work/main.d/glib-2.17.2/gthread/gthread-win32.c
platform/glib/work/main.d/glib-2.17.2/gthread/gthread-impl.c
platform/glib/work/main.d/glib-2.17.2/gthread/gthread-impl.o
platform/glib/work/main.d/glib-2.17.2/gthread/gthread-posix.c
platform/glib/work/main.d/glib-2.17.2/gthread/gthread-none.c

g_thread_gettime is defined in gthread-impl.c as:

***
  if (g_thread_gettime_impl)
    g_thread_gettime = g_thread_gettime_impl;

and g_thread_gettime_impl seems to be not defined
Comment 1 Karsten Bräckelmann 2008-07-22 12:57:51 UTC
(In reply to comment #0)
> /usr/lib/vmware/bin/vmware: error while loading shared libraries:
> /home/ad08/garnome/lib/libgio-2.0.so.0: undefined symbol: g_thread_gettime

Your vmware expects a different glib, and doesn't work with the latest version (built by GARNOME). It should work if you unset $LD_LIBRARY_PATH first, when calling vmware (or any other legacy app from your system env):

$ unset LD_LIBRARY_PATH
$ vmware

Exactly for that reason (well, actually the major memory allocation changes back a few versions) I once hacked up a script to break out the GARNOME env when calling system apps. I'll attach that script in a minute, for convenience.


Closing RESOLVED.

Dieter, if the above does not solve your issue, please feel free to re-open this bug report, adding any additional information that might help. Also, thanks for taking the time to report the issue.
Comment 2 Karsten Bräckelmann 2008-07-22 13:05:28 UTC
Created attachment 115002 [details]
simple script to break out of the GARNOME env

Running the script with no arguments will drop you into bash with the most important stuff reset (as set by the GARNOME session script). If any argument is given, that command is run instead.

NOTE  The ${GNOME_PREFIX} in the script is a custom hack in my session. It
      actually is identical to $GARNOME as per the docs session.

Also, the $@ probably should be re-written to "$@" to correctly pass along args containing spaces. *sigh*