Bug 186967 - first message in conversation fails to show in chat window
Summary: first message in conversation fails to show in chat window
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-12 15:18 UTC by Monty Scroggins
Modified: 2009-03-30 04:59 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Monty Scroggins 2009-03-12 15:18:39 UTC 
Version:           0.70.0 (using 4.2.1 (KDE 4.2.1) "release 103", KDE:KDE4:Factory:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (i686) release 2.6.27.19-3.2-pae

When I initiate a chat session, I double-click the person in the list, and the chat window appears.   I can type a message and hit send.. The icon will animate as if a message has been sent, but it never shows up in the chat window..  it wont show up until the remote person responds..  The chat window might have to be closed and re-initiated.
Comment 1 Matt Rogers 2009-03-29 20:23:06 UTC 
which protocol? i can't reproduce this with the kopete testing protocol, so this leads me to believe it's protocol specific.
Comment 2 Monty Scroggins 2009-03-30 04:57:05 UTC 
I currently login to AIM MSN and Yahoo at the same time.. I was seeing the error in the MSN and Yahoo protocols..   I hadnt attempted to send a message through AIM..  I also verified the error occured no matter which theme was loaded...   The problem seems to have gone away.. There have been multiple updates to my system since I submitted this bug..  Something along the way must have resolved the issue.. 

Monty
Comment 3 Matt Rogers 2009-03-30 04:59:59 UTC 
Since you currently can't reproduce it, let's mark this as resolved for now. If the issue pops up again, we can reopen the bug.