After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 127462 - Sending a message to an unknown JID is impossible.
Sending a message to an unknown JID is impossible.
Status: RESOLVED FIXED
Product: gossip
Classification: Deprecated
Component: General
0.8.0
Other All
: Normal major
: 0.8
Assigned To: Gossip Maintainers
Gossip Maintainers
Depends on: 157841
Blocks:
 
 
Reported: 2003-11-20 10:32 UTC by Ralph Meijer
Modified: 2005-01-19 22:59 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch to fix this bug (1.69 KB, patch)
2003-12-13 09:14 UTC, Martyn Russell 		none Details | Review

Description Ralph Meijer 2003-11-20 10:32:22 UTC 
When choosing Chat->Send Message, specifying a JID which is not on your
roster and choosing Chat, gives a dialog window with an empty (null) JID.

The possibility of sending messages should NOT depend on whether the other
party is on your roster or not.
Comment 1 Mikael Hallendal 2003-11-20 10:46:41 UTC 
Of course not, this is obviously a bug.
Comment 2 Martyn Russell 2003-12-13 09:14:29 UTC 
Created attachment 22400 [details] [review]
Patch to fix this bug
Comment 3 Mikael Hallendal 2003-12-13 13:46:49 UTC 
Thanks!! Commited.
Comment 4 Ralph Meijer 2004-09-09 11:02:43 UTC 
Sorry, but this bug is back again. I think from 0.7.6 onwards.
Comment 5 Ralph Meijer 2005-01-07 11:53:18 UTC 
I tried to trace the problem, and found that in app_complete_name_response_cb,
the entered jid (or nick) is being looked up in the roster. Since I want to chat
with someone *not* on my roster, this will fail and, after a few messages on
stdout about failed assertions, a chat window with an empty (null) JID will appear.
Comment 6 Mikael Hallendal 2005-01-19 22:59:22 UTC 
Been fixed in HEAD.