Bug 455184 - Unable to receive icq messages from slick 0.42 users
Unable to receive icq messages from slick 0.42 users
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: pidgin (Show other bugs)
5.2
i686 Linux
low Severity high
: rc
: ---
Assigned To: Warren Togami
: Desktop
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-13 12:49 EDT by Heiko Adams
Modified: 2014-06-09 07:17 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-06-02 09:04:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
bugzilla: needinfo-


Attachments (Terms of Use)

  None (edit)
Description Heiko Adams 2008-07-13 12:49:28 EDT
Description of problem:
When communicating with slick 0.42 users over icq I don't receive any messages.

Version-Release number of selected component (if applicable):
pidgin.i386.2.3.1-2.el5_2
libpurple.i386.2.3.1-2.el5_2 

How reproducible:
allways

Steps to Reproduce:
1. Start an conversation with an slick 0.42 user
2. receive a message from this user
3.
  
Actual results:
Neither any text nor a blank line are shown

Expected results:
The received text should be shown

Additional info:
Comment 1 Heiko Adams 2008-07-13 15:54:53 EDT
I forgot: When communicating to slick users by using jabber with an icq
transport everything works fine. So it seems to be an problem of pidgin
Comment 2 Warren Togami 2008-11-23 14:16:54 EST
http://people.redhat.com/wtogami/temp/pidgin/
Please test the latest binaries from here and report back.
Comment 3 Heiko Adams 2008-11-23 14:59:07 EST
These binaries killed my pidgin. When launching pidgin on from bash the following error message appears:
> pidgin: symbol lookup error: pidgin: undefined symbol: gst_registry_fork_set_enabled
Comment 4 Warren Togami 2008-11-23 16:34:00 EST
The buildroot turned out to be broken.  Waiting on someone else to fix it so I can rebuild a proper RHEL-5.2 test binary.
Comment 5 Heiko Adams 2008-12-06 16:22:07 EST
After a short test the problem seems to be fixed.
Comment 6 RHEL Product and Program Management 2014-03-07 08:36:17 EST
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Comment 7 RHEL Product and Program Management 2014-06-02 09:04:37 EDT
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).
Comment 8 Heiko Adams 2014-06-09 07:17:05 EDT
This comment is only to clear the needinfo flag.

Note You need to log in before you can comment on or make changes to this bug.