Ubuntu
kdenetwork package

[karmic] Kopete sends extra newlines/breaks in messages.

Bug #54155 reported by fimbulvetr
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KDE Network
Invalid
Medium
kdenetwork (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: kopete

I just moved from dapper to edgy. When messages are received in another client (Gaim), that were sent by kopete 0.12.1 the messages have 1 line break prepended and two line breaks appended to message. This is quite an annoying bug for those receiving my messages. Old kopete (Dapper) did not have this behavior.

------------------------
In Karmic:

Here is an excerpt from XML console with <body> contents slightly modified for readability. Tabs were replaced with "\t" and whitespaces with underlines. The code is 4-space indented (if there's a Markdown support on Launchpad this should appear as a code block, if it is just a plain text, then nope).

    <message type="chat" <email address hidden>" id="42" >
    <body>test._this_message_should_be_a_single_line._\t__\t\t\t\t_\t_\t_\t___\t_\t__\t___\t\t__\t_</body>
    <x xmlns="jabber:x:event">
    <offline/>
    <composing/>
    <delivered/>
    <displayed/>
    </x>
    <active xmlns="http://jabber.org/protocol/chatstates"/>
    </message>

See original description
Revision history for this message
Risto H. Kurppa (risto.kurppa) wrote :

Same here.

And we are not alone:

http://bugs.kde.org/show_bug.cgi?id=92598
http://bugs.kde.org/show_bug.cgi?id=121627

But it seems to be a QT bug and not a kopete bug, so this should fix it sooner or later:
http://www.trolltech.com/developer/task-tracker/index_html?id=118388&method=entry
(I'd guess more likely later.. Maybe KDE 4 has it already..)

r

Revision history for this message
Kieran Hogg (xerosis) wrote :

Looks to be fixed in newer versions. Feel free to re-open if you come across this again.

Changed in kdenetwork:
status: Unconfirmed → Fix Released
Revision history for this message
Alexey Zhukov (drdaeman) wrote :

I have a problem which looks like this (visually this appears as new lines appended after my messages) with Kopete 0.80.2 on Kubuntu Karmic (kdenetwork 4.3.2-0ubuntu4)

When I send one-line messages to XMPP MUC or , I see them back just fine, but others report weird linebreaks on the end of my messages. Did not work for me on Karmic alpha, but I did not bother to report that time (sorry).

This is not exactly newlines, but excessive amount of tabs (\x09) and whitespace (\x20) at the end of every message (in <body> element). While Kopete ignores them, other clients display them. I've tried to search for a bug with something related to whitespace, but this is the only one I found. Sorry if I missed some already open one.

Here is an excerpt from XML console with <body> contents slightly modified for readability. Tabs were replaced with "\t" and whitespaces with underlines. The code is 4-space idented (if there's a Markdown support on Launchpad this should appear as a code block, if it is just a plain text, then nope).

    <message type="chat" <email address hidden>" id="42" >
    <body>test._this_message_should_be_a_single_line._\t__\t\t\t\t_\t_\t_\t___\t_\t__\t___\t\t__\t_</body>
    <x xmlns="jabber:x:event">
    <offline/>
    <composing/>
    <delivered/>
    <displayed/>
    </x>
    <active xmlns="http://jabber.org/protocol/chatstates"/>
    </message>

I didn't found it in RFC, but on jabber.org mailing list I found a claim that whitespace should not be stripped: http://mail.jabber.org/pipermail/standards/2007-July/016134.html

Alexey Zhukov (drdaeman)
Changed in kdenetwork (Ubuntu):
status: Fix Released → New
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

Thank you for updating us about this bug. Marking it Confirmed, Low. Will report this upstream.

summary: - Kopete sends extra newlines/breaks in messages.
+ [karmic] Kopete sends extra newlines/breaks in messages.
description: updated
Changed in kdenetwork (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

This bug has been reported to the developers of the software. You can track it and make comments at: http://bugs.kde.org/show_bug.cgi?id=216800

Revision history for this message
In , xteejx (xteejx-deactivatedaccount) wrote :

Version: 4.3.2-0ubuntu4 (using KDE 4.3.2)
OS: Linux
Installed from: Ubuntu Packages

This bug was reported at Launchpad and is being tracked at https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/54155

------------------
Original report:

I just moved from dapper to edgy. When messages are received in another client (Gaim), that were sent by kopete 0.12.1 the messages have 1 line break prepended and two line breaks appended to message. This is quite an annoying bug for those receiving my messages. Old kopete (Dapper) did not have this behavior.

------------------------
Updated report in Karmic 9.10:

Here is an excerpt from XML console with <body> contents slightly modified for readability. Tabs were replaced with "\t" and whitespaces with underlines. The code is 4-space indented (if there's a Markdown support on Launchpad this should appear as a code block, if it is just a plain text, then nope).

    <message type="chat" <email address hidden>" id="42" >
    <body>test._this_message_should_be_a_single_line._\t__\t\t\t\t_\t_\t_\t___\t_\t__\t___\t\t__\t_</body>
    <x xmlns="jabber:x:event">
    <offline/>
    <composing/>
    <delivered/>
    <displayed/>
    </x>
    <active xmlns="http://jabber.org/protocol/chatstates"/>
    </message>

Revision history for this message
Harald Sitter (apachelogger) wrote :

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. But don't worry! This issue is being tracked by the KDE developers. Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix is in in reaches Kubuntu.

Thanks!

Changed in kdenetwork (Ubuntu):
status: Confirmed → Invalid
Bug Watch Updater (bug-watch-updater)
Changed in kdenetwork:
status: Unknown → New
Bug Watch Updater (bug-watch-updater)
Changed in kdenetwork:
importance: Unknown → Medium
Revision history for this message
In , Andrew-crouthamel (andrew-crouthamel) wrote :

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Bug Watch Updater (bug-watch-updater)
Changed in kdenetwork:
status: New → Incomplete
Revision history for this message
In , Andrew-crouthamel (andrew-crouthamel) wrote :

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!

Bug Watch Updater (bug-watch-updater)
Changed in kdenetwork:
status: Incomplete → New
Revision history for this message
In , Justin Zobel (justin-zobel) wrote :

Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version?

If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!

Bug Watch Updater (bug-watch-updater)
Changed in kdenetwork:
status: New → Incomplete
Revision history for this message
In , Bug-janitor (bug-janitor) wrote :

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Revision history for this message
In , Bug-janitor (bug-janitor) wrote :

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

Bug Watch Updater (bug-watch-updater)
Changed in kdenetwork:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.