GNOME Bugzilla – Bug 510557
crash in Evolution Mail and Calendar: starting evolution for t...
Last modified: 2008-09-15 09:45:26 UTC
Version: 2.22.x What were you doing when the application crashed? starting evolution for the first time Distribution: Debian lenny/sid Gnome Release: 2.21.5 2008-01-17 (GARNOME) BugBuddy Version: 2.20.1 System: Linux 2.6.23.14 #1 SMP PREEMPT Mon Jan 14 19:40:50 MST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 566153216 vsize: 566153216 resident: 28557312 share: 20164608 rss: 28557312 rss_rlim: 18446744073709551615 CPU usage: start_time: 1200725420 rtime: 90 utime: 77 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/home/boat/garnome/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x2b8fe1e07d30 (LWP 29823)] 0x00002b8fdc57d34f in waitpid () from /lib/libpthread.so.0
+ Trace 185924
Thread 1 (Thread 0x2b8fe1e07d30 (LWP 29823))
----------- .xsession-errors (54 sec old) --------------------- [multi-operation 0x00874D40] complete [multi-operation 0x00B09E80] start [multi-operation 0x00B09E80] adding part: 0x00B51960 [multi-operation 0x00B09E80] single progress: Listing passwords -1.000000 [multi-operation 0x00874D40] start [multi-operation 0x00874D40] adding part: 0x00B51960 [multi-operation 0x00874D40] single progress: Listing passwords -1.000000 [multi-operation 0x00B09E80] single progress: (null) 1.000000 [multi-operation 0x00874D40] single progress: (null) 1.000000 [multi-operation 0x00B09E80] part complete (1): 0x00B51960/(null) [multi-operation 0x00B09E80] complete [multi-operation 0x00874D40] part complete (1): 0x00B51960/(null) [multi-operation 0x00874D40] complete ** (seahorse:29793): WARNING **: FIXME: Need to shutdown linc connections ... --------------------------------------------------
Bumping version to a stable release.
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 513395 ***