GNOME Bugzilla – Bug 596077
Too long message in a conference while it is not
Last modified: 2018-05-22 13:43:09 UTC
I upgraded to Empathy 2.28. on ubuntu karmic, and now I'm not able to send messages in a jabber conference. Everytime I join the conference and try to send a messages it says "- Error sending message 'ping': too long message" This is an output from the terminal just in case: $ LANG=C empathy (empathy:4318): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' (empathy:4318): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Intersesting. Could you please run empathy with EMPATHY_DEBUG=all and attach logs please?
Well, since it contains my private information I'm afraid it's not affordable to publish the whole log here for me. I can send you parts of it if you point me on them.
Created attachment 144573 [details] log with EMPATHY_DEBUG=all
It seems I managed to wipe out my personal information from the log, so it's now safe to publish it here I hope.
I don't see anything wrong in these logs. Are you sure that the messages you tried to send have not been properly sent? Furthemore the GLib-GObject-WARNING doesn't appear in the log.
Did you notice this lines: (empathy:10604): empathy-DEBUG: tp_chat_received_cb: Message received: (empathy:10604): empathy-DEBUG: tp_chat_received_cb: Empty message with NonTextContent, ignoring and acking. (empathy:10604): empathy-DEBUG: tp_chat_send_error_cb: Error sending 'ping' (4)? Concerning GLib warning that's because I didn't redirect stderr to the log.
After additional testing I found out that some messages are sent without any problem, while others are not. The same message can be declined for the first time, while it can be accepted for the second attempt. That's completely weird.
Created attachment 144583 [details] Inconsistent bug A screen can say better than thousand words what I mean by saying in the previous post.
Seems to be an error at the CM level. Could you attach Gabble logs when this bug occurs please?
*** Bug 598237 has been marked as a duplicate of this bug. ***
I found telepathy-gabble package but don't know how to get the logs from it, since it seems to be a part of a telepathy framework. Can you point me at how to get these logs?
Oh nevermind I found it.
Created attachment 145424 [details] Gabble log
Reporter: Please do NOT set the gnome target field yourself. Thanks.
Actually I was wondering wasn't it the compose notification that caused the server to reject my messages as flood mistakenly? Any ideas?
Just asked the server developers they say there is no need in composing message for groupchats. Should I file it as a bug?
From http://xmpp.org/extensions/xep-0085.html "The protocol can be used in the context of a one-to-one chat session or a multi-user chat room." So it's fine to use it for groupchats as well.
Reopening as the requested informatoin in comment #1 has been provided in comment #3.
any progress on this bug ??
I'm afraid no, since the bug seems to be fixed already in the latest empathy versions. I think you can close it.
Bug appeared again in 3.4.1 http://ompldr.org/vZTExMA/empathy.png What is wrong? It worked fine in 3.2
This bug has been around for 3 years. 99% of russian speaking users (and not only) can not normally use the IM client that is pre-installed on all distributions with GNOME. In the end, they all migrate to Pidgin (or other IM)
Empathy 3.4.2.3 has still this bug. Proof - http://ompldr.org/vZ2s3Zw
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/empathy/issues/117.