Bug 812656

Summary:	Kopete fails to send large/long formatted messages to WL/Windows Live/MSN contacts.
Product:	[Fedora] Fedora	Reporter:	naguz
Component:	kdenetwork	Assignee:	Than Ngo <than>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	alekcejk, jreznik, kevin, ltinkl, rdieter, rnovacek, smparrish, than
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-13 23:31:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description naguz 2012-04-15 18:51:04 UTC

When sending long messages to MSN contacts, Kopete is AFAIK supposed to split the message into several messages if it is too long to be sent as a single message, instead message sending fails with the yellow error triangle symbol, after a waiting period.


Version 1.2.1
Using KDE Development Platform 4.8.1 (4.8.1)


How reproducible: 100%


Steps to Reproduce:
1: Open a chat with an msn contact
2. Paste a large chunk of text (477 word of lorem ipsum will certainly do the trick) into Kopete. 
3. Hit enter (or send-button)
  
Actual results:
Kopete will show the "working"-symbol for quite a long time, then it will fail, and show a yellow triangle with an exclamation sign next to the top of the message

Expected results:
1: Kopete should split the message automatically, and the message should be delivered.
2: If it can't deliver the message it should get a readable, understandable error message, instead of the litle exclamation mark which is often out-of-view because the top of the message you attempted to send is often out of the viewable chat area if it is a long message

Additional info: Large messages works great with other protocols, and has also been working with pidgin previously. (But it is a while since I have collaborated with papers over msn.)

Comment 1 Fedora End Of Life 2013-01-16 19:56:22 UTC

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Fedora End Of Life 2013-02-13 23:31:51 UTC

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.