Bug 144750 - Unable to speak on MUC from a gmail acount
Summary: Unable to speak on MUC from a gmail acount
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Applications
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-27 16:15 UTC by Jeanuel
Modified: 2010-01-17 15:39 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Makes Kopete-0.70.2 speak in Jabber MUC (2.57 KB, patch)
2009-05-31 17:58 UTC, Oleksiy Kramarenko
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeanuel 2007-04-27 16:15:10 UTC
Version:           0.12.2 (using KDE KDE 3.5.4)
Installed from:    Mandriva RPMs
OS:                Linux

If you are connected to a MUC with a gmail account (like exemple@gmail.com) and try to send messages, you obtain the following message (I'm French) :

Impossible d'envoyer votre message : « test ». Motif : « If set, the 'from' attribute must be set to the user's full JID. »

witch mean :

Unable to send your message : "test". Reason : "If...
Comment 1 Jeanuel 2007-04-27 16:16:10 UTC
On the same computer, with the same account, it work with Psi.
Comment 2 Stefan Sarzio 2008-06-25 15:56:20 UTC
Same problem with KDE 4.1 beta2 on ubuntu.

Comment 3 Stefan Sarzio 2008-07-18 11:44:48 UTC
Problem still exists on KDE 4.1 RC 1
Comment 4 Michael 2008-07-20 03:48:20 UTC
Hi, i am running kopete svn trunk r835161 here, and i can second that bug. i compiled kopete with debug flag and thats what i am getting in the console.

room is "brot@conference.jabber.org", and nick is "schnitzelkuchen".

kopete(31295)/kopete (jabber - raw protocol) JabberAccount::slotClientDebugMessage: "XML OUT: <message from="brot@conference.jabber.org/schnitzelkuchen" type="groupchat" to="brot@conference.jabber.org" id="aac5a" >
<body>err</body>
</message>
"
kopete(31295)/kopete (jabber) JabberByteStream::slotReadyRead: called:  available:  389
kopete(31295)/kopete (jabber - raw protocol) JabberAccount::slotClientDebugMessage: "XML IN: <message from="brot@conference.jabber.org" type="error" to="brot@conference.jabber.org/schnitzelkuchen" id="aac5a" >
<body>err</body>
<error type="modify" code="400" >
<bad-request xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
<text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">If set, the 'from' attribute must be set to the user's full JID.</text>
</error>
</message>
"
Comment 5 Giulio Guzzinati 2008-09-11 19:59:18 UTC
I can confirm this on openSUSE 11.0 with kde 4.1.1.

Does this happen only with gmail accounts?

I will try to see if it happens also with other jabber/XMPP accounts.
Comment 6 Jeanuel 2008-09-11 21:10:05 UTC
It works perfectly with my "@im.apinc.org" account. The problem is specific to gmail accounts.
Comment 7 mchugh19@yahoo.com 2008-11-19 20:21:25 UTC
I just noticed this problem on kubuntu intrepid
Comment 8 Christian Dröge 2009-01-28 14:53:45 UTC
This problem is not specific to gmail. With the new ejabberd 2.0.3 release Kopete users cannot join any MUC, because Kopete sets a wrong 'from' attribute in the message stanzas addressed to MUCs and with ejabberd 2.0.3 the value in this attribute is checked.

This seems to be are XMPP-compliance bug in Kopete. Kopete will have problems with other servers that will check the 'from' attribute as required by the XMPP RFC. For more information on this issue you can read https://support.process-one.net/browse/EJAB-857


Debug output of kopete 0.60.3 on an ejabberd 2.0.3 server:

<message from="test@conference.build.draugr.de/christian" type="groupchat" to="test@conference.build.draugr.de" id="aab9a" >
<body>sd</body>
</message>

<stream:error>
<invalid-from xmlns="urn:ietf:params:xml:ns:xmpp-streams"/>
</stream:error>
Comment 9 Andrey Kartashov 2009-02-21 21:19:33 UTC
the same problem in 0.70.0

kopete from kde3 works fine however.

this bug has been fixed perviously see bug 132611
Comment 10 Ryan Martin 2009-03-13 16:01:11 UTC
I can confirm this bug in Kopete Version 0.60.4 using KDE 4.1.4 (KDE 4.1.4) on Kubuntu Intrepid. 

Attempting to send to a MUC on conference.jabber.org while logged in using a gmail account produced the message:

Your message could not be delivered: "test", Reason: "If set, the 'from' attribute must be set to the user's full JID."

When logged in to the same chatroom from a jabber.org account, no problems were encountered.
Comment 11 Ryan Martin 2009-03-13 16:03:40 UTC
*** This bug has been confirmed by popular vote. ***
Comment 12 stanislav 2009-05-19 15:22:16 UTC
I can confirm this bug in Kopete Version 0.70.2 using KDE 4.2.3 (Arch Linux).
Comment 13 Oleksiy Kramarenko 2009-05-31 17:58:17 UTC
Created attachment 34149 [details]
Makes Kopete-0.70.2 speak in Jabber MUC
Comment 14 Oleksiy Kramarenko 2009-05-31 18:00:34 UTC
Yes, bug still exists (Kopete 0.70.2 built from sources, archive kdenetwork-4.2.3).
Funny but similar much older bug was fixed a long time ago:
http://bugs.kde.org/show_bug.cgi?id=132611

I applied same changes to the same files and got expected result.
Final patch for KDE-4.2.3 is in attached patch, posted in comment #13.
Comment 15 Oleksiy Kramarenko 2009-06-04 16:38:53 UTC
KDE 4.2.4 built from sources, Kopete 0.70.4.
Bug is alive. It can be fixed with the same patch (comment #13).
Do developers read this bugtrack?
Comment 16 Andrey Kartashov 2009-06-05 02:14:00 UTC
> Do developers read this bugtrack?

Apparently, no :)

I was pointing to bug 132611 >3 months ago: https://bugs.kde.org/show_bug.cgi?id=144750#c9

Please try to contact one of the authors directly: http://kopete.kde.org/team.php
Comment 17 Detlev Casanova 2009-06-05 11:09:12 UTC
Apparently, the patch was only applied to a branch, which made kopete loose it in kde4.

The patch seems OK to me, I can apply it so it makes it for kde 4.3.
Comment 18 Detlev Casanova 2009-06-05 11:15:09 UTC
Well, it has already been applied =)
If you can test kopete SVN or kopete from KDE 4.3 beta 1, that would be great.
Comment 19 Roman Jarosz 2010-01-17 15:39:44 UTC
Should be fixed in KDE 4.3.