Bug 491827

Summary: When format outgoing message, the pidgin will crash.
Product: Red Hat Enterprise Linux 4 Reporter: Yewei Shao <mshao>
Component: pidginAssignee: Jonathan Blandford <jrb>
Status: CLOSED WONTFIX QA Contact: desktop-bugs <desktop-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 4.7CC: daniel_atallah, ddumas, deryni, eblanton, lschiere+bugs, mark, redhat-bugzilla, stu, yshao
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 16:14:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
The bug information of the pidgin crash.
none
A more detailed traceback none

Description Yewei Shao 2009-03-24 10:42:20 UTC 
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 

How reproducible:everytime


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.

  
Actual results:
The Font can be saved successfully.

Expected results:
The pidgin will crash.

Additional info:
Comment 1 Yewei Shao 2009-03-25 01:25:40 UTC 
Created attachment 336576 [details]
The bug information of the pidgin crash.
Comment 2 David Ye 2009-03-25 02:03:33 UTC 
It can be reproduced in pidgin-2.5.5-1.el4.i386,pidgin-2.5.5-1.el4.x86_64
Comment 3 Warren Togami 2009-03-25 02:11:47 UTC 
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.

http://fedoraproject.org/wiki/StackTraces
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.
Comment 4 Yewei Shao 2009-03-25 05:14:54 UTC 
It will not crash in RHEL5.
Comment 5 Yewei Shao 2009-03-25 06:14:30 UTC 
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.
Comment 6 Yewei Shao 2009-03-25 07:54:51 UTC 
Created attachment 336603 [details]
A more detailed traceback
Comment 7 Warren Togami 2009-03-25 15:51:23 UTC 
Upstream pidgin says: "have the original poster change their Gtk+ theme to the default theme and see if the problem disappears"
Comment 8 Yewei Shao 2009-03-26 04:57:19 UTC 
When change GTK+ theme to the default theme, the bug can still be reproduced.
Comment 9 Jiri Pallich 2012-06-20 16:14:57 UTC 
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.