GNOME Bugzilla – Bug 467354
crash in Evolution: New email and searching ...
Last modified: 2007-08-18 15:32:17 UTC
What were you doing when the application crashed? New email and searching global address book from MS Exchange server Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 105603072 vsize: 105603072 resident: 38084608 share: 9121792 rss: 38084608 rss_rlim: 4294967295 CPU usage: start_time: 1187272866 rtime: 2227 utime: 1890 stime: 337 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1233704768 (LWP 4017)] [New Thread -1269441648 (LWP 4442)] [New Thread -1244263536 (LWP 4441)] [New Thread -1235600496 (LWP 4018)] (no debugging symbols found) 0xb7fc37f2 in ?? () from /lib/ld-linux.so.2
+ Trace 155697
Thread 3 (Thread -1244263536 (LWP 4441))
----------- .xsession-errors (25 sec old) --------------------- CLIENT: Task: Task::done() CLIENT: Task: emitting finished Very strange! got a DCOPReply opcode, but we were not waiting for a reply! CLIENT: Task: Task::done() CLIENT: Task: emitting finished CLIENT: Task: Task::done() CLIENT: Task: emitting finished CLIENT: Task: Task::done() CLIENT: Task: emitting finished CLIENT: Task: Task::done() CLIENT: Task: emitting finished CLIENT: Task: Task::done() CLIENT: Task: emitting finished CLIENT: Task: Task::done() CLIENT: Task: emitting finished --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 348258 ***