Bug 507986 - pidgin chat box doesn't always update with new text
pidgin chat box doesn't always update with new text
Product: Fedora
Classification: Fedora
Component: pidgin (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Warren Togami
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-06-24 21:02 EDT by Ian Laurie
Modified: 2010-06-28 09:17 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 09:17:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ian Laurie 2009-06-24 21:02:42 EDT
Description of problem:
pidgin chat box doesn't always update with new text

Version-Release number of selected component (if applicable):
many versions up to and including pidgin-2.5.6-1.fc10.i386 (Fedora 10)
many versions up to and including pidgin-2.5.7 (Windows XP)

How reproducible:
random but very often, certainly multiple times per EVERY chat session

Steps to Reproduce:
1. Open a chat with someone
2. now and then, text fails to appear in the upper chat box
Actual results:
Often pidgin does not update the chat box with new text. The user is forced to click the chat box to give it focus, and re-click the text entry box.  This forces the text to appear.  Seems to be only the outgoing text that fails to show up in the upper chat box. This problem exists for me on multiple platforms (Windows and Linux) and goes back many versions.

Expected results:
Text should always appear in the upper box without having to toggle its focus.

Additional info:
This problems exists on both the current Windows and Linux versions of pidgin, and has existed in many recent versions.
Comment 1 Ian Laurie 2009-06-25 20:19:17 EDT
I can confirm the problem is in pidgin-2.5.7-1.fc10 for fedora 10 also.  Presumably fedora 11 would also suffer from this bug.
Comment 2 Ian Laurie 2009-07-13 21:19:34 EDT
Same thing in latest release on fedora 11 ---> pidgin-2.5.8-1.fc11.i586
Comment 3 Warren Togami 2009-11-09 15:16:08 EST
What window manager or desktop environment are you using?
Comment 4 Ian Laurie 2009-11-25 23:19:22 EST
Default GNOME on Linux.
Comment 5 Bug Zapper 2010-04-27 11:14:38 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 6 Bug Zapper 2010-06-28 09:17:14 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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