GNOME Bugzilla – Bug 164592
App crash on jabber server-side disconnect in SSL mode
Last modified: 2005-05-03 15:10:34 UTC
Distribution: Debian 3.1 Package: gossip Severity: normal Version: GNOME2.8.1 0.8 Gnome-Distributor: Debian Synopsis: App crash on jabber server-side disconnect in SSL mode Bugzilla-Product: gossip Bugzilla-Component: General Bugzilla-Version: 0.8 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Gossip crashes when started in SSL mode and a server 'bounce' occurs. A group chat window is open - may have an effect. Steps to reproduce the crash: 1. Run Gossip with connection to Jabber server in SSL mode 2. Wait for server to bounce 3. Crash! Expected Results: No crash. How often does this happen? Daily 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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 -1223461856 (LWP 32548)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 54685
Thread 1 (Thread -1223461856 (LWP 32548))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-19 09:39 ------- Unknown version 0.8 in product gossip. Setting version to "unspecified". 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 jgwinnup@mbvlab.wpafb.af.mil. 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.
This is actually a bug in Loudmouth/GnuTLS, worked around it in CVS.
*** Bug 166023 has been marked as a duplicate of this bug. ***
*** Bug 171861 has been marked as a duplicate of this bug. ***
*** Bug 302715 has been marked as a duplicate of this bug. ***