Red Hat Bugzilla – Bug 471857
Pidgin can not be launched in Server5.2
Last modified: 2009-04-03 08:45:41 EDT
Description of problem:
An error "pidgin:undefined symbol:gst_registry_fork_set_enabled" occur when launched pidgin in Server-5.2
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Work in local machine :
1. Created a yum resource
the baseurl= http://10.66.82.101/redhat/rhel/rel-eng/RHEL5.3-Client-20081112.0/tree-i386/Client/
2. update libpurple and then update pidgin.
3. launch pidgin.
Work in remote stable system:
1. tps-cd 2009:8176
2. yum install libpurple
3. tps-upgrade (the version is pidgin-2.5.1-3.el5.i386)
4. vncserver to
5. user tps-downgrade to downgrade pidgin. (the version is pidgin-2.3.1-2.el5_2.i386)
1. An error "pidgin:undefined symbol:gst_registry_fork_set_enabled" occur when launch pidgin.
2. After downgrading pidgin, it can work well.
pidgin-2.5.1-3.el5.i386 can work well in RHEL-Server5.3
The description above is how did I install pidgin-2.5.1-3.el5.
After installing pidgin-2.5.1-3.el5 in RHEL-Server-5.2, issue "pidgin" in terminal, an error "pidgin:undefined symbol:gst_registry_fork_set_enabled" is displayed.
In RHEL-Server-5.3, pidgin-2.5.1-3.el5 can be launched successfully.
That would happen if Pidgin was compiled on a machine with a version of gstreamer that had the gst_registry_fork_set_enabled function, but used on a machine with an older version of gstreamer which does not have that function.
NOTABUG, you cannot use RHEL-5.3 compiled pidgin on RHEL-5.2.
Please test these binaries. Low priority security errata is coming soon, built against RHEL-5.2 so it should work on both RHEL-5.2 and RHEL-5.3. It will supercede the current 5.3 version.
en, after I update gstreamer, pidgin can be launched.
Turns out that build of pidgin was screwed because the RHEL-5.3 gstreamer was in the buildroot. I am rebuilding it against RHEL-5.2. The pidgin security errata coming soon will be RHEL-5.2, and identical without a rebuild in 5.3.