Description of problem: when starting, pidgin never show up on the screen and is unusable, only a "kill -9" will end the pidgin process. Version-Release number of selected component (if applicable): Pidgin 2.6.6-2.fc12 (libpurple 2.6.6) rpm -qa for pidgin: pidgin-2.6.6-2.fc12.x86_64 rpm -qa for libpurple: libpurple-2.6.6-2.fc12.x86_64 rpm -qa for gst*: gstreamer-tools-0.10.28-1.fc12.x86_64 gstreamer-ffmpeg-0.10.9-1.fc12.x86_64 gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64 gstreamer-plugins-ugly-0.10.13-1.fc12.x86_64 gstreamer-0.10.28-1.fc12.x86_64 gstreamer-plugins-bad-nonfree-0.10.17-2.fc12.x86_64 gstreamer-plugins-base-0.10.28-1.fc12.x86_64 gstreamer-python-0.10.16-1.fc12.x86_64 gstreamer-plugins-bad-free-extras-0.10.18-1.fc12.x86_64 PackageKit-gstreamer-plugin-0.5.7-1.fc12.x86_64 gstreamer-plugins-good-0.10.21-1.fc12.x86_64 How reproducible: Always Steps to Reproduce: 1. install pidgin 2. run pidgin 3. it will never appear anywhere on your screen Actual results: $ pidgin Warning: Unable to create "trees" RDF storage. Performance can be improved by upgrading librdf. ERROR: Caught a segmentation fault while loading plugin file: /usr/lib64/gstreamer-0.10/libgstlv2.so Please either: - remove it and restart. - run with --gst-disable-segtrap and debug. Expected results: Pidgin should start without complaint. Additional info: removing (or mv-ing) the gstreamer file will kind of "solve" the problem because pidgin will be able to start without any warning nor error. # mv /usr/lib64/gstreamer-0.10/libgstlv2.so /usr/lib64/gstreamer-0.10/libgstlv2.so.back
This has been fixed for a while, I believe with gstreamer-0.10.28-2.