GNOME Bugzilla – Bug 474888
crash in Evolution: I clicked on a search fo...
Last modified: 2009-09-21 10:57:19 UTC
What were you doing when the application crashed? I clicked on a search folder. The content panes cleared, but the crash occurred before they populated with the contents of the new search folder. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 224972800 vsize: 0 resident: 224972800 share: 0 rss: 68448256 rss_rlim: 0 CPU usage: start_time: 1189000716 rtime: 0 utime: 37355 stime: 0 cutime:35151 cstime: 0 timeout: 2204 it_real_value: 0 frequency: 4 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 -1233320272 (LWP 6161)] [New Thread -1339941984 (LWP 13705)] [New Thread -1268364384 (LWP 6221)] [New Thread -1328551008 (LWP 6220)] [New Thread -1314673760 (LWP 6210)] [New Thread -1306281056 (LWP 6209)] [New Thread -1297888352 (LWP 6182)] [New Thread -1278219360 (LWP 6180)] [New Thread -1269826656 (LWP 6179)] [New Thread -1259091040 (LWP 6178)] [New Thread -1249657952 (LWP 6176)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 161360
Thread 1 (Thread -1233320272 (LWP 6161))
*** Bug 520216 has been marked as a duplicate of this bug. ***
Bug 520216
+ Trace 191520
hmm, it doesn't make much sense to me, if the strings are accessible, which seems they are, then that have no reason to crash in call to strstr...
This version is no longer maintained, which means that it will not receive any further security or bug fix updates. The current stable GNOME and Evolution version is 2.26. Can you please check again whether this issue still happens in Evolution 2.24 or 2.26 and update this report by adding a comment and changing the "Version" field? Thanks a lot. Again thank you for reporting this bug and we are sorry it could not be fixed for the version you originally used here.
Thanks for taking the time to report this bug; however, closing due to lack of response of the reporter, sorry. if you still see this issue with a current release of evolution (2.26.3 or later), please reopen. thanks in advance.