GNOME Bugzilla – Bug 460508
crash in Evolution: Evolution running, lost ...
Last modified: 2008-01-31 22:45:38 UTC
What were you doing when the application crashed? Evolution running, lost and regained network connection in NetworkManager. This crash has occurred before, although doesn't seem to be everytime - perhaps depends on Evolution doing something in the background when connection is lost? Distribution: Unknown Gnome Release: 2.18.3 2007-07-06 (GNOME.Org) BugBuddy Version: 2.18.1 System: Linux 2.6.21.5 #3 PREEMPT Wed Jun 13 19:49:00 NZST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 80617472 vsize: 80617472 resident: 9162752 share: 5521408 rss: 9162752 rss_rlim: 4294967295 CPU usage: start_time: 1185440575 rtime: 28 utime: 24 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-data-server-1.10' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1220819264 (LWP 1525)] [New Thread -1240822896 (LWP 1547)] [Thread debugging using libthread_db enabled] [New Thread -1220819264 (LWP 1525)] [New Thread -1240822896 (LWP 1547)] [Thread debugging using libthread_db enabled] [New Thread -1220819264 (LWP 1525)] [New Thread -1240822896 (LWP 1547)] [New Thread -1223730288 (LWP 1526)] 0xffffe410 in ?? ()
+ Trace 150640
Thread 3 (Thread -1223730288 (LWP 1526)): #-1 0xffffe410 in ?? () No symbol table info available. #-1 0xffffe410 in ?? () ----------- .xsession-errors (6 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 ** Message: <info> You are now connected to the wireless network 'XYZZY'. --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 437835 ***