GNOME Bugzilla – Bug 155250
gossip crashes on echo message
Last modified: 2005-06-05 10:22:48 UTC
Distribution: Debian testing/unstable Package: gossip Severity: normal Version: GNOME2.8.1 0.7.8 Gnome-Distributor: Ubuntu Synopsis: gossip crashes on echo message Bugzilla-Product: gossip Bugzilla-Component: General Bugzilla-Version: 0.7.8 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: gossip crashes unexpectedly when trying to test echo functionality Steps to reproduce the crash: 1. connect to an ssl server other than jabber.org 2. send a message to jabber.org/echo 3. watch the app crash Expected Results: echo to repeat the message back to you How often does this happen? everytime Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gossip' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1087596832 (LWP 10569)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in __kernel_vsyscall ()
+ Trace 50995
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-12 21:01 ------- Unknown version 0.7.8 in product gossip. Setting version to "0.7.X". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gossip". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was matt@mqatrombone.net. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
My guess is that this is a problem with the old contact list and when a JID isn't in the contact list. I'm in the middle of rewriting this code and this should likely be fixed after that. Keeping it open so that I remember to confirm this when I'm done with the rewrite.
*** Bug 151195 has been marked as a duplicate of this bug. ***
*** Bug 160382 has been marked as a duplicate of this bug. ***
Fixed. I used an account at jabber.org.uk with SSL and NO roster. Connected, send the message as stated to jabber.org/echo and I get a message back (exactly what I sent).