GNOME Bugzilla – Bug 262693
Crash when checking email
Last modified: 2004-08-09 20:14:33 UTC
Distribution: Fedora Core release Rawhide (Rawhide) Package: Evolution Priority: Normal Version: GNOME2.7.90 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Crash when checking email Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.7.2) Description: Description of the crash: Periodic crash when checking email. I've had this since I started running FC3T1 and evolution >=1.5.9 Steps to reproduce the crash: 1. Check email 2. 3. Expected Results: no crash How often does this happen? about 33% of the time. Additional Information: I've got three accounts, two pop and one imap. I pop to localhost and to comast and imap to my work address. Seems to always be when checking the comcast address. Debugging Information: Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -151145376 (LWP 21685)] [New Thread -242644048 (LWP 28994)] [Thread debugging using libthread_db enabled] [New Thread -151145376 (LWP 21685)] [New Thread -242644048 (LWP 28994)] [Thread debugging using libthread_db enabled] [New Thread -151145376 (LWP 21685)] [New Thread -242644048 (LWP 28994)] [New Thread -232154192 (LWP 21787)] [New Thread -221664336 (LWP 21774)] [New Thread -211174480 (LWP 21771)] [New Thread -200287312 (LWP 21765)] [New Thread -179020880 (LWP 21764)] [New Thread -189633616 (LWP 21748)] [New Thread -168526928 (LWP 21746)] [New Thread -158037072 (LWP 21745)] 0x005be782 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 49195
Thread 10 (Thread -158037072 (LWP 21745))
Thread 9 (Thread -168526928 (LWP 21746))
Thread 8 (Thread -189633616 (LWP 21748))
Thread 7 (Thread -179020880 (LWP 21764))
Thread 6 (Thread -200287312 (LWP 21765))
Thread 5 (Thread -211174480 (LWP 21771))
Thread 4 (Thread -221664336 (LWP 21774))
Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** This bug has been marked as a duplicate of 243160 ***