Red Hat Bugzilla – Bug 491827
When format outgoing message, the pidgin will crash.
Last modified: 2013-04-02 00:22:41 EDT
Description of problem:
When format outgoing message in "Tool->Preference", the pidgin will crash.
Version-Release number of selected component (if applicable):
Test run for RHEL 4AS - pidgin-2.5.5-1.el4
Steps to Reproduce:
1. Launch Pidgin and log in an account.
2. Click 'Tools > Preferences ' to bring up Preferences window.
3. Select 'Conversations' tab.
4. Click 'Conversation font" in "Font"
5. In pop out window, click something in it.
The Font can be saved successfully.
The pidgin will crash.
Created attachment 336576 [details]
The bug information of the pidgin crash.
It can be reproduced in pidgin-2.5.5-1.el4.i386,pidgin-2.5.5-1.el4.x86_64
Looking at your traceback I am guessing this is a bug in GNOME's font rendering stack and not pidgin, but we need a complete traceback to know for sure.
Could you please get a traceback after installing all debuginfo packages for the application and libraries that it uses? Also please hit ENTER and not quit before the entire stack trace is done.
These instructions are for doing it on Fedora. debuginfo-install might not exist on RHEL4, so you may need to find and install the matching debuginfo packages manually.
Does this crash in the same place on the RHEL5 version?
It seems to not crash in Fedora 11.
It will not crash in RHEL5.
From the debug info I gave before, the reason seems belong to the libXft.so.2, and when I use "rpm -qf", I have found that the corresponding debuginfo package is xorg-x11. I searched this debuginfo package but can not search anything.
Created attachment 336603 [details]
A more detailed traceback
Upstream pidgin says: "have the original poster change their Gtk+ theme to the default theme and see if the problem disappears"
When change GTK+ theme to the default theme, the bug can still be reproduced.
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life.
Please See https://access.redhat.com/support/policy/updates/errata/
If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.