Version: 0.23.3

What were you doing when the application crashed?
Reproduction of bug 540688 just with Jabber (no IRC involved). Double clicked on the Jabber contact, no window has been opened, but backtrace.


Distribution: Fedora release 9 (Sulphur)
Gnome Release: 2.22.2 2008-05-28 (Red Hat, Inc)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.6-55.fc9.i686 #1 SMP Tue Jun 10 16:27:49 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10499902
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 52875264 vsize: 52875264 resident: 22110208 share: 13893632 rss: 22110208 rss_rlim: 4294967295
CPU usage: start_time: 1214807700 rtime: 156 utime: 138 stime: 18 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/empathy'

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0xb7f3c730 (LWP 1810)]
0x00110416 in __kernel_vsyscall ()

+ Trace 201723

----------- .xsession-errors (552 sec old) ---------------------
(evolution:32675): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
(evolution:32675): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
(evolution:32675): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
(evolution:32675): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
(evolution:32675): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
(evolution:32675): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
BBDB spinning up...
(evolution:32675): e-data-server-ui-WARNING **: Keyring key is unusable: no user or host name
--------------------------------------------------