GNOME Bugzilla – Bug 474489
crash in Evolution: I was typing in an e-mai...
Last modified: 2007-09-20 20:07:09 UTC
What were you doing when the application crashed? I was typing in an e-mail address from an exchange backend. The address was m.fra... and then: Boom! Happy debugging, folks. I really like evolution, and I've been using it since the pre-1.0 days. But is keeps crashing on me. Here, on my work it crashes often when I access the exchange backend to lookup email addresses, at home it always freezes after I click the 'close' button of metacity. But hey, it's free en most often works like a charm. Free beer and apple pie for the developers, you deserve it. 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: 73388032 vsize: 73388032 resident: 13156352 share: 9048064 rss: 13156352 rss_rlim: 4294967295 CPU usage: start_time: 1189148183 rtime: 79 utime: 70 stime: 9 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 -1233615184 (LWP 9059)] [New Thread -1262498928 (LWP 9272)] [New Thread -1254106224 (LWP 9271)] [New Thread -1237320816 (LWP 9267)] [New Thread -1245713520 (LWP 9265)] [New Thread -1235047536 (LWP 9060)] (no debugging symbols found) 0xb7fd07f2 in ?? () from /lib/ld-linux.so.2
+ Trace 161078
Thread 4 (Thread -1237320816 (LWP 9267))
----------- .xsession-errors (77405 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 332979 ***