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 327663 - FC4 segfault: undefined symbol: g_date_get_type
FC4 segfault: undefined symbol: g_date_get_type
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.2
Other Linux
: Normal critical
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-19 04:43 UTC by Penguins Rock
Modified: 2006-01-23 08:04 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Penguins Rock 2006-01-19 04:43:54 UTC
This bug didn't exist in 0.10.0 but after upgrading to 0.10.2 I get the following error when I try to run gst-inpect:

$ gst-inspect-0.10
gst-inspect-0.10: symbol lookup error: /usr/lib/libgstreamer-0.10.so.0: undefined symbol: g_date_get_type

or if I try to play a file that was working with the earlier 0.10.0 version I get the following:
$ gst-launch-0.10 playbin uri=file:///testfiles/movs/test.avi
Segmentation fault

I think this regression might have been introduced in 0.10.1 but I'm not 100% sure. In any case here is what I currently have installed and can reproduce this error with:
# rpm -qa | grep gst
gstreamer010-0.10.2-0.gst.1.4
gstreamer010-ffmpeg-0.10.0-0.gst.1.4
gstreamer010-plugins-good-0.10.0.2-0.gst.1.4
gstreamer-plugins-0.8.8-9
gstreamer-tools-0.10.2-0.gst.1.4
gstreamer010-plugins-base-0.10.2-0.gst.1.4
cairo-1.0.2-2.gst.1.4
gstreamer-0.8.10-1
gstreamer010-plugins-ugly-0.10.0.2-0.gst.1.4
gstreamer010-python-0.10.2-0.gst.1.4

And in case anyone is interested, I'm running the latest stable glib2 availble for FC4 namely:
$ rpm -qa | grep glib
dbus-glib-0.33-3.fc4.1
glib2-2.6.6-1
glibc-2.3.5-10.3
glibc-common-2.3.5-10.3
glib-1.2.10-16

Did g_date_get_type get introduced in glib2-2.8.0 by any chance. It seems strange others haven't reported this bug before me since it seems to be a complete show stopper. Feedback welcome. Thanks!
Comment 1 Thomas Vander Stichele 2006-01-23 08:04:29 UTC
you hava a bunch of rpms from our repository (the gst010) one, but you didn't install glib2 from the repository.

Did you manually copy and rpm -Uhv them ? You should be using yum or apt-get to get these packages so you get all updates.

Update your glib and this will be fixed.