GNOME Bugzilla – Bug 371586
crash in mail_config_get_account_by_source_url in mail-config.c
Last modified: 2010-12-20 17:44:48 UTC
What were you doing when the application crashed? After my first crash (about 5 minutes prior to this one), I killed all evo** processes running, and tried to restart evolution. Evolution locked up, and I was forced to 'kill -9' it. I then tried to open it again, and got this crash. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 123371520 vsize: 0 resident: 123371520 share: 0 rss: 24186880 rss_rlim: 0 CPU usage: start_time: 1162829687 rtime: 0 utime: 90 stime: 0 cutime:84 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1233107280 (LWP 27166)] [New Thread -1317860448 (LWP 27195)] [New Thread -1309467744 (LWP 27194)] [New Thread -1300681824 (LWP 27191)] [New Thread -1275077728 (LWP 27190)] [New Thread -1283470432 (LWP 27186)] [New Thread -1266685024 (LWP 27184)] [New Thread -1258292320 (LWP 27176)] [New Thread -1247143008 (LWP 27175)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 83647
Thread 1 (Thread -1233107280 (LWP 27166))
Can you still reproduce this problem or has it been fixed since?
many dups.
https://launchpad.net/ubuntu/+source/evolution/+bug/97543 :
+ Trace 156160
*** Bug 450837 has been marked as a duplicate of this bug. ***
*** Bug 374646 has been marked as a duplicate of this bug. ***
*** Bug 386389 has been marked as a duplicate of this bug. ***
*** Bug 464657 has been marked as a duplicate of this bug. ***
*** Bug 421006 has been marked as a duplicate of this bug. ***
*** Bug 426270 has been marked as a duplicate of this bug. ***
*** Bug 453672 has been marked as a duplicate of this bug. ***
bug 453672 is from evo 2.10.
*** Bug 472405 has been marked as a duplicate of this bug. ***
*** Bug 493543 has been marked as a duplicate of this bug. ***
*** Bug 533374 has been marked as a duplicate of this bug. ***
bug 576383 , bug 576798 could be related
can we now assume this bug is automagically fixed? since there has been no duplicate in 2 years.
Have not seen any duplicates or similar traces for the recent stable releases. Closing as OBSOLETE.