Bug 241541

Summary:	Regression: Linebreaks in sent messages are not displayed
Product:	[Unmaintained] kopete	Reporter:	Malte Eggers <malte.e>
Component:	Chat Window	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	malte.e, meyerm
Priority:	NOR
Version First Reported In:	1.0.0
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	1.0.80
Sentry Crash Report:

Description Malte Eggers 2010-06-12 13:47:13 UTC

Version:           1.00 (using KDE 4.4.3) 
OS:                Linux

One or more consecutive linebreaks are replaced by a singe space, but kopete does send the entered linebreaks. Incoming messages are also formatted correctly. This seems to be a regression that occured after I upgraded from KDE 4.4.2 to 4.4.4 (I can't select 4.4.4 as a kde version, though, so I selected 4.4.3). This is a problem with XMPP and MSN so I don't think this is protocol specific.

Reproducible: Always

Steps to Reproduce:
send a message with a linebreak, for example:
foo
bar

Actual Results:  
kopete displays
foo bar
as outgoing message. The recipient gets:
foo
bar

Expected Results:  
kopete should display
foo
bar
as outgoing message, too.

Comment 1 Malte Eggers 2010-06-17 13:11:37 UTC

for some reason it just worked today for *one* Jabber contact, for all the others it still didn't. I'll try to figure out, why.

Comment 2 meyerm 2010-06-24 12:08:05 UTC

Seems to be related to the cryptography plugin. I'm using OTR and having the same issues (again ;-) ).

See bug #149082

Comment 3 Malte Eggers 2010-06-24 23:56:37 UTC

confirming that. It does not matter whether or not the other side supports OTR and whether or not it is used. Deactivating the OTR plugin (globally, via the modules settings) make everything working normal again.
It works as it should for some contacts, but for most it does not. I don't know yet if the contacts it works with are always the same, but I'll try to find out.

Comment 4 Malte Eggers 2010-09-14 20:27:47 UTC

It seems like the bug is fixed in 4.5.1. I just upgraded and I can't reproduce it anymore.