Bug 92391 - No notification when joining Jabber groupchat fails
Summary: No notification when joining Jabber groupchat fails
Status: REOPENED
Alias: None
Product: kopete
Classification: Applications
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR minor
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 105753 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-10-30 17:33 UTC by Kenny Johansson
Modified: 2021-03-09 22:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kenny Johansson 2004-10-30 17:33:03 UTC
Version:            (using KDE KDE 3.3.1)
Installed from:    Slackware Packages
OS:                Linux

When joining a Jabber groupchat fails, there's no notification, just a scary silence..
Comment 1 Richard Smith 2004-11-09 03:25:45 UTC
Confirmed in CVS.
Comment 2 Till Gerken 2005-05-16 18:10:13 UTC
*** Bug 105753 has been marked as a duplicate of this bug. ***
Comment 3 Till Gerken 2005-05-29 14:58:50 UTC
SVN commit 419437 by gerken:

Display group chat error messages.
BUG: 92391


 M  +9 -3      jabberaccount.cpp  


--- trunk/KDE/kdenetwork/kopete/protocols/jabber/jabberaccount.cpp #419436:419437
@@ -1423,10 +1423,16 @@
 
 }
 
-void JabberAccount::slotGroupChatError (const XMPP::Jid & /*jid*/, int /*error*/, const QString & /*reason*/)
+void JabberAccount::slotGroupChatError (const XMPP::Jid &jid, int error, const QString &reason)
 {
-	/* FIXME: Present this to the user, damnit! */
-// 	kdDebug (JABBER_DEBUG_GLOBAL) << "[JabberAccount] Group chat error - room " << jid.userHost () << " had error " << error << " (" << reason << ")!" << endl;
+	kdDebug (JABBER_DEBUG_GLOBAL) << k_funcinfo << "Group chat error - room " << jid.full () << " had error " << error << " (" << reason << ")" << endl;
+
+	QString detailedReason = reason.isEmpty () ? i18n ( "No reason given by the server" ) : reason;
+
+	KMessageBox::queuedMessageBox ( Kopete::UI::Global::mainWidget (),
+									KMessageBox::Error,
+									i18n ("There was an error processing your request for group chat %1. (Reason: %2, Code %3)").arg ( jid.full (), detailedReason, QString::number ( error ) ),
+									i18n ("Jabber Group Chat") );
 }
 
 void JabberAccount::slotResourceAvailable (const XMPP::Jid & jid, const XMPP::Resource & resource)
Comment 4 S. Burmeister 2006-08-13 21:35:57 UTC
In 0.12.1 there is no notification if I try to enter a group-chat. Since there is no new window either I think that the attempt failed and a notification should be shown.
Comment 5 S. Burmeister 2006-08-13 21:58:06 UTC
To be more precise: If I do not enter a server, there is an error-message. However, if I enter room: conference, server: kdetalk.net nickname: xyz, there is no error-message.

If one clicks on join groupchat, one aparently already gets an error.

kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML OUT: <iq type="get" to="kdetalk.net" id="ae79a" >
<query xmlns="jabber:iq:agents"/>
</iq>
kopete (jabber - raw protocol):
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML IN: <iq from="kdetalk.net" type="error" id="ae79a" to="xyz@kdetalk.net/Kopete" >
<query xmlns="jabber:iq:agents"/>
<error type="cancel" code="501" >
<feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
</error>
</iq>
Comment 6 S. Burmeister 2006-09-03 08:52:21 UTC
Could someone please re-open this bug, as it is not resolved for kopete 0.12.2.
Comment 7 Olivier Goffart 2006-09-03 22:46:47 UTC
This is not easy to solve since the server doesn't return an error.

The error you pasted is a perfectly normal error. Kopete is trying to guess the default conference server using the deprecated service protocol that ejabberd doesn't implement anymore.
Comment 8 Dominik Tritscher 2008-07-23 21:13:40 UTC
I can confirm that bug with kopete 0.50.80 from Kubuntu packages while trying to connect to the chat room mentioned in comment #5.
Using the "Browser" feature from the connection dialog display an empty list of chat rooms.
Other error messages like non existing servers or a ban from the chatroom where displayed correctly.
Comment 9 Justin Zobel 2021-03-09 22:40:54 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.