GNOME Bugzilla – Bug 448467
crash in Evolution: I just started evolution...
Last modified: 2008-05-06 08:49:44 UTC
Version: 2.12.x What were you doing when the application crashed? I just started evolution to view my emails and then it crashed. Distribution: Gentoo Base System release 1.12.10 Gnome Release: 2.19.3 2007-06-14 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.21-gentoo-r3 #1 SMP Thu Jun 14 19:54:26 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 416972800 vsize: 416972800 resident: 50077696 share: 32608256 rss: 50077696 rss_rlim: 18446744073709551615 CPU usage: start_time: 1182097176 rtime: 117 utime: 103 stime: 14 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47242201425264 (LWP 5252)] [New Thread 1140881728 (LWP 5288)] [New Thread 1132489024 (LWP 5287)] [New Thread 1124096320 (LWP 5268)] [New Thread 1115703616 (LWP 5266)] [New Thread 1107310912 (LWP 5264)] [New Thread 1098918208 (LWP 5263)] [New Thread 1090525504 (LWP 5261)] [New Thread 1082132800 (LWP 5260)] 0x00002af7695ec53e in __libc_waitpid (pid=5298, stat_loc=0x7fff43392dcc, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 141639
Thread 1 (Thread 47242201425264 (LWP 5252))
----------- .xsession-errors --------------------- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- 41 ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory. --------------------------------------------------
*** Bug 448288 has been marked as a duplicate of this bug. ***
bug #448876 could be a dupe..
Bumping version to a stable release.
Dup of bug #523463
*** This bug has been marked as a duplicate of 523463 ***