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...
On the same computer, with the same account, it work with Psi.
Same problem with KDE 4.1 beta2 on ubuntu.
Problem still exists on KDE 4.1 RC 1
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> "
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.
It works perfectly with my "@im.apinc.org" account. The problem is specific to gmail accounts.
I just noticed this problem on kubuntu intrepid
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>
the same problem in 0.70.0 kopete from kde3 works fine however. this bug has been fixed perviously see bug 132611
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.
*** This bug has been confirmed by popular vote. ***
I can confirm this bug in Kopete Version 0.70.2 using KDE 4.2.3 (Arch Linux).
Created attachment 34149 [details] Makes Kopete-0.70.2 speak in Jabber MUC
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.
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?
> 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
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.
Well, it has already been applied =) If you can test kopete SVN or kopete from KDE 4.3 beta 1, that would be great.
Should be fixed in KDE 4.3.