GNOME Bugzilla – Bug 256139
Crash: Segmentation fault during start
Last modified: 2004-03-30 00:31:25 UTC
Package: Evolution Priority: Normal Version: GNOME2.2.2 1.4.4 os_details: GNOME.Org Synopsis: Segmentation fault during start Bugzilla-Product: Evolution Bugzilla-Component: Shell BugBuddy-GnomeVersion: 2.0 (2.2.2) Description: Description of Problem: When I exit evolution with the calendar open and then try to restart it I get a segmentation fauls Steps to reproduce the problem: 1. Exit evolution while viewing the calendar 2. restart evolution 3. Actual Results: seg fault Expected Results: evolution should start How often does this happen? every time Additional Information: on suse linux 9.0 running kernel 2.4.21-192-smp4 on a single processor pentium 4 3.2Gz machine Debugging Information: Backtrace was generated from '/opt/gnome/bin/evolution' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 32134)] [New Thread 32769 (LWP 32137)] [New Thread 16386 (LWP 32138)] [New Thread 32771 (LWP 32139)] [New Thread 49156 (LWP 32140)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x4108bab6 in waitpid () from /lib/i686/libpthread.so.0
+ Trace 45472
Thread 4 (Thread 32771 (LWP 32139))
Unknown reporter: alexander.mitsos@gmx.net, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** This bug has been marked as a duplicate of 243160 ***